Enhancing workflow efficiency with embedded tasks

​In a HCL Universal Orchestrator environment, embedded tasks are self-contained operational units within a workflow, encompassing all necessary logic, execution instructions, and parameters unlike traditional tasks reliant on external templates.

​Embedded tasks facilitate streamlined processes for handling scripts, database operations, and file management independently of external dependencies, creating cohesive and easily managed workflows. This article explores the concept of embedded tasks, their key benefits, practical use cases, and the transformative impact they have on workflow automation.
 
Choosing between embedded and referenced tasks
When deciding between embedded and referenced tasks, the choice often boils down to workflow requirements:

• Embedded tasks: Best suited for workflows that require localized, specific operations. They reduce the need for extensive configuration, simplify processes, and can enhance security by ensuring a controlled and precise management of the definition. Embedded tasks are also flexible enough to support external dependencies when necessary, making them adaptable to various use cases without introducing unnecessary complexity.
• Referenced tasks: Ideal for reusable operations that span across multiple workflows. They promote consistency and modularity. Referenced tasks are best when you need to maintain standardized operations across multiple processes while ensuring easier updates and maintenance.

Organizations prioritizing simplicity and reliability often find embedded tasks to be the superior choice. By consolidating task definitions within workflows, embedded tasks eliminate ambiguity and enable teams to focus on optimization rather than troubleshooting.
Advantages of Embedded Tasks

1. Simplicity and transparency: Embedded tasks integrate seamlessly into workflows, enhancing clarity, maintainability, and shareability. By removing the need for external references, they ensure self-contained, error-resistant and easily manageable workflows.
2. Reliability through isolation: Self-contained embedded tasks are insulated from external disruptions, enhancing reliability and control, especially crucial in systems demanding high uptime.
3. Scalability without complexity: Embedded tasks make it easy to scale workflows without adding complexity. They eliminate the need for extra resources, like creating and managing separate task definitions, saving both time and storage space. This makes it possible to create workflows with minimal management effort.

Embedded automation definition

• When using the Schedlang format, use the BUILTIN parameter to define embedded tasks.
• jobDefinitionRef or jobDefinitionRefId fields are not required at the job level, unlike in YAML/JSON formats for referenced tasks.
• name and workstation fields are required at the job level, though these fields can be ignored at the jobDefinition level for embedded tasks.

Here are some illustrative examples of how embedded tasks can be defined and utilized within workflows using different formats.
SchedLang Format
 
$jobstream
/WS_AGT_0#/JS_DEVICE_MONITOR
DESCRIPTION "Monitor sensor data in real-time"
/WS_AGT_0#TASK_READ BUILTIN
TASK
{
  "executable": {
    "interactive": false,
    "script": "sleep 60",
    "credential": {}
  }
}
RECOVERY STOP
END
 
Yaml Format
 
kind: JobStream
def:
  folder: /
  name: JS_DEVICE_MONITOR
  workstation: /WS_AGT_0
  jobs:
    - name: TASK_READ
      workstation: /WS_AGT_0
      jobDefinition:
        description: Embedded job definition
        type: executable
        task:
          executable:
            interactive: "false"
            script: sleep 60
 

Practical use cases and guidelines for implementing embedded tasks
IT operations automation: Embedded tasks streamline repetitive tasks in IT environments, such as server maintenance, log monitoring, or patch deployment. To ensure task clarity and reliability, each embedded task should have a focused scope, complementing the workflow’s purpose. For example, an embedded task could monitor server disk space and trigger alerts if certain thresholds are exceeded. Testing in isolated environments is essential to verify reliability before deployment.
Data processing in workflows: Data analysts can add tasks directly into workflows to handle data cleaning, transformation, and analysis.
Conclusion

Embedded tasks streamline workflow management by adding tasks directly into workflows, enhancing efficiency, dependability, and agility. This approach reduces complexity, increases operational efficiency, and provides better control over operational environments. Widely applicable in areas like IT operations and embedded systems, embedded tasks support scalable, and transparent workflows—key to modern automation strategies.

Authors

---

Alok Ranjan Barik – Technical Lead at HCLSoftware

He joined HCL in August 2022 as a Backend developer for Workload Automation team. He possesses hands-on experience with platforms including Java, Rest API, microservices, Spring, and MongoDB. Outside of work, he enjoys exploring new places and playing cricket.

---

Maddu Sreekanth – Software Engineer at HCLSoftware.

He joined HCL in August 2023 as a Backend developer for Workload Automation team. He brings a strong foundation in modern technologies and is actively involved in developing innovative software solutions. He is committed to delivering high-quality results and continuously enhancing his technical expertise to excel in his role. Outside of work, he enjoys exploring new ideas and staying up-to-date with the latest advancements in technology.