RGO (Robogator Original) certified ready-made automation tasks are subject to the following standards

What are RGO certified automation tasks

To clarify, an RGO certified ready-made automation task is a collection of Robogator tasks grouped under a Robogator account, available to import with the right license plan from the Robogator cosmos and ready to hit and run immediately after download without any technical error.

Cosmos ready-made automation tasks manifest

1. Seamless start: Download and run the automation tasks without initial configuration by using a default setup.
2. Rich description: Detailed description of the automation tasks.
3. Comprehensible console information: See what works and what doesn't in a way that is recognizable so you can understand it even years from now.
4. Comprehensive error handling: Run the automation tasks without uncertainties.
5. Fun to use: The RGO certified ready-made automation tasks should bring a smile to your face when you use it.

Guideline

The following standards and restrictions for published ready-made automation tasks available on Robogator cosmos are intended to meet the high requirements for end-user usability and to lower the initial barriers for a smooth and pleasant interaction with the Robogator platform.

Account title

Make the account title short and sweet. The title should start with a uppercase letter and be nice and human readable. Here are some examples:

• Desktop cleaner
• Data migration tools
• Password generator

Account image

Select a colorful and relatable image for the automation task account. The main reason for the account image is to have another quick recognition feature to better recognize ready-made automation tasks on the fly in the deep end of the Robogator cosmos.

Task title

The task title should describe the whole function of the task in a few words, also should start with a uppercase letter an be nice and human readable. Here are a few examples:

• Cleans desktop and stores data in archive folder
• Classify files
• Generate a random 32 character string

Task description

For each task, write a clear and simple description that explains exactly what the task is doing. Some examples:

• This task does a desktop cleanup and stores files in an archive desktop folder by cleanup date and time. It is possible to exclude files or directories from the desktop cleanup
• It lists every unique value and calculates how many times each value appears in your selected Csv column. It does this using the column header name of the given Csv file and writes the result to another Csv file.

Task parameters

Use CamelCase parameter names that start with an uppercase letter. Exampels are:

• SourcePath
• DbConnectionType
• Url

Each task must run without any parameter input. This requires default values if needed in the script for each parameter available in the task.

For the parameter description of your tasks, create a single line for each parameter at the end of the task description with the following structure:

• param["Parameter name","Default value","Parameter description"]

Some valid examples are:

• param["PathToFile","C:\temp\","Set the path to the file without the filename itself"]
• param["FileName","","Output csv filename e. g. my_data.csv"]
• param["Amount","0","specify the number of repetitions"]

Using keys

Use CamelCase key names that start with an uppercase letter. Exampels are:

• MapServiceV1ApiToken
• XCorePowerAdmin

Choose a long, task-related key name. This will help prevent keys with similar names in the Robogator key tab. This makes it easier to understand the keys and their belonging.

If you want to use the first available key for the task, use the keyDefaultFirst feature. If you do, add keyDefaultFirst as the key name in the key description.

It is necessary to set a default password. This helps improve the user experience. It also prevents technical errors.

For the key description of your tasks, create a single line for each needed key at the end of the task description with the following structure:

• key["Key name","Default password or token","Key description"]

Here are a few good ones:

• key["ApiTokenForServiceXY","bearer12345678","Add the token for the api with the key name ApiTokenForServiceXY"]
• key["UserPw","pw1234","Store the user password in an key named Password and add it to the task"]
• key["keyDefaultFirst","securePw","The first key that is added to the task is used. The name of the key can be chosen individually"]

Using followed tasks

...

Task tags

Use short and meaningful tags, single words or phrases, to best describe the task, the technology used in the task, and the target field for the task usage. Exampels are:

• Multithreading
• Delete folder
• Write text file

Try to check the already existing tags and reuse them from the Robogator cosmos to reduce multiple variations of the same tag.

Name at least 3 tags per task and create a collection at the end of the task description with the following structure:

• tags["tag1","tag2",tag3"]

Here are some good examples:

• tags["Crawler","Folder names","Csv output"]
• tags["Folder","File","Desktop","Cleanup"]
• tags["Csv","Big data","Read","Multithreading"]

Task chat messages

Use Robogator chat messages (Write to Console) to notify the user about the most important stuff. Use clickable links and bold text to maximize the user experience. The script must start with an initial message. Keep in mind that too many messages will slow down the script.

Task cancellation

Each task must be able to be cancelled immediately. If necessary, add manual cancellation steps to the script to ensure the desired behavior.

Task error handling

Please note this carefully. Ensure that sufficient error handling fallback routes are included in the task script. The goal is to present only informative soft errors to the end user.