There are five options to trigger Rules and apply Actions using Automation: 'On Creation', 'On Edit', 'On all Tasks Completed', 'Budget Threshold Reached' and 'On Contract Value Change'.
Choose 'On Contract value Changed' and press [Save], you will then be presented with the 'Action' tab to add your Actions.
Fig 1 - Contract Value Change option
The 'On Contract value Change' trigger will apply your rule when you make a change to a Contract value.
- If you create a 'On Contract Change' rule then the rule will trigger and each time an edit is done that affects the Contract value.
- If you require a rule to trigger when a Contract is first created, for example, to add an action when it is a high value Contract, then you must use the 'On Creation' trigger instead.
An update to a Contracts value can be made in 3 ways:
- Directly updating the Contract value field
- Updating the Term value
- Adding/removing Financial records
So your Rule could be:
'On Contract value Change' of a <Contract> <=>£40K>, create a <Task> for the <Contract Manager>.
If you do not add any Criteria to your Rule then it will apply to all of your Entity records, if you wish the Rules to apply in certain circumstances then you must specify when the rule should apply using the Criteria.
Contract Value Criteria
There are 5 main field options for selecting Contract Value criteria
Fig 2 - Contract value Criteria options
These fields correlate with the options displayed in the Contract Value field:
[Value] Has value
Fig 3 - [Value] Has Value field
This field can be used for a Rule to trigger if a Contract has a value update of 'Is', 'Has changed from' or 'Has changed to' 'No Value'
Fig 4 - 'No Value' Contract value option
TIP: If you have the 'Enter value' option selected but it is blank, this is interpreted and 0.00 and is a explicit numeric value. A rule based upon 'Has Value = 'Is Yes' will only trigger for contracts where the 'No value' option has been set.
[Value] Lifetime value
Fig 5 - [Value] Lifetime value field
This field can be used to trigger a Rule if the' Lifetime value' has an update of 'Is', 'Has changed from' or 'Has changed to'
Fig 6 - 'Lifetime' value display
[Value] Annual value
Fig 7 - [Value] Annual Value field
This field can be used to trigger a Rule if the 'Annual' value has an update of 'Is', 'Has changed from' or 'Has changed to'
Fig 8 - 'Annual' Contract Value display
[Value] Summary value once
Fig 9 - [Value] Summary value once field
This field can be used to trigger a Rule if the 'Once' value has an update of 'Is', 'Has changed from' or 'Has changed to'
Fig 10 - 'Once' value display via Contract value field
Fig 11 - 'Once' value display using financial data
[Value] Summary value annual
Fig 12 - [Value] Summary value annual field
This field can be used to trigger a Rule if the 'Annual' value has an update of 'Is', 'Has changed from' or 'Has changed to'
Fig 13 - 'Annual' value display via Contract value field
Fig 14 - 'Annual' value display using Financial data
Examples
Below are a few examples of Rules that can be created to trigger a specific Task when changes to the Contract value are made.
Fig 15 - Example Automation Rules
Advanced Contract Value calculations
When a Contract Value is calculated, the Annual, Lifetime, Summary and Once values are always calculated where they can. This calculation allows you to use the 'Advanced display options' in the Contract value screen to display the Contract Value in various ways.
Fig 16 - Advanced Contract value options
Regardless of the Contract Value you have entered or calculated via Financials, the Summary, Lifetime and Annual values are also calculated so they can be displayed if required. With this in mind multiple rules could be triggered for the same action.
I could create a Contract with a Once value of £30K over 3 years, in the background the system calculates that its Lifetime value is £30K and its annual value is £10k.
If I had the below rules created then all would trigger
- Rule 1 - Once value is £30k
- Rule 2 - Lifetime Value is =>£20k
- Rule 3 - Annual value is =<£10k