Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
We've added the ability to merge branches in your Case workflow processes to help you streamline the creation of your business Case flows.
Sometimes creating a business process can leave you with many different routes that you want to lead onto the same action depending on the criteria of the step. By using this new merge feature you will be able to choose different Actions to end in the same outcome.
Watch the following video to find out more:
You can choose to merge together parallel branches or conditional branches.
To merge multiple Actions together, click on the menu of one of the Actions you want to merge and select 'Merge', then 'Add'.
In the following pop-up select the other Actions you want to merge it with from the list of Actions that are available for merging.
Then select which Action you want them to be merged into - you can either choose from an existing Action type or you can choose to create a brand new Action type for this.
The merged Action will then appear in the flow.
Note that you can only merge together Actions within the same step.
If you are merging together Actions from parallel branches, the merge Action will wait for all of its the predecessor Action to complete before it can start.
If you are merging together Actions from conditional branches, the merge Action will start when one of the conditional branches has been completed.
In version 2023.1 of Enate, we've been focusing on making some improvements to Builder for enhanced Case flow construction. You've now got much richer ability to use conditionality within your flows: routing down different paths based upon Action checklist responses is now supported, plus you can now bypass peer reviews of manual actions based on conditionality. Merging of different branches of your flows back together into a single action is now supported too.
Watch this video to find out more:
Check out these and other new features in more detail in the sections below...
Add conditions based on an Action's checklist - we've added the ability to use the results of individual checklist items in your conditions, letting you choose alternate routes depending on how a check has gone.
Bypass unnecessary peer reviews - we've added a new option to automatically bypass a peer review if certain conditions are met. You can add conditions to a Peer Review Action in your Case configuration - if that condition is met, the peer review part of the Action is set to no longer required and will be bypassed. The work flows straight on to the next action.
Merge Case flow branches - we've added the ability to merge branches in your Case workflow processes to help you streamline the creation of your business Case flows. Previously, moving to a new Step would be needed to re-combine multiple branches of a flow. Now this can happen mid-stream within a Step, as many times needed.
You can check out a list of the new Features, Enhancements & Bug Fixes we've included in this release in the following sections. For a more extensive list of changes including API changes, Data Warehouse Changes and any Breaking changes, see the dedicated RELEASE NOTES section.
The allocation method 'From Team By Path' has been removed.
We have added two new allocation methods which lets you allocate work to an individual from a specific User Group:
Individual from User Group will allocate a work item to an individual in the selected User Group based on a round robin basis i.e. user 1, then user 2, then user 3, then user 1 etc.
Individual from User Group (by capacity) will allocate a work item to the individual in the selected User Group who has the lowest amount of estimated hours of work in their inbox
Migration from the 'From Team By Path' allocation method will happen automatically. Upon upgrading to version 2023.1, any processes using the allocation method 'From Team By Path' will be updated to use the allocation method 'Individual from User Group (by capacity)'. Members in the 'Team' of the 'From Team By Path' allocation method will be migrated to a new User Group with the name 'Migrated for allocation - [Team name]'.
See here for further information about how to use allocation methods in Enate:
Following on from the introduction of 'Plus Addressing' in our last release, we've made a further enhancement by adding an option to hide the work item IDs (e.g. '100123-T') used as plus addresses in the 'From' address of emails. This is a system-wide setting made in Builder.
When the new 'Hide Work Item Matching Data in Email Addresses' setting in the system settings section of Builder is enabled, work item IDs will NOT display as plus addresses in the 'From' address. Note that this option is set to off by default.
The impact of this is that if the setting is enabled, instead of seeing emails with
'jane.smith+12345-T@acmecorp.org' in the from field, it will instead show simply as
'jane.smith@acmecorp.org'.
When the new 'Hide Work Item Matching Data in Email Addresses' setting in Builder is enabled, a hidden 'Reply To' field will be added in the background to the email header for emails being sent out of enate, to allow the work item ID to be saved there rather than in the displayed From address. This means that it will no longer show in the 'From' address - not when the email is being composed in Enate, and not when the end recipient receives the email. It will show instead simply as e.g. 'hrsupport@acmecorp.org'
However, when the end recipient clicks reply/reply all to this email, the 'To' address field WILL get automatically populated with an email address AND the work item IDs used as plus addresses (i.e. the mail that the end user is composing will show the 'To' address as 'hrsupport+12345-T@acmecorp.org'. This is because it's using the value in the hidden 'Reply To' field in the email header. This is in order to allow Enate to link this email to the correct work item.
There may be some risk that email client software does not handle the ‘Reply To’ field properly. The global email standard says this field should be supported by all email client rather than must be supported. Enate has tested this with Microsoft and Gsuite and both of these work as desired with a ‘Reply To’ header. Other email clients will also likely work as desired in the same way, but these have not been tested by Enate.
What is the operational impact if an end customer's email client doesn’t support the ‘Reply To’ field? The email client just ignores the 'Reply To' and sends the email reply to the From address (in this example 'hrsupport@acmecorp.org'. This in turn will mean that the Enate system will create a new piece of work rather than linking it into the existing thread. If this does occur, this new work item can simply be manually merged with the correct item.
Some spam email detector technology may increase the risk score for the email with ‘Reply To’ headers set like this because the 'Reply To' address is different to the 'From' address. This is one of many hundreds of factors considered in spam filtering. Customers can be asked to whitelist specific email addresses to mitigate such risks.
We've also added the ability to automatically bypass a peer review if certain conditions are met. A new option is now available to add a conditions to a Peer Review Action in your Case configuration - if that condition is met, the peer review part of the Action is no longer be required and will be bypassed.
This gives you more flexibility when using Peer Review Actions and allows you to avoid any unnecessary peer reviews.
Watch this video to find out more:
To set a condition for a peer review, in your Case flow screen select the relevant 'manual with peer review' type action and, on the Peer Review tab, click the 'Bypass if' icon.
In the resulting popup, set your condition - choosing a data field (which can be standard or one of your own custom data items), then a condition and a value.
Once you're happy with your settings here, click to apply the condition.
The 'Bypass if' icon will then be highlighted, showing that a condition has been added.
Make sure to save the update to your Case and set the new version live.
Selecting the 'Advanced' option lets you create a more complex condition with a combination of multiple criteria, adding a plus symbol between each part. You can check the validity of your expression via the external dotNetFiddle link.
Once you're happy with your settings here, click to apply the condition.
The 'Bypass if' icon will then be highlighted, showing that a condition has been added.
Over in Work Manager, if the condition you have added is met at runtime, the activity will move straight from the manual activity onto the next Action, bypassing the peer review stage. A note will subsequently be displayed in the Actions list on the Case screen, showing that the peer review activity was not required.
Note that users subscribed to receive 'Peer Review Completed' notifications will not receive notifications about peer reviews that have been bypassed.
See here for more information about processing Peer Review Actions in Work Manager:
2023.1.17.0 is a HotFix release for version 2023.1 of Enate that contains one enhancement. There areno new bug fixes, and no known issues, breaking changes or additional breaking API changes in this release.
The change log contains a detailed list of the new features, enhancements, bug fixes and known issues in this version of Enate. A downloadable copy of the New Features & Enhancements Change Log, the Bug Fixes Change Log and the Known Issues Change Log are available below.
This is a downloadable copy of the new feature & enhancements in this version. One additional enhancements has been added since the release of the previous version.
2023.1.16.0 is a HotFix release for version 2023.1 of Enate that contains one enhancement. There is one new bug fix, and no known issues, breaking changes or additional breaking API changes in this release.
The change log contains a detailed list of the new features, enhancements, bug fixes and known issues in this version of Enate. A downloadable copy of the New Features & Enhancements Change Log, the Bug Fixes Change Log and the Known Issues Change Log are available below.
This is a downloadable copy of the bug fixes in this version. No additional bug fixes have been added since the release of the previous version.
2023.1.13.0 is a HotFix release for version 2023.1 of Enate that contains one enhancement. There are no new bug fixes, known issues, breaking changes or additional breaking API changes in this release.
The change log contains a detailed list of the new features, enhancements, bug fixes and known issues in this version of Enate. A downloadable copy of the New Features & Enhancements Change Log, the Bug Fixes Change Log and the Known Issues Change Log are available below.
This is a downloadable copy of the bug fixes in this version. No additional bug fixes have been added since the release of the previous version.
This is a downloadable copy of the new feature & enhancements in this version. One additional enhancements has been added since the release of the previous version.
This is a downloadable copy of the known issues in this version. No additional known issues have been found since the release of the previous version.
2023.1.12.0 is a HotFix release for version 2023.1 of Enate that contains a couple of bug fixes. There are no new features/enhancements, known issues, breaking changes or additional breaking API changes in this release.
The change log contains a detailed list of the new features, enhancements, bug fixes and known issues in version 2023.1.12.0 of Enate. A downloadable copy of the New Features & Enhancements Change Log, the Bug Fixes Change Log and the Known Issues Change Log are available below.
This is a downloadable copy of the bug fixes in this version.
This is a downloadable copy of the new feature & enhancements in this version.
This is a downloadable copy of the known issues in this version.
2023.1.9.0 is a HotFix release for version 2023.1 of Enate that contains a small number of bug fixes. There are no new features/enhancements, known issues, breaking changes or additional breaking API changes in this release.
The change log contains a detailed list of the new features, enhancements, bug fixes and known issues in version 2023.1.9.0 of Enate. A downloadable copy of the New Features & Enhancements Change Log, the Bug Fixes Change Log and the Known Issues Change Log are available below.
This is a downloadable copy of the bug fixes in version 2023.1.9.0. of Enate.
This is a downloadable copy of the new feature & enhancements in version 2023.1.9.0. of Enate.
This is a downloadable copy of the known issues in version 2023.1.9.0. of Enate.
2023.1.8.0 is a HotFix release for version 2023.1 of Enate that contains a small number of bug fixes and a feature enhancement. There are no new breaking changes or additional breaking API changes in this release. There are a small number of new known issues.
The change log contains a detailed list of the new features, enhancements, bug fixes and known issues in version 2023.1.8.0 of Enate. A downloadable copy of the New Features & Enhancements Change Log, the Bug Fixes Change Log and the Known Issues Change Log are available below.
This is a downloadable copy of the new features and enhancements in version 2023.1.8.0. of Enate.
This is a downloadable copy of the bug fixes in version 2023.1.8.0. of Enate.
This is a downloadable copy of the known issues in version 2023.1.8.0. of Enate.
2023.1.6.0 is a HotFix release for version 2023.1 of Enate that contains a small number of bug fixes. There are no new enhancements, known issues, breaking changes or additional breaking API changes in this release.
The change log contains a detailed list of the new features, enhancements, bug fixes and known issues in version 2023.1.6.0 of Enate. A downloadable copy of the New Features & Enhancements Change Log, the Bug Fixes Change Log and the Known Issues Change Log are available below.
This is a downloadable copy of the bug fixes in version 2023.1.6.0. of Enate.
This is a downloadable copy of the new features and enhancements in version 2023.1.6.0. of Enate.
This is a downloadable copy of the known issues in version 2023.1.6.0. of Enate.
2023.1.4.0 is a HotFix release for version 2023.1 of Enate that contains a small number of bug fixes. There are no new enhancements, known issues, breaking changes or additional breaking API changes in this release.
The change log contains a detailed list of the new features, enhancements, bug fixes and known issues in version 2023.1.4.0 of Enate. A downloadable copy of the New Features & Enhancements Change Log, the Bug Fixes Change Log and the Known Issues Change Log are available below.
This is a downloadable copy of the bug fixes in version 2023.1.4.0. of Enate.
This is a downloadable copy of the new features and enhancements in version 2023.1.4.0. of Enate.
This is a downloadable copy of the known issues in version 2023.1.4.0. of Enate.
2023.1.3.0 is the production release of version 2023.1 of Enate that contains a number of enhancements and bug fixes.
The change log contains a detailed list of the new features, enhancements, bug fixes and known issues in version 2023.1.3.0 of Enate. A downloadable copy of the New Features & Enhancements Change Log, the Bug Fixes Change Log and the Known Issues Change Log are available below.
This is a downloadable copy of the new features and enhancements in version 2023.1.3.0. of Enate.
This is a downloadable copy of the Bug Fixes in version 2023.1.3.0. of Enate.
This is a downloadable copy of the known issues in version 2023.1.3.0. of Enate.
Below is a copy of the breaking changes document for version 2023.1. This contains details for all breaking changes within the Data Warehouse and the Enate APIs.
This document lists all the validation codes for the 2023.1 release.
Recommendation for best use of API breaking changes documentation is as follows:
Read through the breaking changes information for APIs
Upon finding reference to an API which you currently use and which has changed, go to your Swagger environment for the quickest way to view the overall impact and new API content definition. Your Swagger environment should always be your go-to place for the definitive explanation of the current API structure. See the Swagger explanation in our main online Help section for more information.
When using conditionality in your Case flows, you can use a number of types of system data as part of your condition, for example standard system work item fields and custom data fields.
We have now added the ability to use the results of individual checklist items, both global and local, in your conditions, letting you choose alternate routes depending on how a check has gone.
Watch this video to see how that can be done, or read below for more specifics and details:
Clicking on the dropdown will reveal the Actions that have checklists to choose from. They will be displayed in the order in which the Actions appear in the flow. Clicking on an Action will show the checks that you can choose to base your condition on, displayed in order in which they appear on the checklist.
You can only use the 'Equals' and 'Not Equals' conditions for conditions based on the results of a check in an Action's checklist, just as you would short text data fields.
The values you can create conditions for against a checklist item are "Yes", "No", and "NA" for Not Applicable. Be aware that these values are case sensitive and should be entered in the value field exactly as above within double quotes.
As standard, make sure to create an 'else' branch, to handle the flow when you're conditions are not met. At runtime, if the condition is not met, the system will execute the 'else' branch.
If you're using the advanced option to build a more complex expression, checklist items can also be incorporated here - once you've picked them from the dropdown list they'll be added into your expression with a unique identifying GUID.
Note that you can only use checks from Actions in a previous step in your conditional expressions and you cannot use check from ad-hoc Actions.
Once you're happy with your condition settings, click 'validate' to ensure they'll work at runtime, then 'OK' to apply the condition to the Case flow.
