Process Driven Customer Interaction
Download as PPTX, PDF3 likes47,697 views
The document discusses enhancements in customer interaction processes for the Camunda community, highlighting issues like lack of end-to-end visibility in business processes and the need for a user-centric approach. It details the evolution of business process architecture and user interactions, emphasizing the importance of combining process-centric and user-centric approaches to improve efficiency. Furthermore, it describes automated workflow deployments, version control, and the significance of backward compatibility in managing deployments.
Process Driven Customer Interaction
- 1. 28/04/2021 Process Driven Customer Interaction For Camunda Community Summit 2021
- 2. SpecialThanks to all my ESP team members
- 3. Krishna Kumar Nair Principal Software Engineer @Walmart GlobalTech India
- 4. Table of contents 1 Problem Statement 2 Architecture Evolution 3 Process Centric + User Centric 4 User Interactions 5 Template Structure 6 Workflow CICD
- 5. Problem Statement • Business did not had end to end process visibility • Code and process tightly coupled leading to longer releases • Business process scattered in multiple layers leading to cascading updates 1
- 7. User-Centric vs Process Centric Users need a rich internet application which can offer them a better visual experience and more interactivity than traditional browser applications – the type typically represented by the single page application (SPA) pattern of interface design.This we call it a User-Centric (UC) approach necessitated by a modern user-interface In Process-Centric (PC) approach having a Business Process Architecture(BPA) is fundamental. The BPA provides a hierarchical view of the core business process that’s driving the business. However, choosing these above approaches (PC or UC) independently leaves us duplicating the flow at multiple places so there arises a need to combine both and leave the flow of the process to BPM and only the layout rendering to the user-interface. 3
- 10. Evolution - 4 6
- 12. User Interactions - Lifecycles 7 User Provides Inputs UserTakes time to fill in User Input by interacting with a Form User Submits User Waits For Response User Edits User Information User fills in inputs and submits After the inputs are submitted user waits for response User Can edit already entered values and resubmit After certain actions user may get information from server
- 13. 8 User Interactions - Lifecycles After completing the required inputs, the user submits User Submits Once the inputs are submitted the user waits for the response to come back from the server UserWaits There are many elements though which user inputs are captured User Inputs User is informed at various stages of the progress User Informed User can edit already entered inputs and submit back. User Edits
- 14. User Edits 9
- 15. UserWaits 1. There are tasks which are long running and based on a specific business process these can take varying times to complete. 2. Partners can have varying tasks as long running for various use cases. 3. UI layer should not have fixed polling for every use case. For example, if a task averages 2 minutes, make your GET call at 2 minutes after the submission. 4. The server responds back with a “Poller” task to the UI with details of the poll frequency and max count of polling and what to display the the user while waiting.
- 16. • Category • Inputs • Display Inputs • Endpoints • Current Steps • Related Steps Structure of PageTemplate Page
- 18. CICD Features Camunda database manages the versions of individual process definition files but it cannot understand the deployment version. We will be deploying a set of files during one deployment and the versioning at the group level is important during events of a rollback Version Control Version Management • Migration info maintained for each environment and deployment. • Migration Version Log History maintained 01; Migration and Process Validation • Existing processes definitions not changeable • Unit Tests performed to validate process definitions 02; AutomatedWorkflow Definition Rollout and Rollback • Single Click Deployment and Rollback. 03; Backward Compatibility Check • No Edits allowed on migrated processes. • No Duplicate process definition files. • Previous Migrated files has to pass the checksum to have a successful current deployment 04; Process definitions before migration have to be validated . Migration and Process Validation Workflow Process deployment needs to be simplified for the devops management team just by the click of a button. Automated Workflow Definition Rollout and Rollback Preserving the integrity of each deployment is really important and hence backward compatibility is really important. Backward Compatibility Check
- 21. Questions ?
- 22. Thank you!();