TechBlog - Messages with tag "Configuration extensions"

Module extensions

This feature is implemented in 1C:Enterprise version

In short, you can now use extensions to modify the modules of standard configurations and add new modules.

Or rather, now you can change any modules, with the exception of ordinary form modules:

  • Common modules
  • Object modules (object module, manager module, etc.) for all types of objects
  • Session module
  • Managed application module
  • External connection module
  • Command modules
  • Form modules
  • etc.

Please note that you were already able to modify managed form modules in the past, but now we have introduced some changes to this process.

For the simplicity sake, we will refer to the phrase “procedure/function” as “method”. Thus, all changes that you can implement in the modules can be divided into 4 groups:



Development of configuration extensions

This feature is implemented in 1C:Enterprise version

As we promised in the previous article, we are gradually expanding the functionality of configuration extensions and improving their applicability diagnostics.

Adding roles

In the past, it was possible to change roles of a standard configuration by adopting them and adding to them objects created in the extension. Now you can create roles in extensions.

We can see two major scenarios involving use of added roles. Firstly, they may be required to create atomic or complex sets of rights to the objects that the extension brings to the configuration (without any binding to the roles existing in the configuration).

Secondly, you can use them to create atomic or complex sets of rights to the configuration objects that take into account specifics of the functionality implemented in extensions.



Methods of integration with 1C:Enterprise applications

What are the most essential requirements for business applications? The following tasks are among the most important ones:

  • Ease of modification/adaptation of application logic for/to changing business objectives.
  • Ease of integration with other applications.

The solution to the first task in 1C:Enterprise was briefly described in "Customization and support" section of this article; then we described it in detail here. Today, we will talk about the second task - namely, integration.

Integration tasks

Integration tasks can be different. To solve some of them, all you need to do is just perform an interactive exchange of data - for example, to send a list of employees to a bank in order to process payroll cards. More complex tasks may require a fully automated data exchange, possibly with involving the business logic of the external system. There are tasks that are specialized, such as integration with external equipment (for example, retail equipment, mobile scanners, etc.), or with legacy or highly specialized systems (for example, RFID tag recognition systems). It is essential to choose the most suitable integration method for each task.



Customizing 1C:Enterprise applications

The demand for software customization (modification for specific user needs) is as old as the first invented software. It is virtually impossible to write an application that suits the specific needs of all users. Thus, adding the option to customize an application without developer assistance is an idea whose time has come. And it shines in business applications because business processes can significantly differ even in enterprises that belong within the same field of business.


Customization of source code

There are several customization strategies. If an application is delivered with its source code, the most obvious solution is editing the code. However, this can significantly impact future updates because merging the altered application with its new version obtained from a vendor can often be difficult, especially if the application is heavily customized.



Configuration extensions

We have brought about a brand new method of adapting applications for specific consumers: the extensions method.

What’s good about extensions?

Extensions offer a different strategy than the already existing one, which involves a change in standard configurations. The use of this new strategy will substantially facilitate the support of standard solutions adapted to the needs of a specific deployment, or a specific customer.