Release 109 - Fixes (Detailed)

The fixes from release 109 are detailed on this supplementary page.

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

  • Fixes
    • Policy Management
      • Fixed a bug that caused text styles not being applied to numbering in exported files
      • Fixed a bug that caused incorrect font family for numbers from list in DOCX exported files
      • Fixed a bug that caused text with spelling mistake not underlined in red when the spellcheck toggle is hidden on the screen
    • Policy Portal
      • Fixed a bug that caused draft document and template/snippet to be publishable on Portal
      • Fixed a bug that caused Activity tab to show user’s previous full name after their details changed

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


Fixes

Policy Management

  • Fixed a bug that caused text styles not being applied to numbering in exported files
    • Pre-conditions:
      • N/A
    • Steps to reproduce:
      1. Create new document
      2. Create several paragraphs, type some text in each of them and apply toggle numbering
      3. Navigate to Format>Text styles and select different styles for normal text and each heading - change font, size, color, apply bold, italic styles
      4. Click “Save” and close Text styles
      5. Apply normal text style for 1st paragraph and different heading styles for other paragraphs
      6. Export to PDF/DOCX/Audit report and check numbering styles in exported files
    • Expected result:
      • Bold and italic styles should be applied to numbering in exported files as well as color, size and font family
    • Dependencies and downstream impacts:
      • Document export
      • Numbering
      • Styling
    • Support Request IDs:
      • N/A
  • Fixed a bug that caused incorrect font family for numbers from list in DOCX exported files
    • Pre-conditions:
      • N/A
    • Steps to reproduce:
      1. Create document
      2. Add numbered list with some text and lines
      3. Select list and change font (Arial for example)
      4. Export the document to DOCX
      5. Open DOCX file and check the font family for the numbers
    • Expected result:
      • Font family for numbers should be Arial
    • Dependencies and downstream impacts:
      • DOCX export
      • Fonts
      • Numbered list
    • Support Request IDs:
      • N/A
  • Fixed a bug that caused text with spelling mistake not underlined in red when the spellcheck toggle is hidden on the screen
    • Pre-conditions:
      • N/A
    • Steps to reproduce:
      1. Сreate a document
      2. Turn on spellcheck
      3. Enter text with spelling mistake
      4. Resize the screen to hide the spellcheck toggle
    • Expected result:
      • After both, steps 3 & 4: the text with the mistake is underlined in red
    • Dependencies and downstream impacts:
      • Spellcheck
    • Support Request IDs:
      • N/A

Policy Portal

  • Fixed a bug that caused draft document and template/snippet to be publishable on Portal
    • Pre-conditions:
      • N/A
    • Steps to reproduce:
      1. Create document

      2. Publish document on Portal through swagger with PUT request on url /v1/portal/management/documents/access and request body:

        1{"isPublic":true,"documentId":"bfb7e70a-b503-491b-aaeb-426579006e3d","version":0,"forceRemoveAccess":false,"userAccessRoles":[],"groupAccessRoles":[]}

    • Expected result:
      • Response code is 400 or other error code
      • Document is NOT published on Portal (there should be a check if document version is released or not)
      • Publication date is NOT displayed on Info sidebar
      • Document is NOT displayed on Portal dashboard
    • Dependencies and downstream impacts:
      • Draft documents
      • Templates
      • Snippets
      • Publish document
    • Support Request IDs:
      • N/A
  • Fixed a bug that caused Activity tab to show user’s previous full name after their details changed
    • Pre-conditions:
      • N/A
    • Steps to reproduce:
      1. Open document in Policy Portal
      2. On the Activity tab, make sure document view events are tracked
      3. Change first (or last) name of current user
      4. See log of activities in the document opened in 1 step
    • Expected result:
      • User’s current full name shows in the Activity tab
    • Dependencies and downstream impacts:
      • Activity
      • Users
    • Support Request IDs:
      • N/A