...
Underneath that, add the troubleshooting macro onto the page. You can add the macro through the “insert” button on the toolbar and searching for “troubleshooting”. The macro takes no arguments.
Allowing access
The macro does not use, store or process any user information but it is required by the framework. Therefore each user will be presented with a message like this on first load:
...
To enabled to macro, click “Allow Access” and then “Accept” on the next page.
Adding answers
Now that you have allowed access but have not added any answers or next questions, the page will look something like the below screenshot.
...
To next step is to create child pages of this original page with some potential answers to the question. The title of the page is important here, because those page titles will be displayed as buttons for readers to select on the main page.
For example, this page structure results in the following options in the troubleshooting page:
...
Adding content to pages
Now we need to continue on with more questions so that we can better understand the reader’s problem. This is done in the same way as the original question. The first paragraph is the question to ask, with all subpages as potential answers to choose from. This can continue down for as long as you need to get to a specific problem.
Any time you add more than the first paragraph to the page a “See More” link is displayed in the macro. This allows the user to get more context, which might help them to answer the question.
Example
See Example Troubleshooting Guide for a very example structure. The macro may not load for you from this space, but will work like below when using a non anonymous login.
...