New Features and Enhancements in PSA Summer 2025

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

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

Configuring AI Resource Summaries

You can now configure the prompt used to generate resource summaries, by managing the parameters that determine the specific fields and related list records that are referenced by the summary. We have added the following parameters for the resource summary prompt:

  • Related Resource Request Fields, which enables you to select the fields and filter the records of the Resource Request related list that you want to include in the resource summary.
  • Related Skill or Certifications Ratings Fields, which enables you to select the fields and filter the records of the Skill or Certification Ratings related list that you want to include in the resource summary.
  • Related Resource Skill Request Fields to Prioritize, which enables you to select the fields and filter the records of the Resource Skill Request related list you want to be prioritized in the resource summary.

Prompt configurations are managed in the AI Prompt Configuration Builder. For more information, see Configuring the PSA Resource Summary Configuration.

Improved Performance When Searching for Resources

We have previously implemented resource availability filtering within the Utilization Engine record, utilizing hours and percentages. We have now enhanced this functionality to include work calendar hours, actual work hours, and excluded hours for resources on specified days. Additionally, we have introduced the Day 1-366 Details (Hours) fields to the Cumulative Availability object.

An Use Enhanced Availability Filtering field is added to the Utilization Settings custom setting. When the Use Enhanced Availability Filtering and Use SOQL Availability Filtering custom setting fields are selected, it enables faster availability searches and improves availability filtering, leading to quicker loading of the Resource Request page and faster resource matching.

For more information, see:

Enhancements to Resource Availability

We've added the Schedule Availability column to the Matched Resources grid in the Resourcing tab of resource requests, which takes resource schedules into account when calculating availability. Previously, resource availability was based entirely on the resource's work calendar hours for the duration of the resource request.

By considering each resource's individual schedule, resource managers can now determine if resources can be assigned to resource requests without overallocation. This helps in staffing projects precisely and evaluates resource capacity, leading to better staffing decisions.

To enable this, we've created the Monthly Availability dataset for Analytics, which stores the scheduling information for all resources in the correct format, enabling the processing of large volumes of resource scheduling data. Updates to resource schedules are pushed to the dataset every 30 minutes to optimize the accuracy of the data used to calculate resource availability.

We've also introduced the following new objects:

  • Availability Dataset Update Log, which ensures real-time schedule availability calculations
  • Monthly Availability, which pushes data to the dataset in Analytics, ensuring it is up to date

For more information, see:

Work Opportunities Hub: Apply Custom Fields to Resource Requests

To enable you to add more relevant information to potential resources for work opportunities on desktop and on the mobile app, we have added:

  • A component property in the Lightning App Builder to give you the ability to use select a field set to use custom fields on the desktop Work Opportunities Hub and the mobile Work Opportunities Hub app. This reduces the time that resources spend searching resource requests, and the time that resource managers spend identifying suitable candidates.
  • Clearer fields and icons that enable resources to find and understand the most relevant information. This helps them to decide which work opportunities interest them the most.
  • A new sort field and a standard Filters panel on the desktop component. These replace the existing sort field and filter function to enable you to find the information most relevant to you faster.

For more information, see:

Work Planner, Opportunity, and Project Pages: User Experience Changes

When you have expanded the details of resources in the work planners or on a resource request record, changed the data, and saved, the details now remain expanded.

We have added the ability to hide the scheduling section in the Create Resource Requests window in work planners and the Project and Opportunity record pages. This simplifies the process of creating resource requests by enabling administrators to set and maintain consistent scheduling. To support this, we have added the Hide Schedule Selection Section field in the Assignment Settings custom setting.

To increase the readability and usability of the Allocation view in the work planners, we have:

  • Highlighted cell values when editing cells in the grid.
  • Removed the highlighting for unsaved changes when you have selected a cell but not edited it.
  • Removed the shading and allocation icons from the top-level row of the Shortlists section.

We have added the Future Scheduled Hours field to the existing fields in the Assignment Progress section of the Record Details panel in work planners. This enables resource managers to have a more complete view of, and quickly assess, an assignment's progress.

For more information, see:

View and Edit Assignment and Resource Request Dates in Work Planner Allocation View

We have enhanced the ability to view and edit the start and end dates of assignments and resource requests in work planners.

Previously, you were only able to change the dates of assignments or resource requests from the Scheduler view. You can now view the start and end dates of assignments and resource requests directly via columns in the Allocation view. You can also update these dates by expanding the list of assignments and resource requests on a record and double-clicking a value to select a new date.

This makes the process of viewing and editing dates of assignments and resource requests more immediate.

We have added a Lightning App Builder component property, Schedule Used for Date Changes. This gives you control of the effects of changing the start and end dates on the duration and scheduled hours of an assignment or resource request.

For more information, see:

Enhanced Customization of Data Displayed in Work Planners

