Road Map

Application Auditing
	Many times, developers need to better track when the last time an app was run, edited, painted, or compiled. They also want to know who performed such an action. Starting with the next update, developers can begin tracking this information directly within the m-Power platform.

Application Relationship Diagram
	Our team is putting the finishing touches on creating a feature that will allow developers to visually see the relationships between applications within a Data Dictionary. This will be very useful for team members who want to better understand how applications are connected with each other, especially from a presentation layer perspective.

BLOB support
	Our team is working on adding BLOB field support to m-Power. The advantage of BLOB support is that these binary fields can hold anything (including PDFs, images, etc...) directly in the database. With this feature you will be able to download this data to the correct file via m-Power.

Workflow Designer
	Slated for 2019 Q1, this feature will allow developers to, graphically, link conditional logic to actions of their maintenance apps to help with common needs. For instance, developers can take advantage of this feature if they want to conditionally call a Task group when a maintainer is executed, but only if certain conditions are met. This feature is intended to replace the Business Rules Designer.

Improved Graphing Wizard
	Our development group is planning an overhaul for the graphing wizard within m-Power. Notable improvements include allowing easier and more robust customization of various graphing options. In addition, a previewing panel will be available to see how graph customizations will appear directly within the m-Painter editor.

Promote to Production
	First released several years ago, the Promote to Production utility is a workhorse of the m-Power platform. However, overtime, developers have been leaving their feedback on ways to improve the process. Expected out in 2018, the enhanced Promote to Production process will allow developers easier ability to add apps to their projects as they go. Additionally, when the time comes to promote, m-Power will have added logic to better understand which dependent files need to be packaged. Finally, the UI will be improved and streamlined to better fit into the overall m-Power platform footprint.

Signature Capture
	This future m-Power project would allow for users to sign a screen on a mobile device that m-Power would electronically save. This saved signature could then later be rendered.

Single Sign on via SAML
	Single Sign-On (SSO) is a commonly requested feature. Customers often want to integrate m- power with other systems. Without a single sign on mechanism, users are required to sign in to each system separately. This is often undesirable. There are many ways to implement SSO. However, SAML (Secure Authentication Markup Language) is a standard used in many industries for secure and trusted authentication between systems. Recently we have found that some customers require this standard be followed in order to be compliant with internal security policies. This project aims to provide a configurable interface so that m-Power can share SSO authentication with any other system available via SAML. With a SAML capability, m-Power developers can setup their m-power systems to validate against any other SAML enabled system. With SAML, developers can also enable their other systems to validate against m-power tables and security features.