Monikers configuration

The Monikers configuration assigns a unique name to every business object and applet in Infor Public Sector. Each product family is separated, named, and given a path to the location of the assembly where the code is found. Applets and business objects are broken down into separate sections.

APPLETS

The APPLETS node defines the applet monikers. This node has a number of child Family nodes, each of which has one attribute:

Attribute Description
name Name of the product family, such as Property or CDR.Building. The family name represents part of the namespace used to locate a particular class. Hansen is always used to begin a namespace so there is no need to specify it here.

Each Family node has a number of child Applet nodes with these attributes:

Attribute Description
class Class name of the applet.
file File name of the assembly into which the applet has been compiled.
name Moniker of the applet.
path Full path of the assembly that contains the applet. This path is relative to the path specified in the PATHS node of the Hansen8 configuration.

COMPONENTS

The COMPONENTS node defines the business object monikers. Like APPLETS, this node has a number of Family nodes as children. Each Family node has one attribute:

Attribute Description
name Name of the product family.

Each Family node has a number of Component children with these attributes:

Attribute Description
class Specifies the class name of the business object to instantiate. You can use this attribute to change the class instantiated at runtime, which is useful in cases like Address where the necessary class could be USAddress, UKAddress, or something else.
file Specifies the file name of the assembly into which the business object has been compiled.
name Fixed moniker of the business object. In most cases this is the same as the class name of the business object. After this name set, it should never be changed.
path Full path of the assembly that contains the business object. This path is relative to the path specified in the PATHS node of the Hansen8 configuration.

Each Component node can have one ASSOC node and one QUERIES node as children.

The ASSOC node has one or more Association nodes as children, each of which specifies an applet that is associated with the parent component. Each Association node has these attributes:

Attribute Description
name Name of the associated applet.
value Moniker of the associated applet.

The QUERIES node which groups predefined queries that may be used for performance reasons. The QUERIES node can have one or more Query nodes as children. Each Query node represents a single query that can be called by the data engine. A Query node can have these attributes:

Attribute Description
accid Access ID for the query. The access ID is a unique number that identifies the permission in Access Control that users must be granted to gain access to this item.
name Name of the query. This same name is used in the code, so it should not be changed.
oracle SQL string to pass to the Oracle database. If you enter a value here, then it is assumed that the sql attribute works for SQL Server only and that this SQL string only works on an Oracle database.
sql SQL string to pass to the database. If this is the only SQL string provided, it may be assumed that it will work with any database (SQL Server or Oracle).

Each Query node can have one or more Parameter nodes as children. Each of these nodes specifies a parameter to be passed in along with the SQL string. Each Parameter node can have these attributes:

Attribute Description
description Description of the parameter.
name Name of the parameter.
sql SQL string for the parameter.
type Type of parameter.