Category 

Use

You use a category to group work items from one or more single-step tasks for a user. A category is the basis for the definition of a subscription. When you define a subscription, you do not reference work items or single-step tasks directly, but the corresponding category.

Assigning Notifications to a Category

Work items or the corresponding notifications are normally given the category that is set as the default category in the scenario. You can also define your own categories. This is useful if you want to define different delivery schedules for particular work items or notifications, for example.

You have the following options when assigning notifications a particular category:

 

Category Defined By	Description	Area of Use
Scenario (Programming)	Category defines the selection logic programmed in the scenario	Can only be used when developing your own scenario
Handler assignment	In handler assignment, a particular category is assigned for one or more single-step tasks	Intended for use by SAP applications
Filter	Category is assigned by the filter	Recommended procedure for SAP customers
Scenario (standard)	Category that is the default in the scenario is assigned	Default setting. Used when the category is not assigned by one of the methods already mentioned

 

Differing Message Templates

If you want to define a differing message template for the work items of a particular single-step task, you just need to specify the ID of the message template required for the relevant single-step task in the Hander Assignment view (see also: Handler Assignment). You do not have to define your own category for this. 

Features

Required Reliability

For each category you can define a required level of reliability for delivery. This is compared with the level of reliability offered by the deliverer. If the deliverer can offer the required level of reliability, the delivery is made at this level. If not, the delivery is made with the next best level of reliability.

Collective Message:

You can control the granularity of messages by grouping notifications in collective messages. This enables you, for example, to reduce the number of messages that the user receives (see also: Granularity of Messages).

Deleting After Sending

You can define whether notifications are deleted after they have been sent. If you want to set up the reminder function in the subscription, you must not choose Delete After Sending(see also: Reminding Users About Unprocessed Work Items).

Priority

You can define the priority for a particular message. You have a choice of three priorities, which are provided by SAPoffice: High, Medium, and Low. The effects of the different priorities and the way they are represented depend on the Groupware that you are using. If you choose priority 1 (High) then the indicator deliver_asap is set for the message. This setting means that the message is sent immediately, without the send job needing to be triggered by SAPoffice.

Activities

...

       1.      In the Scenario view, choose the scenario for which you want to define a category.

       2.      In the Category view, choose New Entries on the toolbar and create a new category in the customer namespace (Z or Y).

If you have not programmed your own handler classes, select the default handler.

       3.      You have the following options to define which work items are to be assigned to the category:

¡        Define a relevant filter and then enter it in the selection schedule (see also: Filter).

Or:

¡        On the Handler Assignment screen, assign a single-step task to the new category (see also: Handler Assignment):

                                                  i.       In the Application Object Type field, enter the single-step task for which you want to define a category.

                                                ii.       In the Category field, enter the name of the category. 

       4.      Choose the required message template.