Who is this article for?

Module developers and Users configuring and testing new projects or changes.

Module developer license and Area access is required to make changes.

Modules are the building blocks of an application. A module can contain data collected in fields, have workflow steps from initiate to close, and follow business rules that hide fields or steps.

Depending on its complexity, an application can be configured from a single module or multiple modules.

Each record created by a module is called an Object. Objects are what users interact with. An object can look and behave differently through its life cycle depending on the rules and behaviors defined in the module, the workflow state it's in, the role of the person interacting with it, and many other factors.

The module definition is stored in a series of configuration tables which are exposed as Platform views. Each of the elements that can be modified within the module configuration is referred to as a target and each target is assigned a target ID.

When a user performs an action on an object, The Platform reads those module definition tables to determine how it should behave. There are many configuration tables that store information about:

• Screen layout
• Levels (e.g. child items)
• Fields, including properties and behaviors
• Roles
• Rules
• Module behaviors
• Printing
• Batch processing
• Web services
• Search options

For additional information on modules visit the Getting Started as a Module Developer.