AllowRepositoryAutomapping - System Parameter
The AllowRepositoryAutomapping System Parameter lets the Logging Service create and update Repository Model entities (BPMs, Integrations, Systems, and Services) from the Repository Binding data in your Log Events. It is off by default.
At a Glance
| Property | Value |
|---|---|
| Key | AllowRepositoryAutomapping |
| Data type | boolean |
| Default | false |
| Read by | Logging Service |
| Takes effect | Within about 15 seconds; no restart needed |
| Status | ✅ Active |
| Since | Nodinite 4.3.0.76 |
How It Works
With custom logging, for example through the Log API, a Log Event can carry the RepositoryBinding Context Option. When AllowRepositoryAutomapping is true, the Logging Service reads it when it processes or reprocesses the Log Event, and creates or updates the described Repository Model entities. BPM Binding is part of Repository Binding, so it also needs this parameter.
When the value is false, the Logging Service ignores Repository Binding data, and you maintain the Repository Model manually.
The structure of the RepositoryBinding data, with examples, is described on Repository Binding and BPM Binding.
Choosing a Value
- Set
truewhen your custom logging sends Repository Binding data and you want the Repository Model to follow what is actually logged. - Keep
falsewhen you maintain the Repository Model manually or through other tools, so Log Events can't change it.