Solving the Challenges of Power Platform® and Dynamics 365® projects with AgileXRM

Example: AgileXRM is a flexible solution for automating credit card fraud claims. The bank was able to run an initial version of the process in days and improve it with user feedback. In just four weeks, they had a version matched the desired business process and many of the requirements were not in the original specs. Version changes are fully auditable and traceable.

Power Automate has limitations on modifying settings after they've been made, Power Apps can disrupt forms and connected data/apps, and potentially lead to errors. The ability to modify applications while in use, becomes increasingly critical to keep pace in a highly competitive environment. Example: Headquarters’ board has indicated that the approval of investment projects greater than 1 million USD in new affiliates in LATAM require the approval of 2 local Directors followed by the positive review by the Regional Director. Previously, the local Financial Dir approved locally and communicated to the Regional office. Also, all investment requests in-flight must follow the new process. While this simple business change is a challenge for a Model driven App, with AgileXRM, a new version of the investment requests process will include the new approval requirement and then migrate all running instances of the previous version to the new one. Fast, easy and in Compliance.

Flexibility is a critical characteristic of Enterprise process apps as it allows organizations to quickly adapt to changes in business requirements and processes. By having a flexible enterprise process application, organizations can respond quickly to new requirements, reducing the time and effort required to incorporate changes and minimizing the impact on business operations.

Configuration-based development, Modular design, Configurability and Collaboration features are well served in Power Apps BUT it falls short on managing new requirements or changes without risking the deployment.

​

Example: A retail bank launched a students’ loan campaign. 2 weeks after, a new regulation sets the maximum interest applicable to this product and it’s lower that the one offered by the bank. Thousands of requests were already initiated thru the bank’s website. The process is managed by AgileXRM so a new version is set to apply the regulation and the existing requests are easily re-evaluated to apply the new applicable conditions migrating them to the new process version.

What could have be done with only Power Apps and how long would it have taken?

What if there is a blackout or an internet outage after you had completed step 39 of your city council building permit application?

AgileXRM is session-less and persistent. If the connection is lost while a process is running, after reconnecting, the browser will resume in the same point where it was left off and maintains the progress.

How do you ensure that data management is correctly done in your business?

Do you track that the change has been effective? … and what is the impact on ongoing processes that were using the previous data value? Is the data change applicable immediately or does it depend on certain rules or events -i.e. next Monday, when the signed agreement is received or when the previous batch expires, etc.

" In AgileXRM: any data change is managed by a process that validates If, When and How that data can be modified "

That’s one of the many uses of AgileDialogs in AgileXRM: any data change is managed by a process that validates If, When and How that data can be modified by checking what impact it may have on other running or planned processes. In addition, it also tracks who changes what, when and how, and very importantly, ensures that the rules to apply the change are followed as defined by the business.

AgileDialogs, a synchronous engine for Inbound and Outbound Scripts for Contact Centers or Help-Desks, B2C Self-service processes, Troubleshooting wizards, How-To Guides and the like.

Example: An online process to buy your theatre tickets may last a minute. Building an airplane is far more complex and may take a couple of years to complete. Can your platform cope with both, short and long term processes?

In a Court of Appeals, there are processes that may last more than a year. Meanwhile there are laws that may change but are not applied retroactively while others may apply to existing cases. Can your platform cope with both scenarios?

AgileXRM handles all process durations and scenarios.

AgileXRM can run different versions of the same process allowing to choose whether new versions should apply to existing running processes, or not.

Example: A service claim process gets stuck because the claimant is no longer a customer, and that was not an event defined in the initial running process. In AgileXRM when an unexpected event affects the execution of a process, an alternative route is set: Role based permissions allow the user to define a subprocess to handle the new event and to complete all needed activities. The subprocess is then connected to the main process and the instance is resumed to execute the new subprocess.