Overview
CAMMS is pleased to announce the January Feature Release for cammsincident.
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.
Improvements on how list items are configured and managed
Here's a quick recap on what was released on the last sprint;
> The Object Configuration area accessed via cammsrisk > Framework >Incident Settings was improved to provide easy updates to field configurations such as;
A new pop up (appearing when clicked on the field name) which allows the user to update all field properties
An easy option of changing/editing field names and display texts within the pop up itself eliminating the need to use the display text menu area
In this sprint, we have improved further on the above, to allow the same list item to be used multiple times within the same object, as well as within the same workflow. This will be an improvement around the previous limitation where the same list item with the same name could not be used for two fields within the same workflow.
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’ setting
When 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.
The system will then check for all fields either marked as;
Required in Save
Required in Submit from cammsincident>Incident Settings>Object configurations> field configurations area and flag the user notifying that they are unable to close the incident prior to entering those missing fields
Attempting to save/submit without the validation being satisfied will trigger the validation message shown below for users;
Image 1 (b): Waring message upon attempting to save/submit and incident closure without filling the required fields
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.
.pdf, .doc, .docx, .ppt, .pptx, .xls .xlsx, .xlsm, .epub, .odt, .odp, .ods, .txt, .msg, .csv, .mpp, .vsd, .vsdx, .eml, .pub, .ecd, .tr5, .qbr, .rar, .zip, .7z, .mp4, .mov, .avi, .wav, .mp3, .mpeg, .gif, .jpg, .jpeg, .png, .gif, .bmp
NOTE: There could be a vulnerability/ threat in uploading and downloading ‘.rar, .zip, .7z’ file extensions, although these are allowed. Caution is advised when using these file types.
