Summary
This is a minor patch release to fix a few high priority issues.
It was released on Wednesday 23 November 2022.
List of issues fixed
Bugs
Reference | Description | Note |
|---|---|---|
LMS-361/LMS-504/LMS-532 (SPT-1056/SPT-893) | changes lost when saving document | This fixes issues with save and auto-save where the provisions locked by a user were not contiguous. When that was the case, in some circumstances not all the changes would be saved. |
LMS-567 (SPT-1102) | cross-references not updating when there is a processing instruction in the middle or end of reference | This fixes an issue where page-line processing instructions within cross-reference (these are only present where the Bill version has been created using the auto-apply amendments feature) cause some cross-reference to update incorrectly. A similar issue was fixed in v.12.2 but didn’t cover all possible occurrences of the issue. |
LMS-536 (SPT-1126) | system performance issues due to infinite code loop | A system performance issue on 10 November was traced to code that, in very infrequent circumstances, could get stuck in an infinite loop. This prevents such loops in future. |
Validation update
In addition to these fixes, the validation rules in the Editor were updated to include an additional rule on x-refs.
The new rule will identify cross-references where the text of the cross-reference (e.g. “section 13”) doesn’t match what Lawmaker is expecting, based on the ID of the target provision stored in the XML. A mismatch like this is a sign that the Update X-refs function hasn’t, or may not, work as expected on this cross-reference and so the reference should be checked for accuracy and potentially re-inserted. (The underlying reason for the mismatch may be due to a user having manually updated the text of the reference at some point after it was made or it may be due to the reference having been affected by an issue that is fixed by SPT-1102 mentioned above or a similar issue fixed in v.12.2.)