Skip to content

Update a configuration by creating a new version

If you want to update an existing project configuration, you can create a new version of it. A typical use case is to fix a configuration bug or change an encryption key.

Requirements

  • You have the configuration file in the editable BALCFG format.

    Why?

    Deployable BEC/BEC2 files cannot be edited. Likewise, it's not possible to read out and edit a reader's configuration. Access to a reader's configuration is limited to support purposes and only covers non-security-relevant data.

    What can I do if I don't have the BALCFG file?

    First, identify the configuration name and version. You can find this information e.g. in BALTECH ID-engine Explorer. Name and version also match the name of the corresponding BALCFG file.

    With that file name, you can check back with the provider of the configuration. If you bought the reader with a pre-existing configuration, please contact us to request a new version.

  • The configuration was not created by BALTECH.

    Why?

    For configurations created by BALTECH (indicated by this naming scheme), only we can create new versions. Please contact us to request one.

Create new configuration version

  1. Open the latest version of BALTECH ConfigEditor.
    Download it here as part of BALTECH ToolSuite.

  2. Open the BALCFG file of the configuration you want to create a new version of.

  3. Click Create a New Version.

    Screenshot: Create New Version button in BALTECH ConfigEditor

  4. A new draft version is created.

    Screenshot: New configuration version created in BALTECH ConfigEditor

  5. Make the required changes to the configuration.

    • To view and edit the settings in an existing component, select it in the Configuration Components list at the top right.
    • To delete an existing component, select it and click the Minus icon.
    • To add a new component, click the Plus icon.

    For configurations created with ConfigEditor v5.00 or above, you'll be notified if added components are incompatible with existing ones, or if you've deleted a required component.

  6. In Administrative Information, describe the Changes in This Version.

    Screenshot: Description of changes for a new configuration version created in BALTECH ConfigEditor

  7. Click File > Save Draft.

The new version will be saved as a draft. Once you've tested your changes and are happy with them, release the new version to export a deployable file. You can deploy this file to your readers without having to remove the previous version.

The description of changes will be added to the Change Log, and the BALCFG file's name changes from -DRAFT to -<version number>.

Screenshot: Changelog for previous configuration versions in BALTECH ConfigEditor   Screenshot: Automated versioning of configurations in BALTECH ConfigEditor

Keep the default versioning

The version information that is automatically added to BALCFG file names helps you keep track of your versions: -DRAFT files are work in progress, whereas files with version numbers have a defined state. By sticking to this versioning, you avoid confusion as you'll never end up with 2 competing versions having the same version number.

Title