The following table lists the attributes, specifies their categories, and describes their roles:
Task Attributes, Categories and Roles
| Option Name | Category | Description |
|---|---|---|
Name | Overview | The name given to the task. Use a descriptive name. |
Documentation | Overview | Some description or documentation about the purpose of this task. As the name states, it is purely for your own documentation purposes. |
Sharing | Overview | Specifies whether the task owner is allowed to invite other users to contribute to and give input about the task. However, the owner(s) remains the responsible person for the task and has the responsibility to complete it. Any user in the UME can become a contributor to the task but needs to be invited. A contributor is allowed to add notes and attachments to a task and to monitor a particular task. |
Notification | Overview | A task provides the features of sending an e-mail notification to a task’s owner when a task has been assigned to him or her. The e-mail contains the usual attributes, like a subject and a body, which can be dynamically customized to include the details relevant to the task. In the notification, a link to the task to be claimed is included. |
Component | Overview | The component attribute needs to be linked to the component containing a UI for the task. Common UI components include online technologies (Web Dynpro Java, Web Dynpro ABAP, Visual Composer), offline technologies (Adobe Forms), and custom technologies. Custom technologies can be used in case you prefer to use any non SAP technology that can be deployed in as AS Java and that is capable of using the API provided by SAP BPM in order to read and write the data of a task. |
Priority | Overview | Specifies the priority of the task. The possible values are Very High, High, Medium, and Low. By default, the value is set to Medium. |
Custom Attributes | Attributes and Actions | Custom attributes enables you to specify business context data in the tasks. By adding business-related custom attributes to task, it helps give the user more context about that task. For instance, you could add the user ID of the person who started the process to which this task relates. This in turn provides relevant business input to the task so that the appropriate steps can be taken or decisions made. A custom attribute has a name (must be unique), label, data type, and expression. Using the Expression Editor, a value can be assigned to the attribute from the task input. |
Custom Actions | Attributes and Actions | Facilitates the definition of your own tasks beyond the standard SAP tasks. Without opening a task, you are able to perform your own defined actions on a task. Custom actions can also be accessed via SAP BPM API. By default, the following actions are available: view, claim, release, and complete. |
Excluded Owners | Roles | Excluded owners are users that are not allowed to complete a particular task. This is a very used feature, because it enables the exclusion of some users from performing a task. A typical scenario in which such a mechanism can be used is in processes involving requestors and approvers. You want to prevent the user who played the role of requestor from being the approver of his own request. |
Administrators | Roles | Administrators are people(users) who are allowed to administer, process, or complete a task. If there is more than one user allowed to execute a particular task, then the actual owner of the task is the user who eventually completes the task. Administrators are also able to view, monitor, and manage processes and tasks and to start and debug SAP BPM processes. In order for a user to be able to properly assume an administrator’s role, he or she will require a set of administration UME roles and groups assigned to his or her user profile. |
Variables | User Texts | For every task that is created, you can specify the text to be contained in the subject and description of the task in a static manner. This is the message or text that the task owner sees in his UWL, a tool that simplifies task management for business users. From the UWL, users can access alerts, notifications, approvals and their tasks. Variables allow us to improve this functionality by catering to the creation of dynamic custom text that can be used in the task’s text and name. A variable has a name (must be unique), data type, and expression. Using the Expression Editor, you can assign a value to the variable based on any context data or available functions. |
Parameterized Texts | User Texts | Specifies the text or message to be sent to the responsible user via an e-mail notification. This text will also be displayed in the user's inbox. The text can be made dynamic by adding variables. Variables can be added to the text using brackets { }. |
Activation Time | Time Constraints | Specifies the time from which the potential owners can see the task. By default, the task is visible as soon as it is created, so you don’t need to set this field if you don’t have special requirements. This information can be expressed by using an expression. |
Start Deadline | Time Constraints | Specifies the time before which the task must have been started by one of the potential owners. If the time is reached without the task being started, then an exception can be raised. You will need to select the checkbox to raise the exception if this behavior is desired. The start deadline can be expressed by using an expression. |
Completion Deadline | Time Constraints | Specifies the time before which the task must be completed by one of the potential owners. If the time is reached without the task being completed, then an exception can be raised. You will need to select the checkbox to raise the exception if this behavior is desired. The completion deadline can be expressed by using an expression. |
Expiration Time | Time Constraints | Specifies the time after which the task us no longer valid or expires. After this time, tasks can no longer be claimed or completed by a user. This task moves into a canceled status. This information can be expressed by using an expression. |