Tag Archives: Dynamics365CE

AgileXRM Release Notes 8.0.26117.20500

Posted on by
Reply

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

AgileXRM Release Notes 8.0.25300.20502

Posted on by
Reply

The main improvements in this end-of-year release are the following:

  • New UX improvements for the AgileXRM Solution
  • Process Manager guides user to any descendant subprocess with error
  • Support Allowed Extensions for File Uploads
  • New API to fully control Snapshots (Point-In-Time) including Transactions

New Enhancements & Fixes

Dataverse/D365 Integration

Enhancements

  • New design for the AgileXRM Solution
    The solution has been enhanced to include the latest Dataverse component technologies and UX improvements, as well as made ready for future enhancements.

    NOTE: Due to a MS issue, the first time the solution is imported over an older version, the Update option should be selected rather than the Upgrade option. After this first time, the Upgrade option will work for future imports of newer versions.

  • DEPRECATION: Run Process and Start AgileDialog Command Bar buttons
    When a Table is Enabled these buttons used to be added to the Main Forms and Views. These are not added anymore as they generated clutter. NOTE: Previously Enabled Tables still have these buttons.

  • Change of Behaviour: Executed Instance record Ownership logic change
    When record is created, the Owner is set to the Model Owner if the Security Context is set to Model Owner

  • IMPORTANT: 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

  • WaitForUpdate Plugin was throwing benign error in trace logs due to concurrent Deletion
  • Generated solutions for Enabled Tables/Activities were including the table metadata which was unnecessary

AgileDialogs

Enhancements

  • Support Allowed Extensions for File Control at environment-level as well as at Control-level
    At environment-level, set them in the AllowedExtensions.json file. At File Control-level, select which of the environment-level ones are allowed.
    NOTE: The Blocked Extensions in Dataverse System Settings still apply.

  • Add API support for Save Snapshot (Point-In-Time)
    This is to cater for situations where end user stays forever on the last confirmation pop-up and does not complete the Dialog.

    DialogsEngine.SaveSnapshot( bool includeCurrentPage, int TimeoutInSeconds )
    API to be called from OnLoadScript if needed.
    If includeCurrentPage is True, include the page when it was entered into (not when it is exited), else leave it out of the Snapshot.

    The TimeoutInSeconds sets the duration of the Page, after which the Page is Cancelled internally and the Dialog continues (i.e. finishes, assuming this was the last Page).

  • Added API to support Snapshot Transactions (Point-In-Time)
    When there are loops in a dialog, allow Modeler to be able to save Snapshot of completed loops, but not abandoned loops.

    Added 3 new APIs to DialogsEngine:

    • SnapshotStartTransaction
      Starts writing Pages in a transaction until Commit or Rollback are called.

    • SnapshotCommitTransaction
      Adds the content of the transaction to the Snapshot
      From this point on, Pages are written to the Snapshot

    • SnapshotRollbackTransaction
      Clears the transaction
      From this point on, Pages are written to the Snapshot v

  • Rolling Session (sliding sessions) supported in External Dialogs

    New config parameters to modify the following:

    • UseTokenLifetime (true/false)

    • ExpireTimeSpanSeconds (in seconds)

    • SlidingExpiration (true/false)

  • Improve File Upload errors so user knows the reason for the error

  • Make the Calendar Control width settable
    Previously it was a fixed width.

  • DEPRECATED: The End Message functionality is deprecated
    With the new AfterSubmit functionality, this static message is not needed.

Fixes

  • Certain characters in the name of a Dialog Model like ~ were breaking the functionality
  • Dialog was closing unexpectedly after error in a FetchXML in the Page
  • Radio Control was not respecting values set in OnLoadScript
  • File Control validation was failing when it was within a Group container
  • Snapshot (Point-In-Time) was not generated correctly when Resuming a Dialog which contained SubProcesses
  • When saving Snapshot (Point-In-Time) it was sometimes timing out
  • Snapshot (Point-In-Time) was not recording which checkbox was clicked
  • Scrollbar was not working in the Dialog History popup window
  • Dialog History before reaching a Page with Disable Back set, was being cleared
  • Breadcrumbs were not working correctly with Disable Back
  • Some Unicode characters were not displayed correctly in Firefox
  • Phone RegEx did not support French style Phone numbers
  • Calendar Control was failing with Before and After conditions in Rules
  • The Contains Data condition in Rules for File Control was not working
  • Search shape was setting output variables to Empty string rather than to null, when there was no value to set

Process Manager

ENHANCEMENTS

  • Show Error triangle in SubProcess shapes whose subprocess instance hierarchy has an error
    If any descendant subprocess has an error in it, the SubProcess shapes above it, all show an error Triangle, so user can drill-down to get to the root cause of the error
  • Change Sort Order for Sessions in an Automatic Activity popup to Descending on CreatedDate
    This avoids having to scroll down to get to the latest session

