a6e5b969-be6e-4756-ae53-47d3cb899ca4.png

f6939e87-70aa-4037-bf60-fb86e892829f.jpg

3d4f1f56-a43d-44f7-bf66-c01b08d1f6d3.nupkg

31098de7-dc23-4371-9c35-ee77e975d751.png

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.

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

Version	Release Date	Download Link
1.0.1	October 7, 2024
Main.xml - This is where all the logic of the automation should be. Make sure the activities are error handled so the Autopilot gets a user-friendly error explanation that can be shared with the end user. AutopilotAutomationTestCase.xml - This file contains a Given-When-Then testing structure: Given - sets up test data and automation conditions When - runs the automation you want to test Then - checks if the automation worked as expected and cleans up the test environment
1.0.1	September 24, 2024
Main.xml - This is where all the logic of the automation should be. Make sure the activities are error handled so the Autopilot gets a user-friendly error explanation that can be shared with the end user. AutopilotAutomationTestCase.xml - This file contains a Given-When-Then testing structure: Given - sets up test data and automation conditions When - runs the automation you want to test Then - checks if the automation worked as expected and cleans up the test environment

Autopilot Automation Template