This workflow renames all new contract records immediately after they are created.
Many organizations want to enforce specific naming conventions for contract records. An appropriate record name gives users quick context and improves search results. Some organizations use a section header within LawVu to prompt users to use a particular naming convention when creating the contract record, however this requires manual effort and is often ignored.
Trigger
Action(s)
How it works
1
Workflow is triggered when a contract record is created in LawVu.
2
Retrieve information about that contract record and construct your desired naming convention.
3
Rename the contract record with the new contract name.
4
(Optional) Add a status message to the LawVu contract record to confirm that an automation has renamed the contract record with the naming convention.
Getting started
You can use this template straight away. Below are some optional modifications you can make.
Optional modifications
Add a step early in this template to add your user as a member to the contract (e.g., the Service Account that owns the flow and is authenticated into the LawVu connector in Power Platforms). You must be a member of the contract record before the action, which updates the name/field. You can configure the Automation Service Account in LawVu to automatically be added to all new contracts in the settings for each contract type, or add an action to “add user to a contract” after the get contract step.
Update our contract naming convention below, outlined as a string of fields in the variable NewContractName.
After completing the flow, update the status message on the contract record. This final step acts as a notice that the contract has been renamed.
Add conditions to the flow - e.g. if you wish for your naming convention to only apply to particular matter types or matters with particular characteristics.
Contract naming convention
When considering a naming convention for matters or contracts in LawVu, you might want to string together several fields from LawVu. Our naming convention flows include a function to remove blanks and consecutive dashes that might appear in the name, such as when the department field is left blank during record creation.
Our suggested naming convention for all contract types (and you could design different ones per type) is:
year month (in words) - contract type - other party - department - contract owner
Details
Pricing
Free
Author
LawVu
Categories
Contracts
Naming
Power Automate
Requirements
Power Automate, part of Microsoft 365 Power Platform, is a low-code automation platform which allows users to create bespoke workflows that customise and connect their legal workspace, creating effiicency through automation and standardized workflows.
The LawVu connector for Power Platform is required to use this workflow template.