New Features and Enhancements in PSA Summer 2024

The following new features have been introduced in the Summer 2024 release of PSA.

If you are upgrading from a previous version, see Upgrading to PSA Summer 2024. This provides a summary of the items that have been added for each feature and details of any required upgrade steps.

Improved Scheduling in Work Planners and Resource Requests

Retaining Schedules When Unholding or Unassigning Resources

We have added the ability to retain the preferred schedule that you have created on a resource request when unholding or unassigning a resource. This increases flexibility when managing schedules, enabling you to use recurring schedules for assignments in the Work Planner, and for resource requests on the Resource Request page.

To support this feature, we have added the following fields to the Assignment Settings custom setting:

  • Retain Schedule On Unhold
  • Retain Schedule On Unassign

For more information, see Assignment Settings

Creating Schedules for Unheld Resource Requests

We have added the ability to define a default schedule, and to select or create a scheduling strategy when creating unheld resource requests in projects, opportunities, and the Work Planner. This enables you to find a resource to fit that pattern rather than fitting the work around resource availability. This is useful for opportunity forecasting, as it will identify and forecast resource requests that are unheld with schedules.

To support this feature, we have added:

  • The Schedule Selection section to the Create Resource Request window, which you open from a project, opportunity, or the Work Planner.
  • The Scheduling Strategy column to the Resource Requests grid in the following windows:
    • Add Resource Requests from Template, from an opportunity or project.
    • Add Records from Template, from a project.
    • Create Project, from an opportunity.
  • The Clone the Preferred Schedule checkbox to the Clone Resource Request page, which you open from the Work Planner.
  • The Default Scheduling Strategy Unheld RRs field to the Assignment Settings custom setting.
  • The Scheduling Strategy option to the APIs for the global classes CreateProjectFromTemplateService and AddFromProjectTemplateService.

For more information, see:

Improved Filtering in the Work Planner

To improve filtering in the Work Planner for a better user experience, we have:

  • We have added the following component properties to allow you to set the default start date and end date in the filters panel of the Work Planner.
    • Start Date Offset (In Days)
    • End Date Offset (In Days)
  • We have excluded the Start Date and End Date fields from the saved filters, as these might not be relevant in the future. You can contact your administrator to set up the default date range of your choice.
  • We have made the filtered data for the region, practice, and group of the resource associated with your Salesforce user visible in the Work Planner by default.

  • We have changed the default view of the Work Planner to the Allocation view and reordered the view list. The Allocation view is more frequently used so now it is listed first, followed by the Scheduler view.

For more information, see

Resourcing Tab Enhancements

When staffing a resource request on its record page with intelligent staffing enabled, the Rank cell is now blank if a suggested, interested, pinned, held, or assigned resource does not match the applied filters. These resources are still displayed at the top of the list. For more information, see Rank.

We have enhanced the Attributes view on resource requests by adding a Matched Skills column, enabling you to easily identify resources with skills specified in the resource filter. This column is visible if specific skills are requested.

The Matched Skills column displays the number of specified essential skills a resource has.

The following color coding is used in the Matched Skills column:

  • Green indicates all essential skills match the filter
  • Orange indicates one or more essential skills match the filter
  • Grey indicates no essential skills match the filter

For more information, see Managing Resource Requests.

Administrators now have the option to display or hide the Worked With Customer filter on the Resource Request record page. With this feature, you can filter resources with assignments for a particular customer. By default this field is displayed. For more information, see Resourcing Lightning Component Properties.

Shortlisting on a Resource Request

We have introduced shortlisting to improve collaborative decision-making in the process of identifying the most suitable resource to be assigned to a resource request. For example, a resource manager can compile a list of shortlisted resources to highlight them as suitable candidates for the request. They might want to share the new shortlist with a project manager, who can add information for each resource in the Manage Shortlist window, then return the shortlist to the resource manager to make the final decision on the ideal resource to hold or assign.

With the shortlisting feature, you can:

  • Add multiple resources to a new or existing shortlist.
  • Select Display Only Shortlisted Resources in the filters panel to return only shortlisted, pinned, held, assigned, and suggested resources, regardless of the filter criteria.
  • Review the shortlisted candidates in the Manage Shortlist window by updating their status and adding accompanying notes.
  • Import custom fields that allow you to provide further supporting information within the Manage Shortlist window.
  • Duplicate a shortlist and its related resource records to link to another resource request that might have similar requirements.

