3. Tasks and Design Canvas


A task is a typically a logical subprocess. For example, consider a master data automation, where the vendor data creation comes in an email. The bot is expected to read the email, create an entry in SAP, upload the attachments and send a response email back to the requestor. This overall process can be divided into the following subprocesses and each subprocess becomes a task in Jiffy:

  1. Reading the email, validating contents, and sending response mail with a request id and making the request available on JDI.
  2. Updating SAP and changing the status of the request to ‘Posted’.
  3. Uploading attachments and changing status of request to ‘Attachment Uploaded’.
  4. Sending a completion email with the document number generated and the status of the request in JDI is set to ‘Closed’.

Design Canvas

Design Canvas is used to design a RPA task. JiffyRPA provides several in-built components for designing a task. The in-built components are available in the design canvas in the right panel known as nodes. These nodes are dragged and dropped on to the canvas. The nodes have to be connected to the Start Task node and the End task node (which are by default available on the canvas).

As per the business requirements, each component has to be dragged on to the design canvas. The components have to be connected to each other in the same order as the task is expected to be executed. Properties of each component has to be mentioned in the properties section in the right panel. Properties of the component varies based on the component selected.

In-built components available in the right side panel are:

  • Data Source Nodes: Refer - Data Sources for further details
  • Sterling Component Nodes: Refer - Sterling Components for further details
  • Validator Node: Refer - Validators for further details
  • Sub Task Nodes: Refer - Sub Tasks for further details
  • UI Nodes: Refer - UI for further details
  • Email Nodes: Refer - Email for further details
  • Miscellaneous Nodes: Refer - Miscellaneous for further details


Data flows from one node to other is achieved through Mappings.

Refer: Mappings for further details.

Below video demonstrates the process of creating a task with multiple nodes and mappings.

Did you find what you were looking for?

Automation Analytics and AI in a box

Contact Us

HfS Hot Vendor

Option3's Automation capabilities featured in HfS Research's Hot Vendors List for Q3, 2018

Access your copy here