2

So I created a simple flow(to create multi-records), enter image description here

So in the first screen it asks to enter some fields and using those fields I create records and in the Decision Block based on certain conditions I either direct them to Create new Record(second record) or Finish.

It works great but when I re-direct the decision to the Test screen again to create my second record. The fields still show the old data in the fields (first record's).

How can I get blank fields when creating the second record?

Assignment Rule, enter image description here

NullVariable is a custom variable that I created and passed EmptyString to it as a default value, SalesOrderName is what I want to make the value blank but not able to populate that in the condition where we seeing NullVariable.

2

This won't work because as you've already discovered, you can't nullify input elements in flows.

You have to split it into two flows. Split it at the step that captures the input values. So at the step where you would usually present the inputs in the UI, call your new flow from within your current one to capture the input elements or whatever you want to do there. Pass whatever you need to back to your original flow and you can call the second flow as many times as you need to capture new input elements. I use this for a user creation wizard and call my New User flow from the wizard as many times as the user wants to create more records, capturing the new values in the UI every time.

Kinda lame but it's the only way I've found to currently make it work.

In my example, I have a wizard that manages an entire entitlement process. At a step in the flow, i make a decision of whether or not i need to create a new contact. If yes, i need to capture some details in an input screen. I may need to create multiple users, so i am going to need to need to call another flow to manage the input screen since i don't want to re-present the screen again with the old contacts info still in there.

enter image description here

The first step in my other flow is the input screen. It then does a bunch of work to actually create a contact, but you'll get the general idea.

enter image description here

When you add that new flow to your current one, you can pass any attributes you need to that in the Variable Assignments section.

enter image description here

Every time your main flow calls the sub flow (I like to call them Worker Flows), it will present your input fields without any values in them.

  • I think you are correct that seems to be the only way, could you provide with any screenshots on how you achieved/built this ? That will help, thank you – Sanjay Aug 28 '15 at 3:51
  • I added some screenshots and explanations. Let me know if you still have any questions. – cricketlang Aug 28 '15 at 4:59
  • 1
    Have you assigned output variables in flow2? In my example I only have inputs onto my flow2 because I actually do the record creation in flow2. If I wanted to get values back to my master flow, I'd create output variables in flow2 and then map those to your variables in the output section of the variable assignments. – cricketlang Aug 28 '15 at 18:19
  • I actually figured so I deleted my post. Yes, its the same reason you explained Variables I created wasn't Output type. All good now. Thanks again ! – Sanjay Aug 28 '15 at 18:38
  • Glad you figured it out! I have some hefty flows setup, so if you run into any other snags feel free to ping me! – cricketlang Aug 28 '15 at 18:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.