This is the last version of V8. The next release will be a major version V9.
The main improvements in this release are the following:

• Support deployment of Models via Solutions
• Support deployment of Model Permissions via Solutions
• Support Context Isolation in SubDialogs
• Support auto-generating Controls from Dataverse/D365 Table Columns
• Support Input and Output Parameters at Model-level
• Support Invited Guest Users in Envision
• Improved UX and stability at Model Design-time

New Enhancements & Fixes

Dataverse/D365 Integration

Enhancements

• Support deployment of Models via Solutions
  When a Model is Published to a Dataverse environment, a new Unmanaged Solution will be generated that contains the Model definition, with name of the Solution having this format:
  AgileXRM Model – [Model Name]
  Inside this Solution there will be a single item that contains the Model definition.It will containg the latest version of the Published Model
  These Model Solutions can be exported as Managed Solutions (individually or grouped together and included in your custom Unmanaged Solution) and deployed downstream just like any other Dataverse Solution
  NOTE: Deleting a Managed Model Solution does not remove the Model from AgileXRM
  
  
• Support deployment of Model Permissions via Solutions
  Model Permissions can also be saved in an Unmanaged solution and exported as Managed and deployed downstream. Please contact us for further details
  NOTE: Deleting a Managed Model Permission Solution does not remove the Model Permissions from AgileXRM
  
  
• CHANGE OF BEHAVIOR: Do not allow deleting Dataverse/D365 Activities that belong to a live process
  Previously this was allowed, but caused desynchronization issues
  
  
• IMPORTANT: After importing the latest AgileXRM Solution, use the Update Enabled Entities button in AgileXRM Administration for both Entities and Activities, so that they are updated with the latest AgileXRM components
  

Fixes

• Publishing an existing Model was overwriting the Runtime Security Context
• Under certain edge circumstances, the Process Instance record was not being associated to the business record

AgileDialogs

Enhancements

• Support Context Isolation in SubDialogs
  There is a new property in the SubDialog shape, called ShareAttributes that is set to True by default. This mimics the old behavior.
  But if it is set to False, it allows isolating sub dialogs and using Input/Output parameters, create independent modular dialogs
  
  
• Allow auto-generating Controls from Table Columns
  Now it is possible to connect to the Dataverse metadata and select the Table Columns and automatically generate the corresponding Controls. The Control is set with the properties of the selected Column (for instance, if a Text Column is selected, the Text Control generated is set with the same Max Length as the Column)
  
  
• Allow hiding History button
  Previously, it was shown but disabled. Now it is not rendered at all
  
  
• Non-PRO functionalities like Feedback and Process Viewer are hidden in PRO
  Each environment has a new IsPRO flag. If set to True, Feedback and Process Viewer buttons are hidden. These functionalities are useful when developing the Dialogs, but have no use in Production
  
  
• If Date Only property is set in a Date Control, the Timezone Independent property is also set to True automatically
  

Fixes

• Global Variables were not useable in the Start Page
• Currency Control inside a Group container was not respecting Control Width settings
• Dialog Task was not working when the Dialog Model name had certain special characters
• DialogsEngine.clearValue() API was not clearing output variables in Lookup Control
• If a Dialog had an error before the first Page, the error message was too small to be readable
• Under certain screen resolutions in combination with certain Height and Width settings, the Dialog buttons at the bottom were not acessible
• File Control was not correctly uploading large files when user was clicking Next button or typing Page Down key quickly
• An unfinished Dialog from a Dialog Activity that was reassigned to another user, was not saving the full Snapshot of the Dialog
• File Control was permitting to upload empty files causing issues downstream. Also implemented improved handling of failed uploads
• Grid Control configured to return additional Columns was returning Internal Value for Date Columns instead of Display Value

Process Manager

ENHANCEMENTS

• 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.

Fixes

• Certain shapes were not displaying the Alert icon when they were causing exceptions
• In the Migrate Model window, the target Model on the right pane was not being positioned correctly
• When an Activity was assigned to a Dataverse/D365 Team via a variable, the Team name was no showing, rather the variable name was showing
• Sometime, false positives of Alerts were showing in SubModel shapes

Process Modeler

Enhancements

• Support Input and Output Parameters at Model-level
  These is a new Ribbon button to open this window. Logic Inspector can also be used to set them.
  This allows setting which variables are used as Input, Output or Input-Output (both) in the Model.
  Input and Input-Output parameters can be set as Required (otherwise they are optional).
  These shapes take this new functionality into account, allowing to set Input and Output parameters:
  • Dialog Activity
  • External Dialog Activity
  • XRM SubProcess
  • Multi SubProcess
  • SubDialog
    
    CHANGE OF BEHAVIOR: The Valid and Required columns have been removed from Logic Inspector. When opening previous Models, Logic Inspector will again flag all variables that are not defined within the Model. Use the right mouse-button to add each one to the Model Variables
    
• Support Invited Guest Users as Modelers
  Invited Users were already supported in the rest of the product, now they can also be Modelers
  
  
• DEPRECATED: Remove Release Options when Publishing
  The section in the Publish window with Release It Later, Release Now and Release On has been removed

Fixes

• Occasionally, when Publishing a Model, an error saying “Template with ID XXXX is already Released” was wrongly showing
• Certain shapes were not being selected automatically upon failing Validation
  Now any shape that fails validation, is automatically selected to let the modeler know which was it
• Display Value of Created On columns returned in Search shape, was returning internal value
• Two-Option type columns in Columns Specification window were only showing True or False rather than their display values
• If a value was retrieved from a Dataverse Column in a Search shape, and it was NULL (DBNull), it was being saved as Empty String in the Variable, rather than null. This was breaking expressions like Convert.ToDatetime(${myVar})
• QueryExpression Editor was not correctly rebuilding certain complex nested Related Entity queries when editing
• Some shape variables were not recognized as valid causing false positives in Logic Inspector
• The Search shape was returning the Internal Value rather than the Display Value (Timezone and Format adjusted) for Date columns
• Importing an XPDL was ocassionally importing the configuration of Multi-Condition shapes wrongly
• Setting Scheduled Start Date to empty in Activities Properties of any Manual Activity was causing an exception
• Sometimes trying to edit the HTML source of an AgileXRM Email Template was casuing an exception

Miscellaneous

• FIX: POSSIBLE BREAKING CHANGE: Ignore Duplicate IDs in Multi Shapes
  Before this, whatever the Multi shape did, it treated each ID it received individually. If an ID was repeated, it also took action on it, Now, it ignores duplicates
• FIX: Processes with a Set Custom Attributes shape configured with ExpectionHandler=Local and OnException=Suspend that threw and exception, were not being suspended
• FIX: CHANGE OF BEHAVIOR: Close Pending Tasks set to True in Set Status shapes, was also closing AgileXRM-managed Activities, and this was causing unexpected consequences