The normal release cycle is usually every Spring, but this is the latest version for AgileXRM V8.

The main improvements in this release are the following:

• Ability to control navigation after Dialog ends
• Support complex conditions in the Single-Condition shape
• Allow running a Dialog against multiple selected records in a View, to do bulk actions
• Support users invited from other Entra IDs
• New Open (record) button in automatic shapes in Process Manager
• Revamp Datetime handling to support all Timezones and all Datatime-type columns behaviors

New Enhancements & Fixes

Dataverse/D365 Integration

Enhancements

• Allow running a Dialog against multiple selected records in a View
  The IDs for the selected records (max 300) in a semicolon-seperated list, will be passed to the Dialog via a variable with this naming convention:

           "guids_" + schemaname + "Selection"

  (e.g. guids_contactSelection or guids_accountSelection)

The schemaname for the Table/Entity is passed in the variable called CrmBeType.
Use a Command Bar button for the View/List to launch it, configured to call the function startDialogByTemplateNameForSelectedIDs like this:

• New AgileXRM Card Form added to Task and Process Task activities
  These Cards are much better suited to display the items in the Timeline.
  In the Timeline configuration, under Activities, make sure Task and Process Task are selected. Then configure each to use the new Card as such:
  
• Support Users invited from other Entra ID tenants to Dataverse
  Dataverse allows and supports adding users from an external Entra ID.
  AgileXRM now also supports this type of users
• Set any Lookups in downstream environments to search by ID first and then by Name
  This is very useful when records are created that have Lookups to master data and that these might have different IDs in different environments
• Support handlebars like {{VARIABLE}} in Dataverse Email Templates as placeholders to map to, from the Send Email shape
• Update Dynamics 365 SDK to 9.0.2.56

Fixes

• Under certain edge circumstances, a Task in Dataverse/D365 was not automatically set to Completed when its associated Dialog became Completed
• Max permitted solution name issue was occurring for very long table names. Generated Unmanaged Solution name prefix for Enabled Entities and Activities are changed from AgileXRMEnabled_ to XRM_ 

AgileDialogs

Enhancements

• Configurable Navigation of user to anywhere in Dataverse after finishing a Dialog
  For example, navigate user to the record that was just created by the Dialog.
  Also supports navigate to a View, a Dashboard or a Web Resource.
  Details are in the documentation here.
• POSSIBLE BREAKING CHANGE: Revamped the handling of Date/Datetime, especially with regards to Timezones
  For internal Dataverse users, the Timezone set in Dataverse Personalization Settings is used. For External or Public/Anon Users, the browser’s Timezone is used.
  The handling of datetime has been redesigned and corrected, hence existing dialogs that were configured to work around previous odd behaviors, would need to be retested, and if needed, reconfigured
• Support Sign-Out Page for invoking from External Portal Site
  This invalidates the SSO token

  <AGILEDIALOGS_SERVER_URL>/Logout.aspx[?post_logout_redirect_uri=<REDIRECT_URL>]

• Allow choosing if a Control takes focus upon load
  
  By default, AgileDialogs focuses the first editable control on the page. This behavior is useful for most cases, but sometimes it is intrusive. It can now be controlled using the new autofocus parameter in the URL querystring:
    autofocus=0   (disables autofocus behavior)
    autofocus=1   (default behavior)
• Add granular control on how Pages are stored in Dialog History (Point-in-Time)
  Adds a HistoryBehavior property to Page Settings tab under Form Options with these values:
  • Default
  • Hide this Page keeping placeholder
    Shows a text like instead of the Page Title: This page was not stored intentionally
    No controls/data is shown
  • Hide this Page completely
    Stores nothing for this page not even a placeholder.
  • Hide Page Data
    Shows controls but without any data. NOTE: Info control is not affected by this setting
    Adds the following suffix to the Page Title: (Data hidden intentionally)
  • Save last Session Data only
    Last Session data overwrites previous sessions’ data
    Adds to the Page Title of previous sessions: (Data hidden intentionally. Only data for last session is kept)
• Indicate which button was clicked in History (Point-in-Time)
• Restrict Control names to valid chars only
• Simplify Calendar Control’s Min and Max setting window

Fixes

• File Control’s Required flag validation was throwing error after the file was replaced
• Start Page was showing Back and History buttons
• Pop-Up pages were too narrow when browser width was low
• DialogsEngine.clearValue method was not triggering the Change event
• Radio controls configured as Button Set were not being saved correctly in History (Point-in-Time)
• Calendar Control was not taking into account the First Day of Week setting in System Settings
• Info control was not respecting Column Span when inside a Group control
• Group control was wrapping long labels erroneously
• Resume button was being shown when a dialog entered a Faulting state
• Built-in variables were not working in Start Page controls based on a query

Process Manager

Enhancements

• Show the Open Task button when user is not an admin, but belongs to the Team the Task is assigned to
• Add corresponding Open button to these automatic shapes:
  • Create Entity, Update Entity, Upsert Entity and Create Note
    For these shapes, the button opens the corresponding record
  • Trigger Power Automate Flow
    The button opens the specific Flow Run
• Show the Team’s name when an activity is assigned to a Team
  Previously, it would only show this generic label “Dynamics CRM Team”

Fixes

• Reassign pop-up window was showing incorrect users for Manual Tasks
• Open Task button was always opening the record for the last session in multi-session scenarios
• Changing the Due Date for a Wait For Update shapes was throwing an error
• Some buttons that did not apply, were being shown for Completed activities

Process Modeler

Enhancements

• Unify Single-Condition and Multi-Condition shapes’ config windows to support complex conditions in the Single-Condition shape
  Previously, only a boolean variable could be used in a Single-Condition shape. Now, complex conditions can be configured using the same familiar condition-editor of Multi-Condition shape.
  RECOMMENDATION: Any Multi-Condition shapes that have only one Rule in them, should be replaced with a Single-condition shape using the same Rule and this way, improve the readability of the models
• Added Save and Save & Close buttons to Page Editor
  This helps the modeler to occasionally save the Page without having to close and reopen it
• Allow Filtering in Environment Explorer to quickly find process models
  Like Checked-out by me, Checked-in last x Days etc.
• Clearly show if Search shape/control is returning First Record Only or All Records
  This was already visible in the property grid but not directly in the config window
• Support text sort in repeating tables in Word shape
• Add field-type icons to wherever fields are shown
• Add the Text-Block icon to the Visio Ribbon
  This Visio tool allows moving the text of a shape, specially useful for shapes that have their labels outside the shape itself like Wait For Update or Delay shapes
• Allow custom Accept header in REST shape and REST-based controls
• Restrict Model names to a valid set of chars
• DEPRECATION: These shapes have been deprecated and may be removed in a future Release. If they are being used in existing models, they will continue to work, but should not be added to any new models:
  • Milestone and Wait for Milestone
  • Intranet User Task
  • Intranet Dialog Activity
  • Web Service (WS)
  • Web Service Extended (WSE)

Fixes

• Search shape was not generating the correct Output Variables after a Column was removed
• The Equals (Ignore Case) label in the Condition shapes’ operator drop-down was not showing correctly
• REST shape was allowing to set the Request Body when the verb was PATCH
• REST shape was throwing an exception when Request Body was empty
• Detach shape (to SharePoint) was throwing an exception with a certain Access Token configuration
• Copy-Paste was not copying over associated Email Templates
• Duplicate Process Model name detection was not taking into account models in the Recycle Bin

Miscellaneous

• Add Suspend, Resume and Wait for Event functionality to the AgileXRM PowerShell Module
• Include NX v8.0, Software Update 2, Cumulative Update 5 (See Release Notes)