Annex - Record already locked

Issue Description

When attempting to sign an annex, if the annex is signed more than three times using an incorrect user account (one without the necessary permissions), the system will display an error message and subsequently block the annex.

Error Message

After several unsuccessful attempts, the following error message may be displayed:

• Error Message: "Record already locked."

Once this error message appears, the annex will be locked, preventing further signing attempts.

Cause

This issue occurs because the system is designed to prevent unauthorized access and modifications. When an incorrect user account is used repeatedly, the system locks the annex to protect the integrity of the data.

Workaround

To resolve this issue, you can use the following workaround:

• Wait for Automatic Unlock: The Oracle lock will be removed automatically after a certain period. Typically, this duration is several hours.

Once the lock is removed, you can attempt to sign the annex again using the correct user account with the necessary permissions.

• Assign Proper Permissions: Ensure that all users who need to sign the annex have the appropriate permissions.

This can be done using the UserPro module. Assign the necessary rights to all relevant users to enable them to use the pharma modules effectively.

Steps to Assign Permissions

1. Open UserPro Module: Navigate to the UserPro module in your system.
2. Select User: Select the user whose rights you want to modify.
3. Assign Rights: Assign the required permissions for signing annexes and using the pharma modules.
4. Save Changes: Confirm and save the changes to update the user's permissions.

By following these steps and best practices, you can minimize the occurrence of this issue and ensure smooth operation within your system.

Below are other useful knowledge base articles you can find related to the same topic:

Impossible to add annex in PI process using a shared folder

Annex viewer can't display files.