1c library of standard subsystems description. Library of standard subsystems. Log analysis

Library of standard subsystems (LSL) is a set of subsystems for configurations on the 1C:Enterprise platform that implement basic functionality and individual functional blocks. Let's try to understand in more detail what it is.

Why was BSP created?

The first version of the BSP was released by 1C back in 2010 for the 1C:Enterprise 8.2 platform. 1C suggests using this library (or its individual subsystems) as a basis for creating your own application solutions. Also, all standard products produced by 1C itself are based on BSP.

The use of uniform modules made it possible to achieve greater standardization of application solutions, and this in turn made it possible to reduce the time spent on studying them (by programmers, administrators, and end users).

For programmers developing application solutions from scratch, BSP allowed them to save a lot of time, because There is no need to independently develop the basic functional blocks included in the BSP. The development and testing was carried out by 1C for the programmer. The programmer now only needs to understand the already developed functionality and learn how to implement the BSP.

How is BSP distributed?

BSP is a configuration for the 1C:Enterprise platform. Moreover, the configuration is not an independent application solution, it is just a toolkit for the developer. The entire configuration or part of the subsystems can be used when developing application solutions.

The delivery of the BSP includes a demo base with an example of implementation. This demo database is available for review on the 1C website. You can read how you can access it in the article.

BSP is not for sale. The BSP distribution kit can be obtained free of charge if you have a subscription to information technology support (ITS). To use an application solution developed on the basis of the BSP, a subscription to the ITS is not required. Partners of 1C can also receive BSP for free.

Official documentation on BSP is located at https://its.1c.ru/db/bspdoc and is available if you have a subscription to ITS.

BSP composition

The BSP consists of many subsystems, which are divided into:

• independent. To implement it, it is enough to transfer all objects to the target configuration and display the objects in the interface. Examples of such subsystems: “Log Analysis”, “Currencies”, “Completing User Operations”.
• integrable. Designed for tight integration with other configuration objects. To implement such subsystems, additional settings must be made. Examples of such subsystems: “Object versioning”, “Filling objects”, “Prohibition of editing object details”.

Currently (July 2017), BSP version 2.4.2 is available, which supports the following functionality:

Specific subsystems will be described in more detail in separate articles.

Implementation of BSP

Before implementing a library of standard subsystems into your configuration, you need to determine the list of subsystems to be implemented. In the simplest case, all subsystems are implemented. Regardless of what functionality is needed, there are mandatory subsystems that are always implemented:

• Basic functionality;
• Updating the information security version;
• Users.

The general implementation scheme consists of the following stages:

1. Transfer of necessary metadata objects to the target configuration;
2. Setting up transferred objects;
3. Using BSP objects when developing new functionality.

To assist in the implementation of BSP, the library includes processing First Implementation of BSP.epf . It is located in the configuration template directory. In the processing there is a brief description of all subsystems and the interdependence of the subsystems on each other is determined.

To check the correctness of the BSP implementation, a report is located in the configuration template directory Checking the implementation of BSP.erf.

How to find out the version of the BSP application solution

There are several ways to find out which version of the BSP is used in a specific application solution:

• Programmatically: call a function StandardSubsystemsServer. Library version() ;
• Interactive: in the “Subsystem Versions” information register, look at the version value for the “StandardSubsystems” subsystem.

Print (Ctrl+P)

Instructions for implementing a library of standard subsystems

The library includes a set of universal functional subsystems,
intended for use in application solutions on the “1C: Enterprise 8.3” platform

Delivery files contains

1. 1Cv8.cf – library delivery file. Not intended to be created
information databases based on a template.
2. 1Cv8_demo.dt – demonstration base.
3. 1Cv8_demo.cf – demonstration database delivery file.

The first implementation of library subsystems in the configuration and updating the version of an already implemented library are noticeably different. After loading the 1Cv8.cf file into an empty configuration, you need to configure the library objects as described in section 2.2, otherwise a message will be displayed when running in enterprise mode

When I first implemented BSP, I used the 1Cv8_demo.cf file, where everything was already configured and loaded it into an empty configuration, and then enabled the ability to change the configuration and methodically deleted the added objects that I did not need in the 1Cv8_demo.cf configuration file and prepared myself another cf file that can be loaded into an empty one configuration without setting up migrated library objects.

In general, the implementation process consists of the following stages:
Stage 1. Transferring metadata objects from the library delivery file to the configuration.
Stage 2. Configuring migrated library objects.
Stage 3. Using library objects when developing a configuration.

