Glossary


  • 1C:Enterprise

    • The system of programs that includes the following:
      • 1C:Enterprise platform, which serves as both development and execution environment.
      • Applied solutions that are based on the platform and vary by scale and purpose.
      • Methodology for creating applied solutions.
      • Information and technological support for developers and end users.
  • 1C:Enterprise mode

    • The primary operation mode of the system, which is intended for end users (as opposed to administrators and developers). In this mode users add, edit, and delete data, generate reports, and perform other applied tasks. 

      See also: Designer mode.
  • 1C:Enterprise platform

    • The execution environment for 1C:Enterprise applications with a set of tools for application development and administration.
  • 1C:Enterprise script

    • A script language that is intended for describing business logic algorithms. It is also used for detailed interface description (if necessary), for integration with third-party applications, and so on.
  • 1C:Enterprise script object

    • A composite data type in 1C:Enterprise script. It usually contains a set of properties, methods, and events.  It is used for describing instances of data that have a state (a set of data instance properties) and a behavior (a set of methods and algorithms triggered by events).
  • 1C:Enterprise server cluster

    • The main platform component in the client/server mode. It is a collection of processes, services, and utilities that serves a single set of infobases. The main function of the cluster is execution of applications. It also provides fault tolerance and load balancing between working servers (while client applications are mostly focused on displaying user interface). 

      Aternatively to the client/server mode, the system can function in the file mode.
  • 1CEClientSetupMake.exe

    • An administration tool. It is a utility for creation of a self-extracting archive that contains a client application together with its installation, startup, and update settings.

      The archive is published on a web server. It is intended for automatic client application update for users that connect to the server cluster over the Internet.
  • Accounting flag

    • An attribute of the "Chart of accounts" applied object. It stores the accounting type for a specific account. For example, it can show whether the accounting is quantitative, or whether accounting is performed in foreign currency.
  • Accounting register

    • An applied object that is intended to store accounting data. It facilitates multilevel and multidimensional analytical accounting, and usage of multiple charts of accounts. It supports optional quantitative, value, and multicurrency accounting with a variety of breakdown options, and so on.
  • Accumulation register

    • An applied object that is intended for storing information on availability and movements of certain values (cash, goods, materials, and so on). It facilitates automation of warehouse accounting, settlement, and planning.
  • Action period  (of a calculation type)

    • A user-defined period when the calculation type is in effect.
  • Actions panel

    • A standard element of the applied solution command interface. It contains commonly used commands for creating database objects, running data processors, and generating reports.
  • Actual action period  (of a calculation type)

    • A period when the calculation type is in effect. The period is calculated by the platform according to "displacement by action period" rule. In general, it can be a composition of several periods. 

      For example, if an employee takes a vacation on the second week of the month, the vacation payment displaces the salary payment on the second week. Therefore, the actual action period for salary payment is a composition of two periods: the first week and the remainder of the month starting from the third week.
  • Administrator

    • A person who provides support for an applied solution used by an enterprise. An administrator adds users and assigns their rights, performs data backup and restoration, and so on.
  • Application

  • Applied object

    • A part of the platform - a prototype used for solving a set of applied tasks. For example, the applied object named Catalog allows adding the following business area concepts to the applied solution: "list of employees", "list of goods", "list of vendors", and so on. An applied object is a composition of 1C:Enterprise script types and objects, infobase tables, applied functionalities, and so on. It is a basic configuration building block. When a developer creates a configuration, they add applied objects to the configuration, specify their properties, and then describe their specific alrogithms in 1C:Enterprise script.
  • Applied solution

    • A program that automates tasks from a specific business area. It is a synonim for "configuration", which is used whenever a document targets end users and potential customers.
  • Attribute

    • 1. A database field that describes all data elements of a configuration object. For example, a configuration object Catalog.Items can have a Vendor attribute. It means that a vendor can be assigned to each catalog item. Developers can create attributes. The platform includes a number of standard attributes, such as Description, Code, DeletionMark, and so on. When accessing data from script, configuration object attributes can be accessed as properties of 1C:Enterprise script objects. 

      2. A property that describes an object. For example, form attributes store data processed by the form.
  • Automated testing

    • A process that emulates users' interactive actions and monitors the results.

      The emulation is performed with help of script objects that provide access to the logical model of the client application interface and form elements.
  • Available fields of data composition schema

    • A field that can be included in a report or used for grouping, filtering, or sorting purposes.
  • Base calculation period

    • A period within which the results of other calculation types that affect the current calculation type by base period are analyzed. 

      For example, if employees receive a bonus based on their salary during the last 3 months, the base calculation period for the bonus calculation type is composed of these 3 months.
  • Base calculation type

    • A calculation type whose result is used in the current calculation type. 

      For example, if bonus depends on salary, the salary calculation type serves as a base one for the bonus calculation type.
  • Business process

    • An applied object that is intended for describing business logic as a roadmap, as well as for lifecycle management of business processes (object instances) from their start till their end. The necessary attribute of business process descrition is its connection to a task, which defines the addressing system and allows planning roadmaps according to the organizational structure supported by the application.
  • Calculated fields

    • Additional fields of the data composition schema, which are created by developers and are absent from data sets. The value of an additional field is calculated according to a formula written in the data composition system expression language. An additional field can be used in the data composition scheme just like a standard field.
  • Calculation period

    • An applied object that is intended for storing records about calculation types that need to be performed, intermediate calculation data, and calculation results.
  • Calculation type

    • An algorithm used to calculate a certain portion of the wages, such as salary, bonus, and so on.
  • Catalog

    • An applied object that is intended for storing constant data. For example, a catalog can store a list of employees, goods, vendors, or customers.
  • CFL file extension

    • A file extension for auxiliary 1C:Enterprise files. These files are used for management of simultaneous user access in the file mode. They have zero size and they are not deleted on closing 1C:Enterprise.
  • Chart of accounts

    • An applied object describing a collection of accounts used for aggregating corporate business data. It is used in bookkeeping.
  • Chart of calculation types

    • An applied object that is intended for storing calculation types.
  • Chart of characteristic types

    • An applied object that is intended for storing characteristic types. A characteristic type is an additional attribute that a user can assign to a database object and then specify its value. For example, color=blue or size=L.
  • Choice form

    • A form that is intended for selecting a single element.
  • Client application

    • A program that runs on a client computer and facilitates user interaction with the system, as opposed to other system components (programs and working processes), which are intended solely for program interaction with other parts of the system or with other program objects. 1C:Enterprise includes three client applications: thick client, thin client, and web client.
  • Client/server mode

    • The 1C:Enterprise operation mode intended for use in work groups or enterprise-wide. It includes the following integrated parts: a server cluster (part of 1C:Enterprise), a client application (part of 1C:Enterprise), and a third-party DBMS.
  • Command

    • 1. An action that a user can perform in the application. 

      2. A configuration object that is intended for describing actions available to users.
  • Command interface

    • A part of user interface that executes commands and performs navigation through the application.
  • Command module

    • A configuration object that describes the algorithm executed by a command in 1C:Enterprise script.
  • Common attribute

    • A configuration object that is intended for:
      • Switching the configuration to data sharing mode.
      • Solving specialized technological tasks, which are not related to the business logic of specific configuration objects.
  • Common command

    • A command that is not related to a specific configuration object. Common commands are used for performing actions that affect the entire configuration, or for actions with data stored in multiple configuration objects of different types.
  • Common form

    • A form that is not related to a specific configuration object. It is used for processing data that is not specific to a single configuration object.
  • Common module

    • A module that contains procedures and functions that can be called from any other configuration module.
  • Configuration

    • An application that is created in Designer and executed by the platform. The basis of the configuration is the configuration object structure, which is described using visual development tools. Object details and their interrelations are specified in object properties, and specific algorithms are described in 1C:Enterprise script. 

      "Configuration" is a synonim of "applied solution", which is used when talking about technological tasks from administrator's or developer's point of view.
  • Configuration object

    • A part of configuration. A configuration consists of objects. When a developer creates a configuration, they add objects based on standard prototypes offered by the platform. Then they specify object properties and describe algorithms of their functioning in 1C:Enterprise script. Configuration objects are grouped by their prototypes. They can have hierarchical structure, and they can have subodinate configuration objects.
  • Configuration tree

    • A tree-like structure that describes the hierarchy of configuration objects.
  • Constant

    • An applied object intended to store a single value that never changes or changes in rare occasions, such as a company name.
  • Data composition schema

    • The main element of the data composition system. It describes where data is taken from and how it is grouped. A single data composition schema allows creation of different reports based on different composition system settings.
  • Data composition system

    • A declarative description tool that is primarily intended for report generation. It facilitates displaying data that has complex structure and includes sets of tables and charts.
  • Data exchange

    • A set of functionalities that allows offline data exchange between 1C:Enterprise infobases or with external applications. Includes the following functionalities: 
      • Universal data exchange: data exchange with any system, registration of data changes, XML serialization, management of exchange messages (including acknowledgements and resolving collisions).
      • Distributed infobase functionality: data exchange (as in universal data exchange) between nodes that have identical configurations, automatic configuration synchronization.
  • Data processor

    • An applied object that is intended for changing data stored in the system. For example, you can use it for deleting obsolete data, importing data from third-party systems, and so on.
  • Data separation

    • The functionality that allows to divide an infobase into areas, each area available to a certain user group only. Still, data storage and processing in all areas are performed by the same configuration. An example of using this functionality is an applied solution that provides accounting service to multiple companies.
  • Data set of data composition schema

    • A part of data composition schema. It describes which fields can be obtained and from what sources, and how they can be used.
  • Database

    • A logical concept, a part of infobase used for storage of the business area data and supported by the configuration. A database cannot exist separately from the infobase.
  • Database object

    • A logical unit of data storage in a database. It represents an entity that exists in real life as an object, creature, or concept, but not as a set of values. Examples of database objects are Company and Employee. Each database object has a unique ID that is stored in the Ref field of the object.
  • Debugger

    • A part of Designer that allows debugging module scripts, track the order of script operator execution, view variable values, and so on. It is located in the Debug menu of Designer.
  • Dependency by base period

    • Calculation register functionality that allows obtaining the base value for a specific calculation type record. This value is a number that affects the calculation result. If the current calculation type depends on other calculation types by base period, the results of these other calculations affect the base value.
  • Designer

    • A part of the platform, the environment for applied solution development.
  • Designer mode

    • The operation mode of the system. This mode allows applied solution development and infobase administration. 

      See also: 1C:Enterprise mode.
  • Desktop

    • A standard element of the applied solution command interface. A user always starts their work in the application from the desktop. The desktop contains commonly used documents, reports, catalogs, and so on.
  • Developer

    • A person who creates or modifies configurations.
  • Dimension (of a register)

    • Each register dimension represents anaccounting slice. For example, a register that stores the item quantities in warehouses can have "Item" and "Warehouse" dimensions. This allows retrieving the quantities of different items in a single warehouse (the "Warehouse" slice"), the quantities of a specific item in different warehouses (the "Item" slice), or the quantity of specific item in a specific warehouses (both accounting slices are applied).
  • Displacement by action period

    • Calculation register functionality that allows calculation of actual action period for a calculation type record (based on the analysis of other calculation type records that displace the current calculation type by action period). In general, the actual action period of a calculation type record (calculated by the platform) is a set of periods, which is a subset of the action period of the calculation type record (defined by the user).
  • Displacing calculation type

    • A calculation type that displaces the current calculation type by action period. For example, sick leave calculation type serves as a displacing one for the salary calculation type because employees do not get regular salary during their sick leaves.
  • Distributed infobase

    • An information system that consists of multiple 1C:Enterprise infobases (nodes), which have identical configurations and exchange data in offline mode. It has a strict hierarchical structure and a single master node. It uses the universal data exchange mechanism to ensure high flexibility of exchange schemes (including exchange with heterogeneous systems).
  • Document

    • An applied object intended for storing business data or events related to the enterprise business. Examples of documents are bills, receipts, invoices, hiring orders, and so on.
  • Document journal

    • A configuration object that allows viewing documents of multiple types.
  • Document register records

    • Records in registers that reflect the changes produced by a document. The records are usually created when the document is posted.
  • Enumeration

    • An applied object intended for storing value sets that are independent from the applied solution point of view. For example, VAT rates (0, 10, or 18%) or order statuses ("Confirmed", "Ready for shipment", "Closed"). The configuration script handles each of these values according to a specific algorithm. Since these values are described in a configuration object, they cannot be changed from 1C:Enterprise script, but their visual representation for users can be changed at any time.
  • Event

    • Situations (known beforehand) that take place in the process of application operation. Events allow developers to alter default platform behavior. When an event occurs, the platform can execute a developer-created algorithm, which is written in 1C:Enterprise script and located in the event handler procedure.
  • Event handler

    • A 1C:Enterprise script procedure that is executed when events of configuration objects take place.
  • Exchange plan

    • An applied object that is used in data exchange scenarios. It is intended for storing information about nodes and data that participate in the exchange. It also defines whether shared infobases are used in the exchange.
  • External connection

    • A method of connection to an infobase in order to access 1C:Enterprise data for external applications, which uses the COM technology.
  • External connection module

    • The module that contains event handling procedures executed on application startup and on exit from the application in the external connection (COM connection) mode.
  • External data processor

    • A data processor that is not a part of configuration. It is implemented as an .epf file.
  • External report

    • A report that is not a part of configuration. It is implemented as an .erf file.
  • Extra dimension type

    • An account characteristic used in analytical accounting.
  • File mode

    • The 1C:Enterprise operation mode intended for a single user or a small group of users in a local network. In this mode all infobase data (configuration, database, and administrative data) is stored in a single file—a file database. The database is managed by a proprietary 1C DBMS, which is included in the platform. The file mode does not use a server cluster; all data processing is performed on client computers or on a web server computer.
  • Folder

    • An applied object element that can only exist in hierarchical catalogs and hierarchical charts of characteristic types. It is intended for grouping other elements of these objects.
  • Folder choice form

    • A configuration object that is intended for selecting an element of folder type.
  • Folder form

    • A configuration object that is intended for displaying and editing elements of folder type.
  • Form

    • A unit of user interface development and implementation. It is a set of elements located in a single window and intended for solving a single specific task.
  • Form element

    • A user interface element that provides interaction with user. It can display data, serve for data input or editing, or simply be a part of form design.
  • Form module

    • A module that contains form event hadlers and form elements.
  • Functional options

    • A configuration object intended for storing an applied solution feature that can be turned on/off at the deployment stage without the need to make changes in the configuration.
  • Independent information register

    • An information register that is not subordinate to a recorder.
  • Infobase

    • A logically integral system that includes a configuration, a database, and data required for administration.
  • Information panel

    • A standard element of the applied solutioin command interface.  It is mostly intended for displaying information about the last actions performed in the application.
  • Information register

    • An applied object that is intended for storing  arbitrary multidimensional data. A time dimension is available. For example, an information register can store currency exchange rates by currency, or a price list by item and by price type.
  • Leading calculation type

    • A calculation type whose result indirectly affects the current calculation type. If the result of the leading calculation type changes, it forces the recalculation of the current calculation. 

      For example, if employees receive a bonus based on their salary and absence periods, the absence and salary calculation types serve as leading ones for the bonus calculation type.
  • List form

    • A form that is intended for viewing lists of data elements. For example, a list form can display a list of items.
  • Managed application mode

    • The mode where managed command interface and managed forms are used for working with the applied solution. 

  • Managed application module

    • The module that contains event handling procedures executed on application startup and on exit from the application in the managed mode. Also, this module can contain declarations of variables that are stored on the client during application execution.
  • Mobile 1C:Enterprise platform

    • The generic name for the 1C:Enterprise mobile application technology. Includes the mobile platform itself and the methodology for creating and publishing mobile applications.
  • Mobile application

    • 1. An applied solution that runs with the mobile platform on a mobile device.

      2. A configuration developed in compliance with mobile platform requirements. It can run both on mobile devices (with the mobile platform) and on desktop computers (with 1C:Enterprise 8).

      3. A file intended for publishing in the application store for further download to mobile devices. It includes the mobile platform for end users, one or several mobile applications, and some additional files (icons, logos, and so on). Such files are created with help of the Mobile Application Wizard.
  • Mobile Application Wizard

    • An external data processor intended for building a mobile application. It is included in the mobile platform distribution kit. The file name is MobileAppWizard.epf.
  • Mobile device

    • A smartphone or a tablet computer running iOS2 or Android operating system.
  • Mobile platform

    • The mobile application execution environment.
        
      It can run on iOS and Android operating systems. It has a number of limitations compared to 1C:Enterprise platform:
      • some configuration object classes are not available;
      • query language and data composition system are not available;
      • distributed infobase mechanism is not available;
      •  the selection of form elements is limited;
      •  the Desktop contains a single form;
      •  step-by-step debugging is not available;
      •  and some other limitations. 

      Two versions of the mobile platform are available:
      • mobile platform for developers, which is used for the development, debugging, and testing of mobile applications;
      • mobile platform for end users, which is used for building mobile applications.
  • Mobile platform for developers

    • The mobile platform version used for the development, debugging, and testing of mobile applications. 

      It features download of mobile applications published on a web server, and automatic restart of a mobile application when an update is available.
  • Mobile platform for end users

    • The mobile platform version used for building mobile applications.

      It does not feature downloading mobile applications or their updates from web servers, but allows creation of infobases on mobile devices based on available mobile application templates.
  • MobileAppWizard.epf

    • The file name of the Mobile Application Wizard external data processor.
  • Module

    • A part of configuration intended for storing 1C:Enterprise script listings. The configuration includes modules of various types. They can belong to specific configuration objects (for example, form modules or object modules) or to the entire configuration (for example, common modules or the managed application module).
  • Module context

    • The assortment of 1C:Enterprise script objects, variables, properties, and methods available within a module.
  • Navigation panel

    • A standard element of the applied solution command interface. It serves as section contents and allows navigation within the section.
  • Object

    • This term can mean one of the following: configuration object, database object, or 1C:Enterprise script object.
  • Object manager

    • A 1C:Enterprise script object that is intended for working with data of a specific configuration object (for example, for a  catalog object this includes searching for catalog elements, adding elements and groups of elements, and so on).
  • Object manager module

    • A module that handles object manager events and extends object manager functionality by export procedures and functions.
  • Object module

    • A module that handles events related to a specific data element of a configuration object (i.e. events related to an infobase object).
  • OpenID Authentication

    • One of the authentication types supported by 1C:Enterprise authentication mechanism. In this case, authentication is performed by an external OpenID provider.

      OpenID authentication offers an advantage over 1C:Enterprise authentication for users that work with a large number of infobases. With 1C:Enterprise authentication, users provide their name and password every time they connect to an infobase. With OpenID authentication, they only provide the name and password once, during the first connection to the infobase. Then the OpenID provider remembers the user and authenticates then automatically.

  • Ordinary application mode

    • The mode where the interface of earlier 1C:Enterprise versions is used for working with the applied solution. This interface supports the thick client only. It does not support automatic interface changes based on roles or functional options.
  • Owner

    • A term that describes subordination relationships between database objects. 

      For example, a configuration includes catalogs named Cities and Streets. Each city has its own list of streets. New York city (an element of the Cities catalog) is the owner of streets Broadway and 1st Avenue (elements of the Streets catalog). Washington DC city is the owner of streets Western Avenue, Eastern Avenue, and Southern Avenue. 

      Sometimes this term is used for describing the data structures where owners are stored. For example, "The Cities catalog is the owner of the Streets catalog". But this usage is not accurate and is considered developer slang.
  • Periodic information register

    • An information register that includes a time dimension. It stores data dimensions sliced by time.
  • Platform

    • A synonim for 1C:Enterprise platform. This synonim can be used when the context obviously refers to 1C:Enterprise platform.
  • Point in time

    • A combination of date, time and a reference to a database object. This concept is intended to explicitly identify the order of database objects in time.
  • Posting

    • The procedure of updating accounting records initiated by a document (creation of register records is a common example). An unposted document is considered a "draft", while a posted one is a fully valid document with its data reflected in the accounting records.
  • Program

    • A synonim for "applied solution". It is rarely used because it does not exactly match the meaning of "applied solution".
  • Query

    • A 1C:Enterprise script object that allows reading infobase data according to a specific instruction (query text).
  • Query language

    • A database query language implemented in the 1C platform. It is a subset of the SQL language, but with many extensions. It allows retrieving complex data selections with specific grouping and sorting. It offers the options to calculate intermediate and overall totals, to limit the number or type of records, and so on.
  • Real-time posting

    • Posting a document in real time, at the moment when a business event occurs. In case of intensive multiuser work real-time posting requires performing checks to avoid collisions. For example, warehouse balance is usually checked during real-time posting in order to avoid selling the same item to multiple customers.
  • Recalculation

    • A part of a calculation register that is intended for monitoring which records are no longer valid due to "displacement by base period" and "displacement by action period" rules. Such records are subject to recalculation.
  • Record form

    • A form that is intended for displaying and editing register data.
  • Record key

    • A set of record fields that is used to ensure the uniqueness of register records. A register cannot contain two records with identical values in all key fields. Record keys are also used for record identification (for example, if you need to find a specific list item).
  • Record user action log mode

    • A client application mode that allows writing to the user action log. You can start an application in this mode by:
      • running a command in Designer (in the Tools menu);
      • running the application from the command line with the /UILogRecorder parameter.
  • Recorder

    • A document that is the owner of register records.
  • Register

    • This term can mean one of the following: accounting register, accumulation register, calculation register, or information register.
  • Register records

    • An element of register data. It is a set of fields with their values.
  • Registration period

    • A date that defines which period the calculation type record belongs to.
  • Regular posting

    • Posting a document to register the accounting changes that occurred in the past. This kind of posting does not require any checks because it simply registers a past event.
  • Report

    • An applied object that is intended for displaying, viewing, and printing data in user-friendly format.
  • Resource (of data composition schema)

    • A field whose value is calculated by a user-defined function during report generation.
  • Resource (of information register)

    • A field whose value is used for calculating register totals. The function used for calculating the totals depends on the register nature. For example, in an accumulation register this function is a sum, while a calculation register uses a more complex function.
  • Role

    • An applied object that is intended for describing the set of allowed actions (rights). Each user of an applied solution is assigned one or several roles. Roles are also used for customizing visibility of data in the interface.
  • Scheduled job

    • An applied object that is intended for scheduled execution of 1C:Enterprise script procedures.
  • Sections panel

    • A standard element of the applied solution command interface. It displays high-level application structure and allows switching between application sections.
  • Session module

    • The module that contains the handler of the session parameter setting event.
  • Settings (of data composition system)

    • A part of data composition system. It describes report layout and specifies the list of data that is retrieved according to a data composition scheme. Applying different settings to a single data composition scheme results in generation of different reports.
  • Settings storage

    • A configuration object that is intended for creating custom settings storage functionalities in cases when standard functionalities do not suffice.
  • Standard attribute

    • A configuration object attribute that is created by the platform. Standard attributes have predefined names. For example, Ref, Parent, Code, and so on.
  • Subsystem

    • A configuration object that is used for building the command interface of the applied solution, as well as for visual formatting of the application functionality and help files into large and small blocks.
  • Syntax Assistant

    • A development assistance tool. This tool provides quick help on 1C:Enterprise script syntax during the creation of the programming code. It includes examples of syntactic constructions that can be added to modules by simple drag-and-drop. It is a part of Designer.
  • Tabular section

    • A part of many applied objects. It is intended for storing data that has the same structure for each element of the applied object, but the amount of data varies between elements. For example, the Employees catalog can have a tabular section named Family. All family members have the same fields: full name and  degree of relationship. But the number of family members can vary.
  • Task

    • An applied object intended for storing user assignments. It describes how assignments are shared between employees (taking the organizational structure into account). Tasks are closely related to business processes.
  • Technological log

    • The log that is intended for analysis of technological problems and abnormal terminations of the system.

      It allows registering data from all 1C:Enterprise applications running on the computer, as well as saving this data to a set of text files.
  • Template

    • A configuration object intended to store various forms of data presentation. It can also store auxiliary data used by some configuration objects or by the entire applied solution. For example, a text or spreadsheet document, a chart, binary data, and so on.
  • Test

    • A program written in 1C:Enterprise script that describes interactive actions performed by the test client. Additionally, a test can compare the actual results of the performed actions against the expected results.
  • Test client

    • A client application that emulates interactive user actions included in the test. 

      Any client application except Designer can run as a test client. You can start a test client :
      • from the command line with the /TESTCLIENT parameter;
      • from Designer with the corresponding startup option.
  • Test manager

    • A client application that is started for performing a test or for managing the user action log. 

      You can only use the thin and thick clients to run test managers. You can start a test manager:

      • from the command line with the /TESTMANAGER parameter;
      • from Designer with the corresponding startup option.
  • Thick client

    • A client application that can run both in 1C:Enterprise mode and in Designer mode. Unlike other client applications, it does not support connections to infobases over the Internet and requires a significant amount of resources to run.
  • Thin client

    • A client application that supports connections to infobases both in the local network and over the Internet. It can only run in 1C:Enterprise mode. Unlike the web client, it must be installed on the client computer.
  • Turnover register

    • An accumulation register that only accumulates resource changes (turnovers) and ignores resource balances.
  • User

    • 1. A person who works with applied solutions in 1C:Enterprise mode. 

      2. An account in the system that has a set of rights, as well as other properties.
  • User action log

    • An XML file that contains information about user activities performed either manually or during automated testing. 

      Recording to the log is only available when the application is running in the record user action log mode. The recording can be performed by using interactive commands, or initiated by a test manager.
  • Web client

    • A client application that supports connections to infobases over the Internet. It can only run in 1C:Enterprise mode. It runs in a browser and does not require installation on a client computer.
  • Web service

    • A configuration object intended for describing web services provided by 1C:Enterprise applied solution.
  • XDTO

    • A platform feature intended for integration with third-party systems. It is a mechanism of object modeling for data described by an XML schema.