Release 2024 Q1 - Fixes (detailed)

The fixes from Release 2024 Q1 are detailed on this supplementary page.

Details for each fix are: pre-conditions, steps to reproduce, expected result, dependencies and downstream impacts, and support request (ticket) IDs (if applicable).

  • Fixes
    • Policy Management
        • Fixed an incident where the metadata form can’t be saved if it contains system fields with disabled user.
        • Fixed an incident where users can’t insert XLSM files as paragraphs.
        • Fixed an incident where renamed release stage causes inability to open a document.
        • Fixed an incident where metadata with type number is displayed incorrectly in table view.
        • Fixed an incident where in rare cases transparent background-color was transformed into black colour.
        • Fixed an incident where incorrect edit shows for paragraph change.
        • Fixed an incident where it is impossible to resolve comments with replies.
        • Fixed an incident where user import via file or swagger failed.
        • Fixed an incident where widget order and dashboard layout do not show correctly for Portal Users.
        • Fixed an incident where Clausematch API (Metadata API) doesn’t return email and user uuid for user picker field.
  • Fix Patch - 137.13
    • Fixed an incident where documents on Policy Portal could not be exported to DOCX.
  • Fix Patch - 137.14
    • Fixed an incident where the metadata save reminder would not automatically closed once the metadata form is saved.

For any questions, please email support@clausematch.com and we will further assist you.


Fixes

Policy Management

🐞 Important bugs that were fixed

  • Fixed an incident where the metadata form can’t be saved if it contains system fields with disabled user.
    • Pre-conditions:
      •  N/A.
    • Steps to reproduce:
      1. Create a document by user 1 and grant owner permissions to user 2.
      2. Create a screen with the system "created by" field and any other custom field.
      3. Login by user 2.
      4. Disable user 1.
      5. Open the document.
      6. Try to edit the custom field.
    • Expected result:
      • The metadata form doesn't consider system fields for validation and could be saved regardless any errors of system metadata.
    • Dependencies & Impact:
      •  Document metadata.
    • Support Request ID:
      •  2293820686
  • Fixed an incident where users can’t insert XLSM files as paragraphs.
    • Pre-conditions:
      •  N/A.
    • Steps to reproduce:
      1. Change configuration on front-end and back-end.
      2. Create a document.
      3. Try to insert XLSM document.
    • Expected result:
      •  XLSM can be uploaded if the instance configuration allows it.
    • Dependencies & Impact:
      •  Editor.
    • Support Request ID:
      •  2151807815
  • Fixed an incident where renamed release stage causes inability to open a document.
    • Pre-conditions:
      •  N/A.
    • Steps to reproduce:
      1. Create template.
      2. Rename release stage to any other name.
      3. Publish template.
      4. Create a document from template.
      5. Release created document.
      6. Open released document.
    • Expected result:
      • Document successfully opens. 
    • Dependencies & Impact:
      • Workflow.
      • Editor.
    • Support Request ID:
      • 2269531010
      • 2151378483
      • 2143806502
  • Fixed an incident where metadata with type number is displayed incorrectly in table view.
    • Pre-conditions:
      •  N/A.
    • Steps to reproduce:
      1. Create metadata with type number.
        1. Leave it empty.
      2. Open documents.
      3. Switch to table view and choose to display the created field.
    • Expected result:
      • Empty cell is displayed if there is no value.
    • Dependencies & Impact:
      • Metadata.
      • Document results. 
    • Support Request ID:
      •  2125839879
  • Fixed an incident where in rare cases transparent background-color was transformed into black colour.
    • Pre-conditions:
      •  N/A.
    • Steps to reproduce:
      1.  Upload or copy content with a transparent backgound-color.
    • Expected result:
      • Text is displayed as it was before without any visible background.
    • Dependencies & Impact:
      • Editor.
      • Portal Viewer.
    • Support Request ID:
      • 2137783111
      • 2125543581
  • Fixed an incident where incorrect edit shows for paragraph change.
    • Pre-conditions:
      • N/A. 
    • Steps to reproduce:
      1. Add content "some text of the Group".
      2. Add comment to paragraph activity.
      3. Add "fra test" so the content will look like: "some text of the frau test Group".
    • Expected result:
      •  Paragraph activity shows "some text of the <ins>fra test</ins> Group"
    • Dependencies & Impact:
      • Editor.
      • Timeline.
    • Support Request ID:
      • 2032748703
  • Fixed an incident where it is impossible to resolve comments with replies.
    • Pre-conditions:
      • N/A. 
    • Steps to reproduce:
      1. Create document.
      2. Add comment to the document (paragraph).
      3. Replay with the same user.
      4. Resolve comment.
    • Expected result:
      •  Comments with replies are resolved.
    • Dependencies & Impact:
      • Comments.
    • Support Request ID:
      •  2293506886
      • 2290695864
     
  • Fixed an incident where user update import via file or swagger failed.
    • Pre-conditions:
      •  N/A.
    • Steps to reproduce:
      • Upload user import via file.
    • Expected result:
      • Users are updated successfully.
    • Dependencies & Impact:
      • Internal API.
      • Users.
    • Support Request ID:
      • 2288327483
      • 2045077310 
  • Fixed an incident where widget order and dashboard layout do not show correctly for Portal Users.
    • Pre-conditions:
      •  N/A.
    • Steps to reproduce:
      1. Login as Portal Manager.
      2. Edit dashboard on Policy Portal and set required layout on left and right side.
      3. Set widgets to be available for everyone.
      4. Login as a portal user.
    • Expected result:
      •  As a Portal user, I see the same widget locations as it was set by Portal Manager.
    • Dependencies & Impact:
      •  Portal Dashboard.
    • Support Request ID:
      •  1942082585
  • Fixed an incident where Clausematch API (Metadata API) doesn’t return email and user uuid for user picker field.
    • Pre-conditions:
      •  N/A.
    • Steps to reproduce:
      1. Create user picker metadata field.
      2. Populate user to the given field in a document.
      3. Call Clausematch API to retrieve metadata information for the given document. 
    • Expected result:
      • Email and user UUID will be returned, so it can be used to match information.
    • Dependencies & Impact:
      • Metadata.
      • API.
    • Support Request ID:
      •  2050434100

Fix Patch - 137.13

  • Fixed an incident where documents on Policy Portal could not be exported to DOCX.
    • Pre-conditions:
      •  N/A.
    • Steps to reproduce:
      1. Open the document in Policy Portal.
      2. Click the Export to DOCX button.
    • Expected result:
      • Document is exported to DOCX.
    • Dependencies & Impact:
      • Document Viewer.
      • Export.
    • Support Request ID:
      •  2565203089

Fix Patch - 137.14

  • Fixed an incident where the metadata save reminder would not automatically closed once the metadata form is saved.
    • Pre-conditions:
      •  N/A.
    • Steps to reproduce:
      1. Edit metadata form.
      2. Click Save.
    • Expected result:
      • Metadata save reminder automatically closes.
    • Dependencies & Impact:
      • Document Editor.
      • Metadata.
    • Support Request ID:
      •  2555879801