We have made it easier for you to customize the Work Planner page. In the Allocation view, you can now hide standard and custom columns. Previously, you could drag column headers to change their location, but only administrators could configure which columns were displayed. Now, you can also toggle between hiding or displaying specific columns on the Work Planner page. This provides you with more control over the information that you want to display in work planners.

We have also increased the maximum number of results that can be displayed in work planners. Previously, a maximum of 1000 assignments, held resource requests, and unheld resource requests were returned. This has now increased to a maximum of 2000 results returned each. This enables resource managers to view larger samples of data when planning project work.

For more information, see:

Enhanced Automated Staffing for Resource Requests

You can now enable auto-staffing for new resource requests that you create from projects and project tasks, and that you add from templates. You can also enable auto-staffing for existing resource requests from the resource request records. For this, we have added the Auto-Assign checkbox to the Resource Request object.

We have also added three list views on the Resource Requests page. These enable you to view the details of multiple resource requests, according to the outcome of the auto-staffing process. To accommodate this, we have added several fields to the Resource Request object.

Additionally, we have updated Resource Request Staffer to work in conjunction with auto-staffing. Resource requests set for auto-staffing are not displayed in Resource Request Staffer.

These enhancements enable you to automatically assign everyday work to resources that meet the work requirements and to follow a different process that requires more manual intervention for more complex work.

For more information, see:

Resource Request Staffer Enhancements

We have introduced the following enhancements to Resource Request Staffer.

Loading Bar

When matching resources to resource requests in Resource Request Staffer, a loading bar is now displayed which keeps you updated with the progress. You can still navigate away from the page and will receive a notification when the process is complete. If you navigate back to the page, the loading bar will display the current progress. This ensures you are informed about the process while maintaining the flexibility to perform other tasks. For more information, see Matching Resources in Resource Request Staffer.

Renamed Tabs

We have renamed the Unmatched tab to Open Requests and Matched tab to Match Results. The name of the grid on the Match Results tab has also been renamed to Resource Request Match Results. This is to better reflect the contents of the tab. The Match Results tab also now displays any issues that occurred during the matching process. For more information, see Resource Request Staffer Overview.

Improved Grid Functionality

The grid's toolbar now includes a Show Selected option, enabling you to display only selected resource requests. You can also group resource requests and select the group's checkbox to select all of the resource requests within the group. The maximum number of selected resource requests has increased to 2,000.

Additionally, you can also now reorder the resource requests in the Open Requests tab by dragging and dropping them. This enables you to customize the priority order of resource requests. The displayed order is used to determine the priority of the resource requests during the matching process. If the resource requests are grouped, you can re-order them within their group.

For more information, see:

Streamlined Record Deletion

To help manage the volume of records in your org, deleting a resource request now automatically deletes its associated resource skill requests. This improves the efficiency of Resource Request Staffer by ensuring that the matching process does not process stale resource skill requests.

Improved Matching

Expired skills or certifications are no longer considered during the match process. You can also now cancel a matching process, enabling you to stop resource matching and select different resource requests. For more information, see How Resources are Matched in Resource Request Staffer and Matching Resources in Resource Request Staffer.

Resource Request Match Quality

We have introduced the following features to assist with understanding the match quality of resource requests.

Resource Match Quality

You can now view a resource's match quality in the Resourcing tab of a resource request and in the Matched Resources tab on the Resource Request Staffer page. We have also added a badge in the Compare Resources window on the Resourcing tab.

The percentage is based on how well the resource matches the resource request details. The match quality also uses the match priority and field weightings defined in the Match Settings panel. This helps you quickly understand how well a resource matches the resource request criteria.

Note:

Match quality is not displayed for resources that were matched prior to upgrading to Summer 2025. To display the match quality, clear the matched resources and match resources to the resource requests again.

An administrator can turn this behavior off using the new Show Match Quality component property in the Lightning App Builder. For more information, see:

Match Indicators in Resource Request Staffer

On the Resource Request Staffer page, the grid in the Match Results tab now displays a visual indicator in some columns. If a matched resource matches the group, practice, region, or resource role on the resource request, the cell value is bolded and Match displays. This enables you to easily identify the match quality of the resource.

Minimum Skill Requirements for Resource Requests

An administrator can now define the minimum number of skills and certifications required when creating a resource request. This helps ensure that resource requests are staffed with resources who are best suited to the work.

For more information, see Resource Request Staffer Overview and Resource Request Settings.

Staffing Logs

We have created the Staffing Log object, which stores details about an auto-staffed resource and the search criteria used to identify the resource. For more information, see How Resources are Matched and Assigned in Auto-Staffing and Staffing Log Fields.

Resource Optimizer Enhancements

We have introduced the following enhancements in Resource Optimizer:

  • You can now click Show Selected in the grid's toolbar to display only selected resource requests.
  • You can now group resource requests and select the group's checkbox to select all of the resource requests within the group.
  • Expired skills or certifications are no longer considered during the matching process.

