Action Audit updates and changes

In response to a request from one of our clients to add a new feature to the software, we decided to introduce a significant change in user roles and permissions. This change allows adding the new feature without compromising the quality of conducted audits.

The new feature allows setting the Yes answer for all audit questions that have not yet been answered. This is a highly debatable option, as its misuse could lower audit quality. Therefore, we decided that the corresponding permission for this feature will not be associated with any role. Instead, we introduced the individual permissions functionality.

As part of this update, two roles that were somewhat unnaturally created during the software's development - each existing just to add a single permission - were removed. Now, there are three available individual permissions:

Filling in the remaining audit questions - a new permission that initiated this change. It allows selecting the answer Yes for all audit questions that have not yet been answered.

Assigning a person responsible for post-audit actions - a permission introduced to replace the Leading Auditor role.

Restricting the selection of individuals to team members only - a permission introduced to replace the Team Leader role.

A feature related to the previously described change, allowing users to select Yes (or another response ensuring 100% compliance) for all unanswered audit questions.

The LPA report now includes information on the number of audits marked as unexecuted. Additionally, in the XLSX version, both the total count and breakdown by specific reasons are provided.

In the submissions module, the list of Kaizen innovative ideas and potentially hazardous events now includes information on the reason for rejection, along with a filtering option.

A filter has been added to the Audit Results Report, allowing users to limit audit results to a selected layer.

A significant change has been introduced in the method of scheduling audits. Previously, Action Audit used a specific division of the year into weeks that did not reflect reality. The year was artificially divided into 48 weeks, 4 for each month: 1-7 days of the month, 8-14 days, 15-21 days, and 22 to the end of the month. Over time, as requirements became more complex, this approach caused more problems than benefits.

After the change, the year is divided into 52 weeks, and calendar weeks are now the primary reference for setting audit dates. However, to make schedule management as universal as possible, an additional unit of time - months - was introduced. The following scheduling frequencies are now available:

* Daily - in two variants: weekdays only and all days of the week,
* Weekly - every X weeks specifying the day of the week,
* Monthly - every X months specifying the day of the month.

Global parameters linked to the audit module can now be defined as related to all audit types or only one type. A similar function already exists within the incident module.

We have added another sign in method to the Web Platform. Following integration with Gmail, the time has come to implement signing using Microsoft Entra ID.

In addition to login, user provisioning (account creation managed with Microsoft Entra) has also been implemented. This feature is aimed at clients using the ENTERPRISE package and requires additional legal agreements and dedicated configuration.

With the introduction of authentication via Entra ID, some other processes related to gaining system access have also been simplified and streamlined.

Previously, on the new audit form, the Subject field was empty, and the auditor had to enter any text to proceed. The implemented change suggests a topic in the form of auditType + areaName + date, e.g., 5S Audit Line XYZ 2025-01-27.

The checklist listing now includes information that was previously not directly available. These are details about: 1) the grading scale, 2) the number of questions on the list, 3) the number of areas where the checklist is utilized.

Files attached to activities often contain critical information that, due to a lack of notifications, did not always reach the action plan owner. Therefore, email and push notifications about a file attached to an activity have been intorduced.

A completely new module has been implemented in the Pulse mobile app, designed for users with accounts in Action Audit or Action Plan as well as for non-logged-in users.

The Private Tasks functionality is a simplified task list designed to be convenient and quick to use while performing other activities, such as shopping, working in the office, or while commuting. Available features have been minimized, but as a result, Private Tasks have the following characteristics:

High usability and convenience - the most important operations are accessible within one or two gestures.

Full privacy - information about tasks remains only on your phone; we do not send them to the cloud or monitor them in any way.

Available to everyone - you do not need an account in Action Audit or Action Plan to use private tasks. A key note: Actions are also available to non-logged-in users, so we recommend caution when sharing your phone with others.