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
  • ESM Admin Manual
  • Template Management in ESM

Template Transformations

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

Template Transformations

Transformations in the Efecte Service Management (ESM) platform enable the automation of data flow between different data cards, streamlining processes by copying values from attributes in a source data card to corresponding attributes in a target data card. This feature is highly flexible, allowing for transformations across any templates within the ESM system.

Key points regarding transformations include:

  • Data Type Compatibility: For a successful transformation, the data types of the source and target attributes must be compatible. This ensures that data is accurately and meaningfully transferred between different parts of the system.
  • Handling Static Attributes: Static attributes, which contain predefined list values, can be transformed based on their string values, even if the source and target attributes are not identical. During such transformations, if the target attribute does not have a corresponding string value, the result will be left empty. This flexibility allows for broader application of transformations across varying types of data fields.
  • Multiple Transformations: A single template can be configured to undergo multiple transformations to various other templates. This capability is particularly useful for escalating or branching out processes based on the data card's lifecycle. For instance, a Helpdesk ticket could be transformed into a Solution data card for resolving an issue, or into a software/hardware order to fulfill a request.

Transformations offer a powerful tool for automating and optimizing workflows within ESM, enabling administrators to efficiently manage data across different modules and templates. This functionality promotes operational efficiency by reducing manual data entry and ensuring consistent data across related processes.

Creating a Transformation

  1. Start with Templates: Navigate to the Templates section from the main menu and choose the template you intend to transform from within the folder tree.
  2. Initiate New Transformation: If it's your first time setting up a transformation for this template, "New" will be the only option under the Transformations dropdown. Select this to proceed.
  3. Choose Target Template: In the following screen, select your desired target template and save your choice. This action will take you to the Transformations view, where you can map attributes from the source to the target template:

Attribute Mapping

  • Ensure that the data types of the source and target attributes are compatible for the transformation to work. Static attributes can be directly transformed using their string values, even if the data types differ.
  • The system provides flexibility in transformations, allowing multiple attributes from one template to be mapped to different templates.
  • Note that certain restrictions apply based on the compatibility of attribute data types, with some requiring checks or transformations and others possibly leading to truncated data.

Compatibility Restrictions

The system outlines specific rules regarding which data types can be transformed into others, such as strings into dates or integers into strings. It’s crucial to refer to these guidelines to ensure the integrity of transformed data:

Target →

Source ↓

String

Integer

Float

Date

String

ok

check

check

check

Integer

ok

ok

ok

-

Float

ok

check/trn

ok

-

Date

ok

-

-

ok

Datetime

ok

-

-

trn

Text

trn

-

-

check

Reference

target name

-

-

-

Embedded reference

target name

-

-

-

External reference

target name

-

-

-

Back reference

target name

-

-

-

Target →

Source ↓

Text

Reference

Embedded reference

External reference

String

ok

-

-

check

Integer

ok

ok

-

-

Float

ok

check/trn

-

-

Date

ok

-

-

ok

Datetime

ok

-

-

trn

Text

trn

-

-

check

Reference

target name

-

-

-

Embedded reference

target name

-

-

-

External reference

target name

-

-

-

Back reference

target name

-

-

-

 

  • ok = source value can be transformed into target value.
  • check = source value must be valid.
  • trn = target value may be truncated .
  • target name = target name of referenced data card.

Special Conditions for Transformations

  • Attributes utilizing the Worklog handler are not supported in transformations.
  • When configuring the transformation, you'll need to specify a default folder for the newly transformed data cards.

Testing the Transformation

After configuring a transformation, it can be tested by opening a data card using the source template and selecting the Transform option. This will create a new data card in the target template with copied attribute values.

Advanced Transformation Settings

  • Metadata for Transformations: Administrators can configure transformations to open in new windows and to use the same source for every transform through specific metadata settings.
  • Multiple Data Card Transformation: It’s possible to create multiple copies of a data card through a single transformation action, with settings allowing up to 99 copies. 
    • This feature is enabled via metadata in multi-value reference attributes:

Considerations

  • Always check attribute compatibility and the impact of transformations across templates.
  • Be mindful of unique attributes in the target template to avoid conflicts during transformation.
  • The ability to transform depends on user permissions and the specific configuration of the source and target templates.

Transformations offer a powerful way to streamline workflows and automate the repurposing of data across different areas of the ESM system, enhancing efficiency and flexibility.

admin esm template transformation format conversions transformation settings

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Editing Template Properties
  • Template Creation
  • Deleting Templates, Classes, and Attributes
  • Importing, Exporting and Localizing Templates

Copyright 2026 – Matrix42 Professional.

Matrix42 homepage


Knowledge Base Software powered by Helpjuice

0
0
Expand