FI Finnish
SE Swedish
FR French
PL Polish
DE German
US English (US)

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

English (US)
FI Finnish
SE Swedish
FR French
PL Polish
DE German
US English (US)
  • Log in
  • Home
  • Platform
  • ESM
  • Other Technical ESM Documentation
  • Handler Documentation

Handler - IDGenerator

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Service Management
    Matrix42 Professional Solution Matrix42 Core Solution Enterprise Service Management Matrix42 Intelligence
  • Identity Governance and Administration (IGA)
    IGA overview IGA solution library
  • Platform
    ESM ESS2 ESS Efecte Chat for Service Management Integrations Add-ons
  • Release Notes for M42 Professional, IGA, Conversational AI
    2026.1 2025.3 2025.2 2025.1 2024.2 2024.1 2023.4 2023.3 2023.2 2023.1 2022.4 2022.3 Release Information and Policies
  • Other Material
    Terms & Documentation Guidelines Accessibility Statements
  • Services
+ More
    • Service Management

    • Identity Governance and Administration (IGA)

    • Platform

    • Release Notes for M42 Professional, IGA, Conversational AI

    • Other Material

    • Services

Handler - IDGenerator

IDGenerator handler generates an ID for the attribute automatically.

For this handler to function as intended, parent attribute should be set unique.

 

The following tables provide information on the attribute settings and metadata requirements for IDGenerator handler.

Table 1. Attribute Settings

Handler name Datatype
IDGenerator String or Number

This handler doesn't require any mandatory metadata configuration.

Table 2. Optional Attribute Metadata

Name Value Description
Digits Integer

Minimum number of digits. The generated ID is zero padded, if needed.

Notice that the number you defined specifies the minimum number of digits an ID consist of, yet the minimum does not limit the maximum. For example, if the value is 4, the first ID is 0001 and the series continues normally after 9999 although next number consists of 5 digits.

template_code prefix

In the Name field, enter a code of the template, whose ID you want to endow with a prefix. The code must be identical to the existing template code.

In the Value field, enter the prefix you want to attach to the ID.

For example, if you give a COM prefix for a computer template, each new computer template's ID includes the prefix COM in the beginning of the ID.

If you set template code as folder metadata, IDGenerator uses it as prefix for data cards in that folder.

Notice that if the attribute data type is number, you cannot use the prefixes!

Replace value with ID String

If the value of the IDGenerator is the same as the value of Replace value with ID metadata, new id is given to data card. All other values are saved as they are given.

You may want to use the Replace value with ID metadata, for instance, in data imports to prevent the manually created data from being replaced with the imported data.

Separate template ID series

true/false (separateTemplateIdSeries)

 

Denoted templates' ID series are separated according to the given prefixes. Notice that in order to enable the feature, you must define each template whose ID series you want to separate by their individual template code and by a prefix.

Separate template ID series metadata enables giving the same ID number with different prefixes to several templates; for example, COM0001 to a computer template and DISP0001 to a display template.

(For backward compatibility, value separateTemplateIdSeries is also accepted, meaning same as true.)

Table 3. Automatically Created Attribute Metadata

Name Description
currentID Metadata will be generated and activated automatically after the first data card including the handler is created. Thus do not insert it manually. It is also recommended not to change the generated value.
currentID_ template_code

Metadata will be generated and activated automatically if the Separate template ID series metadata is defined.

Thus do not insert it manually. It is also recommended not to change the generated value.

The following metadata settings are obsolete:

  • Generate automatically (generateAutomatically) is always true.
  • Generate when saving (generateWhenSaving) is always true.
  • Use generate button (hasGenerateButton) is always false.
  • Unchangeable (unchangeable) is always false.
  • Override prefix from attribute is no longer supported.
 

 

handler idgenerator

Was this article helpful?

Yes
No
Give feedback about this article

Table of Contents

Related Articles

  • Overview of the Handlers
  • EQL Editor
  • Attribute Metadata - ShowCode
  • Attribute Metadata - PrintTemplateName
  • Attribute Metadata - ReferenceSearchFilter

Copyright 2026 – Matrix42 Professional.

Matrix42 homepage


Knowledge Base Software powered by Helpjuice

0
0
Expand