If a resource request doesn't matchFor more information, see Using Resource Optimizer.

Improved Filtering for Role-Based Work Planners

We have improved the ability to filter resources in Line Manager and Resource Work Planners. This helps in refining search results and aligns with the purpose of role-based planners, which is to display only relevant records.

Prior to this release, work planners displayed default filters, and you were able to add or remove resources that were not related to you. For example, line managers could filter resources not reporting to them. To fix this, we have added the Restrict Resource Filter Lightning App Builder property. By default, it is deselected and can be modified by your administrator.

When this property is selected:

  • Line managers can view both their records and the records of the resources who directly report to them.
  • Resources can only view their own records. The Filter by Resource section is hidden from the filters panel, as details of the Salesforce users are listed on the Record Details panel.

For more information, see:

Deactivation of the Project Team Schedule

We've deactivated the Project Team Schedule and it can't be used anymore. We no longer support this feature and it be removed in a future release. The retirement of this feature was announced in Winter 2025. To be able to view when resources assigned to a project are scheduled to work, work with your administrator to start using the Record Work Planner.

For more information, see Using Work Planners.

For more information about the deprecated elements, see Deprecated Elements.

Work Event Calendar: Enhanced Resource Visibility and Planning

Previously, the Work Event Calendar was only available on a project record page and displayed a single, combined calendar of work events for multiple resources. You can now add the Work Event Calendar to any record, app, or Home page. Record pages contain the Combined Calendar view and a new Resource Calendars view that displays work events on individual resource calendars. App and Home pages contain only the new Resource Calendars view. This provides increased visibility of resource availability to enable more efficient resource planning.

You benefit from instant availability checks that eliminate time wasted cross-referencing or using internal messages to solve resourcing problems. It also solves inefficient work scheduling by presenting availability visually, which enables faster decision-making and reduces conflicts.

To support this feature, we have:

  • Added another view to the component.
  • Added three component properties in the Lightning App Builder to control resource fields using a field set, and control the views.

For more information, see:

Project AI Summaries

Note:

This feature is part of the Certinia Early Adopter Program. This program is only available to a limited number of customers. For more information, contact your Customer Success Manager.

We have added Generative AI Project summaries. This enables you to leverage Generative AI to produce summaries of your projects. Project AI summaries provide at a glance information about your project, such as the stage, project manager, and accounts associated with your project. Providing only the relevant information reduces the time you spend manually evaluating your projects and provides a clear description of the project that other stakeholders can review.

Additionally, Project AI summaries display information such as the start and end dates, and the duration of your project.

Project AI summaries also include the following sections:

  • Financials
  • Risks
  • Staffing
  • Deliverables

You can also generate the following summaries from the project summary:

  • RAID (Risks, Actions, Assumptions, Issues, Dependencies, and Decisions) next steps
  • A client facing summary
  • An executive summary

Client facing summaries provide you with a project summary in a format suitable to copy and share with clients. This streamlines the process of providing clients with updates on ongoing projects.

Executive summaries provide you with a project summary in a format suitable to copy and share with key project stakeholders and executive leadership. This streamlines the process of providing updates on project progress.

To support this, Project AI summaries now provide Telemetry data. All users of Project AI summaries will require access to the TelemetryLoggerController Apex class to enable Telemetry when generating summaries.

You can also generate RAID next steps using the project summary actions. This produces next steps covering the actions, assumptions, dependencies and decisions contained in your RAID records.

From the RAID Next Steps window you can also create the following records:

  • Actions
  • Issues
  • Risks

We have also added Generative AI Project Task summaries. This enables you to leverage Generative AI to produce summaries of your project tasks. Project Task AI summaries provide a snapshot of your project, including an overview, tasks nearing completion, overdue tasks, and those requiring attention. The project task summary also provides next steps which covers actions to take on your project tasks. Providing only the relevant information reduces the time you spend manually evaluating your project tasks in Gantt and provides a clear description of project tasks that other stakeholders can review.

For more information, see:

Gantt on a Project Record: Add, Edit, and Delete Project Tasks

You can now add, edit, and delete project tasks. This functionality also supports rollup and work breakdown structure (WBS) calculations.

To ensure that you have the most relevant data in new project tasks, we have added default values for the following:

  • The project task start date relevant to the project status and the position of the task.
  • The work calendar.
  • The duration.

We have also ensured that project task start and end dates are recalculated when you make changes to the work calendars.

For more Information, see:

Gantt on a Project Record: Support for Roll-Ups to Summary Tasks

As part of our continuing improvements to Gantt on a project record, you can now use field sets to add cost-related fields, such as Estimated Hours and Estimated Cost. The read-only summary tasks are calculated when you update the project plan.

For more Information, see:

Gantt on a Project Record: Managing Project Task Assignments

