The main improvements in this release are the following:
- Added Deployments Table to AgileXRM App’s Administration area
- Auto-generate Model Permission Solution
- Added Cancel verb to PowerShell Module
- New FluentUI Theme
New Enhancements & Fixes
Dataverse/D365 Integration
Enhancements
- New FluentUI Theme
The new Theme called theme.fui is in line with Model-driven App design.
Simply change the entry in AgileXRM Configuration:

- Added Deployments Table to AgileXRM App’s Administration area
With support of Deployment of Models via Solutions, to improve visibility of what has been deployed and what has not in the environment, there is a new Table. If a Model throws an Error when being deployed, the error reason can be seen inside the record. Changing the Status Reason to Deploying, retries the deployment - Auto-generate Model Permission Solution
By checking the Create Model Permissions checkbox in the Model record, an Unmanaged solution is created with all the current Permissions defined for this Model. If Permissions are changed later, by changing this checkbox the Model Permissions Solution is updated automatically - Support Model Names in CRM Workflow Custom Action
Previously, the GUID of the selected Model was stored in the CRM Workflow’s custom Action. When such a Workflow was imported downstream, it was Deactivated since the GUIDs of Models are different in each environment. Now, the name of the Model can be used instead, which does not Deactivate the WF and does not force reconfiguring it downstream - Control visibility of the Start AgileDialogs and Run Process CommandBar buttons
These buttons were removed in the previous Release to reduce friction. But they are very useful in DEV environments. Now, the buttons are always added hidden to Enabled Tables’ Forms/Views but they can be shown by a new entry in Configuration table, namely ShowStartRunButton = true (if the entry does not exist or has a false value, the buttons are not shown) - IMPORTANT: After importing the latest AgileXRM Solution, use the Update Enabled Entities button in AgileXRM Administration for both Tables and Activities, so that they are updated with the latest AgileXRM components
Fixes
- The WaitForUpdate shape was occasionally throwing an “Invalid XML” error (HotFix 1)
- In Dialog Tasks, the Assign To Me button was showing even if user did not have Reassign Permission
- The Full+Modeler License was not allowing user to see Process Manager
- Benign errors were being registered in System Jobs against the System Task table like “Record cannot be deleted as it does not exist” or “More than one concurrent Delete requests detected for an Entity”
AgileDialogs
Enhancements
- Support filenames with longer names in File Upload Control
The maximum filename allowed now is 200 characters. For this to work, create a system environment variable called AgileXRM_Temp to point to a directory with 12 characters or less (e.g. c:\tmp) - Timestamp removed from Message window
The timestamp was showing UTC time and that was confusing the users. - CHANGE OF BEHAVIOR: No Rollback Permission needed to go backwards in a Dialog
Previously, apart from Initiate Process permission, a user also needed Rollback permission to be able to click the Back button inside the Dialog. Now Rollback permission is not needed.
Fixes
- LCID was not being respected in Public Sites
- RedirectToTask.aspx page was not passing LCID correctly
- Dialog Snapshot (Point-In-Time) was not honoring “Last Session Data Only” setting
- YesNo Control was not being rendered correctly in History view
- Controls set via Default Value were not populating Output Variables correctly
- Rules Editor dropdowns were not listing Display Variables nor Output Variables from the same Page
- “Culture is not supported” error was showing when looping back to a Page with a Grid in External Dialog Tasks
- In History View, large text was being truncated instead of being wrapped
Process Manager
Fixes
- SubProcess shapes were ignoring the fact that the SubProcess called had different Related Entities for the Main Entity and this was causing unexpected sideeffects. Now, they throw an exception.
- IMPORTANT: The Process Engine DB has to have a Maintenance Plan in place. Specifically, Rebuild Indexes and Update Statistics are a prerequisite for Process Manager to show process status correctly.
Process Modeler
Fixes
- Copy/Pasting multiple Single Condition shapes were occasionally creating corrupted copies
- AgileXRM Email Templates viewing was throwing an excepetion
- Global Variables were wrongly allowed to be Input Variables
- Multi-shapes were allowing configurations without any Columns
- Occasionally “Element is already checked-in” error was being thrown when checking-in Models
Miscellaneous
- ENHANCEMENT: Added Cancel verb to PowerShell Module
It is now possible to Cancel process instances via the PowerShell Module - ENHANCEMENT: Support for Azure Entra External ID
Azure B2C is being deprecated and being replaced with Azure Entra External ID, which is now supported. - FIX: PowerShell Module was throwing an exception when calling Bulk Migrate
- FIX: XSLT Support is being removed by major browsers. AgileXRM does not depend on XSLT anymore.
You must be logged in to post a comment.