Skip to main content
Skip table of contents

07/29/2021 Deployment Notes

Notifications

  • PM2-9096 HOTFIX Some nightly jobs, such as scheduled emails and auto-renewals, occasionally failed.

    • Occasionally, when many operations were running for different tenants at the exact same time, the CLM database became temporarily unavailable.

    • As a result, when the nightly jobs ran, some jobs failed because the database wasn’t yet available to be used (as it was still being loaded into memory).

    • To mitigate this, we added retry logic so that nightly jobs should run as expected.

    • We will contact affected customers directly.

Workflows

  • PM2-9061 DEFECT FIX When a user retracted a workflow, users who had been inserted into the previous phase via the Add Role to Phase trigger were removed from the Available Participants list but remained in the Participant Sequence. This has been fixed; when a user retracts a workflow, users inserted into the previous phase via the Add Role to Phase trigger will be removed from both the Available Participants and Participant Sequence lists.

  • PM2-4441 BUG FIX When a user retracted a workflow and changed trigger field values, users who had been inserted into the retracted phase via the Add Role to Phase trigger remained in future phases. This has been fixed; retracting a workflow and changing trigger field values that affect the inserted users will remove the inserted users from future phases.

  • PM2-8885 DEFECT FIX When a user uploaded a new version of a document, the View History dropdown in the in-app document viewer failed to update the username and date/timestamp. This has been fixed; all document metadata, including the username and date/timestamp, will update when a user uploads a new document version.

Reporting

  • PM2-8838 DEFECT FIX Attempting to filter within the Contracts tab of Reporting returned an error. This has been fixed; users will be able to filter within the Contracts tab as expected.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.