/
Approval (Closing) Of The Change

Approval (Closing) Of The Change

Owned by Lango: Language and translation manager
Last updated: Sept 17, 2024 by Tomas Nagy
2 min read

Closing (approving) the change copy/variant must be done before it is transferred to the original, if the Strict Changes List Policy =Y flag is in OneCore Setup.

The user on the change copy/variant opens the Change Contract History overview via Related/Contract Change History.

Once confirmed, the Contract Change History overview opens.

If the user wants to close (approve) the last change, he/she opens the Contract Change History Card – by clicking on the row or via Manage/Edit.

Closing a row in Change Contract History will be used to approve changes in the same way in the case of a change copy as well as in the case of a variant.

The line closure function works as follows:

  • if Strict Changes List Policy in OneCore Setup = N, the Approve Change button will be hidden – in this case, the system will close the change list automatically when transferring the change copy/variant

  • if Strict Changes List Policy is in OneCore Setup = Y, the Approve Change button will be active and will perform the following steps when pressed:

    • Checks for the new Customer Approval flag

    • if N, it displays an error message and does not continue (i.e. approval will be possible only if Customer Approval = A):

      image-20240619-105924.png

    • if Y, it proceeds to the next step.

  • fills in the Approval Date field, fills in the currently system date

  • changes the flag to Closed/Closed to Y.

  • Note: The date of the customer's consent is entered manually by the user.

If the user (or the system) has closed a row in the Contract Change History, the system will no longer allow you to enter or edit anything on the line (the check is for leaving the card):

image-20240619-105950.png

The user can then transfer the change copy or variant (see the relevant chapters).