Skip to main content

Module type catalogue

This catalogue lists current user-configurable types evidenced by Designer creation menus and active implementation. A class or enum value in source is not included when no current creation/configuration path was confirmed.

Core modules​

TypePurposeDetailed authority
General SetupSystem-wide runtime, service, email, network/API, logging and retry valuesGeneral Setup
FolderOrganise permitted module familiesFolders and naming
DB ConnectionReusable DB access; method selects SQL Server, Oracle, MySQL, PostgreSQL, IBM DB2, ADO or ODBC fieldsDB Connections
File ConnectionPaths, patterns, naming and lifecycle foldersFile Connections
DB DefinitionDatabase data structure/query/update rulesDB Definitions
Flat/XML/JSON/EDI/Excel File DefinitionTyped file structure and parse/write rulesFile Definitions
FlowData, ordered steps, triggers, policy, logging and runtimeFlows
MapDefinition-to-Definition mapping and expressionsMaps
ReportReportBuilder data/layout and outputReports
SQL ScriptSaved interactive SQL workspace/moduleSQL Scripts
ScriptletReusable PascalScriptScriptlets
Variable GroupReusable typed/environment valuesVariable Groups
APIREST Flow grouping and OpenAPI metadata/schemaAPI module properties

Flow child types​

Flow data items are database or file. Active Add Action... step types are Map, Report, Custom Script, Outbound Transport, File Router, Command Line, Custom SQL and Sub Action; use the Flow-step index.

Current triggers are manual/Test Run, schedule, file monitor, REST, inbound Transport and successful linked successor. These are invocation settings/relationships, not standalone ordinary modules.

Concrete Transport types​

DirectionActive typesDetailed authority
InboundFTP, SFTP, LAN, HTTP, IMAP, POP3, MSMQ, IBM MQTransport guide and protocol child pages
OutboundFTP, SFTP, LAN, HTTP, SMTP/email, MSMQ, IBM MQTransport guide and protocol child pages

AS2 and uncreatable/incomplete Flow-step enum values such as Call Plugin, Transaction Commit, DB Disconnect, Wait for File and Inbound Transport are not documented as active current choices. Configuration Templates and Logs are internal/operational artefacts, not ordinary user-created design modules.