Skip to main content

Modules

A module is one functional part of the application, with its server package, its client area, or both. Each page below explains what one module does, how its parts work together, and where to change it.

ModuleServer packageClient areaPage
Model and validationcatalog, visualization, validationcore, validationModel and Validation
Guided workflowselectionconfigurator/guidedGuided Workflow
Deployment profilesdeploymentconfiguratorDeployment Profiles
Configuration artifactsexportconfigurator/guidedConfiguration Artifacts
Deployment packagesexportconfigurator/sharedDeployment Packages
Publishingexportconfigurator/guidedPublishing
ExtractionextractionnoneExtraction Code
ExplorernoneexplorerExplorer
ConfiguratornoneconfiguratorConfigurator
Client foundationsnonecore, api, validationClient Foundations

How the modules work together​

The diagram follows one configuration from the loaded model to a deployment package.

The model module loads and checks the model. The guided workflow and the deployment profiles build on it, and the Configurator combines all three for the user. When the selection is valid, the export modules turn it into files: configuration artifacts first, then a deployment package around them, which publishing can commit to a repository.

Search documentation