Guided SetUp In Scoped Application

[pethumdesilva]

Hi All,

I have created a scoped application and need to add a guided setup to it. Following the documentation provided here, I created a guided setup using the adoption service. In my application menu module, I am using the following URL as the direct link: /now/adoptionservices/setup/{guided setup sys_id}.

However, when I publish my scoped application to the application repository and install it on a different instance, the guided setup module opens with all steps marked as completed, although users can still configure the guided setup.

My question is: What is the correct way to create and publish a guided setup within a scoped application to ensure that it works as expected when deployed to other instances?

Regards,

Pethum

[BurtCrepeault]

Hi,

I don't know if you figured this out, but I've been experimenting with Guided setup lately (in WashingtonDC) and found a way that works pretty well. Befor publishing a new version of the app, I always open the Guided setup for edit. This places it back into Draft mode. I then simply finalize it as usual, so it gets back to Published. Moving to the app to another instance will then have all step set to Not started.

It looks very different in Xanadu, as setups are based on playbooks and you can have an active and published Guided setup, all the while working on a newer, unpublished draft. I'm not sure how both the published and draft version travel well with the app, I still have to try that. Let me know if you have the answer.