Copyright 2021 - BV TallVision IT

Methods, business object and event

  1. Methods are functions that can be executed from a workflow task
  2. Methods are always defined on a business object
  3. A business object should be regarded as the main “object” or “subject” of the workflow
  4. Events are created on the business object (read: the event definition)
  5. Events can be used to trigger a workflow or a workflow task
  1. There is a clear relationship between the event and a business object, as events are created for a business object
  2. Business objects have key fields (almost always)
  3. A method is called by a task which can be triggered by a triggering event
  4. A method can also be called from another method, using macro SWC_METHOD_CALL

Triggering

  1. Events (read: the event instance) can be thrown/created in several ways like: change documents, a workflow, from an ABAP via a function module call or via a test tool
  2. A task can be triggered by a triggering event
  3. A task can be triggered as a step of a workflow
  4. A workflow can itself be started from another workflow (sub workflow)
  5. A workflow can also be started directly (even without event) (e.g. via function module SWW_WI_CREATE_SIMPLE)
  6. A triggering event on a task or workflow needs to be active, this is called linkage (linking a workflow or task to an event)

Containers

  1. Containers hold data that is relevant to the workflow, event or task (or rule)
  2. A workflow has a container. A task has a container. An event has a container
  3. A method has a container. A rule has a container
  4. A binding is a mapping from container to container (e.g. From workflow to a workflow task)

Tasks

  1. Tasks relate to a method. Executing a task is related to executing a method
  2. There are background tasks and foreground tasks or dialog work items
  3. Foreground tasks should be assigned to an organisational unit (an organisation plan, a job, position, role, rule or directly to a user)
  4. Foreground tasks will be presented to Mr. Enduser in the inbox

Reporting and inbox entries

  1. Reporting can be used to find the workflows that started and their status, where errors occured, the log can be used to determine what went wrong
  2. The longtext on a foreground task will appear in the inbox message
  3. Any objects (instances of business objects) in the workflow container of a foreground task, will appear as attachments in the inbox entry