ProProcess V5.0.0

When a sub-process is started, the BAdI /PCH/BPF_PROCESS_START->PREPARE_START_PROCESS() provides information about the corresponding parent process.

In ProProcess Inbox, minor performance improvements have been made when processing complex processes.

The process modelling now supports the Milestone as modelling component.

A ProProcess Milestone is an important step to be achieved in a ProProcess process, and not to be equated with a project milestone.

ProProcess milestones can be defined on:

• exclusive gateways, but only on a unique path
• on exclusive gateways with a maximum of one gate, therefore also within repeat gates
• not within sub-processes
• not on parallel gates

ProProcess milestones can be technically repeated (repeat gates) and skipped.

The list is supplied with four (4) new columns:

• current milestone
• next milestone
• last milestone
• progress

When the Process Designer is started, the object types defined in customising are checked for consistency. If there are inconsistent object types, the process cannot be activated. This check does not prevent the selection of an incosistent object type and errors may still occur.

The customisation consistency checker (program) has also been extended to check that the object types used are correct.

A new function has been introduced that allows Process Responsibles and Administrators to change the status of an object-list.

In addition, objects can be changed directly by a Process Responsible or Administrator without having to change the status of the object list first.

An option has been added in reporting to restrict the selection by agent to currently running activities only.

A new parameter has been added for controlling the graphical display of a process.

There are three display-modes available:

• complete (full)
• compact (consolidated)
• condensed

The process priority is now provided as text in the inbox.

There are times when workitems do not progress because events (SWE_EVENT_QUEUE) are available for processing but could not be processed due to locks. These should show up in the problems and there should be a solver for this.

The Process Analysis Fiori App will be enhanced (from BPF Version 5.0.0) in the ‘Structural representation’ view with statistical data about Milestones.

When a process is deleted by Admin., the runtime error OBJECTS_OBJREF_NOT_ASSIGNED(CX_SY_REF_IS_INITIAL) occurs in rare cases in the class /PCH/CL_BPF_WI_RINBOX method ON_OBJECT_DELETED.

This has been fixed.

If non-unique objects are registered in the key table for the BPF reader /PCH/CL_BPF_API_OBJ_RPRC_ASSGN, there is a program interruption (with a dump) when reading the data (error ITAB_DUPLICATE_KEY in /PCH/CL_BPF_RD_PROCESS->SELECT_BY_OBJECT).

This has been fixed.

In a multi server environment the order of activities within the widgets process hierarchy and process graphic can be incorrect. This has been corrected.

Under the following circumstances, the conditions for a automatic start of a process (on a material object) are not evaluated correctly:

• the object is created/changed via a BO class (e.g. /PCH/CL_BO_MARA)
• the data from the autostart condition is changed in an Exit.

This has been fixed.

When creating a material or document via a BO, incorrect processes could occur. This has been fixed.

To forward an activity (work item) a corresponding workflow authorisation is required. However, the function is also made available to the user if they do not have the authorisation. This has been fixed.

If an object assigned to an object-list is provided in the BAdI, this assignment is not used and the object is always assigned automatically. This has been fixed.

In the class /PCH/CL_BPF_RD_RPROCESS_LISTNG method FILLUP_OBJECT_DATA, the runtime error UNCAUGHT_EXCEPTION (/PRONOVIA/CX_NOT_SUPPORTED) can occur if object data is displayed for an object that does not support certain information (e.g. status). This has been fixed.

The root cause of workflows not starting was not correctly detected in the ‘Troubleshooting’ widget. This has been fixed. The following states are now detected as erroneous:

• Processes with no starting event,
• Processes with incorrectly processed starting events,
• Processes with unprocessed starting events after a period of time.

The widget “Processes for the Object” is not updated while other widgets are refreshed automatically. This has been corrected.

Additionally, the performance has been slightly improved.

When switching between two widgets of type “Process graphic”, old content may be displayed in the widgets. This has been corrected.

The selection condition compares the wrong field against the select-option on the screen. This has now been corrected.

When filtering a list of processes based on their object type, this runtime error occurs. This has been fixed.

The value lists in filters have been sorted alphabetically ascending.

Under certain circumstances, objects are not released in the process designer, which could lead to a memory leak. This problem has been fixed.