View source for Launching a service case from the composite

== Adding a link that passes context ==
It can be valuable to use links or buttons that pass context to the service request that is launched. For example, selecting a button next to the '''Amount Due''' field might launch a Make Payment service request with the amount already selected. Alternatively, selecting a transaction from a list could initiate a dispute of that charge, reducing the number of steps and the amount of typing that the CSR needs to perform to complete the request. In this example, the process flow takes a parameter called <code>TxnId</code>. This parameter is passed to the flow on launch in the configuration of the link. In the following figure, the links in the grid are configured to launch the Dispute Transaction service request. When you click the link, the link passes the value of the ''.TransactionID'' property to the process flow in the <code>TxnId</code> parameter.
[[File:LinksInATable.jpg|none|thumb|786x786px]]
[[File:LinksinatableParam.jpg|none|thumb|681x681px]]
[[File:Linksinatabledispute.jpg|none|thumb|1584x1584px]]
You can also use this feature to optimize the CSR experience when a single selection from a table is the most common use case. Use that option for the most commonly used service requests to gain the highest efficiency in your operation.

For more information, see "Launching a service case from the composite" in [https://community.pega.com/knowledgebase/articles/pega-customer-service-implementation-guide/85/implementing-user-interface-changes-interaction-portal Implementing user interface changes to the Interaction Portal].