Publishing allows you to select, organize, test and publish items that you create in the WalkMe Editor to your Test or Production environments. In the Publish menu you determine the organization of the menu, the environment you wish to publish to and the specific items you want to make available on that environment.
- Common uses for Publishing
- How Publishing Works
- Publishing Environments
- Software Updates to the WalkMe Editor
- Publishing Process Best Practices
- Preview WalkMe Items
- Organizing the Menu
- Publishing WalkMe Items
- Archiving WalkMe Items
- Accessing the Snippet
- Try it Out
Let's Talk A Bit More
Common Uses for Publishing:
- Test WalkMe items on a sandbox environment
- Remove WalkMe Items from an environment by Archiving them
- Organize and configure how items appear in the WalkMe Menu
- Publish items to your production environment
When you click Publish, only the selected items will be published. Items that were already published do not need to be published again. You will receive a message notifying you how many new items are about to be published.
WalkMe regularly updates the WalkMe Editor and we notify all customers in advance about upcoming new features. When the Editor is updated, the WalkMe items you currently have published are not be affected. The Editor account and features included in it may change but the files that you have published remain unchanged on the server. To update items so they include new features from a product release, you need to modify these items and republish them.
When publishing, you have the option to select multiple environments, such as Test or Production. These environments use the same ID code but their snippets are slightly different. For example, the Test snippet will have the same ID but include the word ”test” in the link. Since each environment has a slightly different snippet, WalkMe views them as distinctly different; for example, when you publish an item to the Test Environment those published items are only available to users that have the Test snippet running in their browser. Having a unique snippet for each environment allows you to test out different WalkMe items in a sandbox or staging environment before they are published to your users on a production environment.
The WalkMe Snippet runs in all major browsers and can be deployed by either directly placing it into the code of the website, or as a browser extension. Learn more about the WalkMe Snippet.
Publishing Best Practices
WalkMe recommends the following 7-step process to help you prepare to publish your WalkMe items.
Ensure the Snippet is implemented on your site: In order for WalkMe to work, it has to be implemented on your site. Learn more about the WalkMe Snippet.
- Go over design: WalkMe has pre-made themes or you can customize for yourself. Customizable components include step balloons, Launchers, the Player Menu, the widget, and much more using CSS. Check that the design and colors compliment your site and are consistent across applications.
- Add Goals: The usage graph in Analytics is only half of the information you need to track success. The best way to track success is to use Goals. Learn more about Goals.
- Set Unique User ID Settings: User tracking allows you to see if individual users are reaching their WalkMe goals. By enabling user tracking, you will be able to see an individual’s progress as well as their usage of all the other Apps in the WalkMe Analytics Module. There are a few ways to identify unique users. The easiest is to use WalkMe ID where each user will be assigned an ID. However other methods can be more accurate. WalkMe ID is useful for tracking large numbers of users, specifically for external sites. However, it is not ideal for internal sites where you want WalkMe to remember your user.
For Salesforce users, WalkMe can track the Salesforce User ID. Learn more about Salesforce variables. For non-Salesforce users we recommend using variables. You can also use a Cookie or jQuery to identify your users. However, variables, Cookies, and jQuery will require you to supply a way to identify the user.
- Publish to Test Environment and Run Quality Assurance Tests: Make sure to test all of the items you plan to deploy. Testing ensures that your users have the best possible experience and don’t see breakages or broken links. Also, review text for typos and grammatical errors. Learn more about QA with the self-paced University course 210: Test Drive your Walk-Thru
- Organize the menu: Use the Menu Organizer in the Publishing Menu to organize the order in which your items will appear in the Help and Task (if you have Onboarding) tabs. Learn more about organizing the WalkMe Menu below.
- Publish to Production: Make sure to promote WalkMe on your site. Try using a ShoutOut, Attention Grabber or sending an email to your users announcing it.
Previewing WalkMe Items
Before using the Publish menu, you have the option to preview your work while using the WalkMe Editor. This allows you to view how your implementation will work on the site, without having to publish anything or install the snippet in the site or browser window. While in preview mode, use the Flow Tracker to see what is happening when a Walk-Thru plays. Learn more about the Flow Tracker.
Organizing The Menu
WalkMe allows you to customize how your items appear in the Player Menu. In the left menu are all the items you’ve created in the Editor separated by Walk-Thrus, Resources and Shuttles (the three Apps that appear in the Player Menu). To add items to the menu, simply click and drag them to the End User View on the right side.
In the End User View on the right is a list of items that appear in the menu once they are published. All new items created in the Editor automatically appear here. To remove an item from the menu, simply hover over it and click the trash can. This removes the item from the menu but does not delete it. Return to the left column if you would like to add it back again. To change the order that items appear in the menu, simply click and drag them up or down in the list. Items listed at the top of the menu often are clicked much more often, so it’s important to consider item order. Items on the right End User View list only appear in the menu once they are published.
Onboarding Task List
Above the right menu you can view your Onboarding Task list where you can similarly reorder and remove tasks for onboarding. Onboarding Tasks appear in a separate tab in the WalkMe Menu called Tasks, but it must be enabled for your account in Onboarding Settings to appear in the Menu. Learn more about Onboarding. By default the help menu appears first when users open the Menu but below the right menu you can change the default tab to Tasks instead of Help.
Publishing WalkMe Items
Before you publish, make sure to install the WalkMe Snippet on your site; otherwise, WalkMe will not appear on your environment. Learn more about the Snippet. To publish, click Publish from the Admin bar and select the publish tab and select the environment you wish to publish to. Then select the specific items you wish to publish.
To select items to publish, switch between Apps in the left hand menu and check the boxes next to desired items you wish to publish. At the top of each list you have the option to select or deselect all items. All items that are selected, regardless of the current view are published to your selected environment once you click publish at the bottom.By default WalkMe selects all items that you have previously published. New items you have create are not selected.
After hitting publish, WalkMe will display a notification with the number of the selected items which are about to be published so you can do one last check that you are publishing the correct number of items.
Note: For SmartTips are published by Set, but it is possible to disable a specific SmartTip so it cannot be published. Learn more about SmartTips.
Each item has different app icon that show its current publishing status. These statuses change when switching environments in the Publish menu.
|Draft||Orange icon denotes item is in draft mode. Draft items are not published to the server.|
|Published||Green icon denotes published status. Published items are saved on the server and have not been modified in the Editor since they were published.|
|Modified||Green with an asterisk denotes modified status. Modified items are currently published, but have been modified in the Editor after it was published. Publishing is required to add modified changes to the published item.|
|Archived||Grey denotes archived status. Archived items were previously published, but have been removed from the server or unpublished. Archived items return to draft status once modified.|
Archiving WalkMe Items
To unpublish a WalkMe Item from an environment you must Archive it. Archiving a WalkMe item removes it from the server so it is no longer available to users. Archiving is necessary if you wish to delete a published item. To archive an item open the publish tab, choose your environment, select all items you wish to archive and click Archive at the bottom of the page.
Accessing the Snippet
The Snippet is slightly different for each environment. When installing the Snippet into your site be sure to use select the correct environment before you copy the code.
Learn more about the Snippet and deployment options.
Try it Out
Publish items to your test environment and run a QA test (Quality Assurance). Learn more about QA in our Test Drive course on WalkMe University.
Archive outdated WalkMe items to remove them from the server