Introduction
As customers use our GetAccept integration more and more, it can raise challenges around template management for users:
What template should I use for a particular scenario
What templates should I not use
Where can I find the template
How can I get the information about all these templates that exist
Using the Conditional Setup feature allows an admin or manager to set rules as to when certain templates can and should be used. Remove the need to update your teams regarding your constantly growing content and let them focus on selling.
Use Cases
This tool is here to help you map your process, so can vary greatly how its used from company to company. But here are some examples of how it could be used. Here are a few examples:
If your users are sending from the Opportunity object, then consider setting up the conditions so that different templates are available for different Stages of the opportunity.
Check what products have been added to an opportunity. Maybe opportunities with subscription products should use one template, and service products use another.
Maybe different teams or users should have different templates provided to them for different scenarios.
A combination of the above.
Setup
(Pre-requisites: Ensure that you have our GetAccept integration Version 2.104.0 or higher and that you have the GetAccept_Integration_Admin permission set assigned)
This setup will guide you through creating a Conditional profile.
Navigate to the GetAccept Admin App | Conditional Setup
Click Create profile
Search and select the object you wish to set up the profile for and click Create
At this point a new Profile has been created for you. If you cancel, nothing will be saved. The profile has set up the basics needed for the profile to work well:
It is automatically assigned to the first GetAccept entity it can find.
Its been given a standard name and description which you can edit for your own organization
The entry condition for the profile is set to Sending Object = ‘Account’, or whatever object you have selected when creating the profile.
Then it has also created two branches to get you started. Case 1 - you can begin setting your conditions here. Default Case - this is the fallback branch where conditions cannot be set.
So let's continue to set up the profile.
Navigate to Case 1 and set the conditions as you wish within the IF card. You can set multiple
Next you can decide what you wish to happen in the THEN card. Either decide to select a set of templates or create further child branches. In this example, we shall select templates. In this section you will see the “Filter the template(s)” text, which means that only the options that you select here will be shown to the user. You can change this option on the right to “Suggest selections”, in which case, this template will be suggested to the user, but all other templates are still available
Click select template and specify which templates you wish to have made available to the end user. You can select multiple for both contract and deal room
Click back into the primary object in the overview panel. On the edit panel on the right you can create further branches. In each of these branches you can repeat the same steps as above for every other scenario you’re interested in solving
When all your specific branches have been created. You can finally decide what happens when none of those branches evaluate to true. This can be done by editing the THEN card within the Default Case. Here you have the same possibilities. Either create sub-branches or select the standard default templates you wish to be used
When you are finished, you can hit Save. You can also use the test feature in the dropdown in the top left to see how the conditions work for a specific record
When you’re ready for the profile to be active for your users, click the activate toggle
Notes: How conditional logic works
Only one profile per Object per GetAccept Entity
Branches are evaluated in order from top to bottom. The first branch that matches the conditions of the object will be selected.
Default branches do not have conditions. These branches are last in the running order and should be used as an ‘ELSE’ function when no preceding branch evaluates to true
Profiles can be comprehensive in size and complexity, but there is a limitation of approximately 100 outcomes. (may increase in future)