For more information, see Managing Resource Requests.

Enhancements to Manage Resource Requests

We have implemented the following features and enhancements in the Manage Resource Requests window that opens from the project and opportunity pages.

We have renamed the window and navigation link on the opportunity and project record pages from Update Resource Requests to Manage Resource Requests.

Assign Multiple Held Resource Requests

Previously, you could only assign a single held resource request, but now, as a project manager, you can assign multiple held resource requests using the new Assign Held button in the Manage Resource Requests window.

The Manage Resource Requests window also enables you to view assigned and unassigned resource requests on the Assigned and Unassigned tabs, which are only visible on the project record page. For more information, see Assigning Multiple Held Resources Requests.

You can also customize the Manage Resource Requests table columns using the MassReassignResourceRequestColumns field set in the Resource Request field sets. This enables you to manage the Manage Resource Requests table columns and update fields that appear on an opportunity or project record page. For more information, see Customizing Columns for Manage Resource Requests.

We have also added a Filter panel to the Manage Resource Requests window, enabling you to filter resource requests by resource role and status from the project record page. You can use the filters to refine the results displayed. For more information, see Filtering Resource Requests.

Unhold and Unassign Resource Requests in Bulk via APIs

We have added the following APIs to enable you to unhold and unassign multiple resource requests.

  • ResourceAssignmentService.unholdResourceRequests
  • ResourceAssignmentService.unassignResourceRequests

Using these APIs, you can unhold up to 3500 resource requests and unassign up to 2500 resource requests based on a schedule.

In these APIs, the Retain Schedule on Unhold and Retain Schedule on Unassign fields in the Assignment custom setting determine how PSA processes the work.

  • If the Retain Schedule on Unhold and Retain Schedule on Unassign fields are selected, the schedule is retained when unholding or unassigning.
  • If the Retain Schedule on Unhold and Retain Schedule on Unassign fields are deselected, the schedule is deleted.

Additionally, we have updated the existing ResourceAssignmentService.assignResourceRequests API to assign multiple resource requests and added the UseDefaultStrategy field, which uses the scheduling strategy from the Default Scheduling Strategy field on the Assignment Settings custom setting.

Note: An error is shown if resource requests are unheld and you attempt to unassign them using the ResourceAssignmentService.unassignResourceRequests API.

For more information, see the Certinia Technical Pack.

Save Schedule Data via APIs

We have added the SaveScheduleData method in the ScheduleService API, which allows you to save schedule data. This method handles different types of calculations on the Schedule and Schedule Exception objects. This API is used when saving large volumes of Schedule data to avoid potential issues caused by a series of saves that can temporarily invalidate the data before it reaches a valid state.

For more information, see the Certinia Technical Pack.

Utilization Engine Performance Improvements

We have improved the Utilization Engine performance by calculating resource availability in parallel with the Queueable framework, which results in quicker resource availability calculations.

Actuals Performance Improvements

The following are the new features and improvements that have been implemented in PSA Actuals in Summer 2024.

Actuals Calculation for Reorganized Projects

We have also introduced a queueable job that runs in the background when a project hierarchy is changed. This functionality is only applicable in Continuous mode. This job creates transaction deltas to be processed by ProjectActualsCalculateDeltaContinuous job so that it updates the old and the new parent project's actuals. Also, the Actuals :Need Recalc checkbox in the project page is selected or deselected automatically when the transaction delta creation process succeeds or fails, respectively.

For more information, see:

Prevent Actuals Double Counting

We have improved actuals such that double counting does not happen due to unprocessed transaction deltas. We have implemented this by introducing the Resume Processing button in the Project Actuals Recalculation and Resource Actuals Recalculation wizard flows on the Visualforce page. This ensures the unprocessed transaction deltas are processed before the actuals recalculation is triggered for these flows. It has been implemented for both Immediate mode and Scheduled mode.

For more information, see:

Receiving Asynchronous Process Error Notification Emails

We have added a new Async Job Notification Settings custom setting to enable receipt of the asynchronous process error notifications through email. This helps you to be notified when an asynchronous process fails. You can now specify an email address or a group email address in the Actuals Error Notification Email field added in this custom setting.

