Glossary

Table 1. Glossary
Term	Definition
AccessAs	Mongoose identifier to denote which development entity owns objects having its value in its definition. BaseSyteLine denotes objects developed and maintained by SyteLine development. Core denotes objects developed and maintained by Mongoose development. Objects with no AccessAs value or ue_ denote objects developed and maintained by the customer (or their delegates). Business partners can also develop objects with their own AccessAs value.
AES	Application Event System – Mongoose technology which allows event-driven programming.
CLM	Custom Load Method: a type of IDO method used to retrieve rows of data.
SyteLine .NET Class Types	Extension Class: C# Mongoose entry point of IDO Methods Application Class: term used to represent C# application class code containing SyteLine logic. Closest object to stored procedures. Composition Root Class: Composition Root Class is a class where base product registers its classes as "services". This class is used by a service provider for composing and returning an instance of an object along with all of its dependencies injected into it. Interface: term used to represent C# application interface code responsible to define class signatures.
Extensibility Types	Additive: term used to describe when custom behaviors are appended to SyteLine standard functionality and typically have no merging requirements. Examples are AES event handlers which can be added to Mongoose IDO, session, and task events to perform custom actions on, before, or following SyteLine actions. Copied: term used to describe when custom behaviors are included in objects which have their basis in SyteLine objects which typically have merging requirements outside of Mongoose tools. Examples are EXTGEN stored procedures or app classes which originate as copies of SyteLine objects and contain customer logic within. Personalized: term used to describe when custom behaviors are introduced in Mongoose objects which require a utility to manage. Examples are scoped (site, group, or user) forms requiring Mongoose FormSync process to merge new/updated SyteLine vendor definitions into customer forms objects. Custom: term used to describe an object with no SyteLine basis and represents something unique.
IDE	Integrated Development Environment tool similar to Microsoft Visual Studio.
IDO	Intelligent Data Object: a Mongoose metadata model consisting of properties and methods used as data source for Mongoose development
IDO Custom Assembly	Binary Only: term used to describe an uploaded dynamic link library in accordance with allowable media types Build From Source: implemented from a Mongoose form containing .NET source code with the ability to build
IDO Method	A set of logic available to Mongoose IDORuntime to perform tasks. Two types are supported: Standard used to obtain a scalar set (single row) of results Custom Load used to obtain multiple rows of data or dataset
SSMS	SQL Server Management Studio

AccessAs

Mongoose identifier to denote which development entity owns objects having its value in its definition.

BaseSyteLine denotes objects developed and maintained by SyteLine development.

Core denotes objects developed and maintained by Mongoose development.

Objects with no AccessAs value or ue_ denote objects developed and maintained by the customer (or their delegates).

Business partners can also develop objects with their own AccessAs value.

AES

Application Event System – Mongoose technology which allows event-driven programming.

CLM

Custom Load Method: a type of IDO method used to retrieve rows of data.

SyteLine .NET Class Types

Extension Class: C# Mongoose entry point of IDO Methods

Application Class: term used to represent C# application class code containing SyteLine logic. Closest object to stored procedures.

Composition Root Class: Composition Root Class is a class where base product registers its classes as "services". This class is used by a service provider for composing and returning an instance of an object along with all of its dependencies injected into it.

Interface: term used to represent C# application interface code responsible to define class signatures.

Extensibility Types

Additive: term used to describe when custom behaviors are appended to SyteLine standard functionality and typically have no merging requirements. Examples are AES event handlers which can be added to Mongoose IDO, session, and task events to perform custom actions on, before, or following SyteLine actions.

Copied: term used to describe when custom behaviors are included in objects which have their basis in SyteLine objects which typically have merging requirements outside of Mongoose tools. Examples are EXTGEN stored procedures or app classes which originate as copies of SyteLine objects and contain customer logic within.

Personalized: term used to describe when custom behaviors are introduced in Mongoose objects which require a utility to manage. Examples are scoped (site, group, or user) forms requiring Mongoose FormSync process to merge new/updated SyteLine vendor definitions into customer forms objects.

Custom: term used to describe an object with no SyteLine basis and represents something unique.

IDE

Integrated Development Environment tool similar to Microsoft Visual Studio.

IDO

Intelligent Data Object: a Mongoose metadata model consisting of properties and methods used as data source for Mongoose development

IDO Custom Assembly

Binary Only: term used to describe an uploaded dynamic link library in accordance with allowable media types

Build From Source: implemented from a Mongoose form containing .NET source code with the ability to build

IDO Method

A set of logic available to Mongoose IDORuntime to perform tasks. Two types are supported:

Standard used to obtain a scalar set (single row) of results
Custom Load used to obtain multiple rows of data or dataset

SSMS

SQL Server Management Studio