The name for a custom package. However, Designer displays the name assigned to the package during creation and not the Display Name. Apart from Package Attributes in Designer, the property is also displayed on the Package Information page in Integration Server Administrator.

Display Name is mainly used to identify a custom package in webMethods.io Integration projects.

Specifies the version number for the package. Version numbers need to be in one of the following formats: X.x or X.x.x (for example, 1.0, 2.1, 2.1.3, or 3.1.2). By default, Designer assigns the version number 1.0 to a new package.

Displays the build number of the package. The build number is a generation number that a user assigns to a package each time the package is regenerated. For example, a user might generate version 1.0 of the “Finance” package ten times and assign build numbers 1,2,3…10 to the different generations or builds of the package.

The build number is not the same as the package version number. One version of a package might have multiple builds.

For custom packages, the build number is editable.

Displays a description of the package written by the user who created the package release. For custom packages, the property supports multiple lines of text, which is editable and scrollable.

Displays the version of the JVM (Java virtual machine) required to run the package.

Displays the name of the publishing server that created the package release.

Displays the patch numbers included in this release of the package.

Displays the current state of a custom package. For example, a package might be in the development stage or ready for production. Accordingly, you can select one of the following statuses or select a custom status. For more information about creating custom statuses, see Package Status Preferences.

Displays whether a custom package is safe to use or not. Select the check box if the package is safe to use and clear the check box if the package is not safe to use. By default, the check box is not selected.

Displays a list of values that you can use to search and group custom package assets.

Add a new tag.

Click Add. In the Add a new tag field, enter a new tag, and click OK.

Remove an existing tag.

Select the tag that you want to delete, and click Remove.

Provides an option to generate the package documentation.

For more information, see Generating Package Documentation.