The Automagica Portal offers additional functionalities to manage your robot workforce.
A grasp of the Automagica Portal functionalities:
Bot management: Connect and centrally manage robots
Securely connect bots to the Portal
Assign bots to processes and/or teams
Role / Team management
Create a team and
Process management: create processes that represent automated processes
Queueing: intelligent queueing to divide workload over one or more robots
Scheduling: schedule processes and view schedule
API integration: start processes with an API call
E-mail triggers: start processes with a unique e-mail address
Event reporting: log actions and changes made by (team)members for a complete audit trail
Version control: manage your scripts and keep track of your versions
Keep an overview of development / production versions
Historic overview of versions
Download different versions
Reporting on successful/failed jobs
Overview of performed jobs both in calendar with color codes
Filter jobs based on date / outcome in overview
View logs / rerun jobs
Add e-mail / SMS / Teams / Slack / Telegram notifications on job status
Credential management: keep your credentials in a central secure vault
UI elements overview: view and edit elements recorded with Automagica Wand
After signing up in the Portal Automagica Portal with the one-click-installer if you don’t have a bot installed yet.
Once installed, your robot will be automatically connected. If this is not the case you can manually set this up as described in [the bot section]](bot.md).
Adding a process¶
You can add a process by using the ‘create’ button and selecting process. A process consists of several parts
Name: arbitrary name of the process
Bots: dropdown menu with all your available robots.
Add version: select either a Python (.py), Jupyter Notebook (.ipynb) or Automagica Flow (.json) file to add it to this process.
Entrypoint: If you have created an Automagica Flow with additional Python .py or subflows (.json) you can add those files to the upload. Make sure to specify the main-file as entrypoint, this is the file your automation starts with
Add trigger: once your file is uploaded you can add triggers to start the process
Schedule: specify date/time to run the process
E-mail: obtain a unique e-mail that triggers this process when an e-mail is send to it. Parameters can be put in the subject line
API: API call to trigger the process
Add notification: once your file is uploaded you can add notifications when process fails or ends completes successfully
Once you have defined the process you will see a new section ‘Jobs’ in the menus. If a process is performed it is now called a ‘job’. A job one specific instance of a process, possibly with custom parameters.