Branching based on Portal or User App contect

[Martyn Houghton]

With the introduction of Service Catalogs we can now specify what progressive capture to use and whether it is used for Portal, User App or Both.

In terms of the progressive capture itself we want to try use a single workflow, but need to branch in the capture workflow depending on whether it is being accessed via the protal or user app. What parameter/variable accessible in the progressive capture workflow determines the context it is being run under which we can then use in the decision condition?

Cheers

Martyn

[TrevorKillick]

Hi Martyn

There is nothing exposed to Progressive Capture to say if its running in the Portal or in Collaboration. I will raise this with development and see what they come back with.

Kind Regards

Trevor Killick

[NeilWJ]

Hi Martyn,

A RFC has been raised internally to provide this functionality. Will update you once it has been done and has been released.

Cheers

[Martyn Houghton]

Trevor/Neil

Thanks for confirming that this has been raised as an RFC.

Cheers

Martyn

[Steven Boardman]

@Martyn Houghton just an update to this to let you know in the next Service Manager update there will be an option in progressive capture to branch depending on if the progressive capture is being used as an agent in the user app, or as a customer on the portals.  

This will allow you to branch to different subsequent forms depending on if it is an agent or customer who is following the progressive capture flow

The next Service Manager update should be available in the next fortnight

Steve

[Martyn Houghton]

@Steven Boardman

Thanks for the update, that will help with us to use a single progressive capture but add analyst specific questions.

Cheers

Martyn