
Pegasystems SmartBPM Suite supports a powerful object-oriented meta-model. The information model is based on classes, which contain properties, flows, rules, and more. The class model supports inheritance, aggregation, and associations for one-to-one, one-to-many, and many-to-many relationships. Classes cover rules and processes as well as work objects – data associated with work in the system.
Classes in SmartBPM solutions are persistent; they are stored in and retrieved from an enterprise repository. Pegasystems uses a relational database as the storage for its repository, and the object-persistence mechanism manages the object-to-relational-DBMS mapping.
Processes, including subordinate processes associated with users and assignments, have variables and attributes defined for them as part of a clipboard, an in-memory work area organized into “pages” associated with the activity. Process flows update and extend this data based on user input, events, data sources, rules, and calculations.
The clipboard is persisted from memory into the database as part of process management, generally by an underlying utility automatically invoked by the process. A developer can save a page from the clipboard immediately, or can execute a later commit to persist all saved but not yet committed pages.
The SmartBPM Suite executes objects from the repository, automatically retrieving and executing the correct process, form, decision rule, integration rule, etc., for a given situation. A cache mechanism handles both the stored object and a compiled version, so the system only has to compile a process or rule the first time it is fetched from the repository.
This execution and persistence model provides clear benefits for system users:
Community
See how your colleagues are driving business success with BPM.
What's New
Interested in Learning More? Submit a Request for more information.