All functional subsystems included in the library belong to the parent subsystem “Standard subsystems” in the tree of metadata objects of the configurator. Subsystems designed for configurations designed to work in the service model are subordinate to the “Working in the service model” subsystem.
For the task of initial implementation and subsequent updates of library versions in application solutions, the distribution kit includes a special tool - an implementation assistant (external processing First ImplementationBSP.epf).

Its functions include support for decision-making on the implementation of the library in the configuration, as well as automatic control of the actual result of the implementation. Since making decisions on implementation and monitoring their implementation does not require immersion in the technical details of the implementation, design, implementation and control can be performed by different specialists and at different points in time

Step 1 Transfer metadata objects from file
delivery of the library to the configuration.

First implementation

Step 1. To transfer library objects to your configuration during the first implementation, you need to select the menu command Configuration – Compare, merge with configuration from file in Configurator mode. In the dialog box, specify the library delivery file and confirm the request for support.

Step 2. In the window that opens for comparing and merging configurations, uncheck all the boxes, check the box “include the area of ​​subordinate subsystems” and mark the transferred objects using the command Actions – Mark by supplier configuration subsystems.

From the Standard subsystems group of subsystems, select:

• mandatory subsystems: Basic functionality, Information security version update, Users, Contact information. Note that when implementing the “Users” subsystem for use in the service model
  subsystem "Contact information"
• subsystems that need to be implemented in your configuration, for example, service subsystems, regulatory information and
  classifiers
• if the configuration is supposed to work in the service model, then you need to include additional subsystems that must be transferred to the configuration to work in the service model

Step 3. Additionally, you need to check or uncheck the boxes for individual library objects and their properties and select the merging mode Take from file (Actions – Set mode for all...) and click the Run button. In the window with a list of dependent objects, click Continue.
Step 4. After completing the comparison and merging, proceed to the second stage - setting up library objects. Depending on the number of subsystems being implemented, this step may take from one to several hours.

Updating the library version

This section describes the general scheme for updating to a new version of the library. Separate features of updating each specific version of the library are given in the accompanying document updateSSL.htm included in the library delivery. As a rule, when moving between editions, sub-editions and releases of a library (first,
second and third digits in the version number) additional update steps are required, and when moving between patch releases of the library (fourth digit
in the version number), as a rule, no additional actions are required. In rare cases, when additional steps are still necessary when updating to a patched library release, the corresponding instructions are contained not only in updateSSL.htm, but also in the readme.txt file in the Important section. To update the library version, select the menu command Configuration – Support – Update configuration. In the dialog box, select the Select update file option, set the path to the library delivery file and confirm the request for
updating the vendor configuration version.
Step 1. You must first prepare obsolete library metadata objects for removal from the configuration. To do this, in the window that opens for comparing and merging configurations, uncheck all the boxes next to metadata objects, then set the comparison and merging filter to the value Show those present only in the old supplier configuration in the New supplier configuration group<- Старая конфигурация поставщика, как указано на рисунке.

Next, mark all metadata objects with checkboxes, select the merging mode Take from new provider configuration (Actions – Set mode for all...) and click the Run button.
If there are references to obsolete library objects from other configuration objects or from other objects in the library itself, the Continue button is not available. You must manually clear all references from other configuration objects and proceed to step 2 (but references from library objects will be removed automatically in step 3).
If no references to outdated library objects were found and the Continue button was able to put the configuration into support, then you should cancel the support by returning to the original database configuration (menu Configuration – Database Configuration – Return to Database Configuration).
Step 2. Repeat the command Configuration – Support – Update configuration, specifying the path to the library delivery file in the Select update file option. In the window that opens for comparing and merging configurations, clear all the checkboxes and mark the transferred objects using the command Actions – Mark by subsystems of the new supplier configuration. From the “Standard subsystems” group of subsystems, select:
● mandatory subsystems;
● additional subsystems that must be transferred to the configuration to work in the service model;
● all previously implemented subsystems, as well as subsystems that additionally need to be implemented in your configuration;
● subsystems on which the above-mentioned subsystems depend,

Then check the boxes for transferring the same set of subsystems (metadata object “subsystem”), as well as the Administration subsystem (if it was implemented previously or is planned to be implemented) in the window for comparing and merging configurations.
Select the merging mode Take from the new supplier configuration (Actions – Set mode for all...).

Then you need to mark all obsolete library metadata objects for removal from the configuration. To do this, set the comparison and merging filter to the value Show those present only in the old supplier configuration in the New supplier configuration group<- Старая конфигурация поставщика, как указано на рисунке.

Next, check all metadata objects and click Run. In the window with a list of dependent objects, click the Continue button.
Step 3. After completing the comparison and merging, proceed to the second stage - setting up library objects.

