How can I dynamically display an application-specific training URL in the Walkthroughs panel when a user clicks the button on a card in a Workshop loop layout?

Ask the Community
1

Can Walkthroughs dynamically display training content based on the clicked Workshop card?

I have a Workshop application with a loop layout displaying multiple application cards. Each card is an instance of a child module containing a Training button. Each application has its own training URL.

For example:

  • Clicking Training on the prasad card should open the Walkthroughs panel and display prasad training link or content.
  • Clicking Training on the kumar card should open the same panel but display kumar training link or content.

I want to reuse one walkthrough and dynamically pass the clicked card’s application name or training URL, rather than create a separate walkthrough for every application.

Is this possible using native Walkthroughs? If so, how can I configure the Training button to open the walkthrough and pass these values? If it is not supported, what is the recommended alternative?

2

Hi @SHIVAprasad77
not with native walkthroughs as far as the docs go. walkthroughs open from the Walkthroughs option in the workspace sidebar on the resources they reference, and the content is configured in the walkthrough itself. I couldn’t find a workshop event that opens one, or any way to pass a variable into it

what works natively is doing it inside the card itself. the loop docs say anything that differs per card has to come from the object passed into it, so:

  1. add a training_url property on your application object type (or a field in the struct, if you’re looping over an array)
  2. in the child module, create a string variable = the training_url property of the module interface object
  3. add a drawer to the child module with either:
    • a markdown widget with input = that string variable (e.g. built as Open prasad training), or
    • an iframe widget with URL = that string variable, if you want the training page shown inline. needs the target site allowed in the CSP and its frame-ancestors header
  4. training button (button group) > on click event > Open {drawer name}

every card gets its own drawer with its own link, and it’s one child module for all applications

if you’d still like walkthroughs for the step-by-step part, keep one walkthrough per application and put its link in the same drawer next to the training url