Creating Life and Work Event Processes 

Use

You can use the model processes as applications for life and work events. Alternatively, you can create your own life and work events. If you do, you can use the procedure for including life and work events as described in Configuration of Guided Procedures. You also have to take account of various special features.

Prerequisites

To create your own life and work event processes, you require access to the Guided Procedures Design Time area.

Procedure

...

       1.      For all processes that you want to create, specify whether the process can be run automatically.

○     If you set the indicator for an automatic start, the process is run when an employee selects the link to the life and work event on the area page.

○     If you do not set the indicator for an automatic start, only an administrator with the required authorizations can run the process for the employees.

       2.      Define how many instances of a process can be executed simultaneously by an employee.

You should specify that an employee can execute a life and work event process only once simultaneously in a system. This means that the employee cannot rerun the same process while an instance of that process still exists. However, the employee can continue a process at a later time until all the steps have been marked as completed.

       3.      Define how the employee can process the activities in the blocks of a process.

You can subdivide each process into various blocks. You can then specify for the individual blocks whether employees have to carry out the activities in a block in a fixed sequence or whether they can choose their own sequence. To enable employees to choose their own sequence, set the block type to Parallel.

       4.      In the Customizing settings in the back-end system (Cross-Application Components ® Homepage Framework ® Resources), enter the ID of the process template as the URL parameter for the process. In the Define Resources activity (in the V_T7XSSSERRES view), enter the following data:

○     Object name: AInstantiation

○     URL parameter: process.template.id=<process-id>&process.autostart=true

○     URL of the Portal Content Directory (PCD) page

       5.      For the executable objects, enter the context parameter sap.xss.gp.

This provides the Web Dynpro application with the information that the application runs in the Guided Procedures framework.

       6.      Group the context parameters of the executable objects on the process level.

       7.      In the standard system, each action has an automatically generated role assigned to it. Use a grouping role to group the automatically generated roles. Assign the grouping role to a user (for example, the employee who is to run the process).

The employee now possesses all the ESS authorizations required to run the process.