Release 8th July 2021

Kellie Oxley Updated by Kellie Oxley

Release notes for the 8th July 2021 release

Reference

Impacted area

Description

13614

Supplier contract module

Suppliers must now assign items to a framework that has been set at item level, before they can invite buyers to join the framework.

13627

Buyer contract module

A buyer will now be able to see what assignment level a framework or local contract has been assigned to by the supplier. This will be displayed when a buyer views the framework or the local contract from within the approval tab in the contract module.

13681

Contract module audit trail for Buyers and Suppliers

Where a contract has been approved by a buyer, the audit log will now contain the name of the organisation that originally created the contract.

13628

Contract module audit trail for Buyers and Suppliers

Where a contract has been rejected by a buyer, the audit log will now contain the name of the organisation that originally created the contract.

Multiple

Process Attributes and Additional Attributes

Expansion of the functionality previously allocated to a single Auto PO process attribute. It is now possible to support multiple process attributes each of which can be used as flags and after tagging in attribute manager, returned in a cXML basket return as buyer configured extrinsic tags. Documentation to support this has been updated here:

https://advancedcsg.atlassian.net/wiki/spaces/ACM/pages/1646101258/Process+Attribute+Tagging

https://advancedcsg.atlassian.net/wiki/spaces/ACM/pages/1360334797/Sci-Net+Additional+Attributes

10129

Custom Field Manager

Custom field manager will now refer to header level custom fields instead of PR level fields which makes sense across the multiple domains that custom fields can be used and not just Purchase Requisitions.

13752

Reqs2 Aggregation

There was a possible scenario whereby adding items into an aggregation and later removing it could potentially lead to multiple orders being generated for the item. This has been fixed.

10263

Amendments

If a user has no amendment workflow assigned to them but the business unit in which they reside has an assigned workflow then that workflow will be used.

10262

Reqs2

If a user has no reqs workflow assigned to them but the business unit in which they reside has an assigned workflow then that workflow will be used.

10259

Basket Workflow

If a user has no basket workflow assigned to them but the business unit in which they reside has an assigned workflow then that workflow will be used.

How did we do?

5th August 2021 Release Notes

untitled article

Contact