Objective:
After reading this article, you will have seen an example of how admins can build Youreka so that forms are related to other forms.
Before you get started:
These articles might be helpful before you read this one:
Out of the box, Youreka gives admins a great deal of flexibility when it comes to creating streamlined end user experiences. Between conditional display logic, mobile cards, New Form Buttons, deeplinking, and more, admins have quite a few options to ensure that their end users are seeing the right stuff. However, in some situations, we see customers who require even more when it comes to how their end users should capture data.
In some of these situations, we turn to daisy-chaining forms together. When we use the phrase daisy-chaining, we mean having one form create, populate, and perhaps relate to another form. One way this can be accomplished is by setting up a Salesforce environment to sequence multiple forms, one after another. In the article below, we provide an example implementation where an admin configured an environment with Form Sequencing.
Step 1: Create New Custom Objects
In order to set up Form Sequences, we decided to create three custom objects, and relate them to our other Youreka objects that come with the managed package.
These objects each have their own purpose in allowing us to create sequences of Forms for an end user.
Object Name | Description |
Form Family | Represents an group of forms that are to be assigned and completed, in a specific order |
Form Sequence | Represents a template for which Form Families operate. Form sequences define how Forms are created and made available on mobile |
Form Sequence Template |
A junction object between Form Sequence and Form Template. These FSTs define which Form Templates are used for each form in a Form Family, as well as the sequence in which those Forms are to be filled out |
Step 2: Create Automation for Sequencing
Once the objects are created, we can create automation in the system that responds to records on these objects being created/updated. Here were a few of the scenarios we solved for:
- A user creates a Form and assigns it to a sequence -> create all forms in the sequence
- A user creates a Form Family and specifies a sequence -> create all forms for the Form Family
- A user SUBMITs a form that is a member of a Form Family -> make the subsequent form in the Form Family available on Mobile.
We accomplished all of these automations using Salesforce Flow Builder. Here are what those flows looked like:
Form Sequences: Form Family Creation
Form Sequences: Form Record Creation
Form Sequences: Form Record Updates
Each organization is different in how they might implement this, depending on desired end user experience - and overall system architecture. However, with sequences set up in an environment, an admin can make it so that end users are automatically assigned forms in a specific order, all using basic Salesforce automation tools such as Flow.
Comments
0 comments
Please sign in to leave a comment.