Package Version form in RPA Hub
Use the Package Version form to view the code quality result.
| Name of the rule | Description |
|---|---|
| Package | Associated package of the package version. |
| Version | Version number that identifies the set of components uploaded in a package |
| Application | Application that contains this record. This field is auto-generated. Role required to view this field: admin. |
| Life Cycle Stage Status | Life-cycle stage statuses of a package version. |
| Active | Option to set this package version as active. The active version of the template is used when a template is selected for creating automation in RPA Desktop Design Studio. Only one package version can be set as active. This field is applicable only for Unattended Template and Attended Template package types. For more information about package types, see Create a package to assign to a bot process. Roles required to edit this field: RPA admin and RPA release manager. |
| Code Quality Result | Indicates if the Code Quality Check feature in RPA Desktop Design Studio has detected any errors, warnings, or information in the package.
If the Code Quality Check feature is not enabled, then the value in this field is Not Applicable. Code quality status of package versions are set with highest severity. To review the error or warning, open the package version file in RPA Desktop Design Studio. For more information about code quality check feature, see Code quality check in RPA Hub. |
| Comments | Brief description of the package version. |