See below for what's included with Inspire Planner's June 2025 - Maintenance 1 (1.376.3).
Released To:
All Environments: August 4, 2025, at 10 PM ET
Available In:
All Environments: August 5, 2025
Please note:
Content in this release notes are subject to change until August 4, 2025.
Previously, clicking the Kanban icon in the Gantt Visualforce page caused the project to fail to load. This issue has now been resolved.
Previously, entering a unique Project Key and clicking Save would result in no action, while leaving the Project Key blank would trigger a validation error. This behavior has now been corrected.
The logic for handling the Project Key has been updated—if you provide a unique Project Key when creating a project from a template, it will now save as expected.
Previously, when logging time on behalf of another user, the time entry did not roll up to the timesheet of the actual time entry owner. This has now been resolved—time entries logged on behalf of other users will correctly appear in their timesheets.
An issue preventing users from setting “None” as the default value in a custom picklist within Time Tracker has been resolved. You can now successfully set “None” as the default option for custom picklist fields.
This section contains fixes we've made specific to the Gantt LWC.
We’ve resolved an issue where the calendar modal would get stuck or become unresponsive on smaller screens. The modal now adjusts properly to different screen sizes and remains fully usable.
The issue preventing users from using the Delete key when editing tasks in the Project Schedule has been resolved. Users can now use the Delete key as expected when updating task information.
We’ve resolved an issue where tasks with a custom Completed status were being rescheduled when their predecessor tasks were moved. Tasks marked as completed will now remain fixed, even if their predecessors are rescheduled.
Previously, after clicking the Export button and downloading the PDF, users were redirected to a services URL (https://services.inspireplanner.com:8091/...) where a “File not found” message was displayed. Users then had to manually click the browser’s back button to return to the Project.
This behavior has been corrected. After the PDF is downloaded, users will now remain on the Project page without being redirected.
An issue has been fixed where dragging and dropping a task with dependencies would update the Successor field in the UI, but not on the actual Project Task record. The Successor field now updates correctly in both the UI and the underlying record.
We’ve resolved an issue where saving would result in an endless loading spinner if there was a cyclical dependency in your data. Now, if a cyclical dependency is detected, you’ll see an error message explaining the issue and highlighting the specific rows involved so you can make corrections and try again.
We’ve fixed an issue in the Gantt LWC where creating a child task under an existing task did not automatically update the parent task’s type. Previously, if a task was originally created and saved as a Task (non-parent), and you later indented another task beneath it, the parent task’s type remained as Task instead of updating to Group. This has now been resolved—when a child task is added, the parent task will correctly update to a Group type.
Resolved an issue where clicking the time tracking icon in the Project Gantt would trigger an “Apex heap size too large: 6026016” error when a user had a large number of tasks assigned within the same time frame.
Customers have requested a clearer way to distinguish between Experience Cloud users and internal Salesforce users.
To support this, we've updated the Assigned To dialogue to explicitly display whether a user is External or Internal.
Updated logic for user type display:
If the User License contains “Community”, display External User
Otherwise, display Internal User
We’ve resolved an issue that caused an error to appear when the portable Gantt LWC was added to the Case object’s Lightning record page.
This section contains fixes we've made specific to the Resouce LWC (BETA).
We’ve fixed an issue with Rate Cards where the Effective End Date was not cleared automatically when the Active checkbox was re-checked. Now, when you mark a Rate Card as Active again, the Effective End Date field is automatically cleared as expected.