Fixes

  • The Open Task button for a Dialog Task was throwing a javascript error
  • The Open Task button was not working with all the sessions of a Task
  • Data tab control were cropped in German version
  • Data tab was rendering content of variables
  • Date formats were not respecting Formats set in Personal Settings
  • Task Due Date popup was not respecting user’s Regional Settings Date Format

Process Modeler

Enhancements

  • Support Envision for use by non-Local-Administrators
    Previously, all Envision users had to be in the Local Administrators Group of the PC. Now they can be normal Users

  • Add HTML (Rich Text) Editor to Add Note shape’s Content property
    Dataverse supports HTML in Notes and now these can be set

  • Include “Does Not Contain” Operator in Single and Multiple Condition Editor

  • Change of Behaviour: Auto-set Security Context and Auto-create Model Permissions
    When a new Model is first Published, previously, Security Context and Model Permissions had to be configured manually. Now, Security Context is set to Model Owner for Process Models and to Process Initiator for Dialog Models. Also, All Permissions for root System Administrator Security Role are set automatically

Fixes

  • Model names were allowed to exceed 100 chars breaking Publish functionality
  • When adding new filters to a Search Query, the fields were being added below the related Tables. Though benign, it caused confusion.
  • Email Templates window when maximized, was rendering incorrectly
  • Trying to set the value of an Image column with an empty variable was throwing an exception
  • Under certain circumstances, the buttons in the URL Editor of the Email Template Editor were not visible
  • Visio would sometimes crash when accessed via Remote Desktop and a Page was saved that had OnLoadScript
  • Visio was sometimes crashing when used in high-resolution monitor with high DPI (>150%)
  • Clicking Open SubProcess link (in a SubDialog shape) was throwing an exception
  • Detaching a file which had two consecutive dots in its name, to SharePoint was throwing an exception
  • Selecting My Dynamic Major Version in SubProcess configuration was throwing an error
  • Visio was crashing with multi-language Progress Messages
  • Some windows were not rendered correctly under high DPI settings

Miscellaneous

  • FIX: Internal Caching mechanism did not include Security Context and SLA info for Models
  • FIX: AgileXRM DevOps Import Task was not updating Models with non-consecutive versions

AgileXRM Release Notes 8.0.25007.20500

Posted on by
Reply

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)

Announcing the AgileXRM Community Edition

Posted on by
Reply
person hand reaching body of water

“You’ve got the Holy Grail of Process Management Tools”

— Microsoft Program Manager


AgileXRM has been around for quite a while now and has been fully tried and tested, out there in many clients around the globe, including many hard-to-convince enterprise and public sector customers, helping them manage their Business-critical processes.

AgileXRM started life back in 2006, in the Dynamics CRM 3.0 era, and has since grown and matured through the amazing evolution of Dynamics CRM On-Premise to Dynamics 365 Online and on to the remarkable Power Platform (Dataverse), Microsoft’s Business Application Platform.

All these years, we have been happily occupied with evolving the product through all the feedback we received from our customers, to cater for their ever-changing and increasingly demanding real-world business scenarios. Our customer base was growing just through word-of-mouth!

It is now time to make AgileXRM available to a much larger audience, and what better way to make our product more reachable in the market, than by offering a Free-Forever version of it. With AgileXRM Community Edition you can verify for yourself, the value it brings to your Digital Transformation strategy and how it complements the Power Platform.

Recruitment Process Example

Below we try to answer some questions you may have:

What is the value of AgileXRM for me?

In short, you will be receiving the following:

  • A Microsoft Visio-based Modeler to let you model processes and dialogs
  • Powerful dialog functionality for creating guided interactions for any type of user
  • A Business Process Engine (BPM) to manage the lifecycle of your processes end-to-end
  • A Process Monitor to let you visually see and manage running processes

