New and Changed Features
Now you can view the dataslot information for the process instance by clicking the Dataslots button in the application toolbar. The dataslot information can be helpful, for example, in process debugging.
Role-Based Process Ownership and Visibility
A new “process ownership” concept has been introduced to increase the level of visibility for the managers of specific business processes or a specific business area. A process can be owned by one or more roles. In My Processes (History) Browse, a user of the roles can view all instances of the process that the user is responsible for. Administrators can define which role is responsible for which business process.
Changes to My Processes (History) Browses
The My Processes (History) Browses now display process instances according to role-based ownership instead of creator. A new Creator field has been added to the browses.
Maintaining Process Ownership
Administrators can use Process Ownership Maintenance to define which user role is responsible for which business process. The relationship between Application and Role field is not restricted as one-to-one.
Viewing Completed Work Step in Processes Browse
In the Tile screen view of Processes Browse, you can see active work steps of the process in a child browse. Now in the child browse, a new tab is available aside the Active Work Steps tab to show all completed work steps.
Visibility to Suspended Process Instances
Suspended process instances can now also be seen in My Processes Browse and All Processes Browse.
Launching Processes from Custom Forms
Now the system allows users to launch a process from a custom screen in QAD .NET UI. To achieve this, the application developer defines the custom form and process in BPM Studio and the administrator adds a menu entry to .NET UI configuration file. After these actions, authorized users can see the launch process menu in .NET UI and use it to launch the process.
Packaging and Deploying Business Processes
Now administrators can use a tool bpm_package.sh to package deployed processes, BizRules, and any other BPM artifacts in one BPM environment and deploy or install it to another BPM environment. The artifacts can include business objects, business object meta data, adapters, adapter meta data, dataslot meta data, messages, and any other common resource files.