Addressed an issue with project locking to prevent errors when multiple lock processes attempt to run simultaneously. The system now ensures only one project lock can occur at a time, improving stability.

When a user updates a task that has a predecessor with lag, and that already has an existing Sync Queue record, the user needs to be able to update the existing Sync Queue record even if they do not own it.

To allow for this, the following Inspire Planner Standard permission sets have been modified to grant "Modify All" permissions to the Sync Queue object.

• Inspire Planner Standard User - v1.12 Permissions
• Inspire Planner Standard User - Agile Project Management
• Inspire Planner - Lite User
• Inspire Planner Standard User - Customer Community Plus

This update improves the handling of Parent Task Rollups within the Project Task Trigger. To prevent double execution of rollup logic, the system will now ensure that this logic runs only once per transaction, while allowing other trigger functions to proceed as expected.

With this update, we’ve optimized the code to prevent duplicate execution, improving overall system performance and ensuring accurate project task management. This helps to streamline task creation and update processes while maintaining correct task hierarchy and duration calculations.

A new batch job has been added to the Inspire Planner Nightly Processes Job that will check and correct Project Task Ready-to-Start values. It will also check "sysCreatedByBatchProcess" for open projects and set it to "FALSE" if it is "TRUE."

This is to ensure that Ready-to-Start is correctly updated for project tasks, particularly in cases where failures may result from customer customizations, Apex code, manual data updates, or permission issues that conflict with out-of-the-box functionality.

For existing open projects, the Nightly Job will check "sysCreatedByBatchProcess" for open projects and set it to "FALSE" if it is "TRUE".

The Inspire Planner System Jobs should already be scheduled in your Salesforce org. If not, please refer to How to Schedule Inspire Planner System Jobs for instructions.

The "Predecessor Violation Script" sets "Violation Detected" to TRUE for project tasks that had been rescheduled to start earlier than its predecessor. This is to provide users with an easy way of identifying which project tasks need to be corrected before converting the project from Gantt Visualforce to Gantt LWC. Users then have the option of either adding a "must start on" constraint or applying a negative lag to prevent these tasks from rescheduling according to their predecessor relationship when the project is converted.

There was an issue previously identified where when a "must start on" constraint was applied to the task, the "Predecessor Violation Script" was not setting "Violation Detected" back to "FALSE". With this update, the "Predecessor Violation Script" now correctly sets "Violation Detected" back to FALSE for project tasks where a negative lag or "must start on" constraint has been applied.

Salesforce Production Environment:

If you have already installed the Gantt LWC Conversion Toolkit in your Salesforce Production environment, you will need to update it using this link

Salesforce Sandbox Environment:

If you have already installed the Gantt LWC Conversion Toolkit in sandbox environment, you will need to update it using

When re-assigning tasks via drag and drop in the Resource Scheduler Component, the following now work correctly:

• Salesforce Task assigned to former resource is now deleted unless there are related time entries. A new Salesforce Task is then created for the new resource. This is aligned with what happens when a project task is re-assigned in the Project Gantt.
   
• The task bars now remain in both Project Gantt and Scheduler Gantt after task re-assignment
   
• Resource avatars now correctly display after task re-assignment
   
• The Resource Scheduler task bar colors are now consistent with the Project Gantt task bar colours.