The answer also depends on you background:

  • If you are new to Power Platform and just starting
    Power Platform is many things to many people. You may be looking at Canvas Apps in conjunction with data sources like SharePoint to create your Apps. Or maybe you have already recognized the need for Dataverse as your data repository and want to create more solid and manageable Model-driven Apps. If it is the latter, then AgileXRM would add great value.

    AgileXRM Value: AgileXRM keeps Model-driven process-apps Low-Code (mostly No-Code). Because with AgileXRM, you avoid having to use javascript in your Dataverse Forms and avoid needing to write custom C# code (Plugins etc.). Also being a BPM tool, you will be modelling and configuring your business processes and your User Interfaces/Interactions explicitly with Microsoft Visio, a visual tool that is designed to be understood by business users. Anyone can create very complex process-apps easily and cleanly without extensive knowledge of Dataverse customization.
  • If you are already using Power Platform to some extent and want to do more
    Having delved into the platform already, you probably have recognized how some requirements are harder to implement, either needing resources with expert knowledge or requirements that need too much effort to implement.

    AgileXRM Value: AgileXRM allows you to reach much further and quicker without requiring a higher level of Dataverse knowledge.
  • If you are already deep into Power Platform and have created many complex solutions
    There is no better person than you to know exactly where the pain-points are:

    • Difficulty in correctly capturing the business process requirements
      Business users usually use a flowchart diagram to describe their process requirements, but they will never see it again in the produced apps

      AgileXRM Value: From requirements capture to creation to execution, everyone uses the same Process Model. Everyone sees the same model at design-time and at runtime and it is understandable by everyone.

    • Cost/effort in creating the solutions
      Good expert resources are hard to find in the market and certain requirements demand excessive amounts of code leading to over-customization of the platform

      AgileXRM Value: Implement complex business requirements much faster and by non-developers. Avoid over-customization of the platform by keeping everything truly Low-Code.

    • Cost/effort of maintaining the solutions
      The business logic is split in many parts and hard to see the overall picture, especially when project resources leave or when business requirements change once in production, and how those changes affect existing processes that are mid-flight

      AgileXRM Value: The process logic is being documented with the end-to-end process model as What You Model Is What You Execute, and it is easy to see what needs to be changed and where in the model. You can even compare different versions of the process to see exactly what changed and where.

    • Cost/effort in troubleshooting when things go wrong
      Given the end-to-end business process is split across many components (Flows, Workflows, Actions/Custom API, Business Rules, Business Process Flows, Plugins, Custom Pages and client-side javascript), it is hard to identify what failed and what needs to be fixed. And even when it is identified and fixed, it is hard to evaluate how the changes affect existing processes which are still in progress

      AgileXRM Value: Firstly, you can model error-handling in your business process using alternative paths. Then, there is also a Retry mechanism, but if eventually a step in the process fails, the process is Suspended, and the error is made visually visible in the Process Monitor and recorded in Dataverse against the Process record (and admins are notified). If it is an external issue and it is fixed, Resuming the process is enough to continue. If it is a logic error in the process model, you can correct it, publish it and then Migrate existing running processes to the new corrected version.

    • Handling high volumes and business-critical processes
      When the correct running of the processes is of paramount importance to the business because it touches the organization’s bottom-line, you are aware of the pressure for all of it to work correctly

      AgileXRM Value: Our customers, in both private and public sectors, run Business-Critical Processes with millions of process instances per month. AgileXRM JUST WORKS!

What can I do with AgileXRM Community Edition (CE)?

You can use the full functionality of the Licensed Edition, for up to 25 Users for Free and Forever. You get the Visio-based Process Modeler, the Process Engine, the Process Manager and AgileDialogs.

  • Model and configure end-to-end Business Processes for any of your Dataverse or Dynamics 365 Customer Engagement Apps
  • Visually monitor where you are in the process
  • Handle unforeseen situations by managing the running processes
    Things like jumping from any step of the process to another step. Or even migrating a running process to another version
  • Model and run powerful dialogs (screen flows, agent scripts, wizard-like self-service guides etc.) for internal and external users (Contacts or anonymous users do not need a license)

AgileXRM CE is single-server. If you require High Availability, Archiving or more than 25 Users, you would need to get a License.

How do I get my copy of AgileXRM CE?

Simple: Go through this dialog(Powered By AgileXRM) on our web site and just follow the steps to register.

How is AgileXRM CE deployed to my environment?

AgileXRM CE will be deployed to your chosen Azure tenant and your chosen Dataverse Environment (or Dynamics 365 Org). Everything is done via another nice dialog(Powered By AgileXRM) that will guide you through the steps of the deployment process automatically. You’ll receive a link to this dialog once you register.

AgileXRM CE Deployment dialog

You are going to need the following:

  • Azure Global Administrator credentials for the Consents
  • Azure Subscription Owner credentials (usually same as above) for deploying the Process Modeler and Process Engine VMs to your Azure Tenant
  • Dataverse Environment with System Administrator credentials for deploying the AgileXRM Solution and Consent
    If you do not have one, create a Trial Dataverse Environment here, clicking Start Free button
  • Visio Plan 2 License as the Process Modeler uses Microsoft Visio
    If you do not have one, get it here Visio Plan 2
    NOTE: You can also use a Visio 2019 Product Key (Standard or Professional Editions), if you have one

What if I do not want to (or cannot) deploy anything to our Azure tenant?

You have two options:

  1. If you just want to try AgileXRM CE, you can create a new Azure Trial here
    You get US $200 of credit and you can deploy everything there, which gives you 30 days to try everything

  2. Let us know when going through the registration dialog and we can provide you with one of our AgileXRM Online Trial tenants. This way, nothing is deployed to your Azure tenant.
    You are still going to need a Dataverse Environment (or Dynamics 365 Customer Engagement Org) and an Azure Global Administrator credentials for the Consents.

What is the best way I can try the capabilities of AgileXRM CE?

We do Free PoC’s. We highly recommend that you let us help you to implement your first process-app. That way, you quickly get up to speed and will be able to realize the value that AgileXRM brings to your Power Platform projects.