On Gantt on a project record, you can now add, update, or delete resources assigned to project tasks. This enables you to build and manage your project plans directly on the project record, alongside other project information.

For more Information, see:

Gantt on a Project Record: Ensuring WBS Consistency

When you add, update, or delete project tasks on a project plan, work breakdown structure (WBS) numbers are always recalculated. This means that WBS numbers are correct wherever they are displayed, such as on a project task record, Gantt, and the Project Task Board.

For more Information, see Managing Project Tasks from Gantt on a Project Record

Gantt on a Project Record: Restricted Permissions Handling

We have added privacy for situations where users have only restricted view or edit permissions for specific project tasks and fields. New information banners also identify these situations for users.

For more Information, see Permissions for the Project Gantt Lightning Component.

Inline Editing on RAID Tracker

We've enhanced the RAID Tracker by introducing inline editing to it on the Project Record page, Project Management Workspace, and Experience Cloud Sites. You can now edit the grid fields directly on the component. While the RAID Tracker is view-only in the main RAID view, you can perform inline editing when you switch to any individual RAID object view using Change View. The icon on some grid cells indicates that you cannot edit those specific fields. For all other fields in individual views, simply double-click the cell or select it and press Enter to edit.

For more information, see Using the RAID Tracker.

Introducing Actions, Assumptions, Decisions, and Dependencies in PSA

We've introduced the following objects in PSA to enhance overall project governance and decision tracking:

  • Actions
  • Assumptions
  • Decisions
  • Dependencies

These objects help track critical tasks, conditions, choices, and interdependencies, ensuring accountability, proactive risk and issue management, and informed decision-making throughout the project lifecycle.

Additionally, these objects are integrated into the RAID Tracker on the Project Record page, Project Management Workspace, and Experience Cloud Sites. This enables project managers to analyze and evaluate projects and RAID objects effectively. We've added the following Lightning component properties to the RAID Tracker, enabling you to control the fields displayed in both the Records Details panel and the RAID Tracker grid for individual views.

  • Action Custom Fields Field Set
  • Assumption Custom Fields Field Set
  • Decision Custom Fields Field Set
  • Dependency Custom Fields Field Set

For more information, see:

Introducing RAID to the Project Management Workspace and Experience Cloud Sites

We've added the RAID Tracker to the Project Management Workspace and Experience Cloud Sites. This component assists project managers and teams in effectively managing and tracking risks, actions, assumptions, issues, dependencies, and decisions throughout the project lifecycle. On the Project Management Workspace, the RAID Tracker includes a Project column in the grid, a Projects and Project Manager filter field, and a Project field on the Record Details Panel.

For more information, see Project Management Workspace.

Dynamic Portfolio Creation Through Rules

We have added the ability to create portfolios with dynamic rules. This means your projects are automatically added to your portfolios according to set criteria. Dynamic portfolio creation enables you to set up portfolios and manage larger volumes of projects quickly and easily, making the project management process more efficient. You can also exclude specific projects from your portfolios, even when they meet the criteria set through your rules.

A new table in the Manage Portfolio window enables you to preview the projects in your portfolio. This table displays the projects added by rules, or manually added to the Portfolio Items related list, for ease of viewing when managing your portfolio. When saving the changes made in this window, the Delivery Tracker also updates to reflect the projects contained in the portfolio.

To support dynamic portfolio creation we've also added the Update Portfolio action. This action enables you to update your portfolio to capture all projects that align with the rules created for your portfolio, and automatically remove those that do not.

For more information, see:

Enhancements to Delivery Tracker Through Timeline View

We have added a timeline view to the Delivery Tracker. The timeline view enables you to view the progress of your projects and portfolios, and provides a clear view of when projects in a hierarchy or collection are approaching their start or end dates.

The timeline view has been added to the view switcher which also contains the summary view, and revenue forecast if enabled.

For more information, see:

Enhancements to Project Monitor Rollup

We've added an Action: Update Project Monitor Fields field to the Project object, which manually triggers a recalculation of the Project Monitor Fields for a project. If you save the project with the Action: Update Project Monitor Fields checkbox selected, it updates the Total Assigned Hours and Total Projected Revenue fields on the project and automatically deselects the Action checkbox. For more information, see Project Fields.

We have added a Expires At field to the Process Lock Fields object. This field is used internally to mark the date and time when the lock becomes invalid. The record is created when the process is locked and deleted when it is no longer locked. For more information, see Process Lock Fields.

Supporting Additional Fields in the Record Details Panel in Timesheet Entry

We have added the ability to configure additional fields in the Lightning App Builder (LAB) for the Resource Details panel in Timesheet Entry. This enables you to customize a wider range of fields for greater flexibility and personalization.

The following properties are now available in LAB:

  • Project Record Details
  • Project Task Custom Editable Field Set
  • Project Task Custom Read-Only Field Set
  • Assignment Record Details
  • Milestone Record Details

