Release Notes 1.5.8
Conformatix® v1.5.8
(other Release notes.)
Release date: July 15, 2022
|
Some of the fixes and additional functionalities are related to conformatix risk module and/or multi-site module. If you do not use these modules yet, please consider them and contact us. |
Clients might have perspectives we have not thought of in our planned future releases. Therefor we would like to encourage you to communicate your future wishes with us.
Your requests will be taken into consideration and if they are found usefull for the majority of the clients, we will schedule them for a future release.
New functionalities
Multi Site Module
We are very proud and delighted to announce this new module. With this module we are introducing the possibility to implement a multi site environment.
The multi site environment is usefull for companies with multiple locations, sites, countries and or brands but also for companies that have a multi site certification.
With the Muli Site module, companies can add relations between for example their HQ, entities, branches, locations, brands and / or countries.
This enables you to set up the compliance structure as it seem fit for your organization such as a multi-site certification structure for example. Companies can now rule by exception as processes derived from the global scope based on standards or legislation can be structured based on localized needs.
The Multi-site module is a paid module just like the Risk module and its license must be purchased before you can see and use its options.
See below a simplified diagram example how this new multi-site module can be used.
Naturally the structure stretches beyond this diagram and into the core structure of the application as well.
1.) Administration > Locations
The new locations can be found under the administration menu. Locations can be added to entities, and entities can be added to your company. The goal is to have a process-entity relation where it becomes possible to assign the audit start planning and frequencies per location. Locations can be anything you like as it is a free textfield and has a description field to identify what purpose the location has towards your need.
The current location field at the user section, will be replaced with the new "Locations" dropdown. Current user location values are automatically added to yout company as part of the migration to remain backwards compatibility. We do reccomend to review the locations after the update to ensure they are still logical to your organisation.
Remark: Once a location is used as a relation, it can not be deleted without removing the relations in the parts where it is used (Entities, processes, issues, audits etc.).
2.) Administration > Dropdowns > Stakeholder Categories
With the option to create entities relation(s) to your company, we introduced a flag to a stakeholder category to identify which entities can be used as such relation.
The "Company Entity" switch in a stakeholder category is that flag to identify the category to be used at entities.
Once an entity has the a stakeholder category with this flag enabled, it is populated in the entity dropdown list on company level. (Like subsidaries/branches/countries etc. see 4)
3.) Administration > Entities
Within an entity, you are now able to select and remove one or more locations from the locations list created at Administration > Locations
Ensure to set the "stakeholder category" to the category you created and flagged as "Company Entity" if the entity should be used at company level to create the relation.
4.) Administration > Company
A switch has been added at the main company to create company-entity relation(s). When enabled your company has the option to select one or more entities. The entities can be managed in Administration > Entities. You can add entities to your company here that are "part" of the company group for example. Only those entities with the correct stakeholder category will be listed in the multiselect dropdown.
5.) Processes
By default a process audit frequency and start date is set globally. The Multi-Site module enables you to set audit frequency per location.
When an entity has locations and the "Set audit frequency per location" switch is enabled, on can add the frequency and plan start date to each location.
You must then mandatory set the frequency and audit start date per location for that entity.
In case you do not enable the switch, the audit freqency is global for that proces and the locations are ignored.
6.) Audit > Planning
In case you have a process where audit frequency and start date are set per location(s), they will be reflected in the audit planning. Each location will get a line per process.
In case you have a process where an entity is selected but the audit frequency is not set to the location(s), the audit planning is set as before on process level.
7.) Register an audit
With the new module, it is now possible to register an audit also on location level.
When you register an audit from the process it will take the entity and locations when present into the audit-registration window. In the case an entity has multiple locations linked, you can select other locations.
8.) Register an issue
As with the registration of an audit, creating an issue no will let you also choose an entity. If an entity has one or more locatiuons, you must select a location.
In the event locations are changed for the entity selected in an existing issue which has a location present, it will display that existing location as it creates a snapshot of that location bound to the issue.
9.) Location in screens and reports
The locations will show when the multi-site module is active in several locations and grids:
- Process (if entity is selected and audit frequency on locations is enabled)
- Processes > Audit history
- Audit > History > Audit items
- Issues > Manage
- Insights > Issues
- Insights > Audit report (also in the exported files)
- Administration > Locations
- Administration > Entity > Edit & view
Improvements
Administration > Company
We changed the company configuration page for editing the login settings. The old button to edit these settings is removed and changed to a tab just like security.
Compliance & Dashboard
The routine to update the compliance screen as well as the one on the dashboard has been updated. The new routine will load from the db all the dependencies and check for changes. Only then it will update so it becomes a lot faster and no longer uses a lot of memory each time it is updated.
Risks > Treatment planning > Assign Owner
An email to the assignee is now send out as well as a notification inside the app (Bell top right corner)
Bug fixes
- We fixed an issue where the user logout would land on a wrong page;
- We fixed an issue where the default reset-email template was used;
- We fixed a issue involving the search;
- We fixed some translations;
- We fixed some inconsitent display of date formats;
- We fixed some issues regarding sorting, filters and checkboxes;
- We fixed an issue in the notification area. An updated link to a changed/removed item now lands on the dashboard;
- We fixed an issue that a logout could cause the user to land on a 404 page;
- We fixed an issue in Insights - Compliance overview;
- We fixed an issue in the audit planning, unpublished processes should not generate an audit planning.