6 In-Context Launching Task Flows in Retail Applications

Retail Applications can expose select task flows retailers can directly launch into. This feature is referred to as in-context launching in a Retail Application. Retailers can launch these task flows directly through specific URLs.

Retail Applications will provide information about the various task flows retailers can in-context launch into including the URLs and the required parameters.

Retailers can use these URLs in other web pages as links. For example: the URL to a task flow that invokes the Summary Match Flow in a Retail Application can be added as a link to dashboard report on a BI server.

When the user clicks on a URL to a task flow, the Retail Application will open in a new browser window or tab depending on the specified target of the URL. The requested task flow will be shown as a UI tab within the Retail Application.

Limitations of In-Context Launch via URLs

The In-Context launch feature will not detect if there is an already opened window or tab for the Retail Application. So when a user clicks on a link to a Retail Application's task flow, say, a report on a BI server, a new browser window or tab will be opened even though the user already has an existing browser window or tab opened for that same Retail Application.
If a BI dashboard is added on the Retail Application, and if that dashboard has a report that contains links to in-context launchable task flows in the same Retail Application, a new browser window or tab will still be opened.

List of In-Context Launch Task Flows

Summary Match Flow

In-context launch from the Invoices Due Soon report located on the user dashboard. When this screen is launched from the Invoices Due Soon panel on the dashboard, the system fetches all the invoices and receipts associated with the default match key from the supplier and for the given invoice.

http://<host>:<port>/ReimViewController/faces/Home?navModelItemId=SummaryMatchService&supplier=130001&invoice=INVC 51319 02

Table 6-1 Summary Match Flow

Parameter ID	Required?	Description	Sample URL
Supplier	Yes	Supplier/Vendor Id	http://<host>:<port>/ReimViewController/faces/Home?navModelItemId=SummaryMatchService&supplier=130001&invoice=INVC 51319 02
Invoice	Yes	Invoice/Document Id	http://<host>:<port>/ReimViewController/faces/Home?navModelItemId=SummaryMatchService&supplier=130001&invoice=INVC 51319 02

Discrepancy List Flow

In-context launch from the Invoices Due Soon report located on the user dashboard. When this screen is launched from the Invoices Due Soon panel on the dashboard, the system fetches all the discrepant invoices for the given supplier and invoice

http://<host>:<port>/ReimViewController/faces/Home?navModelItemId=DiscrepancyListService&supplier=2300&invoice=am_6901_1

Table 6-2 Discrepancy List Flow

Parameter ID	Required?	Description	Sample URL
Supplier	Yes	Supplier/Vendor Id	http://<host>:<port>/ReimViewController/faces/Home?navModelItemId=DiscrepancyListService&supplier=2300&invoice=am_6901_1
Invoice	Yes	Invoice/Document Id	http://<host>:<port>/ReimViewController/faces/Home?navModelItemId=DiscrepancyListService&supplier=2300&invoice=am_6901_1