2020.1 Updated Preview
Work Manager
2020.1.6.0 released on Thursday, 9th July 2020.
New Features
  1. Email Content management is now performed within Builder.
  2. Email Content can now be defined in multiple languages for the same Email.
  3. Integration with Abbyy Flexicapture.
  4. Automatically prompt users to create External Contacts for unknown email addresses.
  5. How a Work Item started is captured along with who started it (when started by a User). This information is available in numerous grids, Work Item information card and the Warehouse database for reporting.
  1. Security Enhancement: Enate Username, Session ID, Live/Test Mode, GUI and Session Validity can optionally be included in IIS Logs.
  2. In Builder highlight to users if 1 or more Email Connectors are offline.
  3. Users are warning if the Custom Data on a Work Item they are working on have been changed by another User since they opened the Work Item.
  4. When Actions are started as part of Case Rework they will auto-assign to the User that previously did the Action.
  5. When starting Case Rework Users can select which Sub Cases and Ad-Hoc Actions are Terminated and are shown a list of the Actions which must be Terminated.
  6. When starting Case Rework Users can choose a specific Action within a Step to being the rework from.
  7. Feedback to features released in Preview 1 (2020.1.2.0)
2020.1 Preview
Work Manager
2020.1.2.0 released on Friday 29th May 2020
New Features
  1. A condition can be included at the start of a Step in Builder to decide which Actions start.
  2. System-wide configuration parameter (available in Builder) to choose if users must enter a note or send an email when resolving a Ticket.
  3. System-wide configuration parameter (available in Builder) to choose if users see the Time Tracker. Time on task information is still recorded and is available in Management Reporting.
  4. The supplier of a Contract can now be changed within the Edit Contract screen of Builder (if multiple suppliers have been configured in the system). This change will affect the Management Reporting for all historic and running work items.
  5. Users can now rename and delete Queues from Builder.
  6. Unprocessed emails can be marked as "acknowledged" in Enate Monitor to hide them from view. The user that acknowledged them and when is recorded. Acknowledged emails can optionally be shown.
  7. The ability to set live a Case or Ticket configuration in Builder is now explicit permission. Users who previously had the Process Builder permission will have this permission granted upon upgrade.
  8. The Files of a Work Item can be tagged to identify them to other users, digital technologies and automated Actions (such as OCR).
  9. Due Dates can now be moved to the end of the day. For example, if system returns the due date as 14:30 but you would like to move it to the end of your day which 17:00 as per you working calendar then you can use this option. In the absence of a working calendar, the system will move the time to 23:59.
  10. A new Due Date Method allows the value to be retrieved from a Custom Data field.
  11. Actions can be cut, copied and pasted in Builder. Cutting or copying an Action includes all the chained Actions and it copies all the configuration except local checklist
  1. During peer-review, users can now edit the Record Count, Files and data on custom cards. Except for editing doer Checklist they can edit the Record Count, Files, Contact, Defects, and data on custom cards
  2. While an email is sending from a Work Item the submit and send buttons are disabled to avoid accidentally sending the email multiple times.
  3. After manually editing the current time-on-task value on a work item a new row is shown to count the time from that moment on. This change was introduced to avoid user confusion when they record 5 minutes manually but the system might record 5:05 due to the time it takes them to submit the work after editing the time-on-task. Now it will be recorded as 2 records; 1 record is manually set at 5 minutes and another record will automatically record the additional 5 seconds the item is on-screen.
  4. Custom Cards now execute in Angular 9.1.3 (previously 8.2.14). Customers developing advanced custom cards should review the changelog of Angular 9 ( for changes that may affect their custom code.
  5. While a file is uploading the submit and email send buttons are disabled.
Enate - 2019.5 Changes
Work Manager
1. Introduction
This document highlights the main changes in functionality between version v2019.4 of the Enate Software and the new version, v2019.5.
This document does NOT contain a comprehensive list of all changes & fixes between v2019.4 and v2019.5 - This document should be used in conjunction with the release log of all changes for this version of the software for such a comprehensive list.
2. Work Manager Changes
This section details the changes / new features in v2019.5 that can be found in the Work Manager operations environment.
2.1 Robot Farm View Changes
A. Robot ‘Owned Work’ view option
The Robot Farm View in the Home page has been updated to also show an ‘Owned Work’ view in the grid – this shows work items where a Robot is set as the Owner, for instance when an Action is in a state of "Waiting for more information/Schedule for FollowUp".
B. Last Connection Time now available
The Robot Farm View of the Home Page now shows the robot’s Last Connection Time in a tooltip, when you hover over an individual Robot.
C. Changes to the data displayed in Robot Farm view
There have been a number of updates to the data which is displayed in the robot farm view, as follows: • The view now shows all work a Robot Farm will undertake even if the work item is in a Queue not managed by the currently logged-in user.
• The view now takes into account work the current user does not have permission on when calculating the projected start/end time of work, plus the overall duration of work available to the Farm. The number of work items not shown to the User due to permission restrictions is also shown. Please note that the logged-in user will continue to not see work for which they do not have permission.
• The Robot Farm Summary view on the right side of the Home page will now show the overall duration and count of work items available to the Farm instead of just the work that the current user has permission on and is in Queues the current user is in or manages.
3. Builder Changes
This section details the changes / new features in v2019.5 that can be found in the Builder configuration environment.
3.1 Bulk Upload of Schedule Data
In addition to being able to manually add new rows of schedule periods (i.e. dates) into a schedule, as of v2019.5 you can now upload such data, for multiple periods, in bulk via excel spreadhseets. Here’s how that’s done.
Select the ‘Bulk Upload’ link to bring up the ‘Schedule period bulk upload’ popup. This new UI offers a seamless method for uploading multiple schedules simultaneously. All that’s needed is an .xls or xlsx file with your data, click upload and the data is created.
There are a couple of file format requirements that your data will need to confirm to in the excel file:
• It will need to contain a header row which matches the grid headings of the schedule UI. This needs to include: period, year, start date plus all the custom-made schedule date titles you defined in your schedule structure.
• To exclude any non-schedule date data that might be present in your excel sheets (for example document description/company logos etc.), you can specify the ‘Header Cell’ in the upload popup (see below) before you uploading your schedules. This is effectively telling Enate which point in your excel sheet to start looking for schedule dates – any rows in the sheet which precede your defined header cell will be ignored.
Once you hit the upload button, new rows will be added to your screen in Builder containing the dates from your excel. They’ll be displayed in a different colour in the grid to identify new periods you just added. At this point, you can either discard the changes or, if you’re happy with the uploaded dates, hit save to finish the upload process.
When you hit save, the system will complete the process with confirmation pop up on the screen as below-
3.2 Option to Hide Historic Schedule Data
A further new feature related to schedule data maintenance has been added in version 2019.5 – we’ve added a checkbox to the schedule maintenance screen which, which when ticked, will hide previously completed schedule periods from your view. This can be very useful if you have lots of data from previous periods and would like to focus purely on viewing future dates.
Enate - 2019.4 Changes
1. Introduction
This document highlights the main changes in functionality between version v2019.3 of the Enate Software and the new version, v2019.4.
This document does NOT contain a comprehensive list of all changes & fixes between v2019.3 and v2019.4 - This document should be used in conjunction with the release log of all changes for this version of the software for such a comprehensive list.
2. Work Manager Changes
This section details the changes / new features in v2019.4 that can be found in the Work Manager operations environment. Other larger features are covered in separate sections.
2.1 Enhanced File Attachment Features ( Comms, Files card)
A. Preview Of attachments in Comms / Files section
Documents within a work item can be previewed with a single click – this relates to any document files which can be seen in the Comms, Timeline, and Files Card sections. The document previews will open in a new tab.
•Attachments in the files card can be previewed by clicking on the preview option
•If the file is not previewable, a confirmation banner pops out to explain this, plus offering an option to download the file.
•The file types supported for preview are as follows: txt, pdf, jpg, jpeg, jpe, jif, jfif, jfi, png, gif, web, tiff, tif, heif,heic, svg, svgz.
B. Download multiple attachments
It is now possible to download multiple attachments with a single click from mails in the comms and timeline section. Clicking on the ‘Download all’ icon will download all attachments present in that Comms/Timeline section item.
C. Drag and Drop of Attachments into Email Section and Files Card
The functionality enables users to drag and drop attachments into the Email section and Files Card. When attachments are dragged into Email and Files card sections, the section is highlighted with a green border.
2.2 Enhanced Email Features ( Ticket)
A. Display of the From address all time
The From address now always displays in the email composition section when you are writing an email (This is a change of behavior from previous versions where the from address was auto-hidden if there was only one from address configured). This ensures that the sender will always have a view of the email address being used as the form when sending out emails from a particular work item.
B. Email subject and body for new Tickets automatically copied into title and description
For manually created tickets that are yet to have a title and description entered for them, if you send out an email prior to initial submitting (and saving) of the ticket, the system will auto-populate the ticket title and description from the email subject and description respectively.
Ticket title and description not yet sent...
Upon sending the email, the subject and the body are copied into title and description.
C. Personalized Email Signature
Enate’s Email Signature feature allows you to configure your own signature for outgoing emails. The setting can be found in the user settings from the user profile tab, clicking on your username.
In the resulting ��User Settings’ tab, you can use the Email Signature section to define the signature content to be sent in outgoing emails that you write.
The configured email signature will only be included with the outgoing emails if the
‘Include my signature in the outgoing emails’
checkbox at the foot of this section is checked.
After you have created a signature, clicking on any of the links to bring up the ‘compose new email’
the section in any work item will display the configured email signature at the bottom of the email body.
D. Copy-paste of Email Addresses between To, CC, BCC.
When composing emails, you can easily copy email addresses between the To/Cc/Bcc addresses via the new ‘copy’ icon displayed when clicking into the relevant address field.
2.3 Display of Remaining Hours of SLA when Work Item is Pause.
This feature is an enhancement of Stopping the clock on the work items which are in a state of pause.
If a work item is in a state of Pause, and the Due Date rule configured in Builder is set to
‘Add wait time to due date’
, then the system does not display the due date in the header ribbon. Instead, the system shows the remaining time left until the item is Due. If the work item is yet to pass the due date the message will show as
‘Due: Paused x h y m before due’
. If the work has passed the due date then the message will show as
‘Due: Paused x h y m after overdue’
: work item which is paused where its due date is
on target
due today
: work item which is paused where its due date is
2.4 Test Mode Enhancements
A. Test manager and test users of the Queue
Test mode functionality now allows you to set a different manager for a Queue when running in Test mode vs. Live mode.
: Consider Manager 1 who has access to live mode and is responsible for managing two queues, Funding, and Master Case queue.
In Test Mode, these two Queues can be managed by another user (if they are set as a Team Leader and have Test mode permissions!) – see below where now Manager 2 has been set to be in charge of these two Queues in Testing Mode.
B. Switch Robots between Live and Test
It is now possible to switch a robot so that it can run in test mode or live mode. Specifically, two new activities have been added to the activity libraries for UiPath, Automation Anywhere and BluePrism (and the standard APIs adjusted so this can be called generically) as follows
•Set Live Mode
•Set Test Mode
These actions allow you to flip a robot between test and live states. Once a robot has been flipped into Test mode, subsequent activity calls which the robot might make, e.g. ‘Get more work’ and ‘Create Ticket/Case, etc.’ take place within that context of Test mode, getting and creating only test work items. The robot should be switched back to Live Mode once the process is set to live, so ensure it is then creating live work items.
C. Test Contacts - Separate test contacts in the system
Enate now supports the creation of separate Contact records in Test Mode, i.e. any contact records you create in Test mode will be accessible only to Test Mode users (and contacts created in live mode will be accessible only to Live mode users). This helps to ensure that emails from test packets are not accidentally sent to production users, and vice versa.
2.5 Multiple Queue Managers
Queues can now be set to have more than one manager. This allows manager users to get visibility on another queue without having to become a resource that works out of the queue, and without taking ownership of that queue away from its current manager.
: Consider Manager 1 and Manager 2 as two team leads where Manager 1 needs visibility on the queue of Manager 2. Manager 1 can simply add the queue of Manager 2 to their queues page to get visibility.
Click on the edit option and add the specified queue where it shows that the queue is managed by
Manager 2. This no longer removes managerial responsibility from the current manager.
If a queue is managed by multiple managers then the users that are managed by you are filtered under Managed by me and the other users manged by other mangers are filtered under Manged by others.
2.6 Miscellaneous changes
A. Make column order in search grid persist when doing multiple searches
Once the user adds a column and order preferences to their search grid, these settings will persist when the user logs back in.
B. Added support for latest Microsoft edge browser based on chromium
Enate v2019.4’s Work Manager supports the latest version of the Microsoft Edge browser (based on Chromium).
C. Due Date and Allocation methods
Please note:
the creation of new bespoke Due Date methods and Allocation methods is no longer supported.'
3. Builder Changes
This section details the changes / new features in v2019.4 that can be found in the Builder configuration environment. Other larger features are covered in separate sections.
3.1 Capability to add different start/end time for each day in the
calendar This feature enables users to configure different working hours for each day of the week, irrespective of default working hours.
3.2 Ability to clone a process with local checklists in service matrix
An option has now been provided in the ‘Clone Case’ popup “clone (Include local checklist)”. If this option is selected local checks will also be copied across into the new Case. Previously the cloning of the localised checklists was not supported when cloning a Case (only the global checks were copied across).
3.3 Ability to Force clone a process on the existing ones
This feature enables a user to forcibly clone a process onto an existing process, and so overwriting its settings. The force clone ability is enabled for the processes that are in edit mode.
3.4 Ability to send a Ticket Acknowledgment email to CC users
This feature is an enhancement of the existing functionality where an auto-confirmation email or acknowledgment is currently sent only to primary contact/sender but not to the CC users.
With this enhancement, acknowledgment or auto-confirmation email is sent to CC emails tagged to the work item if send acknowledgment is checked in the email routing.
3.5 New allocation method ‘Completer Of Action’
With this new allocation method, we can allocate certain actions to the user who completed the particular action. The new allocation method decreases the load on the queue and directly assigns the work item to a specified user as per config.
You can configure this type of allocation by selecting the Completer of Action allocation method and selecting a particular action as shown.
3.6 Display of Fixed Frequency Schedule name in packet title.
Work items which have been launched through Fixed frequency-based Schedules will display the frequency name in the work item title, as follows:
Title Format:
[Name Of the Schedule] [Date Month Year Time]
Payroll Process 14 February 2020 15:07
Fixed frequency schedules support localisation, where local language equivalents of Instructions can be specified (Spanish and Portuguese languages currently supported). This can be found in the Frequency Based Schedule column under the Localisation tab.
3.7 Migration of Defects to Builder
The configuration of Defects in Enate has now been migrated from Configuration Manager across to Builder. At the same time, a number of changes have been made to the underlying architecture of the feature which results in some changes to functionality, and some migration aspects to be aware of both before and after migration.
A. Changes
• Defect Categories are now managed in Builder.
• The ‘Party at Fault’ list can now be customized (in Builder). This was not previously possible.
• Defect Categories previously had to be a fixed number of Levels deep (1, 2 or 3). Now each category can be up to 3 levels deep, and you can even mix-and-match some that are only a single level while others have multiple levels.
• The list of available Defect Categories is now shared by Case and Ticket rather than being a separate list for each.
• Defects can now be added to Actions.
• The defects applied to a work item is now shared with any related Cases/Tickets and Actions (just like Custom Data, Files, Contacts, etc). So a defect added to an Action shows on its parent Case. If that Case was launched by a Ticket then they would also show on that Ticket. Likewise, if a Defect is added to a Ticket then it shows on the Case if one is launched from it.
• Defect Categories and Party at Fault list localisations are available and are managed in the standard localisation screen of the builder.
• Previously, Defect Categories had both a ‘hidden’ underlying value and a Display Value which the user saw. This ‘hidden’ value no longer exists, there is just a single value defined.
B. Warehouse aspects of the Defects changes:
• In the data warehouse, only the ‘hidden’ value was exposed with no way of getting the Display Value. Now there is just a single value defined.
• In the warehouse only the values of Defect Categories that had been used were available. The full list of configured defect categories was not available. Now, the warehouse contains the Defect Categories even if they are not referenced by a work item yet.
• The warehouse now contains the localised Display Values in the usual Localisations table
• See separate “Breaking Changes” document for technical details of the new Warehouse database structure.
C. Migration of Defects data
• Defect categories that are on a Case OR Ticket are migrated to a single list on the Service Line – this should be validated manually after the migration has been completed.
• Some customers may have some misconfigured Defect Categories created in older versions of the product. For example, it may be that they have had a Defect Categories of ‘(Select)’ which incorrectly does not have a value defined ending in ‘.Blank’ (perhaps a typo of ‘, Blank’)
– as such, this would be considered a valid category for the user to select in 2019.3 and below, and so this will be migrated over to 2019.4 as a valid defect category. Customers may wish to correct or delete such unwanted defect values, something which can easily be achieved in Enate Builder.
D. Configuring ‘Party at fault’
To configure new / edit existing Defect Party at fault values, click on the settings icon in Builder and select the ‘Defect Parties at fault’.
This will allow you to add or edit the values available here.
E. Configuring Defects
To configure new or edit the migrated defects click the edit link on a Service Line and expand the new advanced settings, and Defect categories can be configured to three levels
In the resulting ‘Update Service Line’ popup, the Defect category configuration can be carried out.
3.8 Advanced Option for Due Date Setting - Variables
An advanced option has been enabled for Due Date rules which allow for the use of custom data variables when setting time adjustments.
Enabling the Advanced option when setting a Due Date rule will display an additional set of options
in the ‘Adjust by’ section.
This will allow you to add/subtract a certain number of Hours/Days/Working Hours/Working Days by selecting from a dropdown of numeric custom data fields.
3.9 Days and Hours in Calendar-driven Due Date Rules
When involving Calendars in Due Date rule configuration, the system now supports Hours And Days (previous versions only supported Working Hours and Working Days when Calendars were involved).
3.10 Improvement of Runtime permissions
Runtime permission calculation is no longer applied via a batch job. This change comes with a marked improvement in the performance of run time permission calculation and a large reduction in SQL server I/O load.
3.11 Service Matrix Page Improvements & UX changes
A number of improvements have been made to the service matrix page in Builder
  1. The free-text search approach has been replaced with the use of dedicated filters for Customer, Contract, Service to allow for easier drill-downs to view specific groups of data.
  2. The creation and modification of customer, contract, service is also available when using the above filters section.
  3. Filters are persisted when returning to the service matrix screen from other sections in Builder, and also after logout/login.
4. Robotics Improvements
4.1 UiPath - New activity for bots to access testing mode
New activities have been added to the UiPath activity library to allow bots to switch between running in live and testing mode, ‘Switch to test mode’ and ‘Switch to live mode’.
Once running in test mode, any subsequent calls the bot makes to Enate to e.g. get more work or create new work items will take place within test mode.
4.2 UiPath -Set assignee activity
A new ‘Set assignee’ activity has been created in the UiPath library to allow bots to assign tickets to specific bots.
4.3 Integration Job for UiPath Robots
Robotics workflow is improved to don’t create Jobs for all bots when new work is available for the specific bot in a farm. After this update, only the required bot will call enate for more work and process the task.
4.4 UNO technology Bot integration is added
Tech Mahindra’s own RPA technology, called ‘UNO’, can now be integrated with Enate as a digital worker.
5. Enate Desktop client app Changes
5.1 Configuration Manager
• The Batch Job approach previously used for runtime permission updates and Pointer process updates has been removed and this entire section deprecated.
• ‘Case defect categories’ and ‘Ticket defect categories’ lookup tables have been removed from Configuration manager and migrated into Builder.
• Repointing of the Pointer process is not a manual activity anymore as it automatically updates the pointer process when the user sets the master process to live.
5.2 Enate Monitor
• New Engine - Runtime permission is now handled by an engine called ‘Permission Cache Update Engine’ which is visible in Enate monitor.
• In the Email section of Enate monitor, a new state of ‘Failed Parsing’ is introduced to identify incoming emails that failed parsing on arrival due to invalid contents, e.g. a missing ‘To’ address.
Enate -2019.3 Changes
Work Manager
1. Introduction
This document highlights the main changes in functionality between version v2019.2 of the Enate Software and the new version, v2019.3.
This document does NOT contain a comprehensive list of all changes & fixes between v2019.2 and v2019.3 - This document should be used in conjunction with the release log of all changes for this version of the software for such a comprehensive list.
2. Work Manager Changes
This section details the changes / new features in v2019.3 that can be found in the Work Manager operations environment. Other larger features are covered in separate sections.
2.1 Bulk Unassign
In addition to being able to assign items in bulk from grids, you can now select to bulk unassign multiple work items.
This unassigns the work items, which then become available for users to Pick up from their work Queue. Users no longer need to navigate into the individual work item in order to un-assign.
2.2 Experimental Feature - Bulk Close of Actions on Inbox
A further bulk activity that can be performed from your own individual Inbox is to bulk Complete actions assigned to you.
The system will then loop through the actions and attempt to complete them. Sometimes it may not be possible to complete each action (for example some mandatory information/checklists may still be incomplete). The system will display a message informing you that this may take a little while to complete all actions, and subsequently confirmation popups regarding the completion/lack of completion of your selected actions.
2.3 Stopping the clock on Work Items in a state of Pause
As of v2019.3, if a work item is in a state of Pause then the Due Date is no longer displayed (AND the Due Date rule configured in Builder is set to ‘Add wait time to due date’), then the system does not display the due date in the header ribbon. Instead, we show ‘Due: Paused’. In a future release, the system will also show the time remaining when the item was placed into a paused state.
2.4 Additional Due Date Status – ‘Unknown’
A fourth status has been added to the previous ‘Red Amber Green’ breakout of works items against their Due Date, that of ‘Unknown’.
Work Items are classified into a state of Unknown when the Due Date is not currently known. This can be in the following situations:
• When the work item has just been started (manually) but has not yet been submitted.
• When the work item is in a state of ‘Paused – Wait for more Info’ AND is set to add the wait time on the Due Date.
2.5 Merging Tickets expanded to cover Tickets not created via email
Until now it has only been possible to merge tickets that were created via email. From v2019.3 onwards, you can now also merge tickets which have been created via Call Handling, via the Self Service portal and split tickets.
2.6 Starting a Case via incoming Emails
Until now the only work item type which is has been possible to auto-generate from incoming emails was Tickets. With v2019.3 onwards, you are now able to also create Cases from incoming emails. See the builder section on ‘Email Routing’ to see how this is configured in Builder.
2.7 Starting a Case from Enate Workflow
It is now possible to configure a Case to start automatically from within a running Case flow, by inserting a ‘Start Case’ Action into your case flow in Builder. See the Builder section for details on how to do this.
2.8 Alerting users when work is assigned to someone else
If you open an unassigned work item and subsequently make a change which would result in it being auto-assigned to you, if during the interim period another user has opened the same work item and has already assigned to themselves, the system will display a warning popup explaining that if you assign the work to you, any unsaved changes from the other user will be lost.
You have the choice to continue with assigning the work to you (which will discard the other person’s unsaved changes) or cancel your reassignment/update.
2.9 New Feature – Views of your data
The new ‘Views’ feature in Enate allows you to view work items in your business area (i.e. those which you have permissions on), specifying your own search criteria. You can search based upon a large number of standard bits of system information, e.g. ‘Last Updated By’, ‘Queue’, and by any of the Custom Data fields in your system.
Access the new ‘Views’ tab from the Navigation pane.
A. Searching
Add the search criteria you want to search by, setting the ‘Condition’ (e.g. Equals, Is greater than, etc.), and a value against which to evaluate the condition.
By default, the system sets an initial value of ‘items due now’.
You can add as many additional sets of conditions as you wish.
B. Search Results
Once you’ve specified your search conditions, hit Search to show Search Results.
The total number of search results will be shown at the top of the grid.
Choosing which data to see in Search Results
As with your Inbox & Owned work grids, you can choose which columns you wish to see/hide in your search results grid. Simply click the cog above the grid and from the ‘Display and Columns Settings’ popup, select the standard system data and Custom Data fields you wish to display.
C. Grouping and Ordering
You can Group By and Order By your results by all of these same criteria.
Only a single grouping criteria can be specified, and results will be loaded upon expanding an individual group.
2.10 Peer Review Comments
For work items that are sitting on a Peer Review activity, users now have the ability to enter separate peer review comments for each checklist item, in addition to the current checklist confirmation dropdown and checklist comments sections.
3. New Feature - Bulk Create
Enate now supports the creation of Cases and Tickets in bulk via the uploading of data from Excel sheets. This section describes how to use the new feature.
Both Tickets and Cases can be bulk uploaded. In order to do so you need to populate a standard excel file with all the relevant information under each header column, then upload it into Enate to auto-create work items. After uploading the excel file but before generating the new work items, items that will be created are displayed on-screen along with validation, allowing you to fix data before uploading. Records are created one by one and then create them in the displayed order.
3.1 Bulk Create Templates
Below are the Bulk Create Sample Files with Examples for Tickets and Cases.
Data entered, e.g. Customer names, etc., must match the values in the system otherwise validation errors will be displayed.
3.2 Using Bulk Create in Work Manager
A. Who can access this feature?
Any work manager user who has access to ‘Create Work item’ will be able to use the bulk upload feature when this feature is enabled.
B. Getting Started
To access the Bulk Create option, simply click on the link in the ‘Create New Work Item’ dropdown.
This will bring up the Bulk Create screen in a new tab. From this screen, you can create new Tickets and Cases in bulk by uploading data from excel sheets.
C. Overview of Steps
The basic steps you will need to run through are as follows:
1. Select an xlsx file (correctly formatted) to upload.
2. From the dropdown, choose which kind of Case or Ticket you wish these items to be launched as.
3. Upload the file.
4. Review the on-screen validation information of your file info.
5. Hit ‘Create’. The system will start creating your Cases/tickets, updating the display to show the Reference numbers.
3.3 How to create multiple Cases
In order to upload Case data, you will require an excel file (xlsx) correctly formatted with the required Columns for Case creation (note, this is slightly different to the Column structure required for bulk creation of Tickets).
The basic rules for this file are as follows:
1. The file format should be .xlsx.
2. Only 1 workbook can be used at a time.
3. There are eight mandatory fields that must be filled in in order to create a Case. These are:
a. Customer
b. Contract
c. Service
d. Case – the name of the Case Process instance you wish to create into.
e. Title – This will be the title for the individual Case work item.
f. Primary Contact (name or email)
g. Subject (name or email)
h. CC (name or email), if any.
i. Requester (name or email)
Each of these (apart from CC) must match with a valid equivalent in Enate, otherwise, that row will fail validation.
4. You can also pass bespoke field data into the Cases as they are being created. To do this, add a column name that precisely matches the data field name in Enate.
5. If any of these bespoke fields are marked as mandatory in your Case process configuration, you MUST supply a value in this field’s column for every row in the upload file (otherwise that row will fail validation and a Case will not be created for it).
Once you are happy with the data in your upload file, select it from the ‘…’ in the File control, and select which type of Case process you intend to bulk create these items into. Select the Type of Case or Ticket and click on the ‘Upload’ button.
Click Upload – this will upload your information on-screen for validation, but will not yet create your Cases. The system will display and validate the data from the upload file. Any validation errors will be displayed in-line for each row, along with a ‘warning’ status marker.
Enate validates the file and allows users to bulk create work items by clicking the ‘Create items’ link.
*Any validation errors will be displayed on the screen and needs to resolve before proceeding further.
Once work items are created in Enate, corresponding reference numbers are displayed on the screen, updated in real-time as each row is processed.
3.4 Validation
Depending upon the different values and different configuration there are a set of defined validations listed or highlighted with a background colour.
1. If the input values are wrong across the columns the validations are listed at the bottom of the grid. Example: If a field column is referenced in the upload file which does not exist in the system, the message will show at the foot of the grid, e.g. “No field to link Column ‘countback days’ too.
2. If the input values are wrong for an individual row, the validations are highlighted with a background colour i.e. Red colour.
The potential errors which can be displayed can be seen in the attached excel file.
3.5 Supported Fields
Bulk create supports below a list of custom field type-
1. CheckBox
2. Date Only
3. Date and Time
4. Decimal Number
5. Email Address
6. List
7. Long Text
8. Multiple level list
9. Short Text
10. Whole Number
Other than custom fields bulk create supports below system properties -
1. Override Due Date
2. Override Due Date set.
3.6 Unsupported Fields
Bulk upload does not support below custom field type-
1. Tables
2. Entity Relationship
There are few other system properties which cannot be added in bulk upload are below-
1. Keep with me
2. Keep Action with me
3. Defects
4. Files
Across the top of the Grid, the system will also display information about the number of work items being created, split across the current status.
Total – No of items contained in the upload file
Created – No of packets created successfully (this will be zero before you start to create).
issues – No of packets with validation issue – this can increase with final validation check made during Case / Ticket creation.
Not Started – No of items remaining to be processed from the file.
Additionally for each line, you will see:
Status - Current state of case item i.e. created, error
Reference - Reference of Case once it has been created successfully.
If you have any validation issues at this point, you can still proceed with the creation of the valid Case items in your upload file. The system will skip over the invalid rows and confirm the creation of the valid ones.
Alternatively, you can fix the validation issues in your upload file before proceeding. Click on “change” at the top of the page to upload the corrected file before proceeding.
A. Creating Cases
When you are ready to go, click ‘Create Items’. The system will start to create the Case items, updating the grid with progress in real-time and giving you confirmation Reference numbers.
During creation, one final validation check is made: the system will validate that no other Case exists in the system with the same Title. If the Title uniqueness check is failed, the system will show a validation error and skip over this row.
You can adjust the data in the underlying file to fix the validation errors, and click the ‘Change file’ link to upload the adjusted file.
Assuming you have not replicated Case Titles (assuming ‘Unique Title’ is set), the valid cases will be created & on-screen confirmation will be displayed, along with Reference number for each item:
Any items which failed validation will not be created (i.e. will be skipped over), but all other valid rows will be created, i.e. you do not have to have a 100% valid file to carry out a bulk upload.
3.7 How to Create multiple Tickets
Please follow the same steps as above, using the Ticket-specific file structure. Note that for Ticket creation you must also provide valid Ticket Category information as part of the upload file.
3.8 Multilingual Support in Bulk Create
The bulk create is supported in user’s preferred languages i.e. Portuguese, Spanish and bulk create excel file should be in the same language as logged-on user’s preferred languages. For example, of Spanish user like to upload a file then excel should be in Spanish and values should match with the values that are configured in Enate Builder under localisations tab.
All the data that are filled in the Bulk Create template should be as same as the values that are configured in the Enate builder under the localisation tab.
EX: If the fields like Primary contact, Subject, CC, Requester have translation values in the localisation tab like Contacto Primario, Tema, CC, Solicitante in the localisation tab then we need to configure the same values in the template.
3.9 Unique Title Setting
A further setting which can be used as part of the upload is the ‘Unique Title’ option at the top right of the screen. Switching this option on will ensure that any work item which is due to have the same title as another item in the upload file will fail validation.
Leave the setting off to allow for work items with duplicate titles to be created.
4. Email related changes
There are multiple changes in v2019.3 relating to enhanced email configuration.
4.1 Important Email Marker
Until now users have been able to see that an outgoing email is marked as Important, but have been unable to see the equivalent for Incoming mails. Users can now also view the ‘Important’ marker for incoming emails.
4.2 Blocked Auto response & Exclusion Email Addresses – Available to all users
Work Manager users are now able to easily see & maintain the list of email addresses to be blocked. Find the link in the navigation dropdown in Work Manager.
You can add, edit and delete email addresses to be blocked.
Two options are available:
• Do Not Send Acknowledgement Email – The system will allow tickets to be created for emails arriving from these addresses, but will not send any auto-response emails out to the address.
• Auto Reject as Spam – The system will not create tickets from emails arriving from this address.
4.3 Superscript and Subscript Formatting when Composing Emails
As part of the options for richer text formatting when composing emails as part of Tickets, Cases & Actions, you can now use the options for inserting subscript and superscript.
5. Builder Changes
This section details the v2019.3 changes which can be found in the Builder section of Enate.
5.1 Master Data access
The system now allows for a more granular granting of access levels to people who have access to Builder. These can all be found in the ‘See More’ section of the Edit User popup in Builder.
The new breakout is:
• Can Access Builder: Allows access to Builder, with the following levels of configuration available:
Add/Edit Language translation
Add/Edit Contract
Add/Edit Service
Add/Edit Case/ticket into a service
Add/Edit Local checklist
Add/Edit Customer
Add/Edit Fixed Frequency Schedule
Add/Edit Schedule records
Set Live and retire
• Can Edit Shared Configuration: You will need this level of access if you also wish to modify core settings / shared data which can be used in multiple places. This will allow access to the follows levels of configuration:
Add/Edit Service Line
Add/Edit Case/Ticket Archetype
Add/Edit Action type in the global menu
Add/Edit/Clone of flavours i.e. Due date, allocation, Action general, Ticket follow up
Add/Edit Ticket Category Global List
Add/edit Global Checklist
Add/Edit Service provider
Add/Edit System Setting
Add/Edit Calendar
Add/Edit custom data and fields
Add/Edit Email settings* (*new in 2019.3)
Add/Edit Schedule Structure
• Can Access User Management: This allows access specifically to the User Management & RPA integration section.
5.2 New Email Configuration in Builder
IMPORTANT NOTE: As part of the upgrade process to v2019.3, ALL Email Input Channels (now called Email Connectors) will be switched off, to allow for manual verification that the migration of these has worked as desired. They can all be viewed in a single place, and manually switched back on, once checking has verified they are correct.
As of v2019.3, a number of changes have been made regarding confirmation of the email server/input channel setting. To help support this, a new section has been added to Builder:
The following changes have been made:
• Terminology change: We will no longer refer to ‘email input channels’, instead we will now use ‘Email Connectors’
• Configuration of this has now moved from the old Client Applications (Configuration Manager) to this new section in Builder.
• The previous approach of:
o Creating Input Channels on a specific master process in Configuration Manager, then
o Linking up those email addresses to specific Ticket instance configuration in Builder (e.g. specifying the incoming email address against a ticket category within the Ticket configuration itself).
Has now been changed to the following, more decoupled, approach.
Two sets of configuration are now carried out in Builder, split into to parts of this email configuration section:
• Email Connectors – Create your email connectors here (similar creating old email input channels, but not yet linked to a specific process).
• Email Routing – where to route incoming emails, i.e. Referencing the email addresses in the Connectors you have created, you can specify which Tickets or Cases should brand new emails into a certain inbox start.
By doing this you can set up and maintain how your Tickets and Cases run in conjunction with email servers, without having to modify the actual Ticket and Case processes all the time.
All configuration will be migrated over from the ‘In-ticket’ configuration to this new location as part of the upgrade.
A. Email Connectors - Detail
To add a new email connector click on the ‘Add Email Connector’ link at the top of the page. This will bring up the details page to configure & test the connection.
The attributes to configure are:
Testing the Connection
Once you have configured the required information you can test the connection via the ‘Open Connection Test’ button.
Default Email Connector for Outgoing emails
Please note, the system by default has a standard outgoing email Connector call ‘SMTP Default Gateway’. You must fill in email configuration into this location – it is required for standard system activities e.g. User Welcome emails etc.
This information was previously defined in Enate Manager but has now been ported to Builder.
B. Email Routing - Detail
Once you have some email connectors defined, you can reference them in email routing to specify where emails coming into each mailbox should be routed by Enate (i.e. which work items it should start).
The attributes to configure are:
Configuration options removed/relocated as a result of this.
As mentioned above, the creation of the dedicated email configuration setting in Builder means the removal of the Inbound email configuration from the Ticket Categories configuration screen. The following sections have been removed.
5.3 Microsoft Office 365 Email Integration with Enate via Graph API model
As of v2019.3, you can now connect to office365 email boxes and pull emails into Enate without needing to use POP3 or IMAP protocols.
A. Configuration Office 365 Graph Integration
To configure the integration between Enate and Office 365, each unique Enate instance must be registered with the Microsoft Identity Platform in the Azure AD of the Office 365 tenant to which you need to establish connectivity.
To create the “App Registration” please follow the guide from Microsoft at
When configuring the Enate App Registration the supported account types option should be chosen based on the mailboxes you wish to access. No redirect URI is required.
Once the App Registration is complete you must add credentials and set up permissions.
To add the required permissions follow the guide at The only required API permission is Application permission of Microsoft Graph\Mail.ReadWrite. It is important to select “Application permission” and not “Delegated permission”. Be sure to grant admin consent for permission within the Azure AD tenant.
Finally to restrict the App Registration to only accessing certain mailboxes (strongly recommended) follow the Microsoft guide at
After Azure AD has been configured to grant access login to Enate Builder as a user with the “Can Edit Shared Configuration” permission. Click the settings cog in the top right and open the “Office 365 Integration” pane and enter the details from your Azure AD App Registration. The Tenant ID (aka Directory or Domain) and Application ID is shown on the Overview pane of the Azure AD App Registration; the client secret or certificate (and private key password) are supplied by you to both Azure AD and Enate.
B. Generating a Certificate
As part of this setup, an Office365 Certificate would need to be generated - Generating a certificate is an activity for your Office365 Administrator to undertake and is done completely independent of Enate. For your reference, we have provided below a SAMPLE of the kind of PowerShell script that can be used to generate such a certificate. It will save the Certificate with the private key (for Enate) to a PFX file and without the private key (for Azure):
$pw = Read-Host -Prompt "Please enter a password for the Private Key" -AsSecureString
$name = Read-Host -Prompt "Please enter a name for the Certificate"
Write-Host "Creating Certifcate $Certname" -ForegroundColor Green
$Cert = New-SelfSignedCertificate -certstorelocation cert:\CurrentUser\my -Subject "CN=$name" -KeyExportPolicy Exportable -KeySpec Signature
$desktopPath = [Environment]::GetFolderPath("Desktop")
Write-Host "Exporting Certificate with Private Key to $desktopPath\$name.pfx" -ForegroundColor Green
Export-PfxCertificate -cert $Cert -FilePath $desktopPath\$name.pfx -Password $pw
Write-Host "Exporting Certificate with Public Key only to $desktopPath\$name.cer" -ForegroundColor Green
Export-Certificate -cert $Cert -FilePath $desktopPath\$name.cer
5.4 Starting a Case from Enate Workflow
It is now possible to configure a Case to start automatically from within a running Case flow. This is done while configuring a Case by adding a ‘Start New Case’ type of Action into the flow.
When an action of this type is added to the flow, an additional tab displays for ‘Start Case’. This will allow you to select the desired case, and whether you wish to launch as a Sub-Case or not.
5.5 Custom Data into Subject Line of Emails in Builder
Until now it has not been possible to place dynamic text references into Email subject definition as part of the case flow configuration. As of v2019.3, it is now possible to add references to field values & some system properties when defining Email Subjects.
Note: in order to reference a specific field in the email subject, you will have to add the desired field onto a custom card which you will need to link to the same action. Fields are not shared across all actions in that case.
The above example is shown for an Action, but the same feature is also available for Cases and for Tickets.
5.6 Miscellaneous changes
Peer Review Icon in Builder
If you need to verify whether an action is a ‘manual’ or a ‘manual with peer review’, mouse over the action icon and the action type will display.
Grouping of Cases in a Service Line
When working with a very large number of different Case & Ticket types, moving around the Service Matrix can become harder work. In order to combat this you can now create higher-level Groups into which you can nest multiple Cases / Tickets. You can then collapse the group, taking up far less space on-screen when you are not working with the items inside it.
Migrated from old config, you will not see any difference – you will need to open the ‘process template’ popup, create new groups. A default “Ungrouped” value has been created, but you can add your own.
This can help reduce the potential number of different service lines which you might have had to create otherwise.
Builder Grids upgraded
The grids in Builder have now been upgraded to the latest agGrid, bringing increased stability and performance, in line with the Work Manager grids.
6. Robotics Changes
6.1 New dedicated RPA Integration section in Builder
A new dedicated RPA section is available in the Builder toolbar:
6.2 Support for MULTIPLE Orchestration Connections
Within this section, you can now configure multiple Orchestration platforms which your Enate instance can be synchronised with.
You can create and edit multiple connections.
The popups are dynamically created according to the RPA Technology selected. As of now, only UiPath Orchestrator is available, however, the equivalent for Blue Prism and Automation Anywhere will arrive in future versions of the product.
Information you can enter here for UiPath Orchestrator:
Furthermore, you can run a live connection test (which will store information in the Connection Log tab of the popup).
6.3 New Activities for Packets using Token Approach
As an initial step towards moving to a purely Token-based approach for authentication between Enate & UiPath, we now have a new ‘Authenticate’ activity which can be used to generate a token for ongoing authentication throughout a process.
The main change is:
• Instead of requesting ‘username and password’ for each individual activity, processes should now use the ‘Authenticate’ activity at the very start of the process, which will return a token which can then be used for all subsequent activity.
• For the moment Enate will continue to support both username & password approach but will focus on using this new Authentication approach. If an Authtoken is present it will use this over the username/password. The username & password attributes have been removed from the main activity GUI, but can still be accessed via the activity properties screen. Over time, the support for the username/password approach will be deprecated and eventually removed in a future release.
6.4 Blue Prism - Support Proxy Settings on each Action
Each Blue Prism activity which connects to Enate has now been given the following three new properties:
• ProxyAddress
• ProxyUsername
• ProxyPassword
Using these attributes, you can now connect a Blue Prism environment to Enate via a Proxy, something which was not previously supported.
7. Data Warehouse / Reporting changes
7.1 Allow to access Enate reporting DB by Odata API
As of v2019.3, access to the information available in the underlying Enate reporting via the Odata API is now supported. This will allow people to access this information without having to go via SQL directly.
7.2 Additional User Data added to Data Warehouse
Additional data has been added to the tblUsers table in the data warehouse, allowing for richer user-driven reporting. The fields which have been added are as follows:
• Timezone
• Email Address
• Retired marker (whether the user has been retired from the system).
• User type
• Preferred Date/Time
• Time
• Language
7.3 Tableau reporting data incorporating permission data from Enate
Runtime permission data is now available in the Data Warehouse. With this information, it will now be possible to build bespoke reports which can incorporate e.g. ‘siloing
This will now allow the creation of dashboards that could incorporate some form of siloing of information.
7.4 Multilingual Data in Warehouse
Enate has added the multilingual data already available for operational users in Work manager to the Data Warehouse – The localised names of objects for Work Manager can now be referenced to produce localised reports.