Field Updates in Mobile

[githubbob42]

Mingle Card: 5790

Analysis

https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_workflow.htm

https://developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/tooling_api_objects_workflowfieldupdate.htm

Sample REST API Calls:

/services/data/v42.0/tooling/sobjects/WorkflowRule/describe

/services/data/v42.0/tooling/query?q=Select+Id,Name,TableEnumOrId+FROM+WorkflowRule

/services/data/v42.0/tooling/sobjects/WorkflowRule/01Qi00000005AM0EAM

/services/data/v42.0/tooling/sobjects/WorkflowFieldUpdate/describe

/services/data/v42.0/tooling/query?q=Select+Id,Name,LookupValueId+FROM+WorkflowFieldUpdate

/services/data/v42.0/tooling/sobjects/WorkflowFieldUpdate/04Yi00000005Z01EAE

Notable Fields:

• When to trigger:
  • WorkflowRule.Metadata.triggerType – onAllChanges, onCreateOnly, onCreateOrTriggeringUpdate
  • see: https://help.salesforce.com/articleView?id=workflow_rules_define.htm&type=5
• Conditions to match (one of the following):
  • WorkflowRule.Metadata.formula
  • WorkflowRule.Metadata.criteriaItems
• WorkflowRule.Metadata.actions - actions of type “FieldUpdate”

“Default field value” feature on new forms will need to augment functionality provided by workflow field updates:

1. Workflow field updates occur after the record is saved. It’s too late to use for defaulting field values.
2. Workflow field updates that have conditions that rely on existing values won’t work because the form is blank
3. default values derived from user context will require some way to pass the current user context down to the conditions/formula defining the default value
4. conditions/formulas used to define a ‘default value’ will need to be parsed so we can sync necessary data that may not be automatically downloaded via a relationship to a base object

Workflow field update information will need to be synced at the same time new metadata/data is synced to ensure needed fields/data are present.

New Custom Object

The Salesforce Workflow Field Updates feature does not meet a basic business case we are trying to solve: default values in forms for any field type

• use Salesforce Custom Metadata objects to manage settings that’s a superset of workflow field update settings
• https://help.salesforce.com/articleView?id=custommetadatatypes_limits.htm&type=5
• Salesforce caps Custom Metadata objects at 10MB total
• normalize data to minimize overall size

Test Plan

Stories

{{ table query: SELECT Number, Name, Owner, Status, 'Story Points' WHERE Type = Story and Feature = THIS CARD ORDER BY Status }}

[githubbob42]

Patty : 10/30/2018 10:27 CDT Documented as New Feature in 10/25/2018 Mobile release notes.