Screenshot:Module

From InfiniteERP Wiki
Jump to: navigation, search
Back button.png   Back to Screens Reference


Module

Manages the modules currently installed.

Module

This tab manages the installed modules in the application.

  • Java Package : Java package for the module
  • Name : A non-unique identifier for a record/document often used as a search tool.
  • Type : A distinct item characteristic used for processes and sometimes grouped within a category.
  • Description : A space to write additional related information.
  • Help/Comment : A comment that adds additional information to help users work with fields.
  • Version : Module version
  • Version Label : Human readable version identifer
  • In Development : Determines wether the module is currently in development process.
  • Translation Required : This module requires of tranlsation
  • Is translation module : This is a translation module
  • Module Language : Language for the current module
  • Has chart of accounts : The module contains a chart of accounts
  • Has reference data : The module contains reference data
  • Reference Data Description : Description for the reference data contained within the module
  • License Type : Type of license
  • Commercial : Commercial Module
  • License text : Module license text
  • Author/Licensor : Module author/licensor
  • URL : An address which can be accessed via internet.
  • Update Information : Information about the update
  • Status : A defined state or position of a payment.
  • Apply Configuration Script : Apply the configuration script when building the application
  • Register Module : This process registers a module in the central repository
  • Enabled : Is the module enabled
  • Default : A value that is shown whenever a record is created.
  • Active : A flag indicating whether this record is available for use or de-activated.
  • Update Version : Update Version
  • Sequence Number : The order of records in a specified document.
  • Organization : Organizational entity within client
  • Module : Module
  • Maturity Status for Update : Minimum Maturity Status of modules for update
  • Client : Client for this installation.
  • Available Update : New version to update the current module

Dependency

Lists all the modules that are form part of the dependencies for the module.

  • Dependent Module : Dependent Module
  • First Version : First compatible version
  • Last Version : Last compatible version
  • Dependency Enforcement : Dependency enforcement defines which are the versions of the dependent module that are compatible with the parent one.
  • User Editable Enforcement : Defines whether the enforcement can be overwritten by user
  • Organization : Organizational entity within client
  • Module Dependency : Defines dependencies ammong modules
  • Module : Module
  • Is Included : Defines whether it is included or just dependant
  • Instance Enforcement : Instance specific dependency enforcement
  • Dependant Module Name : Name of the dependent module
  • Client : Client for this installation.
  • Active : A flag indicating whether this record is available for use or de-activated.

Include

For packages and templates the list of included modules is the list of the modules that form part of the package.

  • Included Module : Included Module
  • Version : First compatible version
  • Dependency Enforcement : Dependency enforcement defines which are the versions of the dependent module that are compatible with the parent one.
  • User Editable Enforcement : Defines whether the enforcement can be overwritten by user
  • Organization : Organizational entity within client
  • Module Dependency : Defines dependencies ammong modules
  • Module : Module
  • Last Version : Last compatible version
  • Is Included : Defines whether it is included or just dependant
  • Instance Enforcement : Instance specific dependency enforcement
  • Dependant Module Name : Name of the dependent module
  • Client : Client for this installation.
  • Active : A flag indicating whether this record is available for use or de-activated.

DB Prefix

DB Prefixes of the module

  • Name : A non-unique identifier for a record/document often used as a search tool.
  • Organization : Organizational entity within client
  • Module : Module
  • DB Prefix : DB Prefix
  • Client : Client for this installation.
  • Active : A flag indicating whether this record is available for use or de-activated.

Data Package

The Data Package is a grouping mechanism for tables within a module. Openbravo has a java business object for each Table. The java package of the java business object is defined in the Data Package. For example: a module for a crm package with the name: org.crm has packages: - org.crm.order - org.crm.customer

The corresponding tables have then the following setting: - Customer, in the org.crm.customer package, resulting in the java class: org.crm.customer.Customer - SalesOrder, in the org.crm.order package, resulting in the java class: org.crm.order.SalesOrder

  • Name : A non-unique identifier for a record/document often used as a search tool.
  • Java Package : Java package for the module
  • Description : A space to write additional related information.
  • Organization : Organizational entity within client
  • Module : Module
  • Data Package : Links a table to a package
  • Client : Client for this installation.
  • Active : A flag indicating whether this record is available for use or de-activated.

Merges

Modules can merge other ones. This table contains information about the merges. A module should be merged in a new major version and once it is merged it should be kept in all future versions. When there is a module merged, multiple DBPrefixes are allowed to maintain the one originally defined by the module as well as all the ones defined in the merged modules.

  • Merged Module UUID : UUID of the merged module.
  • Merged Module Name : Name of the merged module
  • Organization : Organizational entity within client
  • Module : Module
  • Client : Client for this installation.
  • Active : A flag indicating whether this record is available for use or de-activated.
  • AD_Module_Merge_ID

Naming Exceptions

The database objects that do not follow the modularity naming rules but are within the module are defined as Exceptions. This is particularly useful to facilitate the migration of all instances to modules. When an object is added to this tab, it will be exported its module instead of to core.

  • DB Object Type : Database Object type
  • Object Name : Object Name
  • Table Name : Table Name
  • Organization : Organizational entity within client
  • Module : Module
  • ID
  • Client : Client for this installation.
  • Active : A flag indicating whether this record is available for use or de-activated.

Translation

Module information can be translated to different languages

  • Active : A flag indicating whether this record is available for use or de-activated.
  • Language : A method of communication being used.
  • Description : A space to write additional related information.
  • Help/Comment : A comment that adds additional information to help users work with fields.
  • License text : Module license text
  • Translation : An indication that an item is translated.
  • Update Information : Information about the update
  • Reference Data Description : Description for the reference data contained within the module
  • Organization : Organizational entity within client
  • Module Translation : Translation for modules
  • Module : Module
  • Client : Client for this installation.
Back button.png   Back to Screens Reference