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 matter member (e.g. the Service Account, which owns the flow and is authenticated into the LawVu connector in Power Platforms). You must be a member of the matter record before the action, which updates the name/field. You can configure in LawVu the Automation Service Account to be added to all new matters in the settings for each relevant matter type, or you can add an action to this template to “add user to a matter,” e.g. after the get matter step.

• Update our suggested matter naming convention (see below). This is set out as a string of fields in the variable NewMatterName.

• After completing the flow, update the status message posted on that matter record. This is the last action in the flow and acts as a notice that the matter 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.

Combine this workflow with the LawVu setting for simple ticketing. If you do this, business users creating a matter will NOT get a prompt to name the matter or be able to select their lawyer (matter manager).

Matter naming convention

When considering a naming convention for matters or contracts in LawVu, you can 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 matter types (and you could design different ones per type) is:

year month (in words) - matter type - department - matter owner