2026R1.0 - New Features

What's Different:

A new "gateDetails" object is now available in the response of four Project service REST API GET endpoints:

• GET <http://{host}/{context}/rest/projectservice/v1/project/{id}>

• GET <http://{host}/{context}/rest/projectservice/v1/projects>

• GET <http://{host}/{context}/rest/projectservice/v1/download>

• GET <http://{host}/{context}/rest/projectservice/v1/downloadAllWorks>

Whenever the "includeResourceDetails=true" request parameter is included, the "gateDetails" object will be displayed for all Gated Projects included in the response. This object contains the following fields for each Gate:

• id: The 26-digit ID number of the Gate.

• link: A link to further data about the Gate.

• name: The name of the Gate.

• resourceDemands: An object containing data about each Role demand attributed directly to the Gate.

  Note: Demand occurs when a Role been assigned to a work item (or, in this case, a Gate) but no Resource. It is essentially an unstaffed position on the Gate.

  Note: This object will not include any effort demands on work items that belong to the Gate. The demand must be made against the Gate itself.

  This object contains the following fields for each unstaffed "role":

  • id: The 26-digit ID number of the Role.

  • link: A link to further data about the Role.

  • name: The name of the Role.

  • effort: The number of unstaffed hours attributed to the Role on the Gate.

• resourceAllocations: An object containing data about each Resource allocation made directly on the Gate.

  Note: An allocation occurs when a Resource has been assigned to a work item (or, in this case, a Gate).

  Note: This object will not include any allocations on work items that belong to the Gate. The allocation must be made against the Gate itself.

  This object contains the following fields for each allocation, organized by "role":

  • id: The 26-digit ID number of the assigned Role.

  • link: A link to further data about the Role.

  • name: The name of the Role.

  • user: An object containing data about the assigned Resource. It includes the following fields:

    • id: The 26-digit ID number of the assigned Resource.

    • name: The name of the assigned Resource.

  • effort: The number of hours assigned to the Resource allocation.

Benefit:

Prior to this release, Resource allocation and demand information on Gated Projects was available whenever any of the above endpoints were hit. However, the response would only include allocations and demands made directly against the Gated Project itself; there was no way to display assignments made directly on specific Gates.

Example: Have a look at the two assignments below.

Prior to this upgrade, Sandra's allocation (which is made directly against the Gated Project) would be included in API responses while Brady's allocation (which is made directly against a Gate) would not.

With this update, data from allocation and demand toward specific Gates can be integrated directly into other systems, such as Business Intelligence (BI) tools, custom dashboards, or data warehouses.

What's Different:

Each work item's Estimated Costs page now features an "Hours" column, as well as a total count of all assigned hours.

