Workflow Configuration

Automate tasks in sequence with workflow configuration.

Workflow Configuration

Overview

Reduce dependency, improved openness.

Simplify the management and control of work processes, whether automating intricate procedures across various systems, applications, or services, Workflow Configuration plays a pivotal role in achieving efficiency and defined objectives.

Benefits

Efficiency

Enhances efficiency by reducing manual interventions.

Consistency

Ensures consistent task execution as per predefined standards.

Visibility

Gain insights into workflow performance & identify bottlenecks.

Cost Saving

Promotes cost-effective operations by minimizing resources.

Use cases

Scenario: Employee Onboarding 

An HR Manager adds a new employee to the HRMS by initiating a  Service Request (SR). Using a no-code/low-code approach in the workflow editor, a business workflow is created with the required skills. These skills involve creating a user in Active Directory, setting up an O365 email inbox, and generating a work order for offline tasks like ID card creation and asset provisioning. This streamlined workflow enhances the onboarding process. Upon completion, the SR is updated with pertinent details, including user and analyst communication logs, ensuring a smooth and efficient onboarding experience.

Scenario: AWS Elastic container Service creation

Organizations efficiently deploy, manage, and scale containerized applications using AWS fully managed container service automation. This process begins with a Service Request (SR), triggering the Service Automation engine. Configuring workflows is simplified with AWS skills through drag-and-drop in the workflow editor. The AWS workflow involves resource validation, container creation, post-validation checks, and success validation for AWS Elastic Container Service (ECS) creation. Post-creation, the SA engine proactively handles email notifications and communication logs. The process concludes by updating the SR with details of successful container creation and dispatching email notifications to signify the triumphant completion of the AWS ECS process. 

Scenario: CMDB CI Creation 

A user requesting a new CI creation logs a Service Request with all the needed details in the catalog. After logging the request, it undergoes a hierarchical approval process. Once approved, the Service Automation process begins. The Service Request follows a workflow created by adding necessary skills with a simple drag-and-drop. These skills work together to create a special code (JSON payload), call SUMMIT through a special language (API), make the CI in the CMDB, generate a unique ID, and send detailed notifications. After everything is done, the Service Request updates with the important information, completing this efficient and informative CI creation process.