8,849
edits
Changes
no edit summary
*Flexibility offered through custom field configuration (i.e. can be used as a one-time store and not allow users to edit the default field value and can be hidden/shown on page, or alternatively allow users to edit the default field value)
*Visibility (i.e. users can see the field and verify the default value before it is actually saved and stored into the field)
==Calculated Value Field==
*Sequential processing (i.e. on page load, each [[Custom Field Type: Special – Calculated Value|Calculated Value]] field is evaluated in order of their display order)
*Visibility (i.e. users can see the field and verify the default value before it is actually saved and stored into the field)
==[[Value Stores To]]==
*Synchronization (i.e. in the case that you have multiple fields that represent the same data set this can be used to synchronize the values between these fields)
*Transparency (i.e. works behind the scenes)
==[[Template / Type Formula|Template Formula]]==
*Sequential processing (i.e. saving an L3 results in L3 formulas, then L2 formulas, then L1 formulas to be run consecutively. Also within a template formula block, each individual line is processed consecutively thus allowing you to update a field value in one line, and then reference the new field value in the next line)
*Transparency (i.e. works behind the scenes)
==[[Workflow Task Types|Workflow Task]]: [[Update Custom Field Value|Update Custom Field Task]]==A way to update a field value behind the scenes. This is configured as a task within a [[:Category:Workflows|Workflow]]. This requires the Workflow to be triggered against the object whose field you wish to update.===Advantages:===
*Ability to update different areas other than the form the user is directly on
*Server side validity (i.e. can be used for date/time functions to reference server time at exact time of Workflow run time)
