Lifecycle configuration (legacy)

In IBM OpenPages®, lifecycles can be configured to reduce the need to implement business logic through custom triggers.
Lifecycle can be configured to set field values during a transition on fields other than the LC fields. These fields can be short or long text, single and multiple enumerated, Boolean, integer, decimal, date, user, and user group field types. Depending upon the field type, the field values can be set in the following ways:
  • as an absolute or relative value
  • as an addition to an existing value in the field
  • populated based upon a value in another field

For example, this could be used to copy the lifecycle Status field value to the “normal” status field, so that existing views, reports and helpers can continue to use that status field value.

Lifecycles can also be configured with conditional logic to gate transitions. You can use Boolean logic using field values on the object and on immediate child and parent objects. The logic can include values from text, single and multiple enumerated, Boolean, integer, decimal, and date field types. For example, this could be used to prohibit submitting a Loss Event for approval if it does not have a recognition Date value. If the conditions are not met, then the transition processing is stopped. An error is displayed in the user interface and recorded in the log.

For more information on how to configure lifecycles, see the Trigger Developer Guide.