The recipient receives the error notification emails for the following jobs:

  • Actuals Calculate Delta Continuous
  • Actuals Calculate Delta Batch
  • Scheduled Project Actuals Recalculation

For more information, see Async Job Notification Settings.

Enhancements to the Project Task Board

We have made the following enhancements to the Project Task Board:

  • To quickly display the Resources tab in the Record Details panel and view details of resources assigned to a project task, you must now double-click a resource's avatar or initials, instead of using a single click.
  • To make the behavior of the Project Task Board match the behavior of Gantt on a project record, we have changed the default date range displayed in the Resource Schedule section on the Resources tab in the Record Details panel:
    • From a workspace, previously the date range matched the one used in the filter panel, which was one month either side of today's date. Now, the date range is the current week beginning from the start day on the resource's work calendar.
    • From a project record or an Experience Cloud site:
      • The date range matches the project record date range, provided there is both a start and end date present.
      • If either the start date or end date is missing, previously the date range was one month either side of today's date. Now, the date range is the current week beginning from the start day on the resource's work calendar.
  • We have added a new Task Involvement filter, which replaces the My Tasks option in the filter panel. We have also introduced additional Milestones, Projects (visible only in the Project Management Workspace), Resource, Resource Roles, Task Involvement, and Task Timeline filter options for users to filter with increased granularity.

For more information, see:

Manage Resources on Project Tasks

The Project Task Board now includes the Manage Resources functionality, which allows you to:

  • Manage multiple resources for a project task.
  • Assign resources that have already been assigned to the project. You cannot assign a new resource to the project from Project Task Board.
  • Delete resources from a project task assignment. You cannot delete project task assignments that have worked hours logged on the project task.

  • Adjust the hours assigned to a project task by specifying the time each resource spends on that specific project task. By updating the allocation hours, the allocation percentage adjusts automatically, showing how work is divided among the resources assigned to the task.

For more information, see:

Enhancements to Gantt on a Project Record

We have made the following enhancements to the Gantt chart on a project record:

  • Avatars or initials are displayed in the Assigned Resources column. These enable you to see at a glance who is assigned to a project task and you can hover over an avatar or initials to view further details in a tooltip. This is similar to how resource details are displayed on the Project Task Board.
  • You can search for a project task using the Search field we have added to the toolbar. When you start typing characters from anywhere in the project task name, PSA searches the tasks loaded into Gantt and narrows down the search results as you type.
  • The button has been replaced with the Record Details button on the Gantt toolbar. The Record Details panel now features the Task and Resources tabs, providing you with a comprehensive view of your project tasks and resources in one panel.
  • You can set the required field set for the Task tab in the Record Details panel using the new Task Details Custom Fields Field Set field in the Lightning App Builder for the Project Gantt component.

For more information, see:

Display Over Allocation Information in Gantt on a Project Record

The over allocation feature in Gantt on a project record enables you to see immediately when a project task contains over allocated resources and take action to reduce potential delivery risks on the project.

Notes:

To enable the over allocation feature, an administrator must select Show Over Allocation for the PSA Project Gantt component in the Lightning App Builder. Additional object, field, and Apex class permissions are required to enable over allocation information to be displayed in Gantt on a project record. For more information, see Upgrading to PSA Summer 2024.

To show and hide over allocation information in Gantt on a project record, click Over Allocation in the toolbar.

Over allocation is indicated in the following ways:

  • Days or date ranges when resources are over allocated are shaded in gray with a red outline on the Gantt timeline. If you hover over the header at the top of the shading, a tooltip lists the over allocated resources.
  • A Warning: over allocated resources icon is displayed at the start of a row containing a project task with resources assigned who are over allocated during that task. If you hover over the Warning: over allocated resources icon, a tooltip lists the over allocated resources.

For more information, see:

Visualizing Project Task Baseline and Actual Dates in Gantt on a Project Record

We have added the new Comparisons button in the Gantt toolbar that enables you to select either Baseline or Actual Dates, or both the options to compare their dates with that of each project task. The selected option is displayed as a bar below each project task. This helps you to analyze the progress of the project.

