These actions are performed from a contract, not from the contract type. They are available to the contract's participants, as long as the contract is linked to a contract type.
Contract type automations (name, storage, participants, reminders, attached files) used to apply only when the contract was created. They can now be re-applied to an existing contract, so that it follows the up-to-date rules of its contract type.
In this article:
Understanding when automations apply
Contract type automations are applied or re-applied in the following situations:
When a contract is created.
When an import of signed contracts is published.
When the storage form of a signed contract is validated.
When the contract type is changed, from the summary sheet, from the storage form or from a filtered view.
On demand, using the Sync automations action on a contract.
Only the automations for which Tomorro has the required information are applied. The others are simply skipped: nothing is blocked, and no data is changed without your knowledge.
Syncing a contract's automations
Use this action when you have edited a contract type and you want an existing contract to follow the new rule.
Open the relevant contract.
Click the ⋯ in the top right corner.
Select Sync automations.
A confirmation window appears: Sync automations?
The rules of the current contract type are then re-applied to the contract. The storage location, name, participants and attached files may change.
The action only appears if the contract is linked to a contract type. It is not available to external guests.
Applying a different contract type
Changing the contract type of an existing contract automatically re-applies the automations of the new type.
From the summary sheet
Open the contract, then the summary sheet.
Click the Contract type field and select the new type.
A confirmation window appears: Update template automations?
From the storage form
On a signed contract being archived, the Contract type field of the form offers the same confirmation.
When you validate the storage form, a second window may appear: Contract location may change. It warns you that the contract will be moved according to the type's dynamic storage rule.
Changing the contract type of several contracts at once
From a filtered view or the repository, you can apply a new contract type to several contracts at once.
Select the relevant contracts using the checkboxes.
Click Edit in the action bar.
Choose the Contract type field, then select the new type.
A confirmation window appears: Update template automations?.
The automations of the new type are applied to each selected contract.
Sync the automations of several contracts at once
You can now re-sync contracts without changing their type, directly from the contract repository or a filtered view.
Select the contracts using the checkboxes.
In the action bar, open the ⋯ menu.
Choose Sync automations.
The sync runs in the background. A message confirms it has started, you can leave the screen, and the result is sent to you in the notification bell: how many contracts were processed, and the list of failed contracts if there are any.
Three things to know before you start:
100 contracts maximum per operation. Beyond that, the action is disabled.
All five automations run together: the name, the folder, the participants, the reminders and the attached files. In bulk, you do not choose which ones to re-apply: it is a full reset, not a selective touch-up.
Contracts without a contract type are skipped and appear in the failure list. If some contracts did not move, first check that they do have a type. The same applies to a contract you do not have access to.
When the sync moves a contract to another folder, the original folder is not deleted, even if it ends up empty. A bulk sync can therefore leave empty folders behind in the repository, to be cleaned up by hand.
Publishing an import before you have all the information
You do not have to fill in every field before publishing an import of signed contracts.
On publication, the automations for which the information is already available apply immediately.
Contracts with missing information are published anyway and remain visible under Incomplete contracts.
When you fill in the missing fields and validate the storage form, the remaining automations apply in turn.
A contract published without its counterparty or without its end date can therefore be renamed and stored correctly later, without manual work on each contract.
Knowing what is replaced and what is kept
The behaviour depends on the automation:
Contract name: recalculated from the type's dynamic name rule, then replaced.
Storage folder: recalculated, the contract is moved to the matching folder.
Participants: those that came from the previous type are removed, those of the new type are added.
Reminders: those that came from the previous type are deleted, those of the new type are created.
Attached files: those that came from the previous type are removed, those of the new type are added.
Everything you added manually to the contract is kept: participants invited by hand, custom reminders and files uploaded directly to the contract.
Knowing the limits
Editing a contract type does not update existing contracts automatically. You have to use one of the actions described in this article.
An automation whose required fields are not filled in is not applied. Fill in the fields, then run the sync again.
The contract name is only recalculated if the type has a dynamic name rule. Without that rule, the existing name is kept.
Do not want a specific automation to be applied? Remove it from the contract type, apply the type to the contract, then add it back to the type.