As a rule, configurations in 1C are written for users. All configurations are different, but quite often different configurations use the same objects that differ slightly from each other. It is really difficult to imagine a configuration where such entities as items, counterparties, users, and currency would not appear. And some tasks are typical: the possibility of basic differentiation of rights, working with email, tasks for users, etc. But there is a configuration that makes the programmer’s work easier; it contains and structures the standard tasks that employers set for programmers.

If you have worked with different standard configurations from 1c, you will have noticed that they are basically quite similar, many basic functions are the same for all standard configurations. Also from the BSP you can add to your own configuration such standard directories as organizations, banks, a currency classifier and much more.

We will try to figure out which subsystems are responsible for what and how they are interconnected.

If you decide to use a BSP, this does not mean that you need to use all the subsystems that are included in it. The BSP includes a special implementation assistant, which helps to significantly save time when developing a new configuration. The assistant is designed as a step-by-step wizard, using which the developer specifies the subsystems that he needs, and the wizard will create a blank with which you can work in the future. In essence, we receive a template for a future configuration.

If we launch the BSP in thin client mode, we will see this window

At the initial stage, we are interested in the “Developer Tools” tab, with which we will launch the “BSP Implementation Assistant”

The skua itself looks like a step-by-step assistant.

At the first stage, we select the subsystems that we will need in the developed configuration.

For example, like this

After this, you need to specify the file in which we will save the settings. XML file format.

Then we move on to the second stage.

At the second stage, specify additional parameters for each of the selected subsystems.

After you have selected all the parameters, the system will check whether everything was selected correctly and offer different options for tracking errors

Or in this form:

In the following articles we will continue to study working with the library of standard subsystems.

" announced the release on December 21, 2010 of the new edition 1.1 of 1C: Library of Standard Subsystems 8.2 (BSP). Edition 1.1 is the next stage in the development of tools for the developer of application solutions on the 1C: Enterprise 8.2 platform.

Edition 1.1 of the BSP provides a set of universal functional subsystems, ready-made sections for user documentation and technology for developing application solutions on the 1C:Enterprise 8.2 platform. With the use of BSP, it becomes possible to quickly develop new configurations with ready-made basic functionality, as well as the inclusion of ready-made functional blocks in existing configurations. The use of BSP when developing application solutions on the 1C:Enterprise 8.2 platform will also make it possible to achieve greater standardization of configurations, which will reduce the time for studying and implementing application solutions due to their unification according to the set of standard subsystems used.

New in version 1.1 BSP

Edition 1.1 includes a number of new subsystems, some of the previously created functionality is separated into separate subsystems, significant changes have been made to some existing subsystems, and the BSP “Implementation Assistant” has been implemented.

The "Web services for working with files" subsystem provides work with attached files that are physically located in another information base (file library). Any configuration with the “Working with Files” subsystem, which is published as a web service, can act as a file library. The subsystem provides the user with a basic set of operations with files: viewing a list of attached files, adding new files, deleting files, and opening files for viewing.

Using the new “Interactions” subsystem in the configuration, planning, registration and ordering of interactions can be organized: email correspondence, calls and meetings. All interactions, as well as information about interaction contacts, are stored centrally in the information base. For example, this subsystem is actively used in edition 11 of the “Trade Management” configuration.

The "Change Prohibition Dates" subsystem allows you to block changes to any data (documents, register entries, directory elements, etc.) before a certain date. It is possible to configure both one common date for the entire information base as a whole, and several dates for sections and/or individual objects of accounting sections.

The "Attached Files" subsystem allows you to store (attach) files to arbitrary configuration objects. Unlike the “Working with Files” subsystem, this subsystem is aimed at an arbitrarily large number of different types of file owners without losing speed in conditions of restricting user access at the record level. In terms of functions and appearance, the subsystem is close to the “Working with Files” subsystem: collective editing of files, support for full-text search in attached files, electronic digital signature, encryption.

In the "IB Backup" subsystem for file information bases, the ability to perform on-demand backups, as well as setting up a schedule, is implemented. Built-in assistant for restoring an infobase from a copy. For the client-server mode of operation, a notification is provided about the need to configure backup using standard DBMS tools.

The "Electronic Digital Signature" subsystem provides the application developer with a software and user interface for working with cryptography tools: electronic digital signature and signature verification.

The following subsystem is highlighted as an independent one: “Group modification of objects”, which provides a universal service for group modification of properties and details of objects of arbitrary reference type (directories, documents, etc.), as well as the “File functions” subsystem. The "File Functions" subsystem is a technological subsystem that can only be used in conjunction with the "Working with Files" and/or "Attached Files" subsystems. It implements functions common to both subsystems and basic user interfaces for working with files, storing files in disk volumes, functions for supporting RIB and creating an initial image of the infobase.

