New modules can be easily added to the list by selecting Add module. This then presents the Add module screen displaying the fields needed for the module. On selecting Submit, the new module is added to the list for subsequent addition to sequences. The fields are:
|Brief name or description of the module. This description is used by the application whenever there is a reference required for the module being processed, for example, Claim Audit.
|Key assigned to this module. This identifier is stored for references to the module and is used as a lookup value for the module. It lets you modify the description without worrying about the reference to the module. Once you assign and use it, you should not modify it. This identifier is also used in assigning event codes
|Collection rule associated with the module. Select the process from a drop-down list of available collections. This is the rule that the module executes.
|Process type *
|The type of module (Stub, Pega, and External) as it relates to the application
|Indicator that defines whether a measurement should be captured for this module. This allows specific module measurement if the global measurement is off in the system settings.
|Indicator that defines whether any audit information should be reported for this module. This allows specific module audits to be logged if the global audit is off in the system settings.
|Indicator that defines whether to always bypass processing of this module. This is a useful feature during the testing of new modules
|Module bypass table
|Bypass table used for configuring information that can cause the module to be bypassed for specific claims
|A collection rule that can be used to initialize any values pre-run or perform any pre-run logic.
|A collection rule that can be used to finalize any values post-run or add any extensions to the module for client driven processing.
|Module next step
|A collection rule that is executed on completion of the module.