Converting BPDs to processes

Convert business process definitions (BPDs) to processes so that you can work with them in the web Process Designer.

Note: The desktop Process Designer and BPDs are deprecated.

When you convert a BPD into a process, the subprocesses inside it are also converted, and tasks and their properties are maintained. References to linked processes and heritage human services are maintained. However, the referenced artifacts are not converted. To convert your user interfaces, you must separately convert your heritage human services and coaches. See Converting deprecated functions. You can invoke heritage humans services from a process, so you can convert your BPDs and continue to use heritage human services and coaches until you are ready to convert your user interfaces to responsive user interfaces.

The converted process has the same activities, process flow, and properties as the BPD, with the following exceptions:

Ad hoc start events

These events are deprecated and are not supported in the web Process Designer. These events are converted to a Start Message event with no UCA implementation. You need to change the event to an ad hoc activity and implement it as a subprocess.

Activity assignments

The following assignment types (Assign To) are not supported in the web Process Designer because they are deprecated in the desktop Process Designer.

Last User in Lane
Routing Policy
List of Users
Custom

These types are replaced with Lane assignments. To achieve the same effect as these assignment types, you need to implement the function manually by using a team filter or retrieval service. The other settings on the assignment are maintained where applicable, for example User Distribution and Experts Team.

None tasks: The None type is not supported in the web Process Designer. None tasks are converted to empty Script tasks. All other settings are maintained, such as pre/post, skip condition, and loop behavior. The empty Script task is semantically equivalent to the None task.

Items that are not converted

There is no equivalent artifact for these items in the web Process Designer, and therefore they are ignored.

Milestones
Any icon settings on process nodes
Simulation configuration
KPI configuration
Handling error events from previous releases. See Error events in models from V7.5.x and earlier.

How to convert BPDs to processes

Before you begin:

This conversion is one way. After the BPD is converted to a process, you cannot undo the operation, so take a snapshot before you convert the BPD. You can then compare the two by opening the snapshot in the desktop Process Designer and the process in the web Process Designer.
Conversion of BPDs to processes is done at the process app or toolkit level. BPDs in dependent toolkits are not converted automatically. You must open the dependent toolkit and convert the BPDs manually.

To convert a BPD to a process in the desktop Process Designer:

Open the process app or toolkit.
In the library, select the BPD that you want to convert. To select multiple BPDs, hold the Ctrl key and click the BPDs that you want.
Right-click, and select Convert to process.
Expand Processes in the library. The converted processes now appear under Processes.

To convert a BPD to a process in the web Process Designer:

Open the process app or toolkit.
Open the Process App Settings or Toolkit Settings editor.
In the BPD Conversion tab, select the processes that you want to convert and click Convert.
Expand Processes in the library to see the converted process.