Glossary

Each area of knowledge has its own terminology, the same applies to software applications. Certainly, the nomenclature Action.NET uses follows market patterns whenever possible, but there are specific terms related to the system and other words can have a special meaning when using in this context.

This glossary has most of the terms and keywords used by Action.NET and also related concepts and technologies that are relevant to our context.
It is highly recommended to at least read from this glossary once, after you have used Action.NET for a month or two. Reviewing the definitions and nomenclature used by the Action.NET platform and SPIN's engineering and development teams, combined with their experience with the product, will make your understanding of the system empower you to build applications at a higher level.

App Domain OR Application Domain	Represents the virtual isolated computer environment where a DOT NET application runs. Isolated, in this context, means that the areas of memory and components used by programming running in this environment are completely isolated from other programs running on the same computer. The inherent isolation of dot NET domains creates intrinsically secure protection for running projects, as it prevents one process from interfering with the other, even allowing two different versions of the same program to run side by side. A more technical definition of AppDomain is the space that is formed by the boundaries that the Common Language Runtime (CLR) provides around objects created from the same application.
Application or Application	Refers to the final solution or system created using Action.NET. The terms Application and Project are used om near meanings: Design refers to the engineering configuration and files needed to implement the solution and application refers to the conceptual solution that was created.
Assembly or Assembly	Refers to an executable file (. EXE or Library.dll) created using managed code and Microsoft NET framework..
Designer	Engineering Workspace component used to draw and animate monitors and sinoptic screens.
DLL Hell	Term used to refer to complications in running legacy Windows applications because there is no built-in isolation in the DLLs libraries, memory, and COM objects used by the applications. The DOT NET Framework completely eliminates this problem.
Domain, Server Domain, Client	Refers to the values and location of objects in execution. Objects in the server domain are the objects in, server during execution. The values associated with this object are system-throughout. Domain of the Clients are the specific objects that are running on the client station, and each machine can have different values for them.
Internal Module	It is the resources and programs that implement the internal system functions, which run without any user configuration. Examples of this are the Network Sync task and the Report Generator (run in the background). Some Studio tools, for example, ModuleInformation.exe, can display information about the status of these built-in modules, however, this information is only required for advanced system optimizations.
Main Project File or Main file of Project	Refers to the encoded SQL database that contains the project configuration. The extension. TPROJ refers to the current project still under development. As extension. TRUN refers to published projects in read-only files.
Modifier (Device/Points)	Auxiliary parameter to specify modifications to read and write points for a device, such as handling Arrays, bit masks, strings, inversion of bytes, and other operations where the DataType definition cannot define them completely.
Module	A program that accesses the real-time database (BDTR) and can be composed of one or more assemblies.
Namespace	A address space. All objects created with a namespace have unique, univocal names. Address space can also be understood as a way to tie a set of objects. All process variables are grouped into the namespace named Tag; all reports are grouped in the namespace report. The name of an object must be unique within the namespace to which the object belongs.
Object Type (RunObj) type)	Determines the type of object at run time (preview, report script).
Objects, Runtime Objects	Runtime objects are those objects visible (through their names) to access the project through scripts and displays, such as Tags, Reports Alarms, Displays, among others. Namespaces also identify which execution module is responsible for updating these values, for example, the alarm module will start and update the values of the runtime objects associated with alarms.
ObjectValues, PropertyValue	Runtime objects (for example, Tags, deviceNodes, etc.) can have one or more properties set. The TAG (and the property value), for example, MIN, MAX, Description, etc., among other properties.
PropertyWatch	Diagnostic utility to check and modify the values of objects at run time.
OPC Foundation	The OPC Foundation (OPC formally known as Object Linking and Embedding for Process Control) is an industrial consortium that creates and maintains standards for open connectivity of industrial automation devices and systems, such as industrial control systems and process control in general. OPC standards specify the communication of industrial process data, alarms and events, historical data, and batch process data between sensors, instruments, controllers, software systems, and notification devices.
OPC DA Specification	OPC Data Access Specification The OPC Data Access Specification is the first of a specification group known as Classic OPC Specifications.OPC Data Access is a client-server standards group that provides specifications for real-time data communication from data acquisition devices. PLCs to display and connect devices such as Human-Machine Interfaces (HMI), SCADA systems [2] and also ERP/MES systems. [3] Specifications focus on continuous data communication.
Parameters(Tag Configuration)	Definition of behavior and processing parameters for Tag values
Project	A set of studio settings, screen sketches, reports, scripts, and user notes created and edited with a single entity.
projectDB / ProjectDatabase	ProjectDB (or project database) is a database that contains configuration information. Match the files with the <Project>. Tproj (current type, for example) or <Project>_ version. Teng (type released for use, for example).
Property OR Atribute	Property (value) associated with a tag or object.
RunDB, Runtime Database/RtDB	The real-time database created when the project is running. All objects that can be accessed while running (such as tags, displays, reports) are objects in the Runtime database, also called Real-Time Database or BDTR.
Runtime	Refers to a project with modules loaded and in full execution.
Runtime Startup	Operation that is causes the project to go into runtime. This operation can be performed from the TStartup program.exe in the update version of Action.NET or TServer.exe the published version of the project.
Tag	The process variable. Name of a Namespace, which includes all variables created by the user in a project configuration.
Tag Type	Defines the type of objects in the namespace Tag: Digital, Analog, Text. These tags are a class of components or properties accessed directly, such as minimum, maximum, value, quality. Each property is created internally as a ValueType.
Task (Script.Task)	Program written in VB.NET (or C#), which runs on the server or client during the runtime of a project. Execution will be on the server or client, depending on the configuration of the domain property in the script.
TManager	The program that must be run to perform the configuration of a project.
Toggle	Reverse the value of a variable. Values greater than zero are converted to zero; zero is converted to the value "1".
Trust Partial Trust Full Trust or Confidence confidence partial Confidence Complete	Partial Trust: Environment where an application has limited access to resources (restricted access to , folders, running other applications, etc.) , XBAP applications that run within a browser (for example, Internet Explorer) should run under "Partial Trust." Total Trust: Environment where an application has access to all system resources. Applications installed on a computer typically run in "Full Trust" mode.
Visibility (Tag Visibility)	Refers to the Tag visibility system; Tags can be private, public, or protected. Public: The tag value during runtime execution is available for access to external programs via TCP/IP or OPC Server. In addition, the tag value is necessarily global, or shared between all client stations (Server Domain). Protégé: Read-only. Particular: The tag set to "private" cannot be accessed by external applications (OPC Server, TCP/IP) and will run on client or server machines according to the application configuration with the following characteristics: Tags used only in customer-called modules (such as Screens and Reports) run at client scope, or may have different values on each client machine (Domain Client); Tags used in server modules such as devices and alarms have a unique value in the system (Domain Server).
XBAP	Xaml Browser Application (XBAP) is a graphical application using XAML technology that runs within a browser (Internet Explorer).