The Core Functionality subsystem has a new programming interface for batch recording events from client code to the log, as well as for checking whether the log of certain types of events is enabled in the log. Added functions to check the correctness of regulated data (TIN, checkpoint, etc.).

New functions have appeared in the “Business Processes and Tasks” subsystem that significantly expand the scenarios for using business processes in configurations: stopping business processes, hierarchy of subordination of business processes and accepting tasks for execution.

For configurations with a small number of users, the Users subsystem provides a functional option that disables the configuration of user groups and external users in the configuration.

The "Data Exchange" subsystem provides data exchange developers with a new object unloading mode "Unload when necessary", as well as the ability to switch object unloading modes in the "1C:Enterprise" mode. In addition, the data exchange administrator can now configure all object mapping relationships that migrate between infobases, including those that were created by the administrator himself or formed automatically.

The "Working with Files" subsystem uses the standard capabilities of the "Electronic Digital Signature" subsystem. In addition, when scanning documents, it is now possible to adjust the compression level (for TIF), quality (for JPG) and the method of saving to PDF (using an external program).

In the "Access Control" subsystem, a mode for using a simplified interface for setting access rights has been added. This mode is intended for application solutions with a small number of users, each of whom has a unique set of rights and access restrictions. In addition, setting the access rights of users, user groups, external users or external user groups is now possible directly from the element forms of these objects. From the user rights settings form, a complete list of allowed actions (roles) is available, calculated based on the user’s membership in certain access groups. To obtain a complete picture of the rights of a user, user group, external user or group of external users, a detailed report has been developed. As an additional feature, the list of access group members now also displays its “implicit” members: members of user groups (external user groups), as well as user managers.

The subsystem "Individuals" implements checks for completing the series and document number of an individual (military ID, military ID of a reserve officer, diplomatic passport of a citizen of the Russian Federation, etc.).

Along with subsystems, BSP also offers separate methods for developing application solutions. In edition 1.1, the developer is provided with ready-made sections of documentation for inclusion in the description of the configuration developed on the basis of the BSP.

For initial implementation and subsequent updating of BSP versions in application solutions, edition 1.1 includes a special tool - “Implementation Assistant”. This assistant provides decision-making support for the implementation of the BSP in the configuration, as well as automatic control of the actual result of the implementation of the BSP. Since making decisions on the implementation of BSP and monitoring their implementation no longer requires “immersion” in the technical details of the implementation, design, implementation and control can be performed by different specialists and at different points in time.

How to migrate from the previous version

Edition 1.1 is provided to registered users of the 1C:Enterprise 8 system who have a valid subscription to information technology support (ITS).

To update the BSP to version 1.1, version 1.1.1 was released, compatible with platform version 8.2.13 and higher.

Version 1.1.1 of the BSP is published as part of the February 2011 release of the ITS, on the user support website http://users.v8.1c.ru/ and on the ITS website http://its.1c.ru/ (access to these sites only ITS subscribers have).

The general procedure for updating the configuration of an already used BSP to version 1.1.1 is given in the documentation included in the delivery of this version. Features of updating from previous versions 1.0.7, 1.0.6, beta version 1.0.5 and trial version 1.0.4 are described in the update.htm file, also included in the delivery of version 1.1.1.

To update BSP versions in application solutions, it is recommended to use the "Implementation Assistant", which is included in the distribution kit in the form of external processing.

Developer Toolkit "1C:Enterprise Library of Standard Subsystems" (BSP) provides a set of universal functional subsystems, ready-made sections for user documentation and technology for developing application solutions on the 1C:Enterprise platform. With the use of BSP, it becomes possible to quickly develop new configurations with ready-made basic functionality, as well as the inclusion of ready-made functional blocks in existing configurations. The use of BSP in the development of application solutions on the 1C:Enterprise platform also allows us to achieve greater standardization of configurations and reduce the time for studying and implementing application solutions due to their unification according to the set of standard subsystems used.

The subsystems included in the BSP cover such areas as administration of the information base, administration of program users, setting up access to information base data, maintaining various regulatory and reference information (address classifier, exchange rates, calendar charts, etc.). BSP provides basic user and program interfaces for working with tasks and business processes, attached files and electronic signatures, contact information, additional details and information, email messages, etc.

Subsystems can be used in the developed configuration either together or separately. From the point of view of implementation technology, all BSP subsystems can be divided into two categories:

• Subsystems implementing"independent functionality". They are implemented by simply transferring functionality (“implemented and forgotten”) and do not require significant additional settings.
• Integrated subsystems provide functionality intended for use in certain consumer configuration objects (the so-called “tight integration”). When implementing, it is necessary to determine the composition of consumer configuration objects for which functionality needs to be implemented, and then perform a certain number of additional settings, make changes to the code and forms of the selected objects.

