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:
atg.markers.bp.ProfileBasedProcessConfiguration
tracks a profile through a business process. By default, a process of this type tracks the session’s profile.atg.commerce.markers.bp.OrderBasedProcessConfiguration
tracks an order through a business process. By default, a process of this type tracks the shopping cart’s current order. This class is only available if your installation uses Commerce.
The configuration component defines the business process using the following properties:
Property Name | Description |
---|---|
| The name of the business process |
| How to handle attempts to add duplicate markers. Valid values are: Keeping the default ( |
| 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 |
| Boolean used to determine whether a business process is able to process events. Default is |
| The type of - For - For |
| 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.