Who is this article for?

Users who want to learn more about the 23.3 activity management enhancements.

CAPA Escalation is for Corporate Level.

This article details the release notes for Activity Management version 23.3. Discover enhanced features and refinements aimed at improving activity tracking and simplifying management processes, promising an elevated and more efficient experience within activity management.

1. CAPA Escalation Set up at the Corporate Level
   1. Configuration Details
   2. Enhanced System
   3. Escalation Sample Use Cases
2. Task Management Multi-location Assignment Improvements
   1. Configuration Details
   2. Enhanced System
3. Custom Date Range Filter Value in the Action Items Field
   1. Configuration Details
   2. Enhanced System
4. Further Reading

1. CAPA Escalation Set up at the Corporate Level

Currently, there is no option available to set a company-wide Corrective and Preventive Action (CAPA) escalation process. The goal of this enhancement is to establish a company-wide CAPA escalation process, aiming to maintain uniformity in escalations and ensure a transparent and effective CAPA escalation procedure.

1.1 Configuration Details

• Configurable: Yes

Email Escalation For No Of Days (Alerts):

• Public/Private: Public
• Default: 90 Days

Email Escalation For Reminder Start Before (Reminder):

• Public/Private: Public
• Default: 180 Days

Check User Scope For Common Escalation:

• Public/Private: Public
• Default: Yes

1.2 Enhanced System

The enhanced system has the following new features:

• Set CAPA escalations at the corporate level.
• Define escalations based on reminder or alert.
• Establish escalations based on module(s), individual, or multiple modules.
• Configure escalations for the owner(s), supervisor(s), or supervisor's supervisor.
• Configure escalations for a particular or multiple groups.
• Assign escalations for specific users.
• Extend escalations for external users not part of the application or organisation.
• Implement summary emails based on the recipients, instead of individual emails.
• Configure the number of days for due CAPA notification.

Example: The organisation has due CAPAs for more than 90 days, but it wants to send the notification only for CAPAs due in 30 days.

• Configure the number of days for overdue CAPA notification.

Example: The organisation has overdue CAPAs for more than 90 days, but it wants to send the notification only for CAPAs overdue for 30 days.

1.3 Escalation Sample Use Cases

Example: Use case of a corporate-level escalation:

• The organisation wants to send a reminder to the CAPA owner before five days of the due date.
• The organisation wants to send a reminder to the CAPA owner's supervisor before three days of the due date.
• The organisation wants to send a reminder to the CAPA owner's supervisor's supervisor and senior management group on the due date.

To achieve the above use cases, three escalation setups can be set, as below:

1. A reminder escalation set with Type as Reminder, First Reminder Date as five days, Modules as required, Notify Owner as Yes.
2. A reminder escalation set with Type as Reminder, First Reminder Date as three days, Modules as required, Notify Supervisor as Yes.
3. A reminder escalation set with Type as Reminder, First Reminder Date as zero days, Modules as required, Notify Supervisor's Supervisor as Yes, Notify Group as required.

The same can be done for Alerts, as per the business need.

Note: Make use of the configuration for the number of days the email engine will consider for due and overdue notifications. This will reduce the risk of email flooding, if the customer has more due or overdue CAPAs.

2. Task Management Multi-location Assignment Improvements

The current system allows the creation of a task with Draft status for all the selected locations, requiring individual approval for each location. Additionally, it does not provide the capability to select owners or groups based on the locations chosen when creating the task. The purpose of this enhancement is to restrict the creation of tasks for all selected locations to the Enabled status and to enable users to select owners and groups based on the chosen locations, streamlining the task creation process.

2.1 Configuration Details

• Configurable: No
• Title: NA
• Public/Private: NA
• Default: NA

2.2 Enhanced System

The enhanced system has the following new features:

• Reordered the Add to Other Location(s) option before the Assigned To field.
• Presents owner and group options based on the selected task location.

• Includes location information in the group picklist to prevent duplicate name ambiguity.
• Prompts a message for automatic status change to Enabled upon selecting Add to Other Location(s).

• Prevents status change to Draft when selecting Add to Other Location(s).

3. Custom Date Range Filter Value in the Action Items Field

In the current system, users do not have the option to select a filter with a custom range of dates. The purpose of this enhancement is to enable users to view data based on a custom range of dates, providing greater flexibility in data analysis.

3.1 Configuration Details

• Configurable: No
• Title: NA
• Public/Private: NA
• Default: NA

3.2 Enhanced System

The enhanced system has the following new features:

• Added option to select a custom date range.
• Option to select the future date using the custom date range.

Below is an image of the new custom date range filters:

4. Further Reading

• 23.3 Insight Release Notes
• 23.3 Performance Management Release Notes
• 23.3 Risk Assessment Release Notes
• 23.3 Occupational Health Release Notes
• 23.3 Mobile Pro Release Notes
• 23.3 Industrial Hygiene Release Notes
• 23.3 Foundation & Framework Release Notes
• 23.3 Audit Management Release Notes
• 23.3 App Builder Release Notes
• 23.3 LMS Release Notes
• 23.3 IMS Release Notes