ProProcess V5.1.0

With BPF 5.1 a new Activity Reporting is available.

Please see the user manual for more information: BPF Activity Reporting

Add process id to the process reporting selection screen. (selection with * possible)
Add to all related widgets.

In the process reporting widgets quick filters for Process ID and Process Description have been incorporated.

The GUI Dialog for the Task “simple process adjustment” has been redesigned to optimize visual structuring of the activity / agents.

In process reporting, the icon for the object type is now also displayed in the object key column.

A new widget displaying the open activities for a process is available. The available information is identical the the open activity reporting widgets.

Pattern names are allowed but inconsisten checked. From now on only specific users/roles are allowed as selection criteria.

In the graphical display of a runtime process, the role of an agent of an activity is not the role assigned to the activity but the role where the user has been maintained, even if this is an role which as been included. This has been corrected. The role assigned to the activity is now displayed.

A runtime error "Uncaught Exception CX_SY_ITAB_LINE_NOT_FOUND" can occurr in class /PCH/CLA_BPF_MDL_RPRC_LIST Method LOAD_LAZY_INT. This has been corrected.

Columns showing object status data are not displayed, if not at least one other object field is displayed. This might also apply when adding these columns during via layout management. This has been corrected.

An activity in status created usually means, that the corresponding process is in an erroneous state or that the workflow has not yet reached the activity. In both cases ist should not be possible to complete the activity.

This has been corrected.

When zooming using ctrl + mouse wheel and hovering over the “mini map” (or any other control) the whole view and not just the process graphic is zoomed. This can lead to an unusable UI. This has been corrected.

Dynamic process adjustment data is not properly invalidated when required. This can lead to inconsistent behaviour when the same data is changed by multiple persons without leaving the transaction. This has been corrected.

When saving the dialog for the “simple process adjustment” task, the error message “An unknown error has been occurred” is shown if the Dialog contains an activatable task with at least one non changeable agent (User or role). This has been corrected.

The agent activation is sometimes not consistent with the activity activation and/or the customizing. This can happen when:

• An agent which has been defined as “activated” in customizing can be deactivated after the corresponding activity has been deactivated and activated again.
• The activity is initally deactivated but can be activated
• Multiple agents are defined on an not replicatable activity.

This has been corrected.

The activation / deactivation of predefined agents is not possible in the "simple process adjustment" task when the activation shall be reverted to the original activation. Also deletions of added agents is not applied. This has been corrected.

In systems, in which customizing cannot be changed due to system settings (customizing and/or repository not changeable), error messages regaring the customizing setup are displayed. this has been corrected.