Autopilot Automation Template

Cross-platform template used for single-task automations compatible with Autopilot for Everyone with descriptive argument names, using specific datatypes and output arguments.

To build automations that can be leveraged later by Autopilot for Everyone, we suggest the following best practices:

• To allow Autopilot to use the automation on MacOS, build the automation projects with the cross-platform compatibility.
• Focus each automation on a single task. For example, use one to five activities in a single sequence.
• Use descriptive argument names and naming conventions, such as CamelCase format.
• If some arguments are mandatory for the successful execution of the automation, set them as required during the design time.
• Use the following datatypes exclusively:
  • String - rendered as a free text field
  • Int32 - rendered as a whole number picker
  • Double - rendered as a whole or decimal number picker
  • Boolean - rendered as a True / False dropdown
  • Datetime - rendered as a datetime picker
• Use the following output arguments exclusively:
  • ResultMessage - can be either of the following:
    • A string message, which is display back to the user. It usually holds the results of the operation.
    • A string serialization of a JSON or Data Table object.

1. Standardization: Ensures consistency across all automations, making them easier for Autopilot to leverage. 
2. Cross-platform compatibility: Broadens usability across different operating systems. 
3. Simplicity: Single-task focus makes automations easier to understand and maintain.
4. Clear naming: Improves readability for both humans and Autopilot.
5. Error prevention
6. Consistent data handling: Standardized data types and output format simplify Autopilot's interaction with automations.
7. Scalability: Facilitates easy integration of new automations into the Autopilot ecosystem.
8. Efficient maintenance: Uniform structure across automations simplifies updates and troubleshooting.