Stardust provides support for a business object-centric view on Process Data.
In many cases you might intend to access process information via the business objects the processes are working on, for example:
In Stardust these objects are mostly Process Data (e.g. named Claim, Order, Trade, Fund) of a specific structured data type (e.g. Claim, Order, Trade, Fund) whose values or instances are stored in the structured_data_value table of the audit trail.
As different processes store (independent) process data, referring to the same business object via a Primary Key (e.g. Member Id, Fund Name) an implicit version history of the Business Object is created. The latest version could be considered the "current state of a Business Object as known to Stardust".
Stardust Business Objects Management allows you to search for Business Objects, find corresponding Process Instances and even update and/or create Business Objects independently of Processes creating Process Data.
You can mark process data of structured type as Business Objects. A primary key out of the (top-level) data of the structured data type can be defined, which allows to identify the Business Object in the Browser Modeler.
Relationships to other Business Objects can be created by specifying fields with single or multiple cardinality to serve as foreign keys to other Business Objects.
For details on marking process data as Business Object, please refer to chapter Specifying Data of the Business Process Modeling Handbook.
The Stardust Portal provides a view in the Business Control Center perspective to manage Business Objects. It allows to:
For details on this view, please refer to chapter Managing Business Objects in the Stardust Portal documentation.