If you would like to read the Master change notifications articles in chronological order, please see the previous article here: Master change notifications: 'Updates' tab.
Please note:
The 'Updates' tab is available in all subscription plan. The Master change notifications and 'Priority' filter are available only in 'Premium'. Find out more about Premium.
The platform notifies you about changes that have been made to the Master clauses you are using in your Project specifications. This article explains how the platform shows the Master article or clause alongside your Project article or clause and how you can use this view to apply the changes.
Master updates
In the 'Updates' tab within your Project, if you are focusing on notifications that have come from your Masters (which are indicated by a rosette) you can click on it to open up the 'Comparison previewer'. From here, you will see three main sections:
- Current clause: this displays your article or clause as it currently is on the far left, in blue, labelled 'Current clause'.
- Master changes: to the right is a purple middle column, which is labelled 'Master clause', which shows how the Master has been altered.
- Master update notes: to the far right is another purple column, labelled 'Master update notes', which displays a count of the number of 'Master update notes' that have been made, along with their priority level(s).
This is an image of the 'Comparison previewer' for Master updates, with the 'Master update notes' on the right-hand side.
Inform users of how the Master actioned the Lattira/NBS update
If an update has been actioned by a Master, it can now be shown. Otherwise, it is hidden.
If a Project clause has come from a Master (copied) that master will be able to see when there are available Lattira/NBS updates. They can then action those updates. At the Project level, you can see how the Master actioned the Lattira/NBS update. The Project author can then use that to make a decision at the Project level.
Here is an article/clause that has a Master article or clause (as indicated by the rosette):
This is an image of the 'Comparison previewer' for Lattira/NBS updates, with details of how it was actioned in the Master.
Here is a clause that does not have a Master article or clause (as indicated by a lack of a rosette):
This is an image of the 'Comparison previewer' for Lattira/NBS updates, but this clause does not have a Master article or clause.
Modifying articles and clauses
There is now the ability to modify an article or clause while it is being compared to the Master article or clause. There are several ways in which you can do this, which are outlined below:
This is an image of the 'Comparison previewer' for Master updates.
- You make your modifications to the 'Current clause' and then click 'Save': After clicking 'Save', you now must click the ‘Close’ button (or click the ‘X’ in the top right the modal), or you must click 'Done'. If you select 'Close' or the 'X', it will cause the update to remain in the grid, and any previous changes are shown when the modal is reopened. Alternatively, if you select ‘Done’, it will close the modal and remove the update from the grid.
- You make changes to the 'Current clause' but do not click 'Save': If you have unsaved changes and attempt to click 'X', 'Close', or 'Done', a warning modal will appear. It will also appear if you park the clause or mark it as complete.
This is an image of the pop-up that appears if you forget to save your changes in the 'Comparison previewer'.
Once the modal appears, you can then click ‘Save’ and the modal will remain open (see above for how to proceed). You could click ‘Discard’, which will discard any changes, and the modal will remain open. If you click only ‘Done’, it will trigger a warning that says your changes are unsaved. Clicking 'Cancel' will not save or discard anything, but will return you to the 'Comparison previewer'.
3. You decide you don’t want to make any changes and want to dismiss the update: You can either choose ‘Close’, which will cause the update to remain in the grid or 'Done' which will close the modal and remove the update from the grid. Clicking the 'X' button in the top right will have the same effect as selecting ‘Close’.
Copying row content
In the readable Master article or clause viewer, there is also now an icon/button that will allow you to copy changes from the Master to the current article or clause.
This is an image of the 'Copy row content' functionality.
In the previewer, copying chips (i.e. variable, manufacturer, product reference, placeholder or link chips) from the Master into the 'Current clause' destination is currently not available, but this is on our backlog for review.
To avoid losing information in variables, you can manually add the variable you need from the Master destination into your current clause context (e.g. Project). You can do this by:
- Creating an identical variable in the Project.
- Exporting the variable from the Master and importing it into the Project.
Once the variable has been added to the Project/destination, you can add it in the usual way: '~' shortcut.
This gif displays how copying row clauses works.
For further information, you can refer to the following variables articles:
We recommend manually adding all other chip variations into your current clause via the editor.
Parking/unparking a whole article or clause from a previewer
In the 'Current clause', there is now the option of parking or unparking the entire article or clause from the previewer to enable the user to action park/unpark updates from the Master. Within the 'You are editing header' is a parking icon. This icon appears as the letter 'P' surrounded by a circle. If you click this icon, you can park or unpark the clause as it does in the editor. Once clicked, a modal will appear asking if you want to park the clause.
This is an image of the functionality that allows you to park an entire clause.
Selecting 'Park' will park the clause and allow the previewer to remain open. A note will automatically be added and the update will be removed from the grid when the user closes the previewer window. Selecting 'Cancel' will cancel parking and will return the user to the previewer.
This gif displays how to park individual clause rows.
Below are two images, one of an entirely unparked clause, and another of an entirely parked clause.
This is an image of an entirely unparked clause.
This is an image of an entirely parked clause.
If the Master clause is parked, it will display our usual parked styling (italic and struck through). This will also be the case if it is marked as complete, in which case it will display the green 'Complete' overlay. Users will still be able to use the 'Copy row content' functionality when the Master clause is marked as complete.
Automatic 'Update notes' to articles and clauses marked as complete or incomplete
Notifications are a crucial part of a Master author's workflow. Every time you park or unpark a clause, as well as when you mark a clause as complete or uncomplete, the platform will automatically add an 'Update note'. This is because the action of parking and marking as complete happens outside of the clause, so the user is unable to use the 'Save' button to 'Add an update note' manually to notify copied-to Projects/Masters.
Manipulating rows
On the left-hand side, within the current clause, there should be three dots that appear alongside each clause row. Clicking this will cause a menu to appear that will allow you to manipulate the clause by adding or duplicating a new row or adding a table. Therefore, nearly all the functionality from the editor is now also in the 'Comparison preview'.
This image shows the menu that appears when clicking the three dots that appear alongside each clause row.