Customize Button actions in a Walkthrough
- 07 Jun 2024
- 3 Minutes To Read
-
Print
-
DarkLight
-
PDF
Customize Button actions in a Walkthrough
- Updated On 07 Jun 2024
- 3 Minutes To Read
-
Print
-
DarkLight
-
PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Whatfix Mobile enables you to link various type of actions to a button present in the step of a Walkthrough.
Use the following steps to customize a button action:
- Design the Walkthrough as required. For more information see, Create Walkthrough.
- In the configuration panel, expand the Customize Button section.
- Click the Button Actions dropdown.
- Choose the button action you want to add to your Walkthrough step.
List of all button actions
The following are the button actions that can be set for the Walkthrough step:
| Button Action | Impact on Start Step |
|---|---|
| Dismiss | End the Walkthroughand mutes it for the rest of your session. Your title goes here
|
| Flow Opt in | Closes the start screen and starts the corresponding Walkthrough. |
| Button Action | Impact on Walkthrough step |
|---|---|
| Deeplink |
|
| End Flow | Dismisses the step, exits and mutes the Walkthrough for all sessions. Your title goes here
|
| External Link |
|
| Next | Closes the current step and continues with the next step. |
Impact of Button Actions on Discovery Trigger Frequencies
If you have defined a Discovery Trigger Frequency for your Walkthrough, the button actions have the following impacts:
Your title goes here
- The following two Trigger Frequencies, Play once in a life-time and On icon click, are not impacted by any of the button actions.
- The Flow Opt in button action does not impact any Trigger Frequencies.
Tip:
As a best practice, always set the Trigger Frequency as In every session. This ensures that even in the absence of an icon, Whatfix Mobile can discover the Walkthrough.
| In every session | In every session until dismiss by user | Every session until flow complete | |
|---|---|---|---|
| Deeplink | - | - | If configured in last step, on button click, the Walkthrough is considered to be completed and is not auto-triggered in subsequent sessions. |
| Dismiss | - | Impact on start step: Mutes the discovery and from the next session onwards, Walkthrough can be triggered only via icon click and is never auto-triggered. | - |
| End Flow | Mutes the discovery and from the next session onwards, Walkthrough can be triggered only via icon click and is never auto-triggered. | Mutes the discovery and from the next session onwards, Walkthrough can be triggered only via icon click and is never auto-triggered. | Mutes the discovery and from the next session onwards, Walkthrough can be triggered only via icon click and is never auto-triggered. Your title goes here The Walkthrough need not be completed to be muted in this scenario. |
| External Link | - | - | If configured in last step, on button click, the Walkthrough is considered to be completed and is not auto-triggered in subsequent sessions. |
| Next | - | - | If configured in last step, on button click, the Walkthrough is considered to be completed and is not auto-triggered in subsequent sessions. |
Impact of Button Actions on Termination Frequencies
If you have defined a Termination Frequency for your Walkthrough, the button actions have the following impacts:
Your title goes here
- The following two Termination Frequencies, Never and After 'n' sessions, are not impacted by any of the button actions.
- Flow Opt in button action does not impact any Termination Frequencies.
For all button actions, if After 'nTH' time flow completion is configured in the last step, then the Walkthrough is considered to be completed on the button click.
For Deeplink button action, if At assist dismiss by user is configured in the start step, then on button click, the Walkthrough is considered to be completed.
Was this article helpful?