Mobile: How To Edit Walk-Thrus

Updated on July 6, 2020 Download PDFDownload as PDF
Download PDF

The Mobile Console presents the list of captured Walk-Thru steps organized by the different screens in which they were captured:

If these screens were captured previously using Capture Screen, the screens will appear by the names they were given upon their initial capture. You can also set and change each screen’s name from this tab by hovering over the screen name and clicking the pencil icon that appears.

From the Walk-Thru’s WYSIWYG editor in the Mobile Console you can customize the Walk-Thru layout, Step text and design, and Step behavior.

Editing Mobile Walk-Thrus

Editing Mobile Walk-Thrus in Power Mode

Starting from WalkMe Mobile SDK version 1.4.0, you can edit your Walk-Thrus’ flows from your app’s Power Mode.

While previewing an unpublished Walk-Thru, the Edit Walk-Thru option will appear in the Preview menu (the menu that opens when you tap on the green Preview bubble) to make edits:

The first time you select Edit Walk-Thru, you will receive the following warning message:

Pro-Tip: It is best to consult the Mobile Console while editing in Power Mode. As you make edits in Power Mode and save them, you can use the Refresh button in the Walk-Thru’s WYSIWYG editor (next to the Walk-Thru settings icon) to see the new edits reflected in the Mobile Console.

Edits are applied to the Step currently playing (“(2/3)” means you are on the second Walk-Thru Step out of three total Steps) in the Walk-Thru. Starting from iOS SDK version 1.5.0 and Android SDK version 1.6.0, the Walk-Thru Steps flow is also indicated in the Walk-Thru tracker that appears for both Preview and Edit:

In the above image, the user is editing step 4 out of 9 total Steps.

Pro-TipWith WalkMe Mobile SDK v1.15 and greater, you can tap the icon on the right side of the progress tracker to pop the tracker our of its place and place it in your desired location on the screen.

The possible edits are as follows:

  • Add a Step before the current Step;
  • Recapture the current Step;
  • Add a Step after the current Step.

After making an edit, the Walk-Thru will continue to play so you can continue reviewing the flow and decide whether to make additional edits before saving or discard the edits altogether.

Starting from WalkMe Mobile SDK version 1.6.0, edit state is differentiated from regular Preview by a different color:

  • Recaptured Steps appear in hot pink;
  • Newly added steps appear in light pink.

After performing an edit, it is not automatically saved. The number of unsaved edits is represented as a number badge on the Preview/Edit bubble:

You can tap on the bubble again to save the edits or discard them.

While a Walk-Thru is undergoing edits, it cannot be refreshed, since, at this point, there are two sources of truth: the unsaved version you are working on, and the version that will be fetched if you refresh.

To ensure you perform every action in the Walk-Thru’s flow, you may be returned to various points in the Walk-Thru’s flow after editing, depending on the type of edit you made. The various behaviors are as follows:

  • Recapture Step: Will play the Step that was playing before you clicked Edit Walk-Thru (i.e., the recaptured Step);
  • Add Step before: Will play the newly added Step, as capturing didn’t perform the action the Step requires (e.g., if you added a Step that points to a button, you need to tap that button in order to ensure that portion of the flow works);
  • Add Step after: Will play the Step before the new one you added, since the old Step-new Step flow was never tested.

After saving or discarding the edits, you are returned to the Walk-Thru’s Preview and can refresh as usual. Decide whether you want to save or discard your edits before moving on to other campaigns.

Pro-Tip: To avoid confusion, links in a Walk-Thru that’s being edited will not work.

Customizing Mobile Walk-Thrus in the Mobile Console

You can customize a Walk-Thru or set the default style that will then apply to all of a Walk-Thru’s Steps by clicking on the Walk-Thru Settings (paint palette + gear) icon:

You can also customize individual steps by hovering over it and clicking on the gear (Functional Settings) OR  palette (Visual Settings) icon that appears:

If a Step’s individual settings are changed from those in the Walk-Thru’s default style, that Step will no longer reflect the default style unless you restore it (click on Restore to default in the individual step’s settings screen).

A Walk-Thru can be set to display in Spotlights layout or in Balloons layout.

Visual settings

Spotlight customization

Currently, Spotlight Steps have the full range of WYSIWYG customization available; each Spotlight Step can be customized through its own WYSIWYG editor. This WYSIWYG can be opened by clicking the palette icon that appears when hovering over a Step.

Use the WYSIWYG to customize the step’s text, or add Elements to it (e.g., images, buttons, shapes, etc.).

Spotlight Steps contain some unique features, including the following:

  • Button and Shape elements added in Spotlight Steps have a unique call to action (“CTA”) available for triggering the next Step: Next Step. This option is not available if the Step is the last in the screen.
  • Spotlight Steps contain the option to disable default element interaction events, meaning you can prevent an element interaction event if desired during a Walk-Thru.
    • For example, if element interaction is disabled for a Step pointing at a button that opens the app menu, and the user taps the button while the step is playing, the menu will not open, and the Walk-Thru will continue to the next Step.
Balloon customization

Currently, balloon customization is limited to the following settings:

  • Background color;
  • Corners radius;
  • Font family, size and color;
  • Balloon direction: Which direction of the element the balloon will appear on. This setting is applied as possible (if there is not enough space for the balloon to appear where set, it will fall back to another direction);
  • Balloon offset: How far from the element the balloon will appear;
  • Balloon back-cover: Supported only from WalkMe Mobile SDK version 1.8.0.
  • Animation: Supported only from WalkMe Mobile SDK version 1.13.0. Options include Fade (where the balloon fades in and out), Fly in (where the balloon flies into view from the direction of your choice; you may also select “auto” if you want the SDK to decide the direction for you) and Instant (where the balloon just appears instantaneously).
    • Default setting is Fade.

Functional settings

Customizing Step types

WalkMe identifies the element type associated with a given step and sets the Step type according to the user’s expected interaction with the element. If needed, the default Step type can be overridden in the Behavior tab of a Step’s Functional Settings (the gear icon):

The possible Step types are as follows:

  • Input Field: Steps that will be dismissed once the device’s mobile keyboard is dismissed or a keyboard Done button is tapped.
    • With WalkMe Mobile SDK v1.13.0+, you can choose to consider the following actions as the dismissal of an input field:
      • Keyboard Closed;
      • Focus Lost;
      • Keyboard Enter Tapped:
    • Note that mobile keyboards aren’t only text keyboards, but also include number, date, or other value picker keyboards;
    • In the Step’s Functional Settings, you can set Input Steps to receive Auto Focus, which makes WalkMe put the app focus on the Input Step’s element.
  • Swipe (available with WalkMe Mobile SDK v1.14.0+): The next Step will be triggered when the end-user swipes left or right on the app screen;
    • Configure which direction counts as a swipe trigger;
    • Set the swipe sensitivity (how hard the end-user must swipe before the next step is triggered:
  • Tap: Steps that will be dismissed once the element they point to is tapped;
    • Complex elements will always be captured as Tap Steps;
    • Scroll does not count as a Tap interaction that triggers a Walk-Thru Step.
    • From WalkMe Mobile SDK v1.13.0+, you can check the Automation radio button to make WalkMe perform the Step’s tap action for the end-user.
      • Automated Steps won’t show any message to the end-user, but you can add a tap effect so the end-user will see a wave effect when the tap occurs:

With WalkMe Mobile SDK v1.8.0 and above, you can designate steps as skippable, meaning the Walk-Thru will proceed beyond the skippable step despite it not having been triggered (by a tap or keyboard dismissal). The Walk-Thru will move on from a skippable step onto the next step in one of two scenarios:

  1. The Step’s element was interacted with;
  2. The Step’s element is no longer visible on screen.

Pro-Tip: In order to be skipped, the Step’s element must be visible on screen in the first place.

Make a Step skippable by clicking the Step’s Functional Settings gear icon and then checking the Skippable radio button:

You can tell which Steps are skippable by the skippable icon that appears to the right of each skippable Step:

Adding precision settings – Click here for full precision breakdown

Starting from WalkMe Mobile SDK version 1.7.0, you can tweak Walk-Thru step precision settings to improve WalkMe’s ability to identify elements in you app(s). Available tweaks differ between Native and Hybrid apps due to algorithm differences.

To toggle precision settings on, do the following:

  1. Navigate to the MY CAMPAIGNS tab in the Mobile Console.
  2. Click on the Walk-Thru whose precision settings you want to tweak.
  3. Navigate to the Walk-Thru Step whose precision settings you want to tweak.
  4. Hover over the step and click the Function Settings gear icon of Step.
  5. Click on the Precision tab:
  6. Select your desired settings and click SAVE.
  7. Preview the Walk-Thru in your app’s Power Mode and use Refresh Campaign to re-fetch the Walk-Thru with the recent changes made in the Mobile Console.
Precision Settings on native apps

Upon clicking the precision icon For Walk-Thru steps on Native elements, you will see the name of the Element and the sub-heading Text Bypass, and you will be able to select one of Default, Ignore text, and Match text:

If you select Match text, an empty field will appear with the placeholder text “Enter Regex Here,” and this is where you can enter the regex to match the text by.

Precision settings on hybrid apps

For Walk-Thru steps on Hybrid elements, the UI is the same as above, except the options are Ignore ID, Identify by text and Ignore text.

Pop-Up Steps (supported from WalkMe Mobile SDK v1.12.0+)

Pop-Up Steps allow you to add a Step that is not attached to an element as part of a Walk-Thru.

To add a Pop-Up Step, simply hover over the space before or after a Walk-Thru Step and click on the plus sign:

As they are not limited by the position of an element, Pop-Up Steps can be customized using the WYSIWYG to appear anywhere on the screen. They are useful for when you want to ask the user to select an option from a list, or if you want to stop mid Walk-Thru for an elaborate explanation of a process.

Even though they are not attached to an element, Pop-Up steps are still associated with the screen they are added on. This is meant to support the process of the WalkMe Mobile SDK identifying the most relevant Step to start a Walk-Thru from.

The best practice is to set a button with an explicit action for a Pop-Up Step. Note that “Next step” is the only action that can be associated with a button in the Pop-Up that will not close the Walk-Thru when tapped. Any other action set for the button (e.g., “OK”, “Maybe”, “Campaign”, “Settings”, etc.) will close the Walk-Thru.

If a Pop-Up Step is set as the final Step on a specific screen and your use case requires that the Pop-Up Step be dismissed without user interaction when the user moves away from the screen on which the Pop-Up is displayed, you can set the Pop-Up Step to be skippable.

Because they are not attached to an element, Pop-Up Steps can only be edited from the Mobile Console and will not have a “recapture” option from the Edit Walk-Thru menu in Power Mode.

“Wait for” Steps (supported from WalkMe Mobile SDK v1.12.0+)

“Wait for” Steps allow you to make a controlled stop in the Walk-Thru flow when you are waiting for a specific action to happen. When playing a Walk-Thru, a “Wait for” Step will pause the Walk-Thru until the set of rules defined for the “Wait for” Step is evaluated as true.

To add a “Wait for” Step, simply hover on the space before or after a Walk-Thru step and click on the plus sign:

“Wait for” rules include a subset of the rules that are usually available for campaign segmentation or Rules Based Goals, including the following:

  • Session time;
  • Time on current screen;
  • Device orientation;
  • Screens;
  • Elements;
  • Goals;
  • User Attributes.

“Wait for” rules can also be set on rules that are unique to in-flow context, such as the following:

  • Seconds passed: Create a delay in the Walk-Thru flow;
  • Screen transition: Wait for the screen to change before continuing to the next Step;
  • Next step is visible: Wait for the next Step in the flow to become available before attempting to play the next Step;
  • Any interaction on screen: Wait for the user to make any interaction with the current screen in order to continue the flow.

When you use Power Mode to preview or edit Walk-Thrus that include “Wait for” steps, the “Wait for” steps will be marked in yellow on the Preview / Edit progress tracker:

Connect to Campaign (Supported From WalkMe Mobile SDK v1.4.0+)

You can set a campaign to be triggered immediately after the last step in a Walk-Thru is completed:

Start Walk-Thru from Specific Step (Supported From WalkMe Mobile SDK v1.13.0+)

When linking one Walk-Thru to another campaign, e.g., through Connect to Campaign, or when selecting a Walk-Thru as the action for buttons and shapes in the WYSIWYG, you can decide which Step the Walk-Thru will start from.

If you select Auto, WalkMe will start from the most relevant step according to the app screen it is currently on.

Was this article helpful?

Related Articles

< Back