For more information, see Timesheet Entry Properties.

Enhancements to Usability and Navigation in Timesheet Entry

We have improved the usability and navigation of Timesheet Entry in this release, to enhance your time management experience.

You can now enter tasks by selecting Add Tasks from the Create new records menu, when selecting one timecard line. This provides you with multiple ways of adding tasks to your timecard, enhancing the usability and experience of entering time in Timesheet Entry.

We have also enhanced the timecard editing capabilities of Timesheet Entry. You can now navigate to Timesheet Entry from the Timecard record page, including when you are editing a timecard on behalf of another resource.

For more information, see Using Timesheet Entry.

Convert Time Variance Batch Job to Asynchronous Framework

We've made the time variance batch process faster and more reliable by moving a number of time variance classes to the asynchronous framework. This utilizes the asynchronous framework to restrict capabilities and prevent Salesforce from being overloaded with requests, resulting in more predictable and stable performance. To do this, we have added the following new callables:

  • TimeVarianceCallable
  • TimeVarianceEnqueuer

For more information, see PSA Asynchronous Callables.

(Beta) Introduction of Fields Detailing Revenue and Costs Carried Over From Closed Periods in Services Forecasting

Warning:

Services Forecasting is Beta functionality in this release. Further development is required to deliver a fully functional solution. Contact Certinia Support.

To make it easier for you to work out where values in forecast calculations have come from and to track where values have gone, new fields are now available that contain the following:

  • Scheduled, unscheduled, and pending revenue that was not included in the forecast calculations for a given monthly time period because the month was closed for forecasting. When the month is closed, values in the existing Revenue Pending Recognition, Scheduled Revenue, and Unscheduled Revenue fields move into the new Unfulfilled Pending Revenue, Unfulfilled Scheduled Revenue, and Unfulfilled Unscheduled Revenue fields on revenue forecast and revenue forecast type records.
  • Scheduled, unscheduled, and pending costs that were not included in the forecast calculations for a given monthly time period because the month was closed for forecasting. When the month is closed, values in the existing Costs Pending Recognition, Scheduled Costs, and Unscheduled Costs fields move into the new Unfulfilled Pending Costs, Unfulfilled Scheduled Costs, and Unfulfilled Unscheduled Costs fields on cost forecast and cost forecast type records.
  • Scheduled and unscheduled hours that were not included in the forecast calculations for a given monthly time period because the month was closed for forecasting, the associated project was closed, or the associated milestone was completed. Values in the existing Scheduled Hours and Unscheduled Hours fields move into the new Unfulfilled Scheduled Hours and Unfulfilled Unscheduled Hours fields on revenue forecast and revenue forecast type records. These fields only apply to % Complete revenue forecast calculations.
  • Pending revenue and costs for a given monthly time period, excluding any pending revenue and costs carried over from a closed monthly time period. The values are displayed in the new Pending Revenue Before Carryover field on revenue forecast and revenue forecast type records and the new Pending Costs Before Carryover field on cost forecast and cost forecast type records.
  • Pending revenue and costs that were originally intended to be included in forecast calculations for a given monthly time period but were carried over into the next open month because the original month was closed for forecasting. The values are displayed in the new Pending Revenue Carried Over field on revenue forecast and revenue forecast type records and the new Pending Costs Carried Over field on cost forecast and cost forecast type records.

Equivalent fields are also available that show the revenue and costs in the corporate currency. For information on how currency exchange rates are used in Services Forecasting, see Exchange Rates.

The new fields are automatically populated when the forecast jobs are next run. For a full list of the new fields, see Upgrading to PSA Summer 2025.

If you are using Cost Forecasting, cost forecasts are now included in the results when you preview your forecasts, which helps you to trace where the values in your forecasts have come from. A Costs or Revenue column in the grid indicates whether the value in each row relates to costs, revenue, or both. For more information, see Previewing Forecasts.

(Beta) Include Additional Sources of Scheduled Costs and Revenue in Services Forecasting

Warning:

Services Forecasting is Beta functionality in this release. Further development is required to deliver a fully functional solution. Contact Certinia Support.

Project Managers can now plan the use of their expense budgets and see their expected expenses up front, making it easier to compare with actuals and increase forecast accuracy. To achieve this, we have made the following enhancements:

  • Unapproved miscellaneous adjustment records are now included in deliverable cost and revenue forecasts. This means that if you use a miscellaneous adjustment to record a scheduled expense, it is now included in your cost and revenue forecast calculations. For more information, see Miscellaneous Adjustment and Miscellaneous Adjustment.
  • It's now also possible to forecast expense budgets using the Equal Split recognition method. The forecast costs and revenue are split equally between the open monthly time periods on a project as unscheduled costs and revenue. For more information about how the calculations work, see Equal Split Recognition Method for Cost Forecasting and Including Expense Budgets.
Note:

