Function documentationEvent Simulation Locate this document in the navigation structure

 

The creation of an event is simulated and the result specifies which tasks and workflows would be started as receivers of this event.

Features

The result of the test also shows whether errors were diagnosed in connection with the simulated start of the task, which may result in the task or workflow not being started.

The respective error causes are designated with a letter. The legend can be consulted for an short explanation of the error causes. The most common error causes are:

  • There is no workflow definition for the workflow to be started (error cause a).

  • The workflow is not activated (error causes b, c).

  • The type linkage between the triggering event and the task or workflow has not been activated (error cause e).

  • The binding definition from the event container to the workflow or task container has errors (error causes h, i). The task or workflow may nevertheless be started but will probably not be processed as expected.

To remove the error in all of the above cases, position the cursor on an entry and choose   Goto   Task  . This takes you to the definition of the workflow or task in question, where you can take appropriate measures.

Note Note

You activate workflows in the Workflow Builder.

End of the note.

  • A type linkage exists for a task or workflow, but the task or workflow does not exist (error cause g).

    This error can occur if a type linkage is not deleted when its associated triggering event is deleted. Delete the type linkage manually if this occurs. For more information, see Evaluation and Maintenance of Type Linkages.

  • A triggering event is defined for a task or workflow, but the associated type linkage does not exist (error cause d).

    Go to the definition of the task or workflow (  Goto   Task  ) and redefine the triggering event.

  • The actual execution of the task to be started still depends on a check function module being run without errors. It therefore cannot be finally assessed at this point (error cause f).

  • Calls with errors or non-executable calls to tasks/workflows can, for technical reasons, also affect other calls, which may themselves be successful (error causes j, k).

Activities

Executing simulations

Choose   Tools   Business Workflow   Development   Utilities   Event   Simulate Event   to simulate an event.

  1. Describe the event to be triggered with object type and event ID.

  2. Choose to simulate the event.

    Note Note

    You can also simulate an event directly from a step of the type event creator.

    End of the note.