-
Notifications
You must be signed in to change notification settings - Fork 23
Request Builder
"Request Builder" at the moment is used as a part of 2 steps - "UWT: Bulk Operations - Update Records" and "UWT: Bulk Operations - Distribute Action".
For "UWT: Bulk Operations - Update Records" request is used as a template using which every record from chosen set is updated.
For "UWT: Bulk Operations - Distribute Action" request is used as a container for Action's inputs.
There are 2 ways to define request - create request based on record fields (it takes defined fields from source record and puts it into request) or manually populate values field-by-field.
Here is how to create request based on record fields:
- Add "UWT: Request Builder - Build Request from Entity" step to your workflow:
- Click "Set Properties" button to configure step: "Source Entity" is a record reference that is used as a source for request builder. "Source Entity Fields" is a list of fields that will be taken from entity to request separated with |. "Destination Request Fields" is the list of names to be added to "Request" object. "Request" is optional parameter that can accept previously initiated in other workflow step "Request" object:
Here is not you can add field-by-field to request object:
- Add one of "UWT: Request Builder - Set Field" to your workflow:
- Click "Set Properties" button to configure step: pass value you want to add to Request using "Field Value" input - it could be both constant you enter into the field or value from context (like value from entity field). "Field Name" is the name with which field is added to request. "Request" is optional input into which you can pass "Request" created/extended on other workflow step.
If you want to add field with "null" value use "Set Field to Null" Step.
If you want to add lookup field - use "Set Lookup Field" and pass to "Field Value" Record Reference value.
If you want to add optionset field - use "Set OptionSet Field" and pass "Whole Number" value to "Field Value".