BusinessProcessView Table

Typically, before starting an instance, an end user selects a reference to a specific QueryViewSpec as one of the input parameters into a process. In this way, the end user may decide which type of calculation to perform as well as which columns to create as an outcome of the business process instance. After the user selects a parameter set and starts a business process instance, the Infinity platform calls upon .NET code to process a set of records. This .NET code is the heart of the business process. The assembly and class containing this code and is referred to within the BusinessProcessSpec through the ProcessorComponent XML element. The basis for the set of records to be retrieved and processed by the .NET code is defined with a QueryViewSpec. The QueryViewSpec also defines the format of the output of the business process via the columns referenced within the QueryViewSpec. A business process may have more than one associated QueryViewSpec, which is tracked with the BusinessProcessView table. The BusinessProcessView table contains information pertaining to views used for output for a given business process. This table, shown below to the right of the BusinessProcessCatalog table, is a child table of the BusinessProcessCatalog table.

Figure: BusinessProcessView table is populated when a QueryViewSpec contains a BusinessProcessOutput tag

The BusinessProcessView table is populated with a row when a QueryViewSpec which contains a BusinessProcessOutput tag is loaded into the catalog. This defines how the output format joins with the business process. For a given business process, the BusinessProcessView table can contain references to many QueryViewSpecs through the QueryViewCatalogID field. You can deduce that a business process could be run with any one of the several query views referenced.  Below is an example of QueryViewSpec used by the food bank inventory business process. Note the BusinessProcessOutput tag at the bottom of the spec. When the BusinessProcessOutput tag is included, a row is added to the BusinessProcessView table.

Figure: The BusinessProcessOutput XML element links the query view to a business process.