1. Home
  2. Blog
  3. Release Notes - RC23.0421

Release Notes – RC23.0421

RELEASE NOTES

1. ALL REGIONS 

ENHANCEMENTS

[#61286] BE: UPDATE THE VALIDATION ON CREATING/UPDATING REVIEW TO ALLOW REVIEW AUTHOR CAN BE REMOVED FROM STAGES

[#60980] BE: RESTORE A CANCELLED REVIEW FROM THE ZIFLOW ‘RESTORED’ EVENT

[#60671] FIX: MOVE THE REMOVE BUTTON ON FILTERS

[#61129] FE: UPDATE EMPTY STATE OF REVIEW GRID – HOMEPAGE WIDGET

[#61130] FE: UPDATE EMPTY STATE OF REVIEW GRID – PROJECT WIDGET

[#61131] FE: UPDATE EMPTY STATE OF REVIEW GRID – TASK DETAIL

[#61132] FE: UPDATE EMPTY STATE OF REVIEW GRID – REVIEW TABS

FIXES

[#60700] BE: ADD AN ACTIVITY HISTORY WHEN A ROUND IS CANCELLED

[#60706] RESOURCE PLANNER VIEW TOP ROW OF DATES NOT DISPLAYING PROPERLY

[#60429] BUG: INBOX > REVIEWS : FAILED TO LOAD THE FILTERED RESULTS AFTER RELOADING THE PAGE

2. NORTH AMERICA

ENHANCEMENTS

TS PTO ENHANCEMENTS

[#60120] [BO.16] INTRODUCE A NEW STATUS FOR PULSE_USER = N

We have a series of ‘import statuses’ when processing TS PTO records. These import statuses help us debug issues in processing if any found. 

One of the new statuses introduced is ‘Not a Pulse User’. When we receive a TS PTO record for a user that does not have a Pulse account we will mark this as ‘not a pulse user’. This is a status that we don’t need to process this to timesheets and therefore not considered an ‘fail’ that we need to resolve.  

[#60121] [BO.17] INTRODUCE A NEW STATUS FOR AGR_VALID = N

We have a series of ‘import statuses’ when processing TS PTO records. These import statuses help us debug issues in processing if any found. 

One of the new statuses introduced is ‘Not valid in Agresso’. The use case here is that we could have a record that failed for another reason we didn’t resolve in time. Down the line, we look to resolve the error, but now the user is termed, and we cannot process the record.  

This is a status that we don’t need to process this to timesheets and therefore not considered an ‘fail’ that we need to resolve.  

[#60122] [BO.18] INTRODUCE A NEW STATUS FOR ‘USER IS IN THE WRONG OFFICE’

We have a series of ‘import statuses’ when processing TS PTO records. These import statuses help us debug issues in processing if any found. 

One of the new statuses introduced is ‘User is in the wrong office’. The support team can then use this status to move the user to the correct office and reprocess the record using the PTO report.

This is considered a ‘failed’ status that need intervention and should be reprocessed. 

[#60126] [BO.23] ADD NEW PTO MESSAGES FOR THE NEW STATUSES

We have a series of ‘import statuses’ when processing TS PTO records. These import statuses help us debug issues in processing if any found.

We added 4 new statuses as well as readable user friendly outputs which can be viewed in reports and using the ‘My PTO requests’ button. 

3. OTHER CHANGES

[#60382] ADMIN TOOL: BRAND REASSIGNMENT TOOL

For the Brand API clean up, we have added a superuser admin tool to allow the clean up crew bulk reassign brands and products on projects in Pulse. 

The reason for not adding this to the Bulk Amendment tool is that once Brands API is turned on, amendments on Brands & Products are not allowed if the project has any timesheets. This is purely a tool to be used in the clean up. 

The tool is very simple. Select the ‘FROM’ brand & product (no product is an option as this is a new concept). Select to ‘TO’ brand & product. 

This will output the number of projects (all projects, statuses irrelevant). 

4. TECH DEBT 

[#61145] BUG: DATE DISPLAY FOR V2 SYNCS IS MISLEADING

When running the sync, the output dates will be more descriptive e.g. Last Updated about 2 months ago (Last Run about 5 hours ago)

[#61146] BUG: SYNC BUTTON SHOWING FOR V2 SYNCS

Fix – sync button only shows for those users with permission to run v2 syncs

[#60998] BUG: STAFF SYNC INTEGRITY VIOLATION

Fix – To prevent the integrity violation messages during staff sync process. The problem is occurring when we are attempting to change the email address on the linked Users account via the Agresso/UserObserver script.

Solution – Allow the sync will complete. There will not be an entry in the logs for Integrity Violation. There will be an email with the subject “Duplicate Email address found when updating to Agresso Email”

5. REGRESSION BUGS

[#60507] V2 ADVANCED SETTINGS: WIKI TAB DOES NOT GET DISABLED

Fix – The Wiki notes tab of the project does not disappear when the user disabled the Wiki tab on the Advanced Settings for Superusers. 

[#61213] Bug: Task Explorer: Filtering jq failed when using User Department filter