7.4. Defining Custom Types Using XML

Engineering Knowledge Manager

Administration Guide | Chapter 7: Defining Custom Types |

7.3.2. Editing a Custom Type |  | 7.4.1. Schema Definition for Custom Types
Prev |  | Next

## 7.4. Defining Custom Types Using XML

An alternative way of defining a custom type is to create an XML file in an XML editor. You can specify the same settings that you would specify if you were defining the custom type using the New > EKM Type feature (see Defining Custom Types Directly in EKM), with the added flexibility of customizing the new type even further if necessary.

The following are some key points to remember while defining custom types in XML:

- The XML file should conform to the schema definition as described in Schema Definition for Custom Types.

- There can only be one type defined per file.

- The name of the XML file must end with the extension: .type.xml.

- The name of the XML file should start with the type name. This is not a strict requirement but a good practice to follow. For example, the name of the XML file for a custom `Project` type should be Project.type.xml.

- When the XML definition is ready, you can upload it to the `/Administration/Configuration/Custom Types` folder. The upload wizard will automatically recognize the file to be of type `EKM Type` based on its file extension.

- If you want to edit an existing type in XML, you can first download the desired file, make the changes using an XML editor, upload it back to EKM and overwrite the existing file. Alternatively, if the changes are minor and you are comfortable with the XML syntax, you can use the Edit > Content action menu for the selected type to make the changes directly to the file in EKM.

Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.

Prev | Up / Contents | Next

Release 18.2 - © ANSYS, Inc. All rights reserved.