SAP Business Workflow was first introduced in 1995 as part of SAP R/3 Release 3.0 (see: SAP R/3: Architecture, Function, Implementation” by Buck-Emden et.al..)
This longevity speaks to the robustness and deep integration of the tool in the ABAP platform – why also often the name ABAP platform workflow is used. A main goal was and is to distribute workitems (often also called “to dos” or “tasks” – don´t mix up this runtime artefact with the task-object from design time [e.g. TS30000016]) to the next worker to accomplish business outcomes in a coordinated way and as effortless as possible for human workers interacting with a digital system. Same is true for compliance approval processes implemented via flexible workflows in SAP S/4HANA CLOUD – we celebrate 10th Birthday this year.
Almost from the beginning, customizable task attributes and personalized worklist searching & sorting have been essential for enabling end-users to complete their work with freedom and flexibility—allowing them to work in the sequence their company or business process requires. This directly addresses all three psychological needs that Self-Determination Theory identifies as drivers of intrinsic motivation and self-actualization: autonomy, competence, and social relatedness. The concept of “custom attributes”: Company and business process-specific metadata that enables:
- Task filtering and prioritization
- Personalized worklist management
- Context-aware task processing
This blog post deals mainly with the latest technology to define CDS Entity based custom attributes (which is not covered in the workflow overview training BIT602). For the sake of completeness, the older options are also mentioned or linked.
31 and also 10 years are tremendous for software components and tools. Congratulations to all contributed to that amazing story.
SAP Business Workflow was first introduced in 1995 as part of SAP R/3 Release 3.0 (see: SAP R/3: Architecture, Function, Implementation” by Buck-Emden et.al..) This longevity speaks to the robustness and deep integration of the tool in the ABAP platform – why also often the name ABAP platform workflow is used. A main goal was and is to distribute workitems (often also called “to dos” or “tasks” – don´t mix up this runtime artefact with the task-object from design time [e.g. TS30000016]) to the next worker to accomplish business outcomes in a coordinated way and as effortless as possible for human workers interacting with a digital system. Same is true for compliance approval processes implemented via flexible workflows in SAP S/4HANA CLOUD – we celebrate 10th Birthday this year.Almost from the beginning, customizable task attributes and personalized worklist searching & sorting have been essential for enabling end-users to complete their work with freedom and flexibility—allowing them to work in the sequence their company or business process requires. This directly addresses all three psychological needs that Self-Determination Theory identifies as drivers of intrinsic motivation and self-actualization: autonomy, competence, and social relatedness. The concept of “custom attributes”: Company and business process-specific metadata that enables:Task filtering and prioritizationPersonalized worklist managementContext-aware task processingThis blog post deals mainly with the latest technology to define CDS Entity based custom attributes (which is not covered in the workflow overview training BIT602). For the sake of completeness, the older options are also mentioned or linked.31 and also 10 years are tremendous for software components and tools. Congratulations to all contributed to that amazing story. Read More Technology Blog Posts by SAP articles
#SAPCHANNEL