Creating New Case Types in a Service Line
Creating a new type of Case
You are able to create new types of Cases within a Service Line itself by clicking on the '+' icon next to the search bar and selecting 'Case'.
When creating a new type of Case, you can enter the following information:
Attribute | Description |
Name | The name of the new type of Case |
Description | The description of the new type of Case |
Process Groups | Defining a Process group helps you sort your Cases on the Service Matrix Screen. See here for more information. |
Make Contacts Mandatory | This controls whether Users need to enter a Primary Contact and a Requester when filling in details for a Case. It is unticked by default, making the addition of Contact information not mandatory. In order to make contact information mandatory for this type of Case, just tick this box. Additionally, ticking the 'make Contacts Mandatory' setting makes it mandatory to include a contact when launching a Sub Case from an existing Case in Work Manager. |
Initial Estimated Effort Per Record | Established the estimated time it will take a Work Manager user to complete this Case. |
Steps | Globally agreed steps a Case will run through every time that Case type is run. For all customers which use this Case type, these high level steps that run for each Case are the same, although the Actions that run within the steps them might differ. |
Enable Record Count | Enables Work Manager users to use the Record Count for this Case. |
Record Count Description | This only appears if Enabled Record Count has been switched on. You can add description text to a record count to describe to your Service Agents how they should use record count for in that particular process, e.g. Payslip Count. The description will show next to the record count setting in Work Manager at runtime. |
Configuring Steps for a Case Type
You can add, edit and delete the steps of a Case type from the Service Lines page. You can easily reorder the steps by dragging and dropping them. The Milestone % is optional, it denotes the progress reached when this step is completed and it displays in the Case form status tracker control.
When you delete a step, any Actions that were underneath that step will now display as ad hoc Actions. When a step is reordered, the Actions underneath that step will move with the step.
Effect on Live Case Processes
If you make changes to the steps of a Case type, live versions of Case processes of that Case type will not be affected. They will run as previously configured and the step changes won't apply until a new version of the Case process with the updated steps has been set live.
Updating a Case Process to Match Updated Steps
You will be notified in the Case process screen if its steps are out of date i.e. if changes have been made at a Case type-level when you are in edit mode.
![](https://docs.enate.net/~gitbook/image?url=https%3A%2F%2Fgblobscdn.gitbook.com%2Fassets%252F-MR4uErt41EMkGUOTvyd%252F-MlAYBHCIyem9--x7OhD%252F-MlA_w_Hv9DAgltkZ8Zi%252Fimage.png%3Falt%3Dmedia%26token%3D57e73b77-674d-4d4d-9062-1a30e5762b9e&width=768&dpr=4&quality=100&sign=2fa4f0ef&sv=1)
You can click on the Refresh Steps icon in the header of the Case screen to refresh the steps to the latest version.
![](https://docs.enate.net/~gitbook/image?url=https%3A%2F%2Fgblobscdn.gitbook.com%2Fassets%252F-MR4uErt41EMkGUOTvyd%252F-MlAYBHCIyem9--x7OhD%252F-MlAaiUSA6ZWR_smVfa-%252Fimage.png%3Falt%3Dmedia%26token%3Da587ebdb-742e-42c3-870a-f2a2a8fc5c1f&width=768&dpr=4&quality=100&sign=e165a3ed&sv=1)
![](https://docs.enate.net/~gitbook/image?url=https%3A%2F%2Fgblobscdn.gitbook.com%2Fassets%252F-MR4uErt41EMkGUOTvyd%252F-MlAYBHCIyem9--x7OhD%252F-MlAa20ycLr8EMMsTVKR%252Fimage.png%3Falt%3Dmedia%26token%3Dd0361287-8f8c-4d8f-baea-b06b0bc9fc1b&width=768&dpr=4&quality=100&sign=5e15b005&sv=1)
When you click to confirm, you will be shown which changes have been made:
![](https://docs.enate.net/~gitbook/image?url=https%3A%2F%2Fgblobscdn.gitbook.com%2Fassets%252F-MR4uErt41EMkGUOTvyd%252F-MlAYBHCIyem9--x7OhD%252F-MlAaJmQCO2R254_RP6j%252Fimage.png%3Falt%3Dmedia%26token%3D7bfb79ee-5cd2-419f-8bfe-e5f042c2cb34&width=768&dpr=4&quality=100&sign=81031088&sv=1)
Click OK to update the steps to match the steps configured at a Case-type level; new steps will be added to the Case process, steps in the Case process will be renamed, steps in the Case process will be moved along with the Actions underneath them and steps will be deleted and their Actions will become ad hoc Actions.
Effect on Cloning Case Processes
You can clone any Case process which is live under the same service line and all data such as Actions etc. will be cloned, except for schedules.
If the Case you are cloning has the same Case type, then the step names and Actions will all be copied across.
If the Case you are cloning has a different Case type, then the step names will not be copied across, instead they will appear like this:
![](https://docs.enate.net/~gitbook/image?url=https%3A%2F%2Fgblobscdn.gitbook.com%2Fassets%252F-MR4uErt41EMkGUOTvyd%252F-MlEjd0oGS8Ah2HjoPEH%252F-MlEqG6XQkq9p69bmFPr%252Fimage.png%3Falt%3Dmedia%26token%3D0e253ab4-07b8-4667-ae5a-adb6f4bee262&width=768&dpr=4&quality=100&sign=9fec5d74&sv=1)
Actions will be cloned across in their original positions i.e. Actions under the first step of the process being cloned will be the Actions under the first step of the Case process they have been cloned to. If there are more steps in the source process being cloned than in the Case it is being cloned to, the Actions under the "extra" step will become ad hoc Actions.
To update the steps in the Case to the latest version of its own Case type, click to refresh the steps in edit mode.
![](https://docs.enate.net/~gitbook/image?url=https%3A%2F%2Fgblobscdn.gitbook.com%2Fassets%252F-MR4uErt41EMkGUOTvyd%252F-MlEjd0oGS8Ah2HjoPEH%252F-MlEq78g7XO22ae2MpW0%252Fimage.png%3Falt%3Dmedia%26token%3D51a86bc3-a074-47c8-b6cd-a145eec53e18&width=768&dpr=4&quality=100&sign=4d6f8db2&sv=1)
This will update the steps to the latest version in the Case type. If a step has been removed, any Actions that were underneath that step will now display as ad hoc Actions.
![](https://docs.enate.net/~gitbook/image?url=https%3A%2F%2Fgblobscdn.gitbook.com%2Fassets%252F-MR4uErt41EMkGUOTvyd%252F-MlEjd0oGS8Ah2HjoPEH%252F-MlEqUHTu1Xfr_OUxLJM%252Fimage.png%3Falt%3Dmedia%26token%3D133ea3b7-1743-4f50-866b-942c3800be06&width=768&dpr=4&quality=100&sign=8992373a&sv=1)
Subsequent Editing of a Case Type
To edit a Case type’s settings, click on the Case in the Service Lines Screen and edit the information in the right hand side of the screen. Click to save these changes.
Note: these settings are not versioned i.e. when changes are made, they affect all new and running Work Items.
You are also able to see the activity history of your work items , by clicking on the Show Activity button. You can see when the work item was created and by who, as well as if any edits have been made to the work item, when they were made, as well as by who.
You are also able to clone a Case type by clicking on the Clone button in the edit screen. This will clone all of the Case type's settings and data apart from its name. You are able to make changes to any of the settings and data once the Case type has been cloned.
Last updated