Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Configuring indicator for a flow action

Updated on November 22, 2021

To design cases that precisely meet your business requirements, define the results that user interactions with a case have by placing a flow action at a relevant place in a flow. With flow actions, users can update information in an assignment, resolve work, or both.

Consider a scenario in which a customer service representative (CSR) submits a form with a loan request from a customer. You can decide whether the CSR only updates information in a case or whether the CSR can also resolve the assignment and move the case to the next task. An indicator on an assignment or a connector between assignments determines where in a flow that flow action happens.
  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Process category, and then click Flow Action.
  3. In the list of flow action instances, open the flow action that you want to edit.
  4. On the Action tab, in the Indicator section, in the Used as list, specify how you intend to use the flow action:
    • To update the assignment and the current case, select Local Action.

      By performing local actions, users can update, but not resolve, an assignment. The local action retains the flow at the same assignment shape, so that the current user, or another user in some cases, can choose another flow action. Users can invoke local flow actions from a modal window or from a flow action form.

    • To update the current case, complete the assignment, and advance the case, select Connector Action.

      Typically, users invoke connector flow actions from a flow action form. Local flow actions are alternatives to autogenerated controls.

    • To use the flow action as both a local action and a connector action, select Local and Connector.
  5. Optional: To exclude the flow action from the list of flow actions that are available for bulk processing, select Disqualify this action from bulk processing.
    You can perform bulk processing of flow actions in the following situations:
    • The flow action does not have circumstances.
    • For assignments in various cases, the Applies To class of the flow action is a class that is an ancestor to all the cases. For more information about classes, see Understanding class hierarchy and inheritance.

      By default, some standard flow actions do not support bulk processing because the process can involve only one case at a time. To change the default setting, copy the flow action to your ruleset, and then make the change. For more information, see Copying a rule or data instance.

  6. Click Save.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us