Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with visual-workflow
Search options not deleted
user 76909
Visual Workflow allows administrators to build applications, known as flows, that guide users through screens for collecting and updating data. For example, you can use Visual Workflow to script calls for a customer support center or to generate real-time quotes for a sales organization.
5
votes
1
answer
488
views
sfdx force:source:pull doesn't retrieve FlowVisibilityRule
I created a Flow with several conditional rendering of screen components. When I pull the source from the scratch org, the metadata of the flow is missing the FlowVisibilityRule for all the components …
- 191
3
votes
sfdx force:source:pull doesn't retrieve FlowVisibilityRule
Ok, when I set the API version to 47.0 and rebuild it in a newly created scratch org, the visibility rules for the screen components have been pulled.
This is confirmed by looking at the Metadata AP …
- 191