--- sourceDocument: Australia Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications Release : - australia ft:locale : - en-US ft:publication_title : - Australia Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # Create a package # Create a package to assign to a bot process {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Create an unattended or attended package in RPA Hub to assign it to a bot process to execute an automation. ## Before you begin (Optional) Configure the system properties related to Activity Stream, to add or remove the fields. The changes to these fields are captured in the work notes. For more information, see [Configure the system properties for an activity stream in RPA Hub](https://www.servicenow.com/docs/aJv3Q7raSlp9ye2Evn45zw "Configure the system properties for an activity stream of work queues, schedules, packages, process parameters, and shared parameters in RPA Hub. You can add or remove the fields that are captured in the work notes of an activity stream."). Role required: sn_rpa_fdn.rpa_release_manager, sn_rpa_fdn.rpa_developer, or sn_rpa_fdn.rpa_admin ## Procedure 1. Navigate to AllRobotic Process AutomationRPA Hub Workspace. 2. Select the list icon (![List icon.]()). 3. On the Lists tab, under Build, select Packages. 4. Select New. 5. On the form, fill in the fields. {#create-package__table_pyx_mhd_4qb__entry__2} | Field | Description | |-|-| | Name | Unique name of the published package. | | Package Type | Type of the package: * Unattended: Unattended automation * Attended: Attended automation * Skill: Reusable automation * Unattended Template: Template for creating unattended automations in RPA Desktop Design Studio * Attended Template: Template for creating attended automations in RPA Desktop Design Studio {#create-package__ul_zy3_wk3_qqb} | | Application | \[Auto generated\] Application containing this record. Role required to view this field: admin. | | Mark As Default | Option to enable this package as a default package for the current domain. Only one package can be selected as a default package for any domain. This field appears only when Unattended Template or Attended Template is selected from the Package Type field. Roles required to edit this field: RPA admin. | | Description | Description of the package. | [Table 1. Package form] {#create-package__table_pyx_mhd_4qb} 6. Select Save. 7. **Optional:** In the Activity and Compose fields, view the activity of the form, work notes, and additional comments. ## Result After a package is created, the RPA developer publishes an automation from RPA Desktop Design Studio. This process results in a new package version. **Related tasks** * [Retire a package in RPA Hub](https://www.servicenow.com/docs/PC1Lm4_2KBVMKuZMeoF2NQ "Retire a package to turn it off. It is one of the life-cycle stages of a package. After you retire a package, it cannot be used further.") * [Download a package version in RPA Hub](https://www.servicenow.com/docs/ldg9dQF00NvYhWt8Jxda9A "Download a package version in RPA Hub so that it can be opened from the RPA Desktop Design Studio to build, debug, or modify the automation.") * [Publish an automation project in RPA Desktop Design Studio](https://www.servicenow.com/docs/yq7hezGyFjRZzOe21TsztA "Publish an automation project to RPA Hub from RPA Desktop Design Studio as a package or as a template. After publication, you can quickly deploy automation solutions in the RPA platforms by using the packages or by using a template as a framework to create automations.") **Related topics** * [View Audit History](https://www.servicenow.com/docs/access?context=c_HistorySets&version=australia&pubname=australia-platform-security&ft:locale=en-US) ## Package Version form in RPA Hub {#ariaid-title2} Use the Package Version form to view the code quality result. {#package-version-form-rpa__table_ucf_k2x_2rb__entry__2} | 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](https://www.servicenow.com/docs/06RRplYIx24pWqO7F8iDtQ#create-package "Create an unattended or attended package in RPA Hub to assign it to a bot process to execute an automation."). 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. * Error - If a package that is published from RPA Desktop Design Studio with the code quality check as error. If a package has both error and warning, then the code quality check result is error. If a package has both error and info, then the code quality check result is error. * Warning - If a package that is published from RPA Desktop Design Studio with the code quality check as warning. If a package has both warning and info, then the code quality check result is warning. * Pass - If a package that is published from RPA Desktop Design Studio without any code quality check error or warning or info. {#package-version-form-rpa__ul_ilz_4fq_byb} 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](https://www.servicenow.com/docs/6Q56aSvp09uZNS4njgfFLw "A code quality check refers to the process of evaluating the automation file or script to assess its adherence to coding standards, best practices, maintainability, and overall quality."). | | Comments | Brief description of the package version. | [Table 2. Package Version form] {#package-version-form-rpa__table_ucf_k2x_2rb} **Related tasks** * [View a package version in RPA Hub](https://www.servicenow.com/docs/5iBGxJdcd261HpgFsgpYwg "View a package version in RPA Hub so that it can be opened from the RPA Desktop Design Studio to build, debug, or modify the automation.") *[\>]: and then