Unapproved miscellaneous adjustment records and expense budgets are included when you preview a revenue forecast. For more information about previewing forecast data, see Previewing Forecasts.

(Beta) Include Unheld Resource Requests in % Complete Revenue Forecast Calculations for Services Forecasting

Warning:

Services Forecasting is Beta functionality in this release. Further development is required to deliver a fully functional solution. Contact Certinia Support.

To provide more complete and accurate forecasts, it is now possible for % Complete revenue forecasts for projects and milestones to contain data from unheld resource requests (with and without schedules). This includes revenue forecast calculations for weighted values and mid month forecasts.

Note:

You must have the Include Unheld RRs in % Complete field selected on the active revenue forecast setup record.

We have made the following enhancements:

  • You can access separate values for unheld resource request hours and revenue in a % Complete revenue forecast. The hours and revenue are included on revenue forecast type records that have:

    • A revenue source of "% Complete: Milestone Unheld Resource Request" and a revenue type of "Forecast".
    • A revenue source of "% Complete: Project Unheld Resource Request" and a revenue type of "Forecast".

    The values from these resource request type records contribute to the revenue forecast as unscheduled hours and unscheduled revenue.

  • Actual, scheduled, and unscheduled hours are displayed in separate fields on a revenue forecast type record. Values in these fields are allocated to the most appropriate revenue type:

    • Actual hours are allocated to the "Actuals" revenue type.
    • Scheduled and unscheduled hours are allocated to the "Forecast" revenue type.

  • If you are using the Weighting feature for % Complete monthly revenue forecast calculations:

    • You can use a new Unheld RR % Complete Weighting Field setting on the revenue forecast setup record to include unheld resource requests in weighted forecast calculations.
    • We have relabeled the existing RR % Complete Weighting Field setting to Held RR % Complete Weighting Field to differentiate between the two settings but the way it works is unchanged.
    • Separate fields for actual, scheduled, and unscheduled weighted effort are available on revenue forecast and revenue forecast type records to enable you to validate the weighted values returned in revenue forecasts.
  • For accurate mid month Deliverable and % Complete forecasts, scheduled hours and unscheduled hours from unheld resource requests that fall on or before the cutoff day specified on the revenue forecast setup record are now excluded from both the current monthly time period and also from earlier months. Previously, they were only excluded from the current month, which meant that if you did not close a month for forecasting promptly, when the month containing the cutoff day changed, the hours in the original month were no longer excluded and would reappear, causing a sudden, temporary increase in the forecasted values. When the month was eventually closed for forecasting, the forecasted values then returned to normal.
  • When previewing revenue forecast data, any unheld resource requests are included in % Complete forecasts for projects and milestones.

For more information, see:

(Beta) Include Services Forecast Datasets in Services Forecasting

Warning:

Services Forecasting is Beta functionality in this release. Further development is required to deliver a fully functional solution. Contact Certinia Support.

Revenue Forecasting is unaffected and continues to work in the same way as before.

This section outlines the Services Forecast datasets for Analytics that are available.

Services Forecast Live Dataset

The Services Forecast Live dataset contains the most recent revenue, cost, and margin forecast data generated. It is sent to Analytics from your Services Forecasting records in PSA. This dataset enables you to perform a more in-depth analysis of your expected costs and revenue.

You can set up a schedule to update the dataset at regular intervals or run updates on demand.

For more information, see:

Services Forecast Plans Dataset

The Services Forecast Plans dataset contains data sent to Analytics from your services forecast plans in WorkGrid. The dataset can be combined with the Services Forecast Live dataset to create the Services Forecast Reporting dataset in Analytics.

The Services Forecast Plans dataset must be manually created from the PSA Administration page or a revenue forecast setup record. For more information, see:

(Beta) Include Services Credits in Services Forecasting

Warning:

Services Forecasting is Beta functionality in this release. Further development is required to deliver a fully functional solution. Contact Certinia Support.

To forecast all revenue streams related to your services business, you can now select Include Services Credits on the active revenue forecast setup record. This includes data for services credits related to accounts in your revenue forecasts.

If there are any accounts that you do not want to include in your forecasts, you can configure the Exclude from Forecast Account Field setting on the revenue forecast setup record. This allows you to specify a checkbox field on an account record that, if selected, excludes the record from any forecasts. For more information, see Revenue Forecast Setup Fields and Including Services Credits in Services Forecasts.

You can run an account revenue forecast from an account record page. For more information, see Running Account Revenue Forecasts.

Introduction to Services Credits Deliverables

The Services Credits Deliverable feature enables you to group milestones and any other related records, such as resource requests and project tasks, together and present them as a single deliverable. With this grouping, all the related records can be added to projects simultaneously. This helps to streamline the process of adding predefined service offerings to projects represented as services credits deliverables.

