enablerr builder –
modelling instead of programming

The user does not really notice anything about the enablerr builder, unless he is interested in it. It is a separate application that is used to model functions and regulations. Modelled? Isn’t that what you call programming?

No-Code System

In the past, IT specialists used software development environments to make new features or adjustments to an ERP system. That was in the days when all changes had to be made in the software code.

enablerr works quite differently here. Instead of specific software code, we work with events. This is the reason why we speak of a no-code solution.

Events

Events are the core elements with which functions in the enablerr system are constructed. There are different types of these events. On the one hand, there are the types Business Logic and on the other hand those of the type Regulation.

Type Business Logic

In the business logic, we describe how events have to behave, what they have to react to and what they have to accomplish. They refer to the actual business cases that are mapped in the system. For example, recording hours, creating offers, maintaining the customer base, operating the online shop and much more.

Type Regulation

In the event Regulation, we define what rules look like. First of all, we think of the legal requirements imposed by the state. VAT rates, unemployment insurance deductions or threshold values that regulate whether the payroll report to the compensation fund must be made monthly or quarterly.
They can also be sectoral rules that define the maximum weekly working hours or the minimum wage. In the case of company guidelines, the amounts above which payments must be double-checked could be specified.

The Regulations events affect certain Business Logic events. For example, the amount of VAT does not change how a sales order is set up and executed in the enablerr. But it does influence the billing of services. If the tax rate changes, only the value of the VAT regulation event is adjusted. The other events remain unchanged. 

Autonomous events

It is important to know that our events function autonomously. And that is also the reason why we do not have to map rigid process chains that are so difficult to maintain over time. In contrast to other solutions, our events organise themselves autonomously into dynamic workflows.

Even with enablerr, the majority of tasks are processed sequentially, but there is often no need to follow a rigid sequence. The fact that many of us think that processes have to be followed rigidly has to do with the fact that the software has forced us to do so in the past (it could not do otherwise).

Methodological agility

To enable this event autonomy, we have developed a new method of describing, documenting and processing business cases. Thanks to this innovative approach, we are able to separate business logic from regulation. This is the prerequisite for our system flexibility. And the reason why our business logic plug-ins run unchanged in different countries, with different regulations (legal system).

Plug-ins

The events are stored, transported and exchanged in transport containers, which we call plug-ins. The hosting definitions, i.e. how and where your enablerr should run, are also stored in a plug-in.

With this we have the plug-in trio complete.