You can either show or hide Comparisons in the toolbar by using the Show Comparisons property in the Lightning App Builder.

For more information, see:

Full Screen Experience for Enhanced Usability

We have enhanced the usability of Project Gantt, Project Team Schedule, and Project Task Board by introducing the and buttons on each component. The button enables you to expand Project Gantt, Project Team Schedule, and Project Task Board into full view. The button enables you to contract them back to their original view.

For more information, see:

Project Source Tracking

Each time a project is created from a template or opportunity, a project source record is created automatically for the new project. Similarly, a project source record is also created whenever the following actions are performed in a project.

  • Add Assignments from Template
  • Add Milestones from Template
  • Add Project Tasks from Template
  • Add Records from Template
  • Add Resource Requests from Template

To support this feature, we have added the new Action and Status fields on the Project Source object. The Action field displays the type of action performed for which the project source record is created in the project and the Status field displays a message related to the number of records copied successfully or partially. The project source records track the information to analyze performance, and the use of templates to create or modify projects.

A source lookup in the record’s object is also created when a record, such as milestone, assignment, phase, location, methodology, risk, or resource request is copied from the template to the project. This field has the source record from which the record is copied to the project.

.For more information, see Tracking Project Source.

Project Monitor Rollup Asynchronous Process

Prior to this release, if there were less than 10000 assignments for a project, the Total Assigned Hours or Total Projected Revenue from Assignment fields in Project Monitor were updated synchronously whenever the Schedule or Bill Rate fields changed in an assignment, respectively.

We have added the Recalculate Project Monitor Fields field in the Assignment object to make the Project Monitor Rollup process asynchronous. This enables the project monitor fields rollup process to be scalable and more reliable.

For more information, see:

New ASM Triggers Configuration Group

We have added a new handlePracticeTrigger.SetPracticeChainAsync option in the ASM Triggers configuration group. This controls the trigger code that maintains practice hierarchies to run asynchronously.

For more information, see ASM Triggers.

Track Project Financials

You can gain insight into the financial impact of a project’s work as it happens by configuring PSA to track the consumption of a project’s cost and revenue budgets.

In PSA Spring 2024, only revenue and cost relating to timecards could be tracked. In Summer 2024, we have added support to track revenue and cost relating to milestones, expenses, and miscellaneous adjustments.

Once PSA is configured to track the consumption of budgets you can:

For more information about how PSA tracks the consumption of budgets, see the following section Track Consumption of Individual Budgets by All Business Records.

Track Consumption of Individual Budgets by All Business Records

You can track the consumption of individual budgets by the business records that are allocated to them. When milestones, timecards, expenses, and miscellaneous adjustments are completed and included in financials, the relevant value on each business record is allocated to a specified budget. PSA updates each affected budget to show the amount that has been consumed. This means you can always see how much of a budget has been consumed, and how much remains. You can also see a breakdown of the amount consumed by the different record types.

Tracking the consumption of individual budgets is done using budget allocations. Each budget allocation can link a customer purchase order budget, up to three internal budgets, a billable expenses budget and a non-billable expenses budget to business records. The different budgets are consumed as follows:

  • The budget identified in the Customer Purchase Order field can be consumed by milestones, timecards, and miscellaneous adjustments (depending on transaction category).

  • The budgets identified in the Internal Budget fields can be consumed by timecards, and miscellaneous adjustments (depending on transaction category).

  • The budgets identified in the Billable Expenses Budget and Non-Billable Expenses Budget fields can be consumed by expenses, and miscellaneous adjustments (depending on transaction category).

For more information and a precise list of which amounts on business records are allocated to which budget, see Track Consumption of Individual Budgets. For an introduction to the functionality provided by budget allocations, see Budgets .

Expenses Budgets

Billable and non-billable expenses budgets have been introduced to allow the consumption of expenses budgets to be tracked. They replace the need to specify a value in a budget's Expense Amount field.

You create expenses budgets in the usual way, setting the budget type to "Billable Expenses" or "Non-Billable Expenses" as appropriate. Enter the budget amount in the Amount field, and leave the Expense Amount field blank. The value entered in the Amount field will be included in the Expense Transaction in order to contribute to actuals.

For more information, see Budget Fields.

Automatic Linking of Budget Allocation to Business Records

