Skip to main content
All CollectionsPresentation FlowsRulesets
Rulesets | Event - Implement/Remove Preselects
Rulesets | Event - Implement/Remove Preselects

Utilize Ruleset events via Presentation Flows to Implement or Remove a Preselect when creating a presentation

Will Matysik avatar
Written by Will Matysik
Updated over 3 months ago

TIP:

If you have any questions or need assistance with implementing or updating Forms, Rulesets or Presentation Flows, please contact us at customersuccess@sportsdigita.com


Description:

Depending on how your Master Deck is organized, it could save a bit of time to implement/remove entire Preselects of content rather than selecting collections of individual slides. Whether it makes more sense for your organization to start with a larger subset of Preselects and remove the slides and/or Preselects that aren’t applicable based on responses in a Form OR starting from nothing and adding Preselects based on those responses, you’ve come to the right place.

A quick example of a use case to implement Preselects:

Add example: If you have different Preselects that contain slides that are all specific to a sales stage, you would set up a Rule that adds those stage-specific Preselects based on which stage is selected in the Form. In this scenario, you’d implement a Rule for each sales stage option as will be outlined in the screenshots below.


Editing a Rule

details below screenshot)

Name:

Best practice for the Sales Stage example above would be to label the Rule as “STAGE - Proposal” so that you can easily identify the rule that will be adding the slides relevant for the Proposal Stage in case you want to make any changes in the future. You could then have Rules called “STAGE - Prospecting”, “STAGE - Quarterly Business Review”, etc.

Fact Property:

Best practice would be to have your form completed prior to configuring your Ruleset so that the “Labels” (question, prompt, etc) from the Form can be included for easy selection due to the Context you set when creating the Ruleset.

Operator:

The function of the Operator is to compare the variable returned by the “Fact Property” (prompt, question, etc) to what is stored in the “Value” (answer, response, etc).

Equal: Variable matches the set Value exactly

Not Equal: Variable does not match the set Value exactly

Less Than: Variable is less than the set Value

Less Than or Equal: Variable is less than or equal to the set Value

Greater Than: Variable is greater than the set Value

Greater Than or Equal: Variable is greater than or equal to the set Value

String Starts With: Variable string starts with the set Value

String Ends With: Variable string ends with the set Value

String Contains: Variable string contains the set Value

String Does Not Contain: Variable string does not contain the set Value

Value:

When you set a Form as the Context for the Ruleset as mentioned above, you will simply select the Value from the dropdown that corresponds to the Operator you’ve chosen.

Event:

After selecting “Implement Preselects” you will be able to click the “Select Preselect” button to display the full list of your team’s Preselects. You will see them all listed alphabetically or be able to type the Preselect title into the search bar to narrow your options.

TIP:

Be sure to click “Add Rule” in the bottom right hand corner of the Rule AS WELL AS clicking “Save Changes” in the bottom right hand corner of the Ruleset to ensure all changes are saved.


Important Ruleset Notes:

  • While the order of questions in a Form are irrelevant since all responses pass through at the same time, the order of Rules within your Ruleset are VERY relevant. The Rules are processed in chronological order, making it of the utmost importance that you put some thought into whether one Event needs to occur before another.

  • It’s also important to note that each Rule should be associated with a specific response to a question, rather than simply associating it with the question itself.

  • Please be aware that any events left incomplete will cause the entire flow to FAIL.

  • Last note that’s important to highlight is that you can NOT use multiple events in the same rule. Best practice would be to create two rules with the same configuration, each simply leveraging different events.
    Example: Stage = Proposal… “Proposal Preselect” & “Proposal Intro Video”


If you have any questions or need assistance with implementing or updating Forms, Rulesets or Presentation Flows, please contact us at customersuccess@sportsdigita.com

Did this answer your question?