New answers tagged visual-workflow
0
Christoph. Generic SObject and SObject[] are not yet supported at the interface between LWC and Flow (TLDR: You can't get there from here). We're working on it right now, though, and hope to get it into Summer '20. You can get an early taste for some of the experience by looking at how we implemented it for Apex Invocable Actions in Spring '20
We don't ...
0
I have a boolean variable in the subflow called {!continueMaster} which is set to false if it fails. Once the subflow completes (or fails), it is assigned as an output value to another similar variable in the Master Flow. Then, just decision against that variable in the master after the subflow component and stop if it does not equal true.
1
I ended up opening a case with Salesforce.
The case was escalated and their R&D team eventually confirmed that it is a bug. Bug Number: W-7124447.
0
In the worst case scenario, you could just serialize the object, then store that:
var response = component.get("v.equipmentList");
var newList = component.filter(row => row.Quantity > 0);
component.set("v.selectedEquipmentList", JSON.stringify(newList));
In the next component, you'd have to deserialize it again.
0
The core Send Email action doesn't support an arbitrary email address for the sender - the only possible senders are the user running the flow, the default workflow user, or an organization-wide email address.
Changing the Sender Type will change the default (the current user, as you're seeing) to one of the other possible sender types. The Sender Address ...
0
The formula in the validate input section will not fire unless there is a value in the component. So a blank text box will not even bother to check the formula.
0
I believe this is a bug with Salesforce. It can be easily replicated by doing the following:
Create a screen based flow
Create a screen and drop on a Radio Buttons Control
Hook it up to a Picklist Choice Set that reads a picklist from an object(this is important as the bug only happens when reading choices from Salesforce and not when displaying choices ...
5
In short: I managed to do this in Apex by using apex-mdapi AFTER I updated the code to support flowAccesses. - here's the github commit with changes needed to support it. This is the only way I can see to do this through Apex as you need to hit the Metadata API.
Very Long Version
I didn't see anything within SOQL or Tooling API that can be used. It seems ...
0
You could try to implement your flow within a lightning component that is loaded via lightning:out into the VF Page.
I cannot attest to performance or permission challenges, though, since I haven't tested this approach. In any case the flow would run in Classic Styles, not Lightning Styles.
0
Got this to work by doing a loop of the created cases and assigning the case numbers of those to a text variable and passed that variable to a text template. On the final screen, I'm referencing the text template instead of the collection.
1
Values that change in a given screen won't affect the value of any other component on the page. The only thing that listens for changes in the screen at runtime is the conditional visibility -- otherwise, the changes are only registered when the Next button is clicked and everything is sent to the flow engine on the server.
If you want to set a value in the ...
0
Here are the governor limits with Flows.
https://developer.salesforce.com/docs/atlas.en-us.salesforce_vpm_guide.meta/salesforce_vpm_guide/vpm_admin_flow_limits.htm
in case you are not reaching the object limit or overall flow limit, and reaching the max versions in a single flow then you can
in LEX, you can view the flow record and choose view details ...
0
If its visual flow and you dont need that flow anymore you can click go to "View Details and Version" from the flow list view action and can deactivate the latest version which is active.
If it is workflow rule you can directly deactivate from the list view.
If you want the functionality of the flow/workflow then you have to try to merge with existing one ...
1
Your condition for visibility is checking whether RadioButton1 equals $GlobalConstant.True. But if you want the Stores Issues radio group to be displayed based on what's selected in the Call Category radio group, what you need to check is what the value of the radio button group is. In your example, RadioButton1 is a Choice resource, not a radio group.
If ...
0
You might want to change the line where you are entering into createRecordEvent.setParam as follows. While you are at it also make sure that the Account__c and Contact__c (which I hope are look-ups in your case have appropriate FLS settings as well and the name, case is right. That should do the trick.
if(AccountID !="" && AccountID !=null &&...
0
I have found out that in order to create a new quickaction you must either create a global action or object specific action. Please be aware you will need to refresh your flow in order to view the newly created action ( I initially had kept flow builder open and the new action was not fetched!)
1
Based on my experience and verified by other posts around the internet (https://success.salesforce.com/answers?id=9063A000000lObxQAE) I don't think what you want is directly possible.
The reason is, in a flow, you are not binding the Picklist directly to a record in the same way you do when creating Visualforce pages or components. The screen component ...
1
As tugce mentioned, an object-specific quick action will allow you to launch a screen flow by pressing an action button on a Lightning Record Page.
Make sure there is at least one active version of your screen flow, and add the action to the relevant page layout of course.
1
Two main approaches come to mind:
1) Set up conditional visibility
Including two instances of the second input component in the screen
Making one required, and the other optional
Setting up conditional visibility on them so that only one is displayed at a time (based on whether or not it should be required)
You could use decision and assignment elements ...
1
Use the GetRecords Data Element to Query for the Queue SObject.
1
Lookup field must actually be a field of lookup type.
To query for a user object for example, on the lookup component you could select an Object API Name of value "Case" and Field API Name of value "CreatedById" and this appears to perform a SOSL lookup of all fields on the User Object since CreatedById is of field type: Lookup(User).
1
Thank you all for putting me in the right direction.
I made some more research and found out that as @KrisGonsalvez says, the flow runs as an Automated Process user. And as I could find out in the post I mention below, is that autoflows always run in System Context. So it's kind of a way of bypassing the permissions limitations.
How to By-pass User ...
1
go to screen( Contact Info) -> click Toggle -> scroll down the menu of toggle -> "Uncheck" Manually assign variables (advanced).
open decision -> click "add condition" enter update_toggle @ resource -> value. ;)
0
Be aware that in the Spring ‘20 release, will be able to choose what the flow runs as:
https://releasenotes.docs.salesforce.com/en-us/spring20/release-notes/rn_forcecom_flow_fbuilder_system_mode.htm
0
I also encountered similar issue so replaced my Custom metadata with custom object not ideal. But the reported issue has few affected users so not likely to be fixed anytime soon.
6
It apparently runs as the "Automated Process" user.
I see mention of it here https://jenwlee.com/2019/10/01/schedule-a-flow/
More importantly, I scheduled a quick flow to test this and I can see through debug logs that the scheduled flow was executed by the Automated Process User as opposed to the user who scheduled it.
Scheduled Jobs
Debug Logs
1
It's definitely possible to break out of the loop with a decision and directing the flow out of the loop, as suggested in the link you provided.
I think in your case you should go directly to Create Record from the 'Applicable SP Role = ..' negative decision, instead of going back into the loop to wait for it to finish all iterations and check the variable ...
3
Yes you can, your component needs to implement lightning:availableForFlowScreens , the variable name in flow should match the attribute name in your lightning aura component.
<aura:component implements="lightning:availableForFlowScreens" access="global">
<aura:attribute name="greeting" type="String" access="global" />
<aura:attribute ...
0
In my case, it was that the object named in my standardController clause on line 1 of the VF page was not typed in the exact upper and lower case as the object.
0
I believe it is the currently default behaviour.
1) For the flow Screen (lightning_FlowScreen) properties, they are displayed in the alphabetical order and not in the same order as you entered in your LWC.
2) All properties seem text, but actually they are not. For the Boolean typed inputs it will accept {!GlobalConstant.True} or {!GlobalConstant.False} ...
1
It is not possible at least according to Salesforce help page. In the Salesforce help Considerations for the Apex-Defined Data Type article has a Section on Input and Output values and it says:
An Apex-defined variable value can't be set or stored outside the flow.
The value can't be passed to a Subflow element.
Top 50 recent answers are included