This feature is designed to support work that is funded by services credits and enables you to:

  • Equate the work done against a specific service or deliverable when delivering a project.
  • Compare the bid for each service or deliverable to calculate profitability analysis and inform about changes in pricing.
  • Add Services Credits Deliverables to projects using the ServicesDeliverableService API.

For more information, see:

Manual Allocation Adjustment of Services Credits

Previously, the allocation adjustment of services credits was handled by a process that automatically selected the customer purchase records to draw the credits from. You now have the option to either run that process or perform a manual allocation adjustment.

The manual allocation adjustment process enables you to specify which customer purchase records contribute to the adjustment.

We have also added a ServicesCreditsService.manuallyAdjustCreditsForMilestones API for this manual allocation adjustment process. Using this API, you can adjust approximately 200 allocated services credits.

For more information, see Adjusting Services Credits Allocations with Manual Selection of Credits and Permission Sets and Other Technical Documentation.

Allocation of Services Credits Enhancements

We have enhanced the logic that automatically selects the services credits customer purchase records that contribute to the allocation of credits. The enhanced logic takes into account not just the allocation date, but also the milestone's start date. This way, future dated services credits customer purchase records can be made available to the allocation, as long as their start date is on or before the latter of the allocation date or milestone's start date. This means that the automatic allocation process is now consistent with the manual allocation process.

For more information, see Managing Services Credits.

Enhanced Visibility of Payment Status for Service Credits

You can now create Services Credits Customer Purchase records manually from Opportunity Product lines. This allows you to link service credits to Opportunity product lines so that you can track the Services Credits Customer Purchase status in PSA, such as paid or unpaid. As a result, Project Managers can focus on delivering the project with all the financial information they need.

To achieve this, we have added an Opportunity Product field in the Services Credits Customer Purchase object, which connects the Services Credits Customer Purchase object with the Opportunity Product line.

When creating Services Credits Customer Purchase records, you can manually link them to an Opportunity Product line using the Opportunity Product field. Additionally, when you create a Sales Invoice from an Opportunity, the system automatically links the Sales Invoice to the Services Credits Customer Purchase. The Services Credits Customer Purchase payment status then updates to Paid once the Sales Invoice is paid.

For more information, see Services Credits Overview, Services Credits Customer Purchase Fields, and Custom Opportunity Product Fields.

(Beta) Support for Dated Resource Rates

Warning:

The dated resource rates feature is Beta functionality in this release of PSA. Do not adopt it except in sandbox environments. Further development is required to deliver a fully functional solution.

The dated resource rates feature was first introduced as beta functionality in PSA Spring 2025. The PSA Summer 2025 release includes the following enhancements.

Bulk Process to Update EVAs for Dated Resource Bill Rate Changes

The Bulk Update EVAs for Dated Resource Rate Changes process updates all the EVAs in your org to reflect changes to dated resource bill rates. You should run this process whenever dated resource bill rates are updated in your org. For example, if your business updates rates annually, your procedures must include running the Bulk Update EVAs for Dated Resource Rate Changes process when all the updates are complete.

For more information, see (Beta) Update EVA Estimates for Dated Resource Bill Rate Changes.

Estimates vs Actuals Generated from Held Resource Requests Reflect Dated Resource Bill Rates

When EVAs are generated for a held resource request using either a static bill rate or dated resource bill rates, its billable amount is saved in the Requested Billable Amount field on the EVA records. The Requested Billable Amount is divided by the number of hours in the EVA period to calculate the EVA's Resource Request Bill Rate.

For more information, see (Beta) EVA Calculations When Dated Resource Bill Rates Apply to Resource Requests.

Support for Dated Resource Bill Rates in Services Forecasting

When you run project revenue forecasting using the Deliverable recognition method, if assignments and resource requests are using dated resource bill rates those rates are used to calculate a record's revenue. Any custom bill rate fields that might be configured on the active revenue forecast setup record, and static bill rate fields, are ignored.

For more information, see Dated Resource Bill Rates and Revenue Forecasting.

Enhanced Scalability for Services Billing

In the previous release, we enhanced the scalability of the Billing Events Release process. To prevent Billing Release batch jobs from failing to start when the Flex Queue is full, PSA started using an asynchronous framework that initiates a callable to check for available space in the Flex Queue before starting a batch job.

We have also enhanced the scalability of the billing process for the following services billing processes:

  • Mass Billing Events Generation
  • Recalculating Billing Events
  • Combining Billing Events
  • Marking Billing Events as Invoiced
  • Revert Billing Events

To scale the billing process for the Mass Billing Events Generation, we have added a new Queued for Billing Event Generation field on the Project object. Whereas the other billing processes use the Queued field from the Billing Event and Billing Event Batch objects.

The BILL_QueueBillingJobCallable callable checks the Flex Queue's current status. It starts batch jobs when sufficient space is available. If there isn't enough space, the callable will:

  • Marks all the records selected to be generated, combined, or recalculated as queued.
  • Based on the value specified in the Flex Queue Delay custom setting field, reattempt to start the next batch after a set delay to check if the Flex Queue has capacity.

