Packages
The Packages feature in AnalyticsCreator defines reusable logical execution containers for data transformation and ETL orchestration. Each package bundles related transformations or workflows that run in a sequence during deployment or runtime.
Function
Packages allow you to organize and control the execution of transformations and ETL tasks. They can be launched manually, externally, or automatically. Packages support dependency management to define execution order between them.
Access
Packages are managed in DWH > Packages. The interface consists of a List View for searching and managing existing packages, and an Edit View for modifying or creating new packages.
List Packages
The image below shows the List Packages interface with columns labeled for easy identification.
List Screen Properties
| ID | Property | Description |
|---|---|---|
| 1 | Package name | Displays the unique name of the package |
| 2 | Package type | Shows the type of the package (e.g., IMP, HIST, PERS) |
| 3 | Manually created | Indicates if the package was created manually |
| 4 | Externally launched | Indicates if the package is triggered externally |
| 5 | Description | Shows notes or comments about the package |
| 6 | Delete | Deletes the selected package |
| 7 | New | Opens the editor to define a new package |
Packages Edit
The image below shows the Packages Edit interface used for creating or modifying package definitions.
Edit Screen Properties
| ID | Property | Description |
|---|---|---|
| 1 | Package name | Defines the name of the package |
| 2 | Package type | Specifies the processing type (e.g., external, import) |
| 3 | Manually created | Marks the package as user-created |
| 4 | Externally launched | Marks if it should be triggered by external tools |
| 5 | Description | Optional field to describe the package's purpose |
| 6 | Manual dependencies | Lists all packages that can be linked as dependencies |
| 7 | Depends on | Marks if current package depends on another |
| 8 | Add | Adds a selected package as a dependency |
| 9 | Remove | Removes an existing dependency |
| 10 | Refresh | Reloads the list of available dependencies |
| 11 | Cancel | Cancels the edit and returns to list view |
| 12 | Save | Saves the changes made to the package |
Behavior
- Packages control execution flow and organization of ETL tasks
- Dependencies determine execution order and hierarchy
- They can be triggered manually, automatically, or externally
Notes
- Use descriptions to document business context of packages
- Package types determine runtime behavior during deployment
- Keep dependencies updated for proper load order
