Example 2 (advanced technique): Using process key fields to filter records that will be sent to a customized Inbasket

This example describes a scenario that is intended to give you some ideas about how you might combine the advanced technique of process key fields with customized Inbaskets.

You can use workunit data that comes in from workunit process key fields to determine which Inbasket (customized or standard) a work item action should be sent to.

For example, suppose your company has a Purchase Approval tasks that reviews and approves all purchases that come in from vendors. Suppose further that your company has negotiated some special terms with some vendors which states that if you pay these invoices within a faster than normal timeframe, you will get a 10% discount. Because of this you want to give high priority to these invoices.

One way to do this would be to have an additional Task called Speedy Purchase Approval that receives requests for payment from these vendors.

In order to make this scenario work, process key fields would be created for these vendors would need to be created and accessed in the process that routes the purchase orders.

See Adding workunit variables as columns in an Inbasket list.