Bookshelf v7.7: Invoking the Business Rule Processor

A business rule process can be invoked from a run-time event, workflow, or Siebel script. For all three of these invocation methods, you can prepopulate global variables through the input arguments of the BRP. Input argument names must match the global variables you define.

For an illustration of how to invoke the BRP from a run-time event or a workflow, see the process for Data Validation Manager in Siebel Order Management Guide.

NOTE: Within each session, BRP Processor creates a copy of the BRP executable objects. The executable objects belong only to a single login session and are not shared. These executable objects are cached within a login session. Processes can be either released explicitly or implicitly when the open session is closed.

The FINS CAP Processor Service Business Services exposes three methods. Table 24 describes these methods.

Table 24. FINS CAP Processor Service Business Services Methods
Method - Description	Input Arguments	Output Arguments
LoadProcess - The named calculation process definition is loaded and an executable instance of the process is instantiated in the current Web session	System_ProcessName - The name of a calculation process.	None.
RunProcess - This method executes the named process. If the process definition has not been loaded, the processor loads the definition first. Whenever a BRP process is executed, the processor checks if the current process definition cached in the OM instance. If not, the processor instantiates the process definition into the OM instance.	System_ProcessName - The name of a calculation process.	System_ErrorCode System_ErrorMessage System_ErrorSource Return Codes. See Handling Business Rules Processor Errors.
ReleaseProcess - This method releases the named process executable in the current Web session. This does not affect other open Web sessions.	System_ProcessName - The name of a calculation process.	None.