| Type |
Business Area |
Description |
ID |
Impact Level |
| Enhancement |
Resourcing |
A new parameter ‘Show finished projects’ has been introduced to control the visibility and booking behavior of projects in the Finished stage within the Resource View and Project View forms. When the parameter is enabled, finished projects remain visible in a read-only state, preventing users from booking additional hours against them. When the parameter is disabled, finished projects are excluded from the Resource View and Project View forms. |
111175 |
Lvl.2(Moderate) |
| Enhancement |
Subcontractor management |
We have introduced automated Contract Value calculation in the Subcontractors Management form. Users can now input the Cost Budget along with either the Markup Percentage or Markup Value, and the system will automatically compute the Contract Value. |
111387 |
Lvl.1(Low) |
| Enhancement |
Fee management |
Added a new parameter to retrieve the amount directly from the Transaction Amount field in the Voucher table for displaying the WIP Amount and Invoice Amount on the Fee Management form, eliminating the need for additional calculations involving exchange rates. |
111455 |
Lvl.2(Moderate) |
| Enhancement |
Unit based billing |
Finished projects are no longer available for selection in the Unit Code Entry standalone form. Additionally, users are now prevented from selecting header projects that do not allow transaction postings, ensuring greater accuracy and validity in transaction entry. |
111613 |
Lvl.2(Moderate) |
| Enhancement |
Quick project search |
We have enhanced the Quick Project Search form to enforce the configured Project/Category validation rules. As a result, the form now automatically filters out projects that do not meet the defined validation criteria. |
111079 |
Lvl.2(Moderate) |
| Fix |
Fee management |
Fixed an issue where the Invoice Amount on the Invoice Proposal Summary tab was not updating accurately after transaction changes on invoices with NTE fees. With this fix, the amount is now recalculated correctly, ensuring accuracy in invoice totals. |
112632 |
Lvl.2(Moderate) |
| Fix |
Workspaces |
Detected an issue when a Billing Schedule ID was selected during the creation of an Adjustment Request from the PM Workspace, the Project ID was automatically populated; however, the Project Manager and Project Accountant fields remained blank. This fix ensures that both fields are now correctly populated based on the selected Billing Schedule ID, improving data completeness and accuracy. |
112646 |
Lvl.1(Low) |
| Fix |
Misc changes |
An issue was reported where updating the quantity in the Unit Code Entry form at the line level caused the sales price to be automatically set to zero. This fix ensures that the sales price is retained when the quantity is modified, maintaining data accuracy. |
112650 |
Lvl.1(Low) |
| Fix |
Quick project search |
When the project name was updated in Project Operations, the main project name was not reflected in the Quick Project Search table due to this on timesheet line main project name was showing incorrectly. This fix ensures that the main project name in the Quick Project Search table is now automatically updated whenever the project name is modified, maintaining consistency across the system. |
112662 |
Lvl.1(Low) |
| Fix |
Adjustment request |
In prior versions, users were unable to apply filters to the Project ID field on Adjustment Request lines. With this fix, filtering is now supported in the standard (normal) view for the Project ID field. However, please note that filtering continues to be unsupported in the Tree View. |
112667 |
Lvl.1(Low) |
| Fix |
Contract management |
Users assigned to specific roles were unable to approve or reject contract agreements. This fix ensures that users with the appropriate roles can now successfully approve or reject contract agreements directly from the Contract Management form. |
112679 |
Lvl.1(Low) |
| Fix |
Billing schedule |
The cost amount was visible in the Adjust Transactions form despite the ‘Restrict access to cost prices’ role being applied. This fix ensures that the cost amount is no longer visible in the Adjust Transactions form when the restriction is enabled. |
112740 |
Lvl.2(Moderate) |
| Fix |
Contract management |
Earlier, users with assigned roles were unable to view or use the Initialize from Forecast feature in Contract Management. With this fix, users with the specified roles can now access the feature and initialize bucket amounts from forecast data. |
112789 |
Lvl.2(Moderate) |
| Fix |
HR automated events |
An issue fixed where vendor bank accounts were not being created for future-dated worker hires processed through HR automated events. This fix ensures that vendor bank accounts are now automatically created via HR automated events when employee bank account details are updated. |
112822 |
Lvl.2(Moderate) |
| Fix |
Billing schedule |
In earlier versions, users were unable to view posted project transactions from the billing schedule. With this fix, users can now directly access and view posted project transactions from the billing schedule. |
112823 |
Lvl.2(Moderate) |
| Fix |
Time entry power app |
Resolved an issue in the Time Entry Power App where a blank period reference record was being created, and an unexpected error occurred when users attempted to create a timesheet after reaching the configured maximum number of timesheets for a period. With this fix, the system now prevents the creation of additional timesheets once the limit is reached and ensures that no blank period reference records are generated. |
112824 |
Lvl.1(Low) |
| Fix |
Billing schedule |
Resolved an issue where billing schedule creation executed in batch mode could intermittently skip billing schedules for some contracts when processing large volumes of contracts. The issue could occur regardless of whether the batch job was configured to run with threads or without threads, and could also be encountered when multiple users initiated the batch job simultaneously. With this fix, billing schedules are now created reliably for all eligible contracts across large-scale batch processing scenarios, threaded and non-threaded executions, and concurrent batch job runs by multiple users. |
112829 |
Lvl.3(High) |
| Fix |
Contract management |
A scenario reported, where contract management approval workflow where users were previously redirected to all agreement lines instead of the specific approval record assigned to them. With this fix, users are now directed only to the agreement line that requires their approval. |
112848 |
Lvl.1(Low) |
| Fix |
Time entry power app |
When users created a timesheet with the “Allow Zero Hours Entry” parameter enabled and added multiple lines for the same project, the hours were not displayed correctly. This issue has now been resolved, ensuring that hours are accurately displayed across multiple timesheet lines associated with the same project. |
112769 |
Lvl.1(Low) |
| Fix |
Time entry power app |
Rejection icon displayed an incorrect error message when a rejected timesheet header had no associated workflow comments. With this fix, the rejection icon now correctly indicates when no workflow comments are available for the rejected timesheet. |
112860 |
Lvl.1(Low) |
| Fix |
Time entry power app |
An issue reported where duplicate hours were recorded when multiple timers were linked to the same timesheet line. With this fix, hours are now accurately calculated and displayed, even when multiple timers are associated with a single timesheet entry. |
112899 |
Lvl.1(Low) |