When PSA is set up to track the consumption of individual budgets, you can manually assign a budget allocation to individual milestones, timecards, expenses, and miscellaneous adjustments by selecting it in their Budget Allocation field. Alternatively you can leave the field blank and PSA will automatically assign a budget allocation as follows when the business record is included in financials:

  • If no budget allocation is set on a milestone or miscellaneous adjustment, PSA assigns the project's default budget allocation.

  • If no budget allocation is set on a timecard or expense, PSA assigns the budget allocation on the related assignment (if available), or the budget allocation on the related milestone (if available), or the project's default budget allocation.

You specify which budget allocation is the default for a project by selecting the Default checkbox on the budget allocation's record page. A project can have only one default budget allocation.

For more information about defaulting the budget allocation on business records, see Automatic Assignment of Budget Allocation.

Billing Events with Customer References

When PSA is set up to track the consumption of individual budgets, the customer reference held on a billable budget is passed to the billing event items generated for business records allocated to that budget. Billing event items with the same customer reference are grouped into billing events. This means that when you release billing events to your finance system for invoicing, the customer reference on a billing event is available to be included on its corresponding invoice if the integration between PSA and your finance system is updated to support this.

Once a billing event has been released, the customer reference on the associated budget cannot be edited.

For more information, see Passing Customer References through to Billing Events.

Note:

When billing events have customer references, you can only combine billing events that have the same project, account, and customer reference. Billing events can be combined using the Billing Events Awaiting Release tab. For more information, see Combining Billing Events.

Apply Billing Cap to Individual Budgets

When PSA is set up to track the consumption of individual budgets, you can avoid over-billing individual budgets by applying a billing cap to them. To apply a billing cap to a budget, select Apply Billing Cap on the budget record page. PSA then prevents you from releasing billing events that will cause the budget amount to be exceeded.

You can optionally set a tolerance amount for individual customers. For example, if the budget amount is 15,000 USD and the customer's tolerance amount equates to 0.99 USD, PSA will allow you to release billing events up to the value of 15,000.99 USD but will prevent you from releasing billing events for 15,001 USD or greater.

For more information, see Applying a Billing Cap to Individual Budgets.

Notify Users When Consumption of a Budget Exceeds a Threshold

When PSA is set up to track the consumption of individual budgets, the project manager can be sent a Salesforce notification when a certain percentage of a budget has been consumed. This means that the project manager is kept informed about how much of the budget remains.

You can set two thresholds on a budget to trigger these notifications. For example, you might want notifications to be sent when 75% of the budget amount has been consumed, and when 100% of the budget amount has been consumed. If the budget amount is 12,000 USD, PSA will send notifications when the amount consumed reaches 9,000 USD and again when it reaches 12,000 USD.

If an alert recipient is specified on the project, the same notifications are also sent to that contact.

For more information, see Notifying Users When Consumption of a Budget Exceeds a Threshold.

Visibility of Project Budgets Consumption

When PSA is set up to track the consumption of individual budgets, you can view a summary of a project's budgets and the details of which business records have consumed an individual budget.

Project Budgets Component

We have added the Project Budgets grid to the Financials tab of the project record page. This grid provides an out-of-the-box view of the budgets related to a particular project and shows how the project is performing based on budgets.

You must be assigned the PSA - Manage Projects permission set to view this grid.

For more information, see Project Budgets Fields.

Budget Consumption Components

The budget record page now includes the following grids in the Consumption tab:

  • Time-Based Budget Consumption
  • Milestone-Based Budget Consumption
  • Miscellaneous Adjustments-Based Budget Consumption
  • Expense-Based Budget Consumption

These grids show the records that consume the budget without having to navigate away from the budget record. For more information, see:

Permission Set Updates for Project Assignments Breakdown Grid

Prior to this release, access to the Project Assignments Breakdown grid required the Certinia - PSA - Project Manager permission set group. Customers did not want to grant all the permissions included in this permission set group to users who only needed access to the grid.

Therefore, we have updated the required permissions in the PSA - Manage Projects permission set. In this release, users who are unable to view the grid can be assigned just the PSA - Manage Projects permission set instead of the permission set group to view the grid.

For the list of permissions required, see Permissions for the Project Assignments Breakdown Lightning Component.

