When using deferred processing functionality in your Cúram application, you need to configure the DPProcess table prior to runtime in order for it to work correctly.
The DPProcess table, provided as part of the SDEJ, must contain names for the methods within your application that have been modeled and defined as being deferred using the <<wmdpactivity>> stereotype. For each deferred method, you must define a name that describes it, for the processName field. This string value is what must be used when requesting for a deferred process method to be enacted. The primary key of this table is a processName field.
Configuration of Deferred Processing Table details the properties of the DPProcess table.
Property |
Description |
Type |
Requirement |
---|---|---|---|
processName |
Name that describes your deferred processing method. |
String |
M |
interfaceName |
Fully-qualified interface name of a BPO with a <<wmdpactivity>> method corresponding to the deferred process. |
String |
M |
methodName |
The name of the <<wmdpactivity>> method corresponding to the deferred process. |
String |
M |
ticketType |
Code table value describing the type of deferred process. The meaning of this is Application-defined, for example, see the Cúram TicketType code table. |
String |
O |
subject |
Short description of what the deferred process method does. |
String |
O |
Configuration of Deferred Processing Table shows an example of how a DPProcess table might be populated.
processName |
interfaceName |
methodName |
ticketType |
Subject |
---|---|---|---|---|
DO_DEFERRED_OPERATION |
server.curam.bizinterface.SomeProcess |
doSomething |
CLAIM |
This method does something. |
DO_ANOTHER_DEFERRED_OPERATION |
server.curam.bizinterface.SomeOtherProcess |
doSomethingElse |
CASEREVIEW |
This method does something else. |