Along with subsystems, BSP also offers separate methods for developing application solutions. The developer has ready-made sections at his disposal for inclusion in the user documentation for the application solution based on the BSP.

The library's capabilities are fully used in the application solutions themselves:

• and others.

For the task of initial implementation and subsequent updates of BSP versions, application solutions have a special tool - the implementation assistant. Its functions include support for decision-making on the implementation of the BSP in the configuration, as well as automatic monitoring of the actual result of the implementation of the BSP. Since making decisions on the implementation of BSP and monitoring their implementation does not require “immersion” in the technical details of the implementation, design, implementation and control can be carried out by different specialists and at different points in time.

Demo access

Demo configuration "Standard Subsystem Library"

This database is a complete application solution; it can be used as a real working system. The presented functionality, from an application point of view, is intended to demonstrate the configuration capabilities of the "Library of Standard Subsystems" and the "1C:Enterprise.3" platform.

Read more about the platform "1C:Enterprise.3".

Attention:

• Your browser's pop-up blocker must be disabled.
• Your browser settings must allow JavaScript and the use of Cookies.

Launch options

You can work with the demo configuration using a web client or thin client.

To connect to the infobase, select any user from the list. No passwords have been set.

Web client

The managed application web client only works in the following browsers:

• Microsoft Internet Explorer version 6.0, 7.0, 8.0 or 9.0 for Microsoft Windows. It is recommended to use version 7.0.
• Mozilla Firefox version 3.x or later for Microsoft Windows and Linux.
• Google Chrome version 12 for Microsoft Windows.
• Safari version 4.0.5 for MacOS X version 10.5 and higher.

Start online demo

• Normal connection
• GPRS connection

Thin client

To connect to the infobase using a thin client, you need to select the “Web server” connection option and specify the connection string.

If necessary, specify the option to use a proxy.

Realized opportunities

Administration of users and access rights

Shutting down users

• View and end active sessions in the program.
• Temporary blocking of users' work in the program, prohibition of routine tasks.

Users

• Maintaining a list of users working in the program.
• Maintaining a list of external users who have limited access to specialized workspaces provided in the program (for example, My Orders, Respondent Questionnaires, Application Forms, etc.).
• Setting up the rights of users and external users (when implemented together with the Access Control subsystem, it is carried out using the Access Control subsystem).
• Grouping of users (and external users).
• Clearing and copying settings for reports, forms, desktop, command interface sections, favorites, printing spreadsheet documents and other personal settings of users (and external users).

Access Control

• Individual and group configuration of user access rights using profiles and access groups.
• Setting up access rights restrictions at the record level - for individual information base data elements (directory elements, documents, register records, etc.).
• A report on the rights of the user or user group of interest.
• There are two options for implementation into an application solution - regular and simplified. The normal mode for setting access rights is designed for multi-user application solutions, in which, as a rule, group settings of rights are performed based on access groups. In simplified mode, rights are configured individually for each user. The second mode is intended for configurations with a small number of users, each of which has its own unique set of rights.

Administration and Maintenance Tools

• Reports on user activity, duration of routine tasks and critical entries in the log.

• Connecting additional (external) reports and processing to the program without making configuration changes.
• Linking additional reports and processing to specific types of objects or sections of the command interface.
• Routine execution of processing according to schedule.
• Tools for administering a list of additional reports and processing.

Program settings

• Ready-made workstations (panels) for the Administration section.
• Adjusting the composition of administration panels to the current operating mode of the program.

Configuration update

• Automatic configuration update (without opening the configurator) on demand, at a specified time in the future or when the program is terminated.
• Check and receive configuration updates via the Internet (on demand or scheduled).
• Update from a specified file on a local or network drive.
• Applying master configuration changes to the database configuration.

• Evaluation of the integral performance of the program using the APDEX method.
• Simplifies and automates the collection of information about the execution time of each key operation.
• Tools for analyzing measurement results.
• Automatic export of performance metrics.

Find and remove duplicate list elements.

Backup

• Saving backup copies of the file infobase on demand or according to a specified schedule.
• Restoring a file infobase from a copy.
• Notification about the need to configure backup (also in client-server mode).

Scheduled tasks

Listing and setting parameters of routine tasks (schedule, start, stop).

• Deleting objects marked for deletion with integrity control (checking references to deleted objects from other objects).
• Scheduled background deletion.

Managing totals and aggregates

• Administration of totals and aggregates of circulating accumulation registers.
• Regular execution of operations for transferring the total boundary, recalculating and updating aggregates (according to a schedule, when the program is completed).