This process repeats several times, based on the Flex Queue Maximum Batch Retries setting, while the callable monitors the Flex Queue for enough space to start the batch job. These enhancements make batch job handling more reliable, reducing failures during peak periods.

For more information, see:

Enhanced Trigger Control

We've enhanced how you manage your functional-area trigger handlers to give you more precise control.

It used to be difficult to disable a specific trigger because some shared the same name, which prevented independent control. Now, each trigger has a unique name. This enables you to disable a specific trigger without affecting any others by adding a configuration option in the ASM Triggers configuration group.

We've deprecated the old configuration options and replaced them with new ones to give you better control over your triggers.

  • The handleTransactionForBudget option is deprecated and has now been replaced with BudgetManager, FIN_BudgetTrigger, and BILL_BudgetTrigger.
  • The handleTransactionForMiscellaneousAdjustment option is deprecated and has now been replaced with MiscellaneousAdjustmentManager, FIN_MiscellaneousAdjustmentTrigger, and BILL_MiscAdjustmentTrigger.
  • The handleTransactionForTimecard option is deprecated and has now been replaced with Timecards, FIN_TimecardTrigger, BILL_TimecardTrigger, and Transaction_TimecardTrigger.
Note:

If you are an existing user and using any of the configuration options listed above, we recommend that you contact the Certinia Customer Support team. Alternatively, your administrator can create the newly added configuration options in the ASM Triggers configuration group.

For more information, see ASM Triggers and Deprecated Elements.

Enhancements to Data Security

We have made several enhancements to data security and security checks.

Storing Google Maps API Key

Previously, sensitive data, including the Google Maps API key, was stored in publicly accessible custom metadata types. The External API Credentials field was used to hold the API key for the Google Maps integration.

To enhance security, we've implemented a new method for managing your Google API key. You can now securely configure this key directly within your org from the Manage Google Geocoding Services window under Geocoding Services in the PSA Administration tab.

This eliminates the need to store the API key in public custom metadata types, providing increased protection against potential data breaches.

The API key authorizes the Google service to retrieve the geographic coordinates of the specified address.

You can now enter the API key, enable or disable geocoding services, and save your changes all in one place within the Manage Google Geocoding Services window, the same location where you previously activated or deactivated Google Maps.

Note:

Ensure that you have a Google account and a geocoding API key. If not, you must obtain this from the Google Maps Platform. For more information, see Google Documentation and PSA Administration.

Security Checks

Warning:

The following are mandatory requirements and must be carried out after installation of the PSA Summer 2025 package.

From Summer 2025, a large number of field-level security checks are being introduced. These checks prevent potential security vulnerabilities that could allow unauthorized access to data through CRUD bypasses.

We are continuously strengthening field-level security across PSA to ensure compliance with security standards and to provide a more robust data protection framework.

We recommend that you:

  • Review and adjust any custom user permissions to align with the new field-level security requirements.
  • Update your permission sets manually if you have cloned the packaged permission sets or created your own custom permission sets.

For more information, see Upgrading to PSA Summer 2025.

Project Visibility Updates When Generating Billing Events for an Account

We've updated project visibility to align with your organization's sharing settings. Previously, all projects associated with an account were visible, regardless of user permissions. Now, you'll only view projects you have permission to view to reflect your access rights to handle record visibility based on sharing settings and Billing permission controls. This change ensures that projects displayed in PSA now consistently reflect your access rights for record visibility based on sharing settings.

If you have the Billing permission control for a project, then projects will appear in the Select Projects table. This will be applicable whether or not other sharing settings grant you access.

If you do not have the Billing permission control for a project but your sharing settings allow you to view it, the project will be hidden from the Select Projects table. It will instead appear under the Projects without Billing permission control.

If you do not have the Billing permission control for a project and the sharing settings do not grant you access, the project will not appear.

For more information, see Generating Billing Events for an Account.

Sharing Rules on Skills Capacity

We've updated the Skill Capacity page to enforce the Salesforce sharing settings and to ensure the skills matrix is consistent with our security implementation for managing skills in other areas. As a result, you'll now only view the skills, resource skill requests, contacts, and other related records you have permission to view.

To ensure everyone views the right information, you might need to adjust your Salesforce sharing rules and other record-sharing settings. For more details on managing access, see the Salesforce Help and Using Skills Capacity.

Permission-Based Visibility on Search Resources Page

The Search Resources page now enforces object and field permissions, ensuring users only see data they're authorized to access. If you lack the necessary permissions, an error message will be displayed stating that you're missing a required permission. For more information, see Searching for Resources on the Search Resources Page.

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 Academy

If you want to learn more about the new features in this release, see the PS Cloud - Summer 2025 Release Highlights Certinia Academy 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.