Development Package
In Development Package, you organize and group artifacts. These artifacts, for example, APIs, applications, or themes, can be assigned to a package for better handling.
When setting up new artifacts in other tools and services, for example, the App Designer, the Adaptive Designer, or the API Designer, you can often choose to have that artifact become part of a specific package. Packaging facilitates the handling of multiple artifacts that behave in a similar way.
There are several ways to create a package:
After you set up a new package, you can optionally configure a connection to GitHub.
You can view the artifacts within a package in the Artifacts tab.
Template and system packages
You cannot assign your own artifacts to a template package. When the system is upgraded, template packages are imported again, and the import deletes any custom artifacts that were assigned to the package. The App Designer, PDF Designer, and Script Editor reject such an assignment with an error message, both when you create an artifact and when you change the package of an existing artifact.
System packages, such as neptunesoftware-dxp-system-artifacts, are listed in
Development Package, but you cannot select them when you create or edit artifacts.