Difference between revisions of "Workflow Task Type: Update Standard Field Value"
(→See Also) |
|||
| Line 10: | Line 10: | ||
These values can be hard-coded values, or can also use variables. | These values can be hard-coded values, or can also use variables. | ||
| − | You can also use | + | You can also use MySQL syntax to manipulate values using [[sscalculation]] |
Revision as of 14:15, 22 August 2013
The Update Standard Field Value workflow type can be used to write values to standard fields on the object against which the Workflow is triggered.
Standard fields on the following object types can be updated using this method:
- Level 1s
- Level 2s
- Companies
- Contacts
- Transactions
These values can be hard-coded values, or can also use variables.
You can also use MySQL syntax to manipulate values using sscalculation
Examples
To populate the current date (for example, a workflow triggered at status Submitted could be configured to put today's date into a custom field called Date Submitted:
- @date(currentdate)@
To populate a date 1 year from the current date (for example, for a progress report that is due 1 year after the application is submitted)
- <!--@sscalculation(date_add(CURDATE(), INTERVAL 1 YEAR))-->
To populate with a system variable value (for example, to put a submission deadline into custom field when a record is created)
- @system.Submission Deadline@
