Appendix V: Transformations

This section illustrates the transformation to add converters available to the project team. The platform includes the template shown below. The project team must complete the required changes idempotently.

The following template is provided:

<?xml version="1.0" encoding="utf-8"?>

<configuration>

  <configSections>

    <!-- Common converter service configuration -->

    <section name="ConversionServer" type="Aras.ConversionFramework.ConversionServer.Configuration.ConversionServerConfigurationSection, Conversion.Base" />

    <sectionGroup name="ConverterSettings">

     <!-- Place here class configuration section definitions for converters -->

     <section name="ArasCadConverter" type="Aras.ConversionFramework.Converter.Hoops.Configuration.HoopsConverterConfiguration"/>

    </sectionGroup>

  </configSections>

  <ConversionServer>

    <InnovatorServer url="" />

    <Converters>

      <Converter name="Aras CAD to PDF Converter" type="Aras.ConversionFramework.Converter.Hoops.HoopsConverter,ArasCadConverter"/>

    </Converters>

  </ConversionServer>

  <ConverterSettings>

    <!-- Place here configuration sections for converters -->

    <ArasCadConverter>

      <Application converterPath="${Path.To.Hoops.Converter.Dir}\bin\hoops_converter.exe"/>

      <Command arguments="--input_pdf_template_file '${Path.To.Hoops.Converter.Dir}\templates\Blank_Template_L.pdf' --output_pdf '%filepath%\%filename%.pdf' --output_png '%filepath%\%filename%.png' --output_png_resolution '150x150' --output_hwf '%filepath%\%filename%.hwf' --output_prc '%filepath%\%filename%.prc' --camera_default --output_logfile '%filepath%\%filename%'"/>

    </ArasCadConverter>

  </ConverterSettings> </configuration>

The project team must provide information in the transformation file to activate conversion according to the project’s requirements and entitlements.

Below is an illustration of the desired state.

For more specific information about a specific converter, refer to the relevant product documentation. This documentation will provide the essential specifications that need to be added.

The steps outlined below demonstrate how to convert the above template into the desired format.

  1. Add the namespace specification to the document’s top-level element.
  2. Use the Match (name) selector and InsertIfMissing transformation for each section element in the section group.

Observe that a Build System parameter is utilized in the ConversionServer element. The Build System generates a comprehensive list of these parameters. Ensure to review this list and use the parameters associated with the current versions.

Element InnovatorServer:

"${ADT_INNOVATOR_URL}/Server/InnovatorServer.aspx" consider using the simpler ${ADT_DATABASE_INNOVATORSERVERASPXURL}
Note
It is important to utilize these parameters, as the location of various servers in the cloud cannot be hardcoded or predetermined.

  1. For Section Group, add missing Converter elements to the Converters element.

  1. Add converters if missing for the ConverterSettings element. Notice that these elements have child elements.