Create a package to assign to a bot process

릴리스 버전: Australia

업데이트 날짜 2026년 03월 12일

소요 시간: 6분

Create an unattended or attended package in RPA Hub to assign it to a bot process to execute an automation.

시작하기 전에

(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.

Role required: sn_rpa_fdn.rpa_release_manager, sn_rpa_fdn.rpa_developer, or sn_rpa_fdn.rpa_admin

프로시저

Navigate to All > Robotic Process Automation > RPA Hub Workspace.
Select the list icon ().
On the Lists tab, under Build, select Packages.
Select New.

On the form, fill in the fields.

표 1. Package form
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
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.

Select Save.
옵션: In the Activity and Compose fields, view the activity of the form, work notes, and additional comments.

결과

After a package is created, the RPA developer publishes an automation from RPA Desktop Design Studio. This process results in a new package version.

Package Version form in RPA Hub

Use the Package Version form to view the code quality result.

표 2. Package Version form
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. 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. 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.