Subscribe

UiPath Automation Hub

The UiPath Automation Hub Guide

Understanding the Citizen Developer Flow

The flow for Citizen Developers enables users from within the organization to share attended automations that facilitate their day to day tasks and have them reviewed by the business and the CoE. Specific roles and collaborator roles are designed to assist during the automation flow. It leverages Automation Hub and Studio as the main tools for managing the entire lifecycle for Citizen Developer automation.

The Citizen Developer automation is the base of this flow. This is ready to use code created for low risk, simple or medium tasks, activities, or processes that users can directly upload in Automation Hub.

The automation submission process is designated upon specialized Roles and Collaborator Roles created around the Citizen Development flow. This allows the System Administrator to gather a group of experts and assign them the specific tasks facilitating the automation flow towards general consumption.

Below you can find a list containing the Roles and Collaborator Roles created to support the automation flow:

A customised automation submission form is made available under the Share button and allows Citizen Developer Self Users as well as Citizen Developer Power Users to share their automations.

18881888

Each automation undergoes a review process before being made available for wider use. After a Citizen Developer shares an automation, this is automatically sent to a review process composed of the following stages:

  1. Business review – completed by a Business Reviewer; performed with the scope of evaluating if the automation has the potential to bring benefits to a larger audience and also of estimating the interest from potential consumers.
  2. Technical review - completed by a Technical Reviewer; performed with the scope of checking the quality of the code and confirming whether the automation is ready for large consumption.

Before its implementation the automation can be:

  • Approved for CoE: meaning its development type is changed to CoE. It's then sent to > Qualification Phase status Approved where a Project Manager is assigned as a Collaborator in order to perform all the required actions for the Implementation phase.
  • Approved for Citizen Developer: meaning the automation is sent to > Development status Not Started. Any Citizen Development Power User can access the Implementation view, choose the automation, and further develop it.

Please find below the graphic design of the entire flow:

📘

Note:

Automations that haven't passed the review phase (still in Business Review - Awaiting review phase) aren't visible to standard users until approved.

📘

Note:

Automations that haven't passed the review phase (still in Business Review - Awaiting review phase) aren't visible to standard users until approved.

To facilitate the review process, the Automation Pipeline module has now the following views:

  • All: a list containing all the automations in all phases and statuses.
  • Review: a list containing automations in Idea, Assessment, Business Review, and Technical Review phases
  • Decision Pipeline: a list containing automations in Technical Review phase and Rework Required status.
  • Implementation: a list containing automations in Analysis, Solution Design, Development, Testing phases, or the ones in Qualification - Approved.
  • Live: a list containing automations in Live phase.

📘

Note:

Besides automations, the views from the Automation Pipeline module also contain ideas in different phases and states. To filter ideas from automations use the filtering option available for the Idea Source column.

18881888

The goal for each shared automation is to be made available in the Automation Store. Here you can request or get automations and integrate them in your day to day work with the help of UiPath Assistant.

Updated 6 days ago


Understanding the Citizen Developer Flow


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.