Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Version 16.0.0 of Lawmaker introduces some new features, updates the look and feel of the Editor and includes some bug fixes.

It was released on 23 March 2024.

New features and improvements

...

There is now an option when generating a PDF of a document (e.g. Bill, SI, amendment list) to produce a large print version. That will produce a PDF where all the text is 20pt Arial to aid readability. This is a general features designed to work across all document types but there may still be some edge cases where the output isn’t perfect (e.g. numbers may overlap with text in certain circumstances and text in tables may overlap between cells) and we’ll be improving this feature in future versions based on additional feedback.

See Generating and viewing a PDF .

...

Generation of PDFs and publishing documents in the background

...

  • Generating a PDF (from the Project tab or within the Editor)

  • Publishing a document

  • Importing a document from legislation.gov.uk

A notification will appear at the bottom of the screen indicating that the operation is in progress. When the operation is finished, you’ll see a another notification pop up at the bottom of the screen. In the case of PDFs, you can click on the notification to open the PDF.

...

New version of Oxygen Web Author

...

  • the design of the panels at the right hand side (e.g. Document Checks and Document Information) has changed so icons are used instead of names.

  • Find and replace (ctrl+F) now appears as a panel on the right hand side rather than as a dialog box. makes it easier to see both the search panel and the document with results highlighted. Moreover, it makes it possible to see all search results at a glance without having to scroll through the document.

  • A Tags Display Mode switcher was added directly in the breadcrumb bar to make it easier to change the amount of Tags that are displayed when exploring the document structure. part of breadcrumb bar showing tag display mode switcher on the leftImage Added

Upgrading the version of Oxygen also resolves some security flaws present in earlier versions.

