Introduction
The following document describes the feature “Create new activity for the workflow” as-is and shows how to create a new activity for the workflow. There are no requirements for a to-be state. Instead, the process is fully described in form of a manual with the following goals:
- Research feature components and constraints
- Prepare a manual that can be shared in case of questions related to the workflow activities
The described creation process assumes the user needs to create a completely new workflow activity. None of the existing values in all tables can be reused, therefore the whole process should be completed. In case some of the values can be reused - the respective steps can be skipped. For example, the OCLT activity already exists -> Step 1 can be skipped (the user just needs to know the code). The “coupled[1]” system has been taken as a template, for the “decoupled[2]” system only changing value procedures will change. Concept of the table stays the same.
Component overview
The current process of creating a new activity for the workflow consists of 4 components (and 1 backend file):
Name | Page | Table | link | Description |
---|---|---|---|---|
(or separate Table in DB if the system is “de-coupled”) | SAP HANA Editor | The core list of activities. Affects My Calendar List of All activities to be used in the system (not only workflow activities). Activity value is obligatory in the table to process the next steps. Name from this table is used as description of activity in My Calendar. | ||
List of UI Activity Group | IDMS_WF_UIActGroup | /SetupEntities/List/Workflow/IDMS_WF_UIActGroup | Affects Agenda UI Activity Group values to be shown in the Calendar. Icons appear in the Agenda/Widget related to activities. If the activity belongs to the group - the related icon appears. | |
List of Workflow Activities | IDMS_WF_ActType | /SetupEntities/List/Workflow/IDMS_WF_ActType | Affects Workflow/Agenda/Activity widget List of existing workflow activities. Created activity will be shown in the workflow, Agenda and Activity widget. | |
List of All Activities | IDMS_ActivityTypeGroup | /SetupEntities/List/SalesAndLeads/IDMS_ActivityTypeGroup | Affects My Calendar A new entry should be created for the activities to appear in the Calendar. | |
file | The file can be accessed only by request to backend development. It is required to have a table entry to create a new UI Activity Group. The file operates dependency between:
|
The picture below shows reused values in different tables for better understanding of different value namings. Please note: It is not showing DB’s table relations/table keys.
Create a new workflow activity process
Step 1: Create value in the OCLT SAP B1
The OCLT SAP B1 table is not available via UI. It can be accessed only via SAP HANA Editor. Creating value in the OCLT table is crucial for the next steps. Without value in SAP B1 activity cannot be created.
The example of values in SAP HANA Editor:
Create new value in the OCLT SAP B1 table by providing:
# | Name | Description | Cross-Reference value in other tables | Affects UI (User UI/Admin forms) |
---|---|---|---|---|
1 | Code | Identifier of the activity | - | |
2 | Name | Activity description, to be shown in UI |
Field: B1 ActType
Field: Activity Type Code | My Calendar (name of the planned activity) |
3 | Data Source | - | - | |
4 | User sign | - | - | |
5 | Active | Status: Y/N | - | - |
Step 2: Create value in the UI Activity Group (IDMS_WF_UIActGroup)
The step can be skipped, if there is already a UI Activity Group that can cover the use of the new Activity.
Important: The Activities with UI Activity Groups with Code=N (Automatic) will not be displayed in the Calendar, Agenda, and Activity widget. They are considered as hidden.
The UI Activity Group values are used in the following sections:
- Agenda (Icons appear in the related activities)
- Activity Widget
The example of values in DSW UI:
# | Name | Description | Cross-Reference value in other tables | Affects UI (User UI/Admin forms) |
---|---|---|---|---|
1 | Code | Alphabetic code from the Backend file |
Field: Activity Group Code | |
2 | Name |
Field: UI Group Code | ||
3 | White icon | - | Activities in the Agenda related to the chosen Lead | |
4 | Blue icon | - | All other activities related to the BP, besides the chosen Lead | |
5 | Show in History | Status: Y/N | - | - |
Step 3: Create value in the Activity type table (IDMS_WF_ActType)
Activity type table directly affects the drop-down list of activities in the workflow, as well as activity widget and info in Agenda tab.
The example of the values in DSW UI:
# | Name | Description | Cross-Reference value in other tables | Affects UI (User UI/Admin forms) |
---|---|---|---|---|
1 | Code | Free code | - | - |
2 | Name | Free name | - | - |
3 | Description | Description of the activity | - | - Dropdown inside Workflow - Activity widget - Agenda |
4 | UI Group Code |
Field: Name | ||
5 | B1 Act Type |
Field: Name
Field: Activity Type Code | My Calendar (name of the planned activity) | |
6 | Is Critical | - | - | |
7 | Resource key | Translation resource key | - | - |
Step 4: Create value in the Activity type group table (IDMS_ActivityTypeGroup)
A new entry should be created for the activities to appear in the Calendar.
# | Name | Description | Cross-Reference value in other tables | Affects UI (User UI/Admin forms) |
---|---|---|---|---|
1 | Code | Any Non used code | - | - |
2 | Name | Any Non used name | - | - |
3 | Activity Group Code | Activity group code letter |
Field: Code | - |
4 | Activity Type Code | Value from OCLT SAP B1 |
Field: Name
Field: B1 ActType | My Calendar (name of the planned activity) |
5 | Description | Description (not shown anywhere) | - | - |
[1] Coupled system - DSW connected to the SAP B1
[2] Decoupled system - DSW disconnected from the SAP B1, DSW’s DB are used instead to replace SAP B1 tables
Add Comment