How to use the Join Decision condition in Identity Flows

This video will discuss the concept of a join decision in CyberArk Identity Flows. It will explain that a join decision allows you to take different paths based on a certain condition but eventually return to the same path. This is useful when you need to analyze a result, perform actions based on that result, and continue with the flow. The video will provide an example of a simple flow where an API is polled for a joke, and the join decision is used to check the response status. If it's 200, the flow proceeds down the left path with a 10-second delay. The speaker emphasizes that a join decision requires at least one child element. They mention that there will be future videos discussing split and branch decisions, which are similar but have different outcomes and additional details.
Videos in the Decision condition series:
Join decision - (This video)
Split decision - • How to use the Split d...
Branch decision - • How to use the Branch ...
For more information, see documentation: docs.cyberark....