Bulk Create Work Items
Last updated
Last updated
The Bulk Create feature lets you create large numbers of Cases and/or Tickets via the uploading of data from Excel spreadsheets.
You can find a link to the Bulk Create page in the ‘Bulk Create’ link in the ‘Create New Work Item’ dropdown.
This will bring up the Bulk Create screen in a new tab. From this screen select whether you want to bulk create Cases or Tickets. You can then download the relevant Excel template, populate it, then upload it to the page - making sure to fill in any mandatory fields beforehand.
You can download a template of the excel file. The excel templates available will conform to whichever language you currently have set in your Enate user preferences.
Once you have added the data into the excel file, save and close it, then on the Bulk Create screen click to select the file.
You can then choose if you want to allow work items with duplicate titles to be created by using the ‘Unique Title’ option. Leaving this option off allows work items with duplicate titles to be created. 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.
Once you are happy, click on the ‘Upload’ button. This will upload your information about the Cases or Tickets from your file on-screen.
You will see the following information:
Total – the total number of items contained in the uploaded file that will be created
Created – the number of items that have been created successfully (this will be zero before you start to create)
Issues – the number of items with validation issues (these need to be fixed before the items can be successfully created)
Not Started – the number of items that are waiting to be created
Additionally, in the grid you will see that a 'Status' and 'Reference' column have been added - these will be filled in by the system when the items get created.
All you need to for now is to click ‘Create Items’ and the system will start creating your Cases/Tickets. The information displayed will update to show the number of items that have been successfully create and the reference numbers of the work items created.
It should be noted that excel uploads of up to 2000 rows are supported in bulk create. Sheets with more rows than this can lead to potential errors.
If you are using version 2022.5 or above of Enate, please use the in-product templates from the bulk create page. If you are using version 2022.4 or below of Enate, please use the templates below
You can download the excel file templates to bulk create Tickets from the following links:
You can download the excel file templates to bulk create Cases from the following links:
The mandatory fields which must be filled in order to create a Case are:
Customer
Contract
Service
Case - the process name
Title - the title for the individual Case work item.
Note that the Primary Contact and Requester fields are only mandatory for a Case when the 'Make Contacts Mandatory' option is set to 'on' for the Case type you are bulk creating in the Service Lines screen in Builder. If you do want to fill these fields in, make sure to adhere to contact record requirements.
The mandatory fields which must be filled in order to create a Ticket are:
Customer
Contract
Service
Ticket - the process name
Title - the title for the individual Ticket
Ticket Description
Ticket Category Level 1
Ticket Category Level 2
Ticket Category Level 3
Primary contact - the main contact you are dealing with for this query. See section about contact record requirements.
Requester - the contact that raised the initial request. See section about contact record requirements.
Note that all data entered must match existing values in the system, otherwise validation errors will be displayed.
Any contact records used in a bulk create file i.e. Primary Contact, Requester, Subject and CC contacts must adhere to the following rules:
the email address of the contact must be used
the contact must already exist in the system
the contact must be scoped to the same customer that the Case/Ticket will be created under
Optional fields that can be filled in for both Tickets and Cases are:
Subject - the contact the work item is about. See section about contact record requirements.
CC email address(es) - any further contacts which can be copied on any correspondence. See section about contact record requirements. Also note that when adding two or more CC email addresses, please make sure to separate the addresses with a semi colon (;) with no spaces either side e.g. user.one@example.net;user.two@example.net.
Override Due Date - enter the new due date. See date formatting section.
Do Not Send Automated Emails To Contacts - whether or not you want to send system-automated emails, such as request acknowledgement emails, to the contacts of the work item. Enter 'True' or 'False', this also applies for languages other than English.
Please be aware that any dates entered must have the following formatting:
DD-MM-YYYY HH:MM
Note that hours and minutes entered can either be in the 24 hour system format i.e. 23:00 or in the 12 hour system format with an AM/PM after it i.e. 11:00 AM.
Valid date format examples:
25-05-2022 23:25
25-05-2022 11:25 PM
If you choose not to enter hours or minutes, the system will set a default time of 00:00.
You can also pass custom data fields into the Cases/Tickets as they are being created. To do this, add a column name which precisely matches the data field name in Enate. 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).
Bulk create supports below list of custom field type:
Check Box
Date Only - see date formatting section.
Date and Time - see date formatting section.
Decimal Number
Email Address
Hyperlink - note that hyperlinks with customised display text are not supported i.e. the text entered in a hyperlink field must be the entire URL of the hyperlink e.g. https://www.enate.io/ and NOT Enate Website
List
Long Text
Multiple level list
Short Text
Whole Number
Bulk create does not support below custom field type:
Tables
Entity Relationship
Additionally, the following system property fields are not supported when bulk creating work:
Keep with me
Keep Action with me
Defects
Files
If you do have any validation errors, these will be highlighted in red and a ‘warning’ status icon will be displayed. If the input values are wrong throughout an entire column, validation errors will be displayed at the bottom of the grid e.g. if a field column is referenced in the upload file which does not exist in the system. If the input values are wrong for an individual row, a ‘warning’ status icon will be displayed at the start of the row and the individual validation errors will be highlighted in red. You will then need to modify the file, click to 'change file' and select to upload your updated file.
You can still proceed with creation of the valid Case items in your upload file. The system will skip over the invalid rows and confirm creation of the valid ones, but the invalid items will need to be resolved before they can be created. You can do this by modifying the file and then clicking to 'change file' and select to upload your updated file.
Click here to see the full list of potential validation errors for Bulk Create:
Potential Validation Errors for Bulk Creation of Work ItemsBulk Create is also supported in all of the languages that Enate offers: French, German, Spanish, Portuguese Brazilian, Romanian, Polish, Hungarian and Russian.
Note: the bulk create template uploaded should be in the same language as the logged-in user’s preferred language. For example, if a Spanish user wants to upload a bulk create template, then the template they upload should be in Spanish.
Additionally, the column header values in the bulk create template should match the values that are configured in Enate Builder in the Localisations page. If the translations for fields like Primary contact, Requester, CC, Subject or any Custom Data Fields have been modified in the Localisations page, then the column headings in the bulk create template need to match these values.
