Show TOC

App Extensibility: Workload Management for TasksLocate this document in the navigation structure

Use

You can extend Workload Management for Tasks according to your business needs for different aspects. For this purpose, the following extensibility options are available:

  • Header data for list of tasks

  • List of tasks for the selected claim handler

Header Data for List of Tasks

The header data includes the list of claim handlers with their assigned open tasks and information on the business card of the claim handler. To extend the header data to include own fields, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs:

UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Customer extension using the following BAdI

S3.view.xml

extTaskDetailHeader

ICL_WLM_TASKS (AdjusterTaskCount)

ICL_WLM_USER_TASK_COUNT_INCL (DDIC structure: ICL_WLM_USER_TASK_COUNT)

BADI_ICL_ODATA_WLM_TASKS

List of Tasks for the Selected Claim Handler

As soon as you select a claim handler in the app, the system displays the open tasks of the claim handler with certain task data. To extend the displayed task data to include own fields, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs:

UI

Back End/ABAP

View

Extension Point

Design Time: Gateway Entity

Design Time: Extension Include (in DDIC Structure)

Runtime: Customer extension using the following BAdI

S3.view.xml

extTaskTableColumns

None

None

BADI_ICL_ODATA_WLM_TASKS

S3.view.xml

extTaskTableItems

ICL_WLM_TASKS (AdjusterTask)

ICL_WLM_USER_TASK_INCL (DDIC structure: ICL_WLM_USER_TASK)

BADI_ICL_ODATA_WLM_TASKS

Note

Note the following when displaying tasks:

When the system selects the corresponding data for tasks, it searches for workflows with object ID TS20700091 (table SWWUSERWI, field TASK_OBJ) and category ID ICLACT (table SWW_WI2OBJ, field TYPEID). If you use other IDs for your workflow processing, you must override the above-mentioned default values in the CLASS-CONSTRUCTOR of class CL_ICL_WLM_ODATA_HELPER using an implicit enhancement option. At the end of the CLASS-CONSTRUCTOR you need to adjust the entries in the internal tables gt_task_obj_rg and gt_typeid_rg to suit your requirements.

Additional Extensibility Entities

Business Add-Ins (BAdIs)

The following BAdI is available for extensibility purposes:

  • BADI_ICL_ODATA_WLM_TASKS (OData services for tasks in Workload Management)

    For more information, see the BAdI documentation.

Extension Includes

In addition to the extension includes described above, the following extension include is available:

DDIC

Extension Include

Use

ICL_WLM_USER_TASK_REASSIGNMENT

ICL_WLM_USER_TASK_REASGNMENT_I

You can use this extension include to store additional information once one or multiple tasks have been transferred from one claim handler to another claim handler, such as information in message output.

If there are additional fields available in the OData service, you can display these fields on the UI. For more information, see the extensibility documentation for the respective SAP NetWeaver release on your front-end server at http://help.sap.com/fiori_implementation Start of the navigation path Extensibility Information for SAP Fiori Next navigation step Extending the UI Layer Next navigation step UI Extensibility Workflow Next navigation step  Next navigation step Checking the SAP-Enabled Extension Options Next navigation step Extension Points End of the navigation path.

UI Controller Hooks

To plug in and execute custom code, the following hooks are available in the controller code:

Controller

Hook

Use

S3.view.xml

extHookOnDataReceived

Call task list for a claim handler

You can do the following, for example:

  • Calculate or determine content of customer-specific UI fields that are not provided directly by the back-end system via include structures.

  • Control that certain standard fields are not displayed on the UI

Note

The control cannot be hidden.

If there are additional UI controller hooks available in the controller code, you can add own code. For more information, see the extensibility documentation for the respective SAP NetWeaver release on your front-end server at http://help.sap.com/fiori_implementation Start of the navigation path Extensibility Information for SAP Fiori Next navigation step Extending the UI Layer Next navigation step UI Extensibility Workflow Next navigation step  Next navigation step Checking the SAP-Enabled Extension Options Next navigation step UI Controller Hooks End of the navigation path.

More Information

For a general description of the extensibility options and procedures of SAP Fiori apps, see http://help.sap.com/fiori_implementation Start of the navigation path Extensibility Information for SAP Fiori End of the navigation path.