Name: Creating Identity Flows in SAP Customer Data Cloud
Uploaded: 2024-5-22
Duration: 378 s
Description: In this video, you’ll learn the Identity Flow terms and components, and how they can be published and invoked. Followed by a demo on creating an identity flow in SAP Customer Data Cloud.

Share feedback

<p>We are aware of intermittent issues in accessing the learning content</p>

We are aware of intermittent issues in accessing the learning content

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

Please try again later

Sorry, we encountered an error

Try again or reset results to continue browsing

We didn’t find what you’re looking for

To continue, please log in

Your session has timed out

Explore {title} at SAP Learning. Find out more!

Enhance your learning experience for free

<div><div><div><div>In this video, you’ll learn the Identity Flow terms and components, and how they can be published and invoked. Followed by a demo on creating an identity flow in SAP Customer Data Cloud.</div></div></div></div>

Creating Identity Flows in SAP Customer Data Cloud

Welcome to this video on Creating Identity Flows  in SAP Customer Data Cloud.  In this video, you’ll learn the Identity Flow terms and components,  and how they can be published and invoked.  Followed by a demo on creating an identity flow  in SAP Customer Data Cloud. Let’s go over some key terms.  An Identity Flow is a flow that launches a single screen-set or a set of screen-sets to gather additional data from the users at any point in the customer journey.  The Identity Flow Builder  is our web-based tool that creates  and implements Identity Flows on your sites.   It uses components to build Identity Flows,  which enable you to control the flow itself  or trigger certain events or actions.   Identity Flows consist of one or more components that interconnect.  There are 5 components available:  Condition, Time Period, Counter,  Event, and Screen-Set actions.  Conditions allow the setup  of a JavaScript expression  that controls the flow of the Identity Flow.   The Condition action can use the fields  in your schema.  Time Period The Time Period action is a time frame control  in the Identity Flow. It allows you to control  when an identity flow runs.   There are three execute choices until, during, and from, for the time frame.  Counter A Counter controls the flow of the Identity Flow,  allowing you to control how often you show a screen-set  and limit the display of a progressive profiling screen to an end user.  Event An Identity Flow triggers an event  when an Event component  is encountered in an Identity Flow.  Screen-Set A Screen-Set is a set of screens you've predefined.   The Identity Flow Screen-Set action invokes one specified screen during the Identity Flow.  After creating and editing an Identity flow,  you can test the flow, save it as a draft,  or publish it.   In case you change or edit a published version,  the state will be “Draft with the prior version Published”.  After publishing the Identity Flow,  the slide out arrow on the Flow Builder screen  contains the code snippet  that invokes the Identity Flow.   Copy and paste the code snippet  into your CIAM application  and invoke the identity flow  using the SAP Customer Data Cloud Web SDK.   Now, we’ll demonstrate  how to create a new identity flow,  add components to it,  and publish the flow.  Our goal is to ask users who aren’t opted in  to a specific subscription for their opt-in.   For those users we want to present one of the screens.  Choose “Flow Builder” in the User Interfacing menu.   You are brought to the identity flow overview page.  On this screen you’ll see all identity flows created so far with the option to edit or delete them.   Choose “Create Identity Flow” at the top right.  Here we can define the name for the new Identity Flow  as well as a description for it.   Please keep in mind that these properties can’t be changed  after the flow is created.  Enter “Ask for Additional Subscriptions”  for the Identity Flow name.   Then choose Save.   You’ll come to the Flow Builder screen  with an empty flow.  Add your first component by choosing the “Start” rectangle  at the top.   In the popup, you can choose  from the five components.  For our example, we’ll select a condition component. Choose “Condition”   and name it “Check for Subscription”.   In the field Javascript Expression  we’ll add a javascript code, which should return a Boolean,  to check if the two subscriptions in the system are false.   Choose “Save”.   The condition-component was successfully added to the flow.   Next, choose the plus-symbol  from the “false” path of the previously created condition.   We’ll choose the screen-set component.   Change the name to “Show Communication Screen” and choose your desired screen-set and screen  Choose “Save”.   The Screen-Set component was successfully added to the flow.  This flow can be enhanced as desired  using the different true and false paths with the components you learned before.   For now, choose “Publish” then “Confirm”.  Proceed by choosing the slideout symbol  on the right of the flow builder screen.   As part of the slideout  you can see the details of your current flow as well as the code snippet,  which can be used to invoke the identity flow from your CIAM application.   Please make sure that the identity flow is only initiated during a valid session where the user is logged in.  Let’s place the code snippet in the CIAM application and test the flow with one of the profiles.  The profile used for the test has no subscription assigned.  Let’s login with this profile.   For this we’ll enter the profile’s credentials  into the CIAM application’s login screen.   After logging in, the identity flow is triggered because the logged in profile has no opt-in  for the two available subscriptions  which were configured  as part of the identity flow condition.  The communication screen is successfully presented to the user.  We’ll subscribe to the two subscriptions.   To verify that the identity flow works correctly,  and the condition is executed as expected,  we’ll logout and do another login  with the same user as before.   The login was successful  and the communication screen  was not shown again.   This concludes our video  on creating Identity Flows  for SAP Customer Data Cloud.   Thank you for watching.