Skip to content

Publish the Solution

Here is our plan for this lesson:

  1. Deploy the Benefit Claims Processing solution from Studio Web to your personal workspace
  2. Run the process end to end

Goal

Until now, everything ran in Debug mode inside Studio Web. In this lesson you'll publish the Benefit Claims Processing solution and deploy it, so the process, the agents, the robots and the Action App run as a real automation in Orchestrator, outside the designer.

Publish vs. deploy

A UiPath Solution goes through three stages on its way to production:

Stage What happens Where
Publish Studio Web packs all the projects of the solution into one versioned solution package Studio Web, then the tenant's Solutions list
Deploy The package is installed into an Orchestrator folder. You choose the folder and map the resources (connections, storage buckets, indexes) Orchestrator → Solutions
Activate The deployed processes, agents and apps become available and can start running Orchestrator → Solutions

Each time you publish, you get a new version of the package. You can then upgrade an existing deployment to that version, instead of deploying from scratch.

Steps

1. Check the solution for errors

Studio Web only publishes a solution when all its projects are valid.

  1. Open your Benefit Claims Processing - <Your Name> solution in Studio Web.
  2. Check the Explorer and the Problems panel for errors or warnings in any project.
  3. Fix any errors before you continue.

2. Deploy the solution

  1. In the Studio Web toolbar, click Deploy.

    Studio Web toolbar with the Deploy button highlighted, above the Explorer of the Benefit Claims Processing solution

  2. Choose the deployment destination Personal and click Deploy.

    • Personal packs and deploys the solution into your own personal workspace. Only you can see and run it, which is all you need for this exercise.
    • Shared publishes the package to a shared feed (the tenant feed or a folder feed) and deploys it into a shared Orchestrator folder, where other users with access to that folder can run it. It requires permissions to create solution folders and deployments in the tenant.

    Deploy dialog with Pack to set to Personal and the Deploy button highlighted

3. Run the process end to end

Now register a real application through the deployed Benefits Assistant Conversational Agent and follow it through the whole process.

  1. In Automation Cloud, go to Agents → Conversational.

    Automation Cloud product menu opened from the apps launcher, with Agents highlighted under More Agents navigation with Conversational highlighted under Agent Registry

  2. Find the Benefits Assistant Conversational Agent and click Open, then Chat.

    Conversational agents list with the Open button of the Benefits Assistant Conversational Agent highlighted

    Benefits Assistant Conversational Agent page with the Chat button highlighted

  3. Register a new application, the same way you did in lesson 10:

    • type I'd like to apply for SNAP benefits.
    • give your own email address, so you receive the final email
    • attach Sample application.pdf when the agent asks for the application
    • attach Sample pay stub.png when it asks for the paystub
    • check the summary and answer yes
  4. Wait until the agent confirms that the application was submitted.

  5. Open Maestro and find the new BenefitClaimsProcessing instance. Follow it through the robot and the three agents, until it stops at the Case Worker Review task.

    Automation Cloud product menu opened from the apps launcher, with Maestro highlighted Maestro navigation with BPMN instances highlighted

    Maestro BPMN instance of BenefitClaimsProcessing in Running status, with all steps completed up to the Case Worker Review task, the execution trail and the global variables

  6. Open the Case Worker Review task in Action Center, review the agents' conclusions, and approve or reject the application.

  7. Check your inbox for the approval or rejection email.