STAEDEAN LifeCycle documentation

How to: LifeCycle Actions

The LifeCycle actions table is used to record specific actions set for the LifeCycle state or the LifeCycle state transition.
Action handlers are an extension point of the LifeCycle framework. A state transition implements actions using these action handlers.
You can pass arguments to an action handler. For example: the action handler for posting sales documents can have two arguments: post and ship.

LifeCycle actions are set on two levels:

  1. The LifeCycle state
    LifeCycle state action are always applied.
  2. The LifeCycle state transition
    LifeCycle state transition actions only apply to the specific transitions (From State ; To State).

In other words the LifeCycle state actions will always apply to the State and do not have to be repeated in the LifeCycle Transition Actions.

To setup LifeCycle state actions

  1. From the LifeCycle card click States
  2. On the LifeCycle States page select a state and click Actions.
  3. On the LifeCycle Actions page, click New and fill in the fields.

To setup LifeCycle state transition actions

  1. From the LifeCycle card select the LifeCycle line.
  2. Click Line/Actions.
  3. On the LifeCycle Actions page, click New and fill in the fields.
Field M Description
Type √ Select the type of LifeCycle state transition trigger. The following types are available.
• On Status Change - This type triggers the Action during the transition From state to the To state.
• After Status Change - This type triggers the Action when in the To state.
Action Handler Name* √ Select an available action from the list. These actions are provided through a specific code unit.
Argument √ When the action requires arguments, a Boolean is shown. The arguments are set in the Arguments window through the Related Information, Action, Arguments option.
Batch Processing* Using this function, the user can submit specific tasks for background processing. When a Job Queue entry is created for the LifeCycle Instance, the Job Queue will process the specified action. A Microsoft Dynamics BC Application Server (NAS) running the Job Queue parameter is required for this purpose. The LifeCycle Instance submitted will have the status Pending until completed or Failed based on the processing policy.
Processing Policy* These settings apply to batch processing and are interpreted as follows.
• Stop and show the first processing error - The processing will be stopped and the error message is stored in the LifeCycle Entry Detail.
• Errors are not processed - The processing will continue and try to complete as many records as possible. Error messages are stored in the LifeCycle Entry Detail.
Status* Select the status of the transition action. The options for this field are as follows.
• Enable - Action is active and will be executed.
• Disable - Action is not active and will not be executed.
Product* Some LifeCycle actions are relevant only if a certain product has been activated. Use this field to define that product.
  • Upon initial installation these fields are not visible and have to be added to the page through the Personalize option

Default Actions Handlers

The following action handlers are common for all products:

Name Description
PrintReport Prints a report for a record. Specify the report number in the argument.
SendDocForApproval Sends the current record to the workflow as specified for the same table.
CancelWorkflowApproval Cancels the workflow running for the table specified in the LifeCycle.

LifeCycle Setup