BpmnProperties (Camunda BPM Javadocs 7.10.19-ee)

Fields
Modifier and Type	Field and Description
`static PropertyKey<ActivityImpl>`	`COMPENSATION_BOUNDARY_EVENT`
`static PropertyKey<ConditionalEventDefinition>`	`CONDITIONAL_EVENT_DEFINITION`
`static PropertyListKey<ErrorEventDefinition>`	`ERROR_EVENT_DEFINITIONS`
`static PropertyListKey<EscalationEventDefinition>`	`ESCALATION_EVENT_DEFINITIONS`
`static PropertyMapKey<String,EventSubscriptionDeclaration>`	`EVENT_SUBSCRIPTION_DECLARATIONS` Declaration indexed by activity that is triggered by the event; assumes that there is at most one such declaration per activity.
`static PropertyKey<Boolean>`	`HAS_CONDITIONAL_EVENTS`
`static PropertyKey<ActivityImpl>`	`INITIAL_ACTIVITY`
`static PropertyMapKey<String,TimerDeclarationImpl>`	`TIMER_DECLARATIONS` Declaration indexed by activity that is triggered by the event; assumes that there is at most one such declaration per activity.
`static PropertyKey<Boolean>`	`TRIGGERED_BY_EVENT`
`static PropertyKey<String>`	`TYPE`

Constructors
Constructor and Description
`BpmnProperties()`

Method Summary
- Methods inherited from class java.lang.Object
  clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

public static final PropertyKey<String> TYPE

public static final PropertyListKey<EscalationEventDefinition> ESCALATION_EVENT_DEFINITIONS

public static final PropertyListKey<ErrorEventDefinition> ERROR_EVENT_DEFINITIONS

TIMER_DECLARATIONS
```
public static final PropertyMapKey<String,TimerDeclarationImpl> TIMER_DECLARATIONS
```
Declaration indexed by activity that is triggered by the event; assumes that there is at most one such declaration per activity. There is code that relies on this assumption (e.g. when determining which declaration matches a job in the migration logic).

EVENT_SUBSCRIPTION_DECLARATIONS
```
public static final PropertyMapKey<String,EventSubscriptionDeclaration> EVENT_SUBSCRIPTION_DECLARATIONS
```
Declaration indexed by activity that is triggered by the event; assumes that there is at most one such declaration per activity. There is code that relies on this assumption (e.g. when determining which declaration matches a job in the migration logic).

public static final PropertyKey<ActivityImpl> COMPENSATION_BOUNDARY_EVENT

public static final PropertyKey<ActivityImpl> INITIAL_ACTIVITY

public static final PropertyKey<Boolean> TRIGGERED_BY_EVENT

public static final PropertyKey<Boolean> HAS_CONDITIONAL_EVENTS

public static final PropertyKey<ConditionalEventDefinition> CONDITIONAL_EVENT_DEFINITION

Class BpmnProperties