...
This includes several new features and enhancements to improve your user experience within the system. The release set for 24th January 2020 and will include the following features.
1. Improvements on how list items are configured and managed
Here's a quick recap on what was released on the last sprint;
...
| Info |
|---|
Note: Please note that this will only function as above for the field type: List items (custom single select and custom multi select) and the previous restriction between common field names will still be there for fields of other types. |
2. Ability to restrict users from closing an incident if all mandatory information are not filled
Incident administrators now have the ability to restrict users from closing an incident unless all mandatory fields of the incident are filled.
A new configuration has been introduced to the standard ‘CloseObject’ in incident accessed via cammsincident >Incident Settings > Object configurations > Close Object titled ‘Restrict Incident Closure Until All Required Fields Are Entered’ which will be unticked by default.
...
Image 1 (a): ‘Restrict Incident Closure Until All Required Fields Are Entered’ settingWhen this is opted and saved, the above business logic will apply across the workflow and when any user with edit permissions to the close object is attempting to either save/submit an incident which will change the ‘CloseIncidentStatus’ from previous (this can be any status except close) to ‘Close’ status.
...
Attempting to save/submit without the validation being satisfied will trigger the validation message shown below for users;
...
| Info |
|---|
Note: This will work for both simple and detailed warning messages which can be configured from cammsincident>Incident Settings>Miscellaneous settings area. |
3. Allowed file type extensions from file uploaders within cammsincident
File type extensions that users can upload within cammsincident are limited to the below file extensions in order to enhance system security measures.
...