The column displays the total number of hours each Resource is assigned to the work item. These hours (along with the Resource's rate) are used to calculate the Estimated Cost of the assignment under the "Amount" column.

Tip: See Estimated Labor Costs for information on how Estimated Costs are calculated from Project Central assignments.

Note: The "Hours" column will only display values for estimated labor costs. Manually entered Estimated Costs will not display any values under this column.

Benefit:

By displaying the number of assigned hours next to each estimated labor cost, Project Managers are provided with increased visibility into the financial impact of work effort. This allows them to plan Resources more efficiently and make better staffing decisions before their estimated labor costs become actual labor costs that must be compensated.

What's Different:

Visibility rules defined for work item Tags and Custom Fields on the Field Management page are now applied to work item Summary pages as well as the Create Work wizard.

Note: Users require the "Field Management Administration" Context permission to access the Field Management page and configure visibility rules.

Note: If visibility is not configured for your PowerSteering environment, reach out to your PowerSteering representative to enable it for you.

Prior to this release, work item visibility rules only applied to the Create Work wizard. When administrators edited the visibility rules for an Object Type, the rules would not apply to Tags and Custom Fields that existed on the Summary page once the work item was created.

Example: Alex's PowerSteering environment has two location-based Tags attached to Projects: "Texas Cities" and "New York Cities". If a Project has a Texas location, it does not need a New York location, so Alex would only like the "New York Cities" Tag to be visible when the "Texas Cities" Tag is empty.
Under the "Project/Work Types" menu on the "Field Management" page, he selects "Project" and adds the following function into the "New York Cities" Formula Builder: isEmpty(this, @Tag[Texas Cities]).

This function is helpful while creating Projects; the "New York Cities" Tag disappears whenever a value is selected for "Texas Cities".

Click thumbnail to play.
Prior to this release, however, this would not be the case once the Project was created. Selecting a value for "Texas Cities" on the Project's Summary page would not cause the "New York Cities" Tag to disappear.

Click thumbnail to play.

With this update, Tag and Custom Field visibility rules will be respected on work item Summary pages as well as the Create Work wizard.

Benefit:

Prior to this release, the lack of visibility rules on Summary pages would lead to inconsistencies and confusion, especially because these rules were respected while creating work. Project circumstances change constantly and Tags and Custom Fields often require new values after projects are created. When this is the case, the same visibility rules applied to Tags and Custom Fields should be applied. It ensures that users only see relevant Tags and Custom Fields, helping them focus on key details without distraction from unnecessary fields.

What's Different:

Users now have the option to view up to 500 Timesheets at once on the Manage Time page.

Prior to this release, the Manage Time page featured a pagination of 50 Timesheets at once.

With this update, users can now view 100, 250, and 500 Timesheets at once on the page.

Benefit:

Increased pagination options reduce navigation and improve efficiency while reviewing and approving large amounts of Timesheets at once.

What's Different:

The "My Reports", "My Data Extracts", and "Public Reports" pages now feature a "Last Run By" column for each listed report. This column indicates the user who most recently ran the report. If the report ran automatically due to a schedule, the column will simply display a "Scheduler" value.

Like other columns, select the "Last Run By" column header to sort the table alphabetically (or twice to sort it in reverse alphabetical order) by these values.

Tip: Select any name under the column to reveal some basic information about the user. From here, select More... to navigate to the user's profile.

Benefit:

The new "Last Run By" column provides visibility into who most recently ran each PowerSteering report. It also indicates whether the report was manually run by a human or generated automatically by a report schedule. This improves transparency into how report data is refreshed and whether it was run manually or by a schedule.

What's Different:

A new "Resource Pools at Period (Role)" column is now available for reports created using the Report Wizard. This column is available for "User/Timesheet" and "User/Timesheet by Period" report types under the "Timesheet" section.

When included in reports, this column displays the Resource Pool(s) the user belonged to during the Timesheet period. Additionally, the user's assigned Role on the work item will be included in parentheses.

Note: This is the Role that has been assigned to the user on the work item, not the Role the user selected while submitting the Timesheet.

Example: Brady belongs to three different Resource Pools. On March 24^th, he was reassigned from the "Development Team" Resource Pool to the "Public Relations" Resource Pool.
When a user runs a "User/Timesheet by Period" report, the "Resource Pools at Period (Role)" column will display different values based on the "Period" (which, in this case, is daily). The March 23rd submission indicates he belonged to "Development Team", but the March 24^th submission indicates he belongs to "Public Relations" instead.

Benefit:

Prior to this release, users could apply a "Resource Pools (Role)" column to these report types. This column would only display the Resource Pool(s) the listed user currently belongs to, not the ones the user belonged to during the indicated Timesheet period. Many organizations use Resource Pools for cost tracking or capacity planning, so Resource Managers would have to manually inspect specific Resource data themselves in order to find this information. By implementing the "Resource Pools at Period (Role)" column, report builders can ensure that User/Timesheet reports will display the correct historical context and organizational grouping for each Timesheet submission.

What's Different:

Users can now include the sequence numbers for work item Programs while creating PowerSteering Report Wizard reports. While editing the report's columns, users will now find two new columns under the "Project" section: "Program sequence" and "Program sequence and name".

• Program sequence: The sequence number of the Program the work item belongs to.

• Program sequence and name: The sequence number of the Program the work item belongs to as well as the name of the Program itself.

Benefit:

Sequence numbers provide an easy way to view Programs in their intended sequence and track where they fall in the Work Tree. Including them in reports provides context into the structure and order of work items, making reports easier to interpret and align with Program planning.

Prior to this release, there was no way to include this data in reports; report builders would have to rely on other tools such as Upland Analytics to retrieve Program sequence numbers and match them with work items. With this update, Program sequence numbers can be included directly within PowerSteering reports, eliminating the need to navigate through the application to provide them.

What's Different:

Source work item summary pages will now display a list of generated child work items. Whenever a work item is used as source work, its child work items will be listed under "Generated work items" at the top of the Summary page.

This feature is enabled for every PowerSteering work item by default, but administrators have the ability to disable it by deselecting the "Display work generated items" checkbox while editing Object Types.

Note: Only PowerSteeringadministrators can configure Object Types.

Benefit:

Prior to this release, users would have to navigate to a work item's References page to view all of its generated work. With this update, these work items are now listed directly on the Summary page of the source work, eliminating the need to tediously switch from page to page while trying to view generated work items. This is especially beneficial for source work items that are created specifically as vessels for work generation.

What's Different:

The "Project Reports" Summary page module has been updated to reflect the new PowerSteering data grid interface.

Prior to this release, the module reflected the legacy PowerSteering interface for data grids.

With this update, the "Project Reports" module has been upgraded to the new interface. It now matches the other modules on the Summary page.

Benefit:

With this upgrade, the "Project Reports" module now contains the same features that are available for other PowerSteering data grids, including the ability to customize columns and export the grid data. Additionally, it matches the interface of other modules, contributing to a uniform look and feel of the Summary page.

What's Different:

The Copy page has been updated to reflect the new PowerSteering "UI 2.0" interface.

Prior to this release, selecting Project → Copy from the Navigation Menu would automatically open up the legacy Create Work page.

With this update, selecting Project → Copy will open up the new Create Work wizard.

Benefit:

The new Create Work wizard breaks down the process of creating new work into separate steps, alleviating the informational overload that comes with lengthy "Create New" pages. Additionally, it matches the new "UI 2.0" interface, contributing to a refreshed look and feel PowerSteering.

What's Different:

Announcements can now be viewed on pages in PowerSteering that reflect the new "UI 2.0" interface.

Prior to this release, users could only view announcements on PowerSteering pages that still retained the legacy interface. Pages that featured the new interface (New Resource Review, Financial Review, Add Work, etc.) would not display any current announcements at the top of the page.

With this update, pages with the new "UI 2.0" interface will also display active announcements.

Benefit:

Announcements provide an effective way to communicate important updates and notices to PowerSteering users. Unlike emails or other external communications, all users can see them as soon as they log in to PowerSteering. However, many users may find themselves working exclusively within "UI 2.0" pages, especially if their roles are specific (i.e. creating work items, managing Resources, etc.). When this is the case, they may not get a chance to read certain announcements for a significant amount of time. Adding announcements to "UI 2.0" pages helps keep all PowerSteering informed and up-to-date, regardless of where they spend most of their time in the application.