Automation Co-Pilot using embedded widget overview

You can use a widget that embeds automation built on the Automation 360 platform that can be applied natively on any supported web application.

Capabilities

iFrame widget
A widget that is composed from an HTML inline frame, or simply iFrame widget, can be used as a "window" to access another website located in your current web application environment. In addition, the iFrame widget provides reliable and secure methods of quick integrations performance without the need for heavy development work, when involved with custom integrations.
For example, your current web application environment is domain 1, which can access a widget that shows a website from domain 2. These two domains exist in one shared environment, without you navigating to a separate page or window.
iFrame widget experience on supported web applications

The Automation 360 platform can support embedding an iFrame widget on any web application that supports the iFrame technology to access external contents. Many software-as-a-service (SaaS) web applications support the iFrame widget to allow for customization in a secure environment.

Business users can add contextual workflow automations from inside their most used and preferred enterprise applications. This approach means that users need to add only minimal code to their most used web applications, which when applied can produce a rich, friendly, and more secure interactive user experience.

Actions that can be performed with iFrame widget
Business users can use iFrame widget to perform the following:
  • Invoke local automations on their desktop.
  • Invoke multi-step process workflows from Automation Co-Pilot requests.
  • Monitor request progress to completion.
  • Receive notification of pending tasks.
  • Respond directly to pending tasks from iFrame widget.
  • View the history of currently running or previously completed automations.

Requisites

  • Ensure that you have the proper role and permissions. Create users for Automation Co-Pilot
    • Automation Co-Pilot for Business Users license.
    • Proper roles for Co-Pilot Admin and Co-Pilot User.
  • Automation 360 v.26 or later.
  • Google Chrome, Microsoft Edge Chromium, or Apple Safari web browsers. See Browser requirements for Automation Workspace.
  • Automation Co-Pilot web interface.
  • Web application that supports iFrame technology.

Process flow

  1. Set up your iFrame widget for a web application.
  2. Assign automations to a team for them to access data from the iFrame widget.
  3. Configure widget settings in a web application to properly access iFrame widget.
  4. Deploy the iFrame widget.
Workflow map: Click the following schematic image to view the Automation Co-Pilot using embedded widget workflow in an interactive visual format:
Automation Co-Pilot schematic mapAutomation Co-Pilot Integrations