This article lists the issues currently known in the Compliance and Requirements area, identified during and after the latest release. Fixes are in progress for all of them.
Where a workaround is available, it appears in a highlighted box under the issue. If you come across something not listed here, contact support and quote the reference code shown next to the issue.
Content & validity
We are aware that there might be some structural issues caused by the new way of presenting content. Some content was originally added to fit how the system previously worked. Our Compliance Libraries team has reviewed the current content and is already working to fix these imperfections in newer revisions of the respective libraries.
Existing duplicate requirements may appear out of order
With the new structure, duplicate requirements can now be maintained. In some cases these already existed in the requirement data and will now be displayed. If you see existing duplicate requirements out of order, they will be corrected with the next authority update.
New duplicate requirements are still being added
Creating duplicate requirements is a completely new feature. Our Compliance Libraries team needs to readjust the content to add these duplicates for each library, which may take some time.
| Workaround: Links can be created to the duplicates but be aware that the connections will become outdated when our compliance team updates structure and dates |
Missing images - COMPLIANCE-108
Images may sometimes appear broken. The image is not missing (the system still indicates that it exists), but it displays as broken. This issue is on our highest-priority list and we expect to deploy a fix as soon as possible.
Connections & requirement actions
Actions can reach collapsed sub-requirements - MANUALS-9989
When you apply an action, such as adding a connection, owner, or task to a parent requirement and choose “Add for sub-requirements,” the action can also be applied to child requirements that are collapsed and were meant to be excluded.
| Workaround: Expand the requirement structure before applying a bulk action so you can see exactly which requirements will be affected. |
In the checklist view, after using Edit connection and closing the dialog, then selecting one or more requirements with the checkboxes and choosing Actions > Add connection, the dialog can still show “Edit connection.” In this state, a new connection may not be added, or the action may fail when several requirements are selected.
| Workaround: Reload the checklist before adding a connection so the dialog resets. |
Even when a requirement is collapsed in the library, it is currently still possible to add a connection to one of its collapsed children from the manual view.
| Workaround: Avoid adding connections to collapsed requirements from the manual view until this is fixed. |
Wrong duplicate text shown when connecting to a duplicate - MANUALS-9983
When adding or editing a connection to a duplicate requirement from the manual view, in Monitor > Compliance, the regulation text shown can be from the first duplicate.
| Workaround: Clicking Regulations from the references sidebar will still show the correct regulation text. |
“(no heading)” connections show no heading text in the library view - COMPLIANCE-108
If the heading dropdown is left empty when you save a connection, it is assigned an unintended “(no heading)” value, which then shows no heading text in the library (both Regulation and Checklist views).
| Workaround: When setting a connection’s heading, select [No heading] explicitly rather than leaving the dropdown empty. |
When there are many deleted requirements with connections, “Remove all links” on the Deleted filter only removes links for the batch currently loaded on screen.
| Workaround: Scroll to load more requirements and run “Remove all links” again, repeating until all links are cleared. |
Cannot delete a connection when ownership is restricted but no owner is assigned - COMPLIANCE-42
When “Allow only requirement owners to manage connections” is turned on but a requirement has no owner assigned, deleting a connection is currently blocked, even though anyone should be able to manage it in that situation.
| Workaround: Assign a requirement owner, then delete the connection. |
In the Edit connection dialog (Regulation and Checklist views), the assigned Responsible person may not show until you click into the dropdown, because it loads slowly. The same can occasionally happen for Requirement Owner.
| Workaround: Click into the Responsible or Owner dropdown to load and confirm the assigned person. |
A deleted connection stays visible for a moment - COMPLIANCE-38
After deleting a connection, it can remain visible briefly before the list refreshes. Clicking delete again during that short window causes an error.
| Workaround: Wait for the list to refresh after deleting before taking any further action, and avoid clicking delete twice. |
Nested GM / AMC / Appendix structures under review - COMPLIANCE-34
We are reviewing edge cases in deeply nested structures, for example, an Appendix nested under a GM, or an AMC under an Appendix, to confirm that “Add to children” and collapsing behave as expected. If you work with these structures and notice anything unexpected, let support know.
“Not applicable” status & warnings
Changed requirements set to “Not applicable” do not show a warning in the interface - COMPLIANCE-103
When a requirement is set to Not applicable and the requirement later changes, the resulting warning appears in the checklist export but not in the on-screen Regulation and Checklist views. These requirements are also not caught by the “Has warnings” filter.
| Workaround: Use the checklist export to identify Not applicable requirements that carry a warning. |
You can apply Not applicable to sub-requirements in bulk, but removing it currently has to be done one requirement at a time. Support for removing it across sub-requirements is being added.
| Workaround: Remove the Not applicable status one requirement at a time, or go to Checklist, select the requirements using the checkboxes, choose Actions > Mark not applicable, move the Not applicable slider to off, and update. |
Checklist & printing
When printing the checklist, the manual revision name is not shown after the manual name in the “Manual / Heading” column (it should read “Manual name - Revision name”). This affects the printout display only.
| Workaround: Use Export to Excel for the time being if the manual revision needs to show in the exported data. |
Connections may not display for requirements with many connections - COMPLIANCE-47
In the checklist, if a requirement has more connections than fit in the visible area, some may not appear until the full requirement row is in view. When a row is too tall to fit on screen, connections may not show at all, or only at certain scroll positions.
| Workaround: Scroll so the full requirement row is visible, or zoom the browser out so more fits on screen. |
Importing requirements
Duplicate requirements may appear, sometimes out of order - COMPLIANCE-98
With the new structure, duplicate requirements can now be maintained. In some cases these already existed in the requirement data and will now be displayed. If you see duplicate requirements out of order, they will be corrected with the next authority update.
A changed requirement can appear as both deleted and added on import - COMPLIANCE-12
When you import a file in which an existing requirement’s text has changed, that requirement can be shown as both deleted and added instead of simply changed. This is resolved for the actual import. The test/preview import may still display it as deleted.
| Workaround: Proceed with the actual import. The result is correct even if the test/preview shows “deleted.” |
Modules, tasks & display
Cannot select a single library in Compliance module settings - COMPLIANCE-25
In the Compliance module settings, the libraries dropdown currently only shows “All,” so an individual library cannot be selected. Existing modules already scoped to a single library continue to work and update normally. The issue only appears if you try to change a module’s settings.
| Workaround: Avoid changing settings on modules already scoped to a single library, and contact support if you need to create or reconfigure one. |
Requirement dropdown empty when adding a comment from a task - COMPLIANCE-27
When you click Add comment in the Edit task view, you are redirected to the filtered My tasks view and the requirement dropdown can be empty. It should list the library’s requirements with the task’s requirement pre-selected. A related tab-title display glitch is already fixed.