Improvements to Compact Time Entry and Expense Entry

The following are the improvements that have been implemented in PSA Expense Entry in Summer 2024

Accessing Global Projects in the Expense Entry Lightning Web Component

We have updated the PSA - Enter Expenses Against Projects and Assignments permission set so that you can access the global projects in the Expense Entry Lightning web component. This permission set is updated to grant read permission to the following fields on the Group, Practice, and Region objects, respectively:

  • Group ID Chain
  • Practice ID Chain
  • Region ID Chain

Improvements to Time Entry

We have made the following enhancements to Compact Time Entry:

  • A Submit window has been added to Time Entry when submitting time using Start and End Times mode.

You can now view the timecards associated with your time entries when submitting or submitting all timecards.

For more information, see:

Enhanced and Improved Time Entry

In this release we have enhanced PSA's time management capabilities with the introduction of the new Timesheet Entry grid. With Timesheet Entry, you can enter more information directly on your timecards, as well as save and submit multiple timecards simultaneously. Additionally, you also ability to log hours against various projects and assignments. Plus, you can add daily notes with additional details like the location for off-site meetings, directly in the grid. This results in a clearer view and better control over time management.

You can also customize the grid as required by dragging the columns, changing the default columns displayed, and using the right-click actions.

The new Timesheet Entry is designed to save you time while entering time, creating a more streamlined process for time management. It is designed to handle larger volumes of timecards and improved the performance in terms of data load times additionally.

To support this enhancement, we have renamed Time Entry to PSA Compact Time Entry. This name is displayed in the Lightning App Builder when adding components to your pages, and helps to differentiate between the different time management components.

The following columns are displayed by default in the Timesheet Entry grid:

  • Project
  • Assignment
  • Monday
  • Tuesday
  • Wednesday
  • Thursday
  • Friday
  • Saturday
  • Sunday
  • Total Hours
  • Status
  • Notes

For more information, see:

Performance Improvement to Timecards

We have improved the performance of the timecard submission process by making parts of it optionally asynchronous. For this, we have added the following custom settings:

  • Enable the Timecard Async Submit custom setting field in the Timecard Entry UI Global custom setting to speed up the timecard submission process. We recommend enabling this custom setting only if you have a complex timecard approval process that takes a long time to run because when the setting is enabled, and the process fails, the notification is delayed due to the asynchronous process.
    • To manage the notification, we have added the Redirect Notification To Time Entry field in the Timecard Entry UI Global custom setting. If you select this field, clicking a notification from the bell icon redirects you to the Project Time Entry LWC UI page.
  • Enable the TC Transaction Platform Event custom setting field in the Advanced Settings to asynchronously create timecard transactions. Timecard transactions are used in the Actuals calculation process and have no impact on how Actuals are calculated.

For more information, see:

Improved User Experience for Managing Skills and Certifications

This feature enables resource managers, project managers, and line managers to make more informed decisions during staffing and resource selection. This provides them with the ability to easily assess and select the Skill, Certification, or Category record type they are rating, including non-Certinia record types.

We have:

  • Deprecated the existing Manage Skills button and page, opened from the resource request record.
  • Added a new Manage Skills button to the Actions tab on the resource request record.
  • Added the Record Type column to the Manage Skills and Edit Skill Filters windows.
  • Enhanced the display of skills by adding the record type to skills in the Skills and Certification search field.
  • Added the Show Manage Skills checkbox in the Lightning App Builder for the PSA Actions: Resource Request Details component.

For more information, see:

Mass Managing Skills and Certifications for Resource Requests

We have enhanced the Manage Resource Requests window. You can now use this feature to manage skills, certifications, and skill sets on multiple resource requests when working with projects and opportunities.

  • In the Manage Resource Requests window, the Manage Skills button is displayed. When you select multiple resource requests and click Manage Skills, the Manage Skills window opens. You can search for the skill or certification and skill set that you want to add, remove, or update for the selected resources requests together.
  • You can also edit and delete multiple resource requests in the Manage ‌Resource Requests window. Columns such as Resource Role are editable with picklist values.

For more information, see Mass Managing Resource Requests.

Estimates Versus Actuals Performance Improvements

