Operation and Connection to Application Functionality (BC-BMT-WFM) 

Purpose

You use this process if you want to test or demonstrate workflow functions.

Demo example for notification of absence in IDES

In IDES, the scenario described can switch between the users WF-MM-3 (creator of notification of absence) and WF-MM-4 (superior).

Both users hold positions that are assigned to the organizational unit US Purchasing. The position of the user WF-MM-4 is the chief position of this organizational unit. It is described by the job head of department, the activity profile of which includes releasing notifications of absence.

IDES may contain other workflow templates and workflow tasks (from the workflow tutorials), which are used to process the same notification of absence.

When you "run through" the scenario, you must be sure only to execute the work items for the workflow template WS30000015 .

Prerequisites

You have made the settings described in the section Preparation and Customizing (BC-BMT-WFM) .

Process Flow

A user enters a notification of absence. This is carried out from the transaction accessed by following the path Tools ® Business Workflow ® Development ® Environment ® Demo: Fill out form.

Entering a notification of absence and creating an event

The action of entering (and saving) a notification of absence creates a new object of the object type notification of absence and automatically generates the event created for this object type. The event container of this event contains:

This event is the triggering event of the workflow template for processing a notification of absence.

Approving a notification of absence

The user you entered as the holder of the position designated as chief position finds a work item in their workflow inbox, which represents the standard task Approve notification of absence. They approve or reject the notification of absence by executing this work item. Attachments can be appended to the work item explaining any reasons.

Important: The processing of this work item must completed in the end using the function Set to 'Done'. (This procedure is defined as a property of the underlying standard task.)

The decision made by the superior determines how the workflow progresses. If the request is rejected, the creator of the notification of absence must make the next move.

Additional information on this step

This step is subject to deadline monitoring. If the superior has not started processing the request within 5 minutes, the creator of the notification of absence is notified as the notification agent for deadline.

This procedure is defined in the description of the step within the workflow definition.

According to the settings you made in Customizing, all employees (= possible agents) whose activity profile is described by the job head of department (or another job you chose) can in principle approve the notification of absence. At runtime, however, this decision is only to be made by the head of department (= selected agent) "playing" the role of this employee's superior. The relevant person is determined from the organizational plan of the company via role resolution.

Employee's decision on how to continue

If the superior rejects the notification of absence, the creator of the notification of absence is asked to decide whether they want to revise or withdraw it.

Additional information on this step

If the creator decides not to revise the notification of absence, the rejected notification of absence is deleted in a background step.

This terminates the workflow.

If the creator decides to revise the notification of absence, they are immediately asked to change it. Advancing with immediate dialog makes it possible for this functionality to be offered without the employee having to choose a work item from their workflow inbox.

What next?

If the creator has decided to revise their notification of absence, it is resubmitted to the superior for approval.