...
If you know which amendments are likely to fail, you will be better placed to use the auto-apply feature effectively , without and to avoid creating problems in the resulting bill XML. The details of the known limitations listed below may should help you to avoid applying manage problematic amendments when creating an “as amended” version of a bill.
In future Lawmaker release releases we intend to fix or refine the behaviours listed here.
...
Amendments to rows, columns, and text in specific cells in tables can’t be auto-applied. We plan to extend auto-apply to handle these instruction types in future. For now, you will have to apply these amendments manually. If you do attempt to auto-apply amendments to tables, there is a slight risk that the amendment will appear to apply successfully but produce bad XML in your bill version.
Unhandled amendment wording sometimes causes amendments to be applied successfully but disappear from the editor
We have found that amendments which are worded slightly incorrectly sometimes appear to apply correctly (Lawmaker reports that they were successfully applied), but when the new bill version is opened in the Editor the amendment is missing.
There are two known cases of problematic amendments which suffer from this issue:
“leave out … and substitute” - amendments which use the word ‘substitute’ in place of ‘insert’ will appear to be applied successfully but may not show up in the Editor
amendments which leave out a phrase beginning with punctuation, such as leave out “, and any other costs”, will appear to be applied successfully but may not show up in the Editor
We are currently fixing the bug which prevents Lawmaker accurately reporting success and failure of auto-applied amendments such as these.
Amendments which insert or leave out a combination of sections/paragraphs and Parts, Chapters, and cross-headings
...