Support for automation versioning
Introduction
Automation versioning is the process of updating the new versions of all the executed automation. The process of saving the automation versioning can be done by updating the newly released automation immediately. The new version needs to be saved with a new number based on the last version of the automation.
- 1 Introduction
- 2 Overview
- 2.1 Purpose
- 2.2 Scope
- 2.3 Automation versioning Feature
- 2.4 Benefits of Automation Versioning
- 2.5 Steps to use Automation Versioning
- 2.5.1 Task field
Overview
Automation versioning is a process of saving the new version of the executed automation. It’s associated with the series of storing the new versions of the automation. Sapper has curated a feature that allows you to take advantage of automation in various ways or versions called version control. Versions are different configuration information used for the same automation. When the user enters the details and saves the automation, it becomes the first version of that particular automation.
The automation versioning alludes to unused duplicates automation artifacts once you make changes so you'll back and recover those changes to track the critical changes in the automation.
Then, every time the configured configuration data you enter changes, and a new version is created. All the versions of automation get saved immediately so that they can be swiftly utilized by you based on the requirement. Also, automation versioning helps you to track the history of the all executed automation. It will help you to perform the required changes based on the need. From the automation history, you will be able to check the specific automation by searching about it.
Purpose
The core purpose of automation versioning required to track the automation changes, when new automation is created.
Scope
The automation versioning consists of various scope, which are mentioned below:
Automation versioning is ensuring reproducibility inside the automation tests environment since client doesn’t have to manually remember which automation artifact utilized to get desired output.
It’s a centralized automation artifacts storage.
The automation versioning include allows for connect the automation artifacts and tracking the output of it.
Users can execute the automation from the automation preview, only if the automation has any published version. Also, the automation which has published (live) status can not be deleted, automation can only be deleted once the user unpublished it.
Automation versioning Feature
Automation versioning is associated with various features. The core features related to versioning are present in the top right corner of the automation environment. These are version information, Test and execute and publish. For more information please visit the below table.
Input | Description | Example |
|---|---|---|
Version Information | Gives information about all the versions. From this top right corner option of the automation environment, you will get the details of the automation version. | 
|
Test and execute | This button is for testing the automation. It validates configurational details and executes only if they are free from any flaws. |
|
Publish | You can Publish the automation and it will run as per the provided configurational data. At a time only one version can be published for the executed automation. |
|
Benefits of Automation Versioning
Automation Versioning helps to enable you to conduct an effective analysis on the executed automation.
You can easily review all the automation, and can modify it based on the requirement. It can be deleted, and edited from the original automation copy.
The automation versioning ensures that different versions of the automations are distinguishable from each other. It allow you to easily identify the latest version
Automation versioning also helps you to fix the errors and ensure higher productivity with a seamless process.
Steps to use Automation Versioning
To view the automation versioning you need to visit the automation environment from the automation tab and reports from the Sapper home page.
2. If you want to visit the specific version details then you have to visit the automation environment form the automation tab. In the automation environment you will be able to view the versioning information's from the top right side of the screen.
3. Once you will click on the “Version Details” icon, the new form will be appear on the screen.
4. In this tab you will be able to access the details related to the automation version, created by, created date, last modify by, and the actions field. In the action field you will get the options for restore version and automation publish. You can use these actions based on your requirement.
Input | Description | Example |
|---|---|---|
Version | Versioning is a way to categorize the unique states of the executed automation as it is developed and released. In this field you will be able to view the number of automation version. | 1, 2 and 3. |
Created by | In this field you will be able to view the automation creator name. It can be represent in a email or username format. | |
Created date | This field is describe about the creation date of the specific automation. You will be able to view the date in the mention format: mm/dd/yyyy hh:mm AM/PM | 05/26/2022 05:15 AM |
Last modify by | In this field you will get the details of the last modifier. It can be view in a username or email format. | |
Actions | The action field is associated with core two aspects i.e., Restore version and Publish. You will be also able to access the details of unpublished |
|
5. You can also get the version details for the specific automation by downloaded it from the automation environment by selecting the “Export” option from the top right of the screen.
6. Once you download it you will get a detailed file with the automation and versioning information.
\"schemaPath\" : \"/properties/response/properties/lastUpdatedDateTime\"\n
},\n \"onlineMeetingInfo\" : {\n \"type\" : \"null\",\n
\"id\" : \"_97de949aaa4c4381aa9f751946b3effc\",\n \"order\" : 8,\n
\"path\" : \"[\\\"response\\\"].[\\\"onlineMeetingInfo\\\"]\",\n
\"schemaPath\" : \"/properties/response/properties/onlineMeetingInfo\"\n
},\n \"chatType\" : {\n
\"type\" : \"string\",\n \"id\" :
\"_87ddbbda2af44e88bdc8d23d32394d5b\",\n
\"order\" : 9,\n \"path\" : \"[\\\"r
"Microsoft Teams : Create Chat room\",\"description\"
:\"Microsoft Teams is a proprietary business communication platform developed by Microsoft, as part of the Microsoft 365 family of products.
\",\"applicationId\":\"628dc402ca5c80129020d501\",\"integrationType\":\"REST\"},{\"sappertasktype\":\"TP_NATIVE_APP\",\"bpmnType\":\"serviceTask\",\"id\"
:\"node_3_Microsoft_Teams_1653642080020\",\"name\":\"Microsoft_Teams\",\"title\":\"Microsoft Teams : Send Meeting Details to User\",\"description\"
:\"Microsoft Teams is a proprietary business communication platform developed by Microsoft, as part of the Microsoft 365 family of products.\",\"applicationId\"
:\"628dc402ca5c80129020d501\",\"integrationType\":\"REST\"}],\"error\":{\"node_3_Microsoft_Teams_1653642080020\":[],\"node_2_Microsoft_Teams_1653642074739\"
:[],\"node_1_Microsoft_365_1653642039050\":[]}}}","deleted"
:false,"createdDate":"2022-05-27T10:15:26.742Z[UTC]","createdBy":"Sample@sapper.ai","name":
"Meeting Work around ","id":"62909089ca5c80129020d61d",
"projectId":"Base","bpmnDefinition":"<?xml version=\"1.0\"
7. You will be also able to view the version details from the reports tab.
8. In this tab you will get a detailed details of the multiple automation. In this tab you will get the name of the automation, version, trigger type, status, execution start time, elapsed time and actions. From this tab you can get the details for the selected automation version. The versions can be 1.0, 2.0, 3.0 and so on. It will be updated based the new automation execution.
Input | Description | Example |
|---|---|---|
Automation Name | Provide the name of the automation. This field will explain about the specific automation name. | Get Application List |
Version | This field includes the version number for the specific automation. | 3.0 |
Trigger Type | A trigger type represent a set of actions that used for performing the response. Sapper supports three type of trigger type, i.e., On Demand, Webhook, and Scheduled. |
|
Status | The status field is associated with the various aspects, i.e., Failed, Completed, Waiting, Running and Triggered. |
|
Execution start time | The execution start time is the automation starting time. It can be represent in this format MM/DD/YY, HH:MM AM/PM | 5/29/22, 11:22 PM |
Elapsed time | The elapsed time associated with the running time of the automation. This field can be represent in this format hh:mm:ss:ms | 00:00:03:51 |
Actions | The actions field associated with the core two field, i.e., Show task and Download. The show task field is represented the detailed information's of the automation. The download option allow you to save the specific automation. |
|
Task field
The task field associated with the detailed data related to the specific automation. This field consists task name, task type, success count, failed count, elapsed time, data size and record processed.
Key | Description |
|---|---|
Task Name | This field represent the specific task name. |
Task Type | The task type is associated with the specific type of the automation task. |
Success count | This field associated with the success count of the automation. |
Failed count | This field associated with the failed count of the automation. |
Elapsed time | The elapsed time is associated with the automation running time. |
Data size | This field represent the data size of the automation. |
Record Processed | The record processed field includes the number of automation record that has been processed. |