|
|
| (13 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | The '''Update Custom Field Value''' workflow task type can be used to write values to custom fields on the object against which the Workflow is triggered.
| + | #REDIRECT [[Workflows_Overview#Task_Type:_Update_Custom_Field_Value]] |
| | | | |
| − | These values can be hard-coded values, or can also use [[variables]].
| + | {{DeprecatedPage}} |
| − | | |
| − | 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 one year from the current date (for example, for a progress report that is due one year after the application is submitted):
| |
| − | * '''<!--@sscalculation(date_add(CURDATE(), INTERVAL 1 YEAR))-->'''
| |
| − | | |
| − | To populate with a [[System Variables|system variable]] value (for example, to put a submission deadline into a custom field when a record is created):
| |
| − | * '''@system.Submission Deadline@'''
| |
| − | | |
| − | ==See Also==
| |
| − | * [[Update Standard Field Value]]
| |
| − | * [[Workflow Task Types]]
| |
| − | | |
| − | [[Category:Workflows]]
| |
This article is deprecated and the information contained within may no longer be correct.
