Difference between revisions of "Nomenclature"

From TempusServa wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 11: Line 11:
**Action: Configurable behavior depending on status
**Action: Configurable behavior depending on status
*Field: A single data point of a record   
*Field: A single data point of a record   
**Block: Collection of fields
**Block: Collection of fields for the purpose of access management
**Validation: A check on whether or not a field has received correct data
**Validation: A check on whether or not a field has received correct data
**Dependency: A field's existence can be made dependent on other things
**Dependency: A field's existence can be made dependent on other things
*User group: Determines who has access to which data and features
*User group: Determines who has access to which data and features
*Codeunit: Java code for specialized functionality
*Template: Tool for automatically creating documents and interfaces by feeding values into a predefined layout.
*Interface:


==Parts==
==Parts==

Latest revision as of 11:15, 1 September 2023

Objects

  • Dashboard: Front-end page
    • Widget: UI element in a dashboard
  • Section: Collection of entities
  • Entity: Describes a type of record, including its behavior and datatypes (This is a class in OOP)
  • Record: Main data holding thing (This is an object in OOP)
    • Revision: How many times a record has been changed
  • Status: Configurable state a record is in
    • Level: Assignable number to a status
    • Action: Configurable behavior depending on status
  • Field: A single data point of a record
    • Block: Collection of fields for the purpose of access management
    • Validation: A check on whether or not a field has received correct data
    • Dependency: A field's existence can be made dependent on other things
  • User group: Determines who has access to which data and features
  • Codeunit: Java code for specialized functionality
  • Template: Tool for automatically creating documents and interfaces by feeding values into a predefined layout.
  • Interface:

Parts

  • Front-end: The system that the normal user sees
  • Back-end: Where the front-end is configured
  • Database: It's a database