Each business process is defined by a configuration component that extends the atg.markers.bp.BusinessProcessConfiguration abstract class. Two subclasses of the BusinessProcessConfiguration class already exist:

The configuration component defines the business process using the following properties:

Property Name



The name of the business process


How to handle attempts to add duplicate markers. Valid values are:
- ALLOW_DUPLICATES - no duplication check
- REPLACE_DUPLICATES - delete all duplicate markers, and add the new marker
- NO_DUPLICATES - if the marker already exists, discard the new one. This is the default value.

Keeping the default (NO_DUPLICATES) means that once a business stage has been reached, no change is made if that stage is reached again.


Boolean used to indicate whether a business process is active. Disabling an active business process causes all associated tasks to halt. For example, the achievement of new stages in a disabled business process will not be tracked. When you re-enable a business process, it begins at the point to which it had stopped. Default is true.


Boolean used to determine whether a business process is able to process events. Default is true.


The type of RepositoryItem to which the markers are attached. This property is used for deleting all markers attached by a given business process. The default value is derived from the value of another component property:

- For ProfileBasedProcessConfiguration, the value is provided by the ProfileRepositoryMarkerManager.markedItemType property. Typically, the value is user.

- For OrderBasedProcessConfiguration, the value is provided by the OrderTools.defaultOrderType property. Typically, the value is order for Consumer Commerce, and b2border for Business Commerce.


An array of the names of the stages that make up the business process.

The two important properties here are stageNames and duplicationMode. You need to define the stages of the business process that you might want to track. Make sure that your application design will allow you to mark these stages using a scenario, a servlet bean in a JSP, or directly using the business process tracking API. See Marking Business Process Stages and the atg.markers.bp package in the ATG Platform API Reference for more information.