We have improved Estimates Versus Actuals (EVAs) calculation when changes are made to timecards by incrementally adding timecards to the existing EVAs instead of doing a full EVA calculation. We have also made the EVA process more reliable by improving the existing asynchronous EVA calculation process.

When timecards are created, updated, deleted, or undeleted, the full EVA calculation is done asynchronously by default. You can now select whether you want the EVA calculation to be incremental or asynchronous by selecting the Calculate EVA Actuals Incrementally custom setting field in the Est Vs Actuals Settings.

  • If the Calculate EVA Actuals Incrementally custom setting field is deselected, the full EVA calculation is done.
  • You can also disable the EVA calculations using the RecalculateEstVsActuals Disabled custom setting field in the Triggers custom setting.

We have also added a new Enable EVA Process Notification custom setting field in the Est Vs Actuals Settings, which enables receiving of EVA job execution process notifications through a toast message.

Note: Ensure that the RecalculateEstVsActuals Disabled custom setting is deselected to receive EVA job execution process notifications.

For more information, see:

Geolocation Improvements

We have made the following improvements to the Geolocation feature:

  • Renamed the Crypto Key field to API Key. This field stores the API key used when making calls to Google Maps.
  • Added a layout for the External API Credential custom metadata type.
  • Deprecated the Encrypt field because it is no longer in use.
  • Enhanced logging and error handling. You can view error logs on the App Logs tab and async job process records on the Async Job Records tab.

For more information, see Setting Up Google API Keys.

Improved Performance in Services Revenue Forecasting

We have added several enhancements to Revenue Forecasting to make processing large volumes of data more efficient:

  • Revenue Forecasting now uses queueable Apex instead of batch Apex.
  • We have introduced a new system-only Revenue Forecast Staging object. Revenue forecast staging records store data temporarily while the forecast is being generated and the records are then deleted. These records do not require any user interaction.
  • We have added a new Maximum Concurrent Jobs field to the Revenue Forecast Setup object. This field enables you to control the maximum number of queueable Apex jobs for forecasting that can be run at the same time. You must enter a value based on the number of asynchronous Apex jobs you expect to be available when the forecast runs. Running more jobs at once means the overall process will finish more quickly, however, bear in mind that performance might vary at different times of day because the speed at which the jobs run depends on availability.

For more information, see:

Additional Recognition Method in Services Revenue Forecasting

An additional recognition method of Equal Split: Months/Actual Days in Part Periods is now available in Revenue Forecasting. It enables you to forecast revenue for partial periods more accurately when using Equal Split.

When you run a revenue forecast using this recognition method, revenue for the first and last part periods is calculated based on the number of days on the project or milestone in those periods, as a proportion of the total number of days on the project or milestone. For more information and an example showing how the calculation works, see Equal Split Recognition Method.

Deprecated Features and Functionality

In this release, we have deprecated the following features and functionality.

Generate an Invoice Directly from a Budget Record

The ability to generate an invoice directly from a budget record will be deprecated in a future release. The feature was intended to represent a pre-bill or deposit but its functionality is limited. Instead milestones or miscellaneous adjustments are typically used to represent deposits.

See Upgrading to PSA Summer 2024 for a list of fields that we recommend you do not use because they will be deprecated in a future release.

Replacement Manage Skills Button and Window

We have deprecated the existing Manage Skills button and window, opened from the resource request record quick actions. There is a new Manage Skills button on the Actions tab on the resource request record that opens an improved Manage Skills window. This improvement ensures that you can more easily access and manage skills and certifications, contributing to a more efficient resource management process.

Release Content

We want to help you find all of the information and resources that you need to use our products effectively.

In-App Guidance

Certinia in-app guidance uses Salesforce user engagement features to deliver Certinia content, such as tutorials and walkthroughs, directly from our products.

In this release, we've updated our in-app guidance. For more information, see PSA In-App Guidance.

Certinia Trailhead

If you want to learn more about the new features in this release, see the PS Cloud - Summer 2024 Release Highlights Certinia Trailhead module. This module will guide you through the new features in PS Cloud.

Fixes

Fixes are listed on the Known Issues page of the Certinia Community. You can access this page from the Community Support Hub. For a brief description of the issues that have been fixed in this version of PSA, see the relevant section of the Known Issues page.