This article provides a deeper look at the key improvements delivered in Precursive 2.26. It is intended for customers, admins, and power users who want to understand what changed, how new capabilities work, and enablement guidance on how to successfully roll out these changes. Version 2.26 introduces a single Resource Plan view that lists assigned Resources and open Resource Requests together, so you can see demand and assignment side by side and fill a request without leaving the plan.

Assigned Resources and Resource Requests in one view

Highlights

View assigned Resources and open Resource Requests together in the Resource Plan, and assign a Resource Request without leaving the view.

What changed

Precursive previously separated assigned Resources and open Resource Requests into two modes, each carrying its own filters that you could not save. The Resource Plan now lists both row types in a single view. A Show selector in the filter panel controls which rows appear, and your selection applies in every grouping and saves with your filter.

How it works

• The Show selector in the filter panel controls which rows the plan lists:

  • Assigned. The plan lists the Resources assigned to work. This reproduces the previous Resource Plan view.
  • Unassigned. The plan lists open Resource Requests that hold no Resource yet.
  • Both. The plan lists assigned Resources and open Resource Requests together.

• Resource Requests appear as their own rows. Each row carries an Assign button that opens the assign flow.

• Saved filters store the Show value alongside the filter criteria. Save, Save As and Mark this view as my default apply under every selection. Filters you saved previously resolve to Assigned.
• Precursive ships two Public Filters. All Resources opens on Resources, and All Resource Requests opens on Resource Requests.

• The Resource Plan embedded on a Project or Phase record page opens on Both. The standalone Resource Plan opens on Assigned.

• The Settings cog holds Grouping, Booking Unit, Show as and Utilization Range.

• Resource and Resource Skills criteria describe a Resource, so they apply to assigned rows only. Resource Requests drop out of the results while either criterion is active.
• Load more replaces pagination at the group level and at the row level.
• The Resource Plan excludes Archived Projects under every Show selection.

Enablement guidance

The package upgrade applies the permission set changes that the Resource Plan depends on. Precursive moved four Booking date fields into the Core Platform permission sets as read-only and removed them from the Resource Management permission sets.

• Participant: firstBookingStartDate__c, lastBookingEndDate__c
• Phase: firstBookingStartDate__c, lastBookingEndDate__c

Review the loading settings in Precursive HQ > Resource Plan Performance Settings. Rows to load becomes Groups to Load and controls how many top-level groups load before Load more. Rows to Load per Group is new, defaults to 25, and controls how many rows load inside each group. Resource Request rows to load no longer takes effect.

The public views need no manual steps. The upgrade renames All to All Resources in place, so a user who marked All as their default keeps that default, and adds All Resource Requests.

What else changed

• Precursive upgraded the timeline library behind the Resource Plan, resolving the known security vulnerabilities in that library and its dependencies.

Data model

New fields: