Action Set Library

Action Set Library

This feature will help save you time creating Web Journeys, adding user sessions and actions to audits, and managing those journeys, user sessions, and actions as changes occur. You can save a series of actions as an "Action Set" which can then be reused across Web Journeys and Web Audits. You can then edit those steps from one central location which will push the update to all Web Journeys or Web Audits where applicable.

With ObservePoint's Action Set Library you can:
  • Store and access commonly used actions—such as a login sequence—in a singular place
  • Distribute actions across multiple journeys or audits all at once, instead of one by one
  • Apply rules to Action Sets to be applied wherever the Action Set is used.
  • Customize action sequences for multiple journeys and audits

How to Create an Action Set

In order to create an action set you can do this in one of two ways. The first is to go to the Action Set Library and then click Create New.

After that you'll be in a screen very similar to the one used in Web Journey creation. All you need to do is add the steps you want to include. You'll notice there are some additional settings that apply specifically to Web Journeys or Web Audits.

The second is by going to any existing Web Journey or Web Audit that contains actions or a user session. Now to the left of the actions you will see a button labeled Create Action Set. 

Once you click that you'll have the option to select which actions you are interest in saving as a set. The steps must be in order and contiguous (no skipping actions).

Then you can click Save as New Action Set.

When you save an Action Set it's going to ask you if you want to replace the same actions in other Web Journeys and Web Audits. Most of the time you want to select Yes here and replace those steps. What it's doing is going to every single Web Journey and Web Audit and checking the steps to see if it finds a match, if it finds a match and you select Yes here it will replace those steps with the Action Set. 

Note: The actions have to be the identical (it will only look at the first selector, so long as you ensure that one is the same in the steps in both places it should find the other instances of the steps).

When you select "yes" it's going to show you all the Web Journeys and Web Audits it finds where it can do a replacement. Select which ones you're interested in having replaced and click the confirm checkbox before saving. As noted once this is done it cannot be reverted.

Once you save the steps that are included in the Action Set, it will collapse down into a single action with type "Action Set".

Selecting An Existing Action Set

Along with the other updates you'll now see Action Set as an Action type in any Web Audit or Web Journey. To use it, simply add an action with an Action Type of "Action Set". From there you can select which Action Set you're interested in adding.

Once it's added you can include more steps after or before that set. The Action Set itself will always be tied to the main copy so remember that it can't be edited unless you also want to change the steps for everywhere else the Action Set is used. 

Managing Action Sets

To manage or update your Action Sets go to the Action Set Library from the main screen of ObservePoint.

From here you can see any Action Sets you've saved and where those Action Sets are used within your account. If you need to update the steps, make a copy or delete an action set, hover over the one you're interested in and the icons will appear to the right.

When deleting you'll see a pop-up screen warning you of the potential repercussions. Make sure you are absolutely positive you want to delete an Action Set before you do as you could potentially break all the related Web Journeys and Web Audits.

There is another way to edit your Action Set and that's from within any Web Journey or Web Audit where it's been applied. You'll see the button to Edit Action Set next to that step. 

Note: Remember any edits done to an Action Set will be applied across EVERY instance of that action set in any Web Journey or Web Audit where it exists.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.