[External X-refs

The Tag X-ref function will now tag some external references as well as internal references.

By “external reference” we mean a reference to an Act, secondary legislation or EU legislation.

The references that are currently handled are those references where the Act or SI title is included as part of the reference, e.g. “section 5 of the Criminal Justice Act 2000” or “paragraph (1) and (2) of regulation 45 of the Procurement Regulations 2023”.

The feature uses the data behind legislation.gov.uk to lookup and identify the appropriate legislative documents.

External references that are not currently handled (but will be tackled in later releases) include:

...

References that refer back to a previously mentioned Act or SI etc., e.g. “section 7 of that Act”

...

References that implicitly external due to their context but don’t directly include the title of the Act or SI etc., e.g. references in provisions following a statement like “Section 32 of the Criminal Justice Act 2000 is amended as follows.”

...

screenshot of the Lawmaker Editor with the side panel icons highlightedImage Added

UK and Scottish Bills - Order of Consideration validation

...

To cancel the save, click on the banner at the bottom of the screen. The banner will change when the save operation gets to a point when it can no longer be cancelled.

...

When you cancel a save: you will be taken back to the Editor, your document will be as it was before the save, and you will be able to make further changes to it. The save button should be activated allowing you to restart the save operation.

This is particularly to help in the situation reported by users in some organisations that the save operation gets stuck at 0% or later but it may also be useful where you have triggered a save on a large document by accident and don’t want to wait until it is complete.

As part of these changes, we’ve also improved the robustness of the save operation generally so that the progress bar will be skipped if it is likely to cause problems (due its reliance on Websocket technology which can be blocked in some networks).

See Saving your document

Auto-application of amendments - checking for page/line information

...

  1. Any manual page breaks that have been inserted in the document will now show up in the document check panel to make it easier to find and delete them when no longer needed - 

    Jira Legacy
    serverSystem JIRAJira
    serverId18b81902-662f-326c-8748-cd8a7213ac3e
    keyLMS-913
    .

  2. A warning will appear if a table cell in a Bill contains complex content such as a quoted structure or a nested table because it may affect line numbering.

  3. Definitions that contain two separate text paragraphs will be highlighted as it is likely that these were intended to be two separate definitions. This can sometimes happen when a user copies and pastes the content of a definition or uses shift+Enter to insert an additional paragraph.

  4. Empty definition elements, where everything has been deleted other than the definition element itself, are now highlighted and a quickfix option to delete the empty element is provided (LEGDEV-6125).

  5. Placeholders that contain text when they should be empty are highlighted and quickfix . This happens when attempts are made to overwrite the content of placeholders in a document that show key document info (e.g. the document title). It can also occur when the placeholders in templates that should disappear when you type into them don’t disappear for some reason. Quickfix options are provided to resolve the issue (by either deleting deleting the placeholder element text or deleting the textplaceholder element, depending on the specific issue).

  6. Provisions containing opening words but no child provisions (e.g. a subsection with no child paragraphs) are highlighted with an option to convert the opening words back to normal content. Usually Lawmaker will do this automatically but the document check provisions provides an additional way to pick up any cases left behind. (LMS-1642)

  7. Any provisions that contain two number elements rather than just one are highlighted and a quickfix provided to delete the second number element (

    Jira Legacy
    serverSystem JIRAJira
    serverId18b81902-662f-326c-8748-cd8a7213ac3e
    keyLMS-2019
    ). All provisions should have a maximum of one number element but sometimes by copying and pasting a provision can end up with more than one.

  8. Highlight cases where an unnumbered paragraph has been used to create something looking like a quoted structure (textual amendment) a numbered paragraph when a numbered provision type (e.g. a “paragraph (a)” or “subsection (1)”) should have been inserted instead (LEGDEV-6090).

Fixes and updates to existing rules

  1. The check for correct numbering format now works correctly in relation to paragraphs within EU articles(

    Jira Legacy
    serverSystem JIRAJira
    serverId18b81902-662f-326c-8748-cd8a7213ac3e
    keyLMS-2295
    )

  2. Schedule numbers are now allowed to be in the format of "Appendix x" as well as "Schedule x"  (

    Jira Legacy
    serverSystem JIRAJira
    serverId18b81902-662f-326c-8748-cd8a7213ac3e
    keyLMS-1807
    )

  3. Fixed the issue causing false positives where amendment's stage doesn't match the Consolidated List stage because of the addition of the Bill number to the list stage version.

  4. Fixed an issue causing false positives in relation to two lists back-to-back in an SI’s explanatory note ( [LMS-2302] Explanatory notes and an error message - Jira Service Management (atlassian.net))  

  5. Errors like “"Advisory: There is only one schedule so its number should be "Schedule" not "Schedule 3" no longer show when opening a single schedule with Edit portion of document feature. The x-ref rule that checks citation matches the reference metadata has been updated to cope with external references.

New organisations

The following organisations has have been added to Lawmaker:

  • The Church of England (SPT-1556)

  • The Attorney Generals Office (SPT-1440)

Bug fixes

can not keyFixed an issue in Scottish Bills that caused line numbering to stop in the PDF if the document contained a quoted structure with an indent set to “indent -1”

Fixed an intermittent issue that could cause submission of a amendment list containing a large number of amendments to stop part-way through. The fix should also improve performance when submitting a large number of amendments.

keyFixed an issue that led to the auto-apply amendments feature failing entirely in certain cases where the XML markup of the amendment or Bill provision was complex.

as being a tracked change.

keythe case of a Schedule inserted within a quoted structure in a Schedule.

Fixed an issue preventing users from updating an amendment to “on hold” because the system has retained a lock on the amendment despite it being deleted from all amendment lists.

keyPrevented amendments which span a quoted srtucture from being auto-applied because it leads to corrupt XML. (This is a temporary fix until a way is found to make amendments of this type auto-apply correctly.)

Issue key

Status

Summary

User support ticket

SPT-1579

QA Ready

Fixed an issue where UK amendments created before an "as introduced" bill is published

cannot be viewed in the Amendment Manager tab and therefore can’t be submitted

LMS-2351

SPT-1559

Done

Line numbering: line numbers stop appearing in th if in tbodyFixed an issue that could stop line numbering appearing in a PDF of a Bill if it contained a table with a heading row somewhere other than the top of the table.

SPT-1547

Done

Quoted structure with indent -1 causes line numbering to fail in Scottish Bills

Jira Legacy
serverSystem JIRA
serverId18b81902-662f-326c-8748-cd8a7213ac3e

LMS-2471

SPT-1545

QA Ready

Submission of amendments stopped part way through list

Jira Legacy
serverSystem JIRA
serverId18b81902-662f-326c-8748-cd8a7213ac3e
key

LMS-2351

SPT-1520

QA Ready

Auto-apply fails on certain amendments

Jira Legacy
serverSystem JIRA
serverId18b81902-662f-326c-8748-cd8a7213ac3e

LMS-2288

SPT-1494

QA Ready

Individual Fixed an issue where individual whitespaces inserted in tracked changes not mode didn’t shown in the PDF of SI

Jira Legacy
serverSystem JIRA
serverId18b81902-662f-326c-8748-cd8a7213ac3e
key

LMS-1835

SPT-1460

Done

Fixed an issue with Following text after a quoted structure which was misplaced in the PDF in schedules inserted within schedules

Jira Legacy
serverSystem JIRA
serverId18b81902-662f-326c-8748-cd8a7213ac3e

LMS-1834

SPT-1340

Done

Cannot set 'Deleted' amendment to on hold

Jira Legacy
serverSystem JIRA
serverId18b81902-662f-326c-8748-cd8a7213ac3e
key

LMS-1334

SPT-1267

QA Ready

Amendment spanning quoted structure incorrectly applied

Jira Legacy
serverSystem JIRA
serverId18b81902-662f-326c-8748-cd8a7213ac3e

LMS-305

SPT-678

Done

Change to the duplicate/checksum rule for imagesFixed an issue that prevented different images with the same filename being inserted into documents in different projects