Transform Settings

Transform configuration references to mapping configurations (defined in separate mapping files) that can be used to select and transform the input's objects and their properties. All the transform-related settings are grouped into a set of extensions. Each extension section in the configuration file is optional and can be repeated any number of times. These extensions are used to modify particular parts of an object and its properties.

The default configuration file contains the following transform extensions:

• Patterns 2D: Allows you to select, via Conditions, which type of graphical objects to amend so that tags can be associated or disassociated with graphical elements using the Group and Ungroup functions and add new Attributes to the grouped and ungrouped objects. For more information, see Patterns 2D.

• Base Mapping: Modifies the engineering data of a model’s objects present in the extracted data. For more information, see Base Mapping.

• Presentation Mapping: Adjusts the output graphics properties, such as materials and color. For more information, see Presentation Mapping.

• Text Mapping: Used in 2D drawings to customize textual objects visible in the drawing, either by varying the font that is used or mapping specific characters/text strings to alternative values. For more information, see Text Mapping.

• Rescale 2D Transformation: Enables you to adjust/scale the SVG graphics, OLE object resolution and line thickness. This may be needed when the drawing’s resolution is not matched with the resolution of the monitor or printer where the SVG will be viewed. For more information, see Rescale 2D.

• CSV Reporting: Exports the extracted input data from the extracted data in the form of a readable CSV file format. For more information, see Appendix A: Mapping Configuration.

  Notes:

• As a number of mapping configuration files can be associated to a project configuration, order of execution of these files is determined as follows:

  • When only one DefaultBaseMapping extension is added to the transform configuration, all the mapping entries from different mapping nodes are consolidated and applied on the extracted data at once.

  • When multiple DefaultBaseMapping extensions are added to the transform configuration, individual extensions are executed in order, independent of each other.

• Mappings applied as part of an extension are overridden by the other extension if conflicting mapping entries are present in its mapping configurations.

The Transform panel in the user interface presents the active project's transform settings as read-only content. The content has anchors linked on the special attribute locator that helps in navigating to the configuration file of an individual extension. When you run the project, it invokes the transformation extensions as configured in the configuration file and modifies the output. For more information about the transformation functions and available syntax, see Appendix A: Mapping Configuration.

To update transform settings:

1. Click the Transform panel in the Project Settings page to open the Transform details page.

   

2. Click Edit to open the settings in a Notepad to modify the default configuration settings relating to Transform.

3. If required, modify dependent mapping files by clicking on the anchor links placed in the main configuration view.

   Note: Settings are automatically saved upon saving and closing the Notepad session.

4. After all the settings have been saved successfully, click Run to process the input file(s).

   Notes:

• Any update in the configuration document must be saved before running the process.

• Set the tracking of changes provided by each Transform extension using annotations feature, as shown in the above XML configuration. For more information about annotations, see Appendix C: Tracking Changes in Data.

• A CSV Report that is defined in the Transformation configuration file can have its output path defined by the outputFolder parameter. This parameter is optional, and when it is not set, the CSV file is written to the EIWM location by default. The output folder must be in the File System, not an S3 Bucket nor an AVEVA Cloud Storage folder.

• For more information about handling system attributes, see Appendix H: Handling of System Attributes.