|
|
| (15 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | 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.
| + | #REDIRECT [[Workflows_Overview#Task_Type:_Update_Standard_Field_Value]] |
| | | | |
| − | Standard fields on the following object types can be updated using this method:
| + | {{DeprecatedPage}} |
| − | * 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@'''
| |
| − | | |
| − | | |
| − | ==See Also==
| |
| − | * [[Update Custom Field Value]]
| |
| − | | |
| − | [[Category:Workflows]]
| |
This article is deprecated and the information contained within may no longer be correct.
