Launchers Best Practices
- 28 Aug 2024
- 2 Minutes To Read
-
Print
-
DarkLight
-
PDF
Launchers Best Practices
- Updated On 28 Aug 2024
- 2 Minutes To Read
-
Print
-
DarkLight
-
PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Add Launchers to a Launcher collection
A Launcher once created, must always be a part of a Launcher collection for it to reflect on the page or application. A Launcher collection is a group of Launchers belonging to the same page.
For more information, see Add a Launcher to an existing collection.
Create one or two Launchers per page
Create one or more Launchers on the same page. However, it is recommended to limit the number of Launchers to one or two per page. For more information, see Create a Launcher.
your title goes here
Visibility rules are defined for the Launcher Collection. So even if you have only one Launcher on a page, it needs to be part of a collection.
Create one Launcher collection per page
Whatfix evaluates only one Launcher collection at any given time. If there are two or more Launcher collections on the same page of an application, then only one of them gets evaluated.
When editing or modifying a particular page to add a new Launcher, look for any existing Launcher collection for that page. Don't create a new Launcher collection for a page if the collection already exists.
For more information, see Adding a Launcher to an existing collection.
Note
The criteria for evaluation depends on the visibility settings or the number of conditions (in case visibility settings are the same for two segments).
Provide URL paths for Launcher Segment across different Application environments
If you want the same Launcher segment to work across application environments, then provide URL paths instead of the complete URLs. If this is not done, the Launcher segment in one environment may not work in another.
Look for Existing Launcher Collection on a Page
When editing or modifying a particular page to add new Launchers, look for any existing Launcher collection for that page. Don't create a new Launcher collection for a page if the collection already exists.
Choose an appropriate button style for the Launcher
Use different button styles to suit the underlying application. Choose between Filled (Primary) button, Outline (Secondary) button, and Text button styles based on your use case.
Use Launcher level configurations to select different button styles for a Launcher that appears on a page.
For more information, see Customize a Launcher.
Provide clear and concise text for the Launcher
Keep the text in the Launcher short. The text of the Launcher should give the end user clarity on the information rather than being something generic.
Place your Launchers contextually
Place the Launcher where the end user will most need it on the application, and not in a generic location. If there's a dashboard or homepage, place a Launcher that launches a Flow to guide users through key features or updates.
Preview the Launcher before pushing it to Production
Once you are done creating a Launcher, test the Launcher in the Preview mode and ensure that the Launcher appears in the right location.
For more information, see Preview a Launcher.
Was this article helpful?