Difference between revisions of "Workflow Task Type: Update Standard Field Value"
| Line 2: | Line 2: | ||
Standard fields on the following object types can be updated using this method: | Standard fields on the following object types can be updated using this method: | ||
| − | * | + | * {{l1}}s |
| − | * | + | * {{l2}}s |
| − | * Companies | + | * [[Organizations|Companies]] |
| − | * | + | * [[Contact]]s |
| − | * Transactions | + | * [[Transactions]] |
These values can be hard-coded values, or can also use variables. | These values can be hard-coded values, or can also use variables. | ||
Revision as of 09:53, 26 September 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:
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 standard field, for example the "Start Date" standard field:
- @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 a standard field when a record is created)
- @system.Submission Deadline@
