ProProcess V4.0

1 Necessary migrations
2 Further notes
3 Breaking Changes
4 Important information on how ProProcess works from version 4.0
5 Release Notes

Necessary migrations

When updating to BPF V4.0 or higher, the following migrations must be carried out.

A workbench and customising transport is required for the migration.

Updating the standard tasks

Existing standard tasks must be updated using the report /PCH/BPF_SETUP_STANDARD_TASKS (Generate/update tasks option) and transported to the corresponding downstream systems.

The update must take place on a client in which repository objects can be changed.

Typically, this is the development client on which the ProProcess workflows are generated.

Non-updated standard tasks can lead to errors when activating or executing workflows.

Initial definition of the modelling client

The modelling client must be initially defined for existing processes using the ProProcess tools or transaction /PCH/BPF_UPD_CPRC_LS.

The update must take place in the client in which the processes are modelled.

Processes without a modelling client cannot be changed, activated or versioned.

Updating the process workflows

Migration of processes to the new workflow generation using the programm /PCH/BPF_MIGRATION_WF_GEN_VS. The same authorisations are required as for the activation of ProProcess processes.

The migration must take place in the client in which the processes are modelled and activated.

Further notes

The generation of workflows has been adapted with ProProcess 4.0. New processes and new process versions are always generated with the new functionality.

Processes that were activated before version V4.0 are not updated automatically.

Processes may now only be changed in the corresponding modelling client in order to avoid data inconsistencies.

Processes without or with the wrong modelling client cannot be edited, activated or versioned.

Due to the complexity of the adjustments and the modelling and extension options, it is strongly recommended that processes are tested after updating and migrating to ProProcess V4.0 or higher.

If migration is not carried out against recommendation, the processes must still be tested.

There are breaking changes. Customer-specific implementations must be checked and adapted if necessary.

Breaking Changes

Synchronous sub-processes are started differently from BPF V4.0. Customer-specific implementations may need to be adapted. Existing or non-migrated processes are not affected.
Adjustments have been made to the internal structure of BPF. Customer-specific implementations that use internal BPF functionalities may need to be adapted.
The semantic objects and actions change in the delivery. Customer-specific catalogues and groups must be checked.

Important information on how ProProcess works from version 4.0

Information on Functionality for ProProcess Version 4.0 or greater