Version: 7.0

Modules

📄️ Package: Register Action

When adding objects to workflows it can be chosen between objects or actions. To add actions of a package to the selection they have to be registered first. This task can be done with this module.

📄️ Package: Build Release

This module creates a release archive of the current version of a packages in a client. The archive can be installed with the module pm.Install in any client

📄️ Package: Compliance

The module evaluates if the objects of a package follow a configurable set of rules. Different tests can be used to verify these rules.

The module is able add credentials to a storage object. The data can be used when installing packages. If login or connection objects are part of a package the credentials can be restored using such a storage object.

📄️ Package: Download Credentials

The module is able to download and save the credentials of a storage-object. Based on the given name of the storage object all client and environment specific storage objects are included. For each storage object a directory is created and within this directory a file is stored for each entry.

📄️ Package: Check Dependencies

The module is able to check if the dependencies of a package are fullfilled in a client. Therefore a package archive or the package name and the dependency definitions has to be provided. The results of the check will be written to the report. Optionally the results can be written to a variable object.

📄️ Package: Create Dependency Definition

The module determines the dependencies of a package and creates a dependency definition automatically. The creation of the definition can be influence by setting an operator and a base version.

📄️ Package: Verify Dependency Definition

The module checks if the dependency definitions in the metadata variable are correct. Therefore the real dependencies of the package are determined. This set is compared with the dependencies from the metadata variable. Dependencies that are missing or unnecessary will be registered as errors. Additionally the version comparsion in the definition can be checked against the packages in the current client. The results of the analysis are stored in a variable.

📄️ Package: Build Documentation

This module generates documentation for objects of a package. The documentation is based on template that can be created for each object type. The format (text based) can be chosen freely. Examples for possible output formats are be HTML, Confluence Storage Format, Markdown or SVG.

📄️ Package: BPMN2Workflow

BPMN is a specification for describing processes. On base of such a definition this module creates a workflow with the defined tasks. The BPMN process needs to fullfill several condition so the generation of the workflow is possible.

📄️ Package: Index

Builds a package index containing a list of installed packages and its metadata

📄️ Package: Build Index Documentation

This module generates documentation for the index variable. The documentation is based on a template. The text format of the template can be freely selected. Examples of possible output formats are HTML, Confluence Storage Format, Markdown or SVG.

📄️ Package: Initialize

The module creates a template for a new package by creating the necessary sub-folders and a variable for metadata

📄️ Package: Install

Package release archives created with the module pm.Build can be installed in any client with this module. The installation consists of serveral steps.

📄️ Package: Listing

Designation

📄️ Package: List folders

Lists the base folders

📄️ Package: Report about Installation

The module creates a report about all installed packages in a client. The report will be stored in the structured documentation of an object.

📄️ Package: Report about Modifications

The module searches for modifications of all packages in the client, that have been made after the last build. The last build is identified by the timestamp in the metadata variable or if not found be the timestamp of the last modification of the metadata variable. The results of the analysis are stored in the structured documentation of a given object.