Service subsystems

• Storing and viewing the history of changes to directories and documents (the user who made the changes, the time of the change and the nature of the change, accurate to the details of the object and the details of its tabular parts).
• Comparison of arbitrary versions of objects.
• View and rollback to a previously saved version of an object.

Group modification of objects

• Group modification of arbitrary details and tabular parts of program objects (directories, documents, etc.). The ability to change the values ​​of additional details and information, taking into account the rules preset in the program for prohibiting editing of object details.

No change date

• Blocking changes to any data (documents, register entries, directory elements, etc.) entered before a certain date.
• Flexible setting of one general change prohibition date for all program objects as a whole, or several dates for sections and/or individual objects of accounting sections.

• Electronic replacement of stickers on the edges of the monitor, which you can use without leaving your program window.
• Quick list of notes on your desktop, list of notes by subject, general list.
• Different colors and design of the text of notes, inserting pictures into notes.

• Support of the requirements of Law 152-FZ “On Personal Data”.
• Managing personal data access events (setting up event usage, obtaining the current state of event usage, preparing a program configuration form).
• Classification of personal data by area.
• Accounting for consent to the processing of personal data.

• Display various information (for example, advertising) when the program starts.

Contact Information

• Adding details for entering contact information to arbitrary directories and documents: postal addresses, email addresses, telephone numbers, etc.
• Automatic or manual verification of the correctness of addresses (when used together with the Address Classifier subsystem).
• Providing a classifier of countries of the world (OCSM).

• Entering personal reminders in the program for the right time.
• Linking reminders to arbitrary program objects.

Setting the order of elements

• Setting the order of elements of custom lists using the Up and Down buttons.

Seal

• A software interface and a ready-made workstation for generating printed forms of arbitrary program objects.
• Output of printed forms in the form of spreadsheet documents and office documents in Microsoft Word and OpenOffice.org Writer formats.
• Sending printed forms by email, saving to a computer or in attached files (when used together with the Attached Files subsystem).
• Connecting external printing forms, as well as printing external printing forms complete with the main printing forms (when used together with the Additional reports and processing subsystem).
• Printing a QR code image based on a given text string.

Full text search

Setting up and performing a full-text search for all data in the program.

Attached files

• Program and user interfaces for attaching files (attachments) to arbitrary program objects.
• Support for an arbitrary number of different types of file owners without loss of speed when restricting user access at the record level (RLS).
• Collective file editing, scanning, electronic signature and encryption.

Checking the legality of receiving updates

Software and user interfaces to confirm the legality of receiving a configuration update.

Properties

• Adding additional properties to arbitrary documents and reference books.
• Display property values ​​in any reports and dynamic lists.
• Separate storage of properties both in the program object itself (additional details) and outside the owner object in a special information register (additional information).
• The ability to set the same properties for different objects, mandatory properties, and other service capabilities.

• Displays information about the parent and child documents for the selected document, as well as the entire structure of their relationships.

Electronic signature

• Software and user interface for working with cryptography tools: electronic signature and signature verification.
• Sending applications for the issuance of a CEP certificate to the 1C:Enterprise Center and installing them on the computer.

Technological mechanisms and software interfaces

Basic functionality

• General-purpose procedures and functions for working with strings, with other data types, with a log, etc.
• Standard roles (Administration, Full rights, Thin client launch, etc.).
• Automatic tracking of renaming of metadata objects.
• Basic service capabilities of the program administrator (registration log, setting the title of the program window, etc.).

Prohibition of editing object details

• A software interface for checking the mandatory completion of some object details that determine the nature of the object (conventionally called “key” details).
• Prohibition of editing “key” details of recorded objects.
• Checking the possibility of changing “key” details by a user who has the rights to do so.

Updating the infobase version

• Performing initial filling and updating of infobase data when the configuration version changes.
• Display information about changes in the new configuration version.
• A programming interface for executing exclusive, online, and deferred update handlers.

Prefixing objects

• Automatic assignment of prefixes to objects taking into account program settings.
• Prefixation of objects in the context of infobases and Organization list elements.
• Program interface for re-prefixing lists and documents when the infobase prefix changes.

Working in a service model

• Includes a number of subsystems necessary for the configuration to work in the service model:
  • Support for data separation (selecting common classifiers and program settings that are used as a whole for the information base).
  • Sequential execution of tasks in different data areas to reduce the load on the 1C: Enterprise Enterprise server.
  • Transition from the local operating mode to the service model (and back) based on the mechanism for unloading and loading data areas via xml files.
  • Automatically create backup copies of data areas on a schedule.
• Integration of the configuration with other service components - the service manager and the supplied data service:
  • Messaging mechanism for guaranteed delivery of messages between different information systems.
  • Synchronization of lists and user rights in the service manager and in the application. Managing data areas from the service manager.
  • A technology for exchanging data between applications running in a service model, as well as with information databases installed locally on users’ computers.
• Offline work with the application in the service without a constant Internet connection:
  • The ability to work autonomously with the program in conditions of no Internet or low data transfer speed.
  • Possibility of collaboration via the Internet and offline for several users.
  • Possibility of consolidating information from different workstations operating autonomously.
  • Automatic release update of a configuration that works offline.
• It also includes a number of subsystems that are not intended for independent use. They must be included in the configuration only in conjunction with the corresponding main subsystem. For example, if the Currency subsystem is marked for implementation, you should also mark the Currency subsystem in the service model.

File functions

• Technological subsystem not intended for independent use; only in conjunction with the subsystems Attached files and/or Working with files.
• General functions and basic user interfaces for working with files, storing files in disk volumes, functions for supporting RIB and creating an initial image of the infobase.

Monitoring Center

• Collects anonymized statistics on configuration usage.
• Transfers anonymized statistics to a single quality control center.

Integration with other programs and subsystems

Loading data from a file

• Loading tabular data into arbitrary lists and tabular parts of documents.

Integration with Bukhfon

• The ability for Bukhfon infrastructure users to launch an application directly from the configuration.

Data exchange

• A software interface and ready-made workstations for organizing collaboration in a distributed information base and for synchronizing data with other programs.
• Data synchronization on demand and automatically according to a schedule.
• Connection through various communication channels: local or network directory, email, FTP resource or via the Internet (including data synchronization with applications in the cloud).
• Flexible configuration of data synchronization rules between programs, assistant for matching identical data.
• Tools for monitoring and diagnosing data synchronization.
• The ability to develop exchange plans using or without conversion rules, convenient debugging of event handlers for conversion rules in the configurator.
• Automatic update of the configuration of the RIB slave node (when used together with the Configuration Update subsystem).

Sending SMS

• Software interface for sending and checking the delivery status of SMS messages.

Receiving files from the Internet

• Program interface for receiving files from the Internet.
• Receiving a file from the network on the client.
• Saving files on the client computer, in the information database.
• Request and storage of proxy server parameters.

Working with email messages

• A software interface for sending and receiving email messages.
• Maintaining a list of email accounts.
• Basic user interface for sending messages.

Distribution of reports

• Distribution of reports and additional reports by email.
• Publishing reports on FTP, in network directories and in folders of the Working with Files subsystem.
• Run on a schedule or interactively.

Regulatory reference information and classifiers

Address classifier

• Storage and provision of an address classifier (FIAS) for use in other application subsystems.
• Entering and checking the correctness of addresses via the Internet using the vendor’s web service.
• Loading an address classifier into the program from the user section of the vendor’s website or from a specified directory (when working offline without a permanent Internet connection).

Banks

• Storage and provision of the RF Bank Classifier (BIC) for use in other application subsystems.
• Loading the Russian Bank Classifier (BIK) from the ITS disk and from the RBC website, automatically or on demand.

Currencies

• Storing and providing access to the list and exchange rates.
• Selecting currencies from the All-Russian Classifier (OKV).

Opening hours

• Storing information about calendar schedules used in the enterprise.

• Storing information about production calendars used at the enterprise.
• Receiving a date that will occur in a specified number of days according to the specified calendar and another program interface.

Organizations

• Maintaining the Organization's directory with contact information in the program.
• Template for developing an Organization directory in an applied configuration.

Working with counterparties

• Checking the details of counterparties according to the Federal Tax Service in the Counterparties list, documents and reports.
• Filling out the details of counterparties and creating a Dossier of the counterparty according to the Unified State Register of Legal Entities and the Unified State Register of Individual Entrepreneurs.

Application subsystems and user workstations

• Conducting surveys for external users of the program.
• Development of questionnaire templates and conducting surveys based on a list of respondents.
• Tools for analyzing survey results.

• Interactive input of tasks for program users.
• Informing users about their current tasks.
• Monitoring and control of task execution by stakeholders - authors and task coordinators.
• Basic functionality for developing custom business processes in a configuration.

Report options

• Collaborate with report options provided in the program and created by users.
• Quick access panel to report options.
• A universal report form with quick settings, sending reports by mail, setting up report mailings, autosum and other service capabilities.
• Software interface for fine-tuning the appearance of reports.

• Plan, record and organize interactions: emails, calls, meetings and SMS messages.
• Storing all interactions and their contacts in an information base.
• Working with the results of interactions.

• Collective editing of files in a hierarchical folder structure.
• Storing and providing access to file versions.
• Attaching files from the file system, creating files using a template, or receiving from a scanner.
• Electronic signature, encryption.

• Displaying a list of the user's current affairs on the desktop (new letters, tasks, requests, uncoordinated orders, etc.).

Product functionality update

Description of modifications and features of the new version

Version 2.3.5

Update announcement, trial version:

Version 2.3.5 includes the delivery of an international version of the library, which is intended for the development of localized solutions for the 1C:Enterprise system. The international version does not contain the national specifics of any country, and the inclusion of specifics for a particular country is carried out uniformly for any country. Development based on the international version is carried out in the Russian version of the built-in language of the 1C:Enterprise platform.

NEW IN VERSION 2.3.5:

• the “Working with Files” subsystem has been developed;
• a mechanism for outputting contextual reports has been implemented;
• in the Interactions subsystem, work with email attachments has been improved;
• the layout of the administration panels has been improved (the "Program Settings" subsystem);
• The software interface for working with contact information and electronic signatures has been expanded.

In order to simplify the first implementation and regularly update the BSP functionality in configurations in version 2.3.5:

• included in the delivery is a tool to reduce the labor intensity of updating configurations for corrective releases of the library;
• the autonomy of subsystems for the purpose of selective implementation has been significantly increased, and the basic (mandatory) part has been reduced;
• The implementation in the configuration of the subsystems “Filling Objects”, “Print”, “Additional Reports and Processing” has been unified.

A complete list of features of version 2.3.5 is presented in the UpdateSSL.htm file included in the library distribution.

Version 2.3.4 from 11/24/16

Version 2.3.4 is a development of edition 2.3 of the “Library of Standard Subsystems” toolkit, which is intended for developing configurations on the 1C:Enterprise platform version 8.3.8 and higher. In this case, the configuration property “Compatibility Mode” must be set to “Do not use”.

“1C:Enterprise Library of Standard Subsystems” (BSS) provides a set of universal functional subsystems, ready-made sections for user documentation and technology for developing application solutions on the 1C:Enterprise platform. With the use of BSP, it becomes possible to quickly develop new configurations with ready-made basic functionality, as well as the inclusion of ready-made functional blocks in existing configurations. The use of BSP in the development of application solutions on the 1C:Enterprise platform will also make it possible to achieve greater standardization of configurations, which will reduce the time for studying and implementing application solutions due to their unification according to the set of standard subsystems used.

The subsystems included in the BSP cover areas such as

• Administration of users and access rights;
• Administration and maintenance tools (installation of updates, backup, additional reports and processing, performance assessment, etc.);
• Service subsystems (object versioning, notes and reminders, printing, full-text search, attached files, electronic signature, etc.);
• Technological mechanisms and software interfaces (general-purpose procedures and functions, updating the information security version, working in the service model, etc.);
• Regulatory and reference information and classifiers (address classifier, banks, currencies, etc.);
• Integration with other programs and systems (data exchange, working with email messages, sending SMS, sending reports, etc.);
• Application subsystems and user workplaces (questionnaires, business processes and tasks, interactions, reporting options, etc.).

In total, the BSP includes 58 subsystems. The full composition of the subsystems, their purpose, implementation procedure and recommendations for use are given in the documentation for the library.

Together with subsystems, BSP also offers separate methods for developing application solutions, which are described in the documentation for the library. Using the BSP, it is much easier to develop configurations that meet all the requirements of the “System of standards and methods for developing configurations for the 1C:Enterprise platform”.

In addition, for administrators and specialists in the implementation of application solutions, external processing units are supplied as part of the BSP, which can be used autonomously without the BSP to solve a number of administrative and “repair” tasks: query console, group modification of objects, registration of changes on exchange plan nodes, hiding confidential information, etc.

How to migrate from the previous version

Edition 2.3 is provided to registered users of the 1C:Enterprise system who have a valid subscription to Information Technology Support ().

Version 2.3.4 is compatible with platform version 8.3.8 with compatibility mode disabled. The general procedure for updating the BSP subsystems used in configurations to version 2.3.4 is given in the documentation. Features of updating from previous versions are described in the updateSSL.htm file.

To update BSP versions in application solutions, it is recommended to use specialized tools included in the library distribution kit:

• External processing FirstImplementationBSP.epf – designed to simplify the process of first implementation of the library. Allows you to select subsystems for implementation taking into account their dependencies on each other, as well as remove code fragments of unused subsystems.

We are waiting for your assessments - we strive for you to find answers to your questions regarding the use of the software for your purposes. Write comments - we will try to answer how we can solve your problems.