Editing Data Type & Message Type Artifacts

Now before proceeding, let’s understand some terms here:

For data type artifact, you can find following details of in the Overview and Structure tabs.

Most of these fields will be empty when you create new artifacts from Cloud Integration. To assign values in this case, you must edit the artifact.

For data types, you can only edit following details from Structure tab.

When you select the node, you see following more details. Now, can click Edit to modify or add the details. So, basically for a data type you can edit only following fields:

• Name: You can change the name of any node except the root node. The name of two nodes can’t be same.
• Type: You can switch from the primitive type to referenced data type, that is, if your data type is defined by built-in type then you can change and assign a user-defined data type or vice versa.

• If you switch from Primitive to User-Defined: The namespace and package name of the referenced data type will be auto populated.

  Note: For root node and child attributes, you can reference only Simple Data Types. So, only those allowed Data Types will be listed in the dialog box.

  
  

• If you switch from User-Defined to Primitive: Choose the Value and namespace will be auto populated depending upon your choice of built-in or derived values.

  

Moreover, consider the following details before modifying or assigning a new type to any node:

• Occurrence: If the selected node is an Attribute, you can decide whether it is Required or Optional.
• Max Occurs and Min Occurs: For elements, you can decide its maximum and minimum occurrences.

Now, based on what ‘Type’ is selected for a node, Restrictions are populated. These restrictions only appear for Simple Data types, elements or attributes with Primitive Type assigned to them. These are used to limit the value range of these nodes. To know more about the restrictions and its value range, see Restrictions.

Adding Nodes

When you edit a data type, other than editing the existing nodes, you can also add new nodes, that is, new elements and attributes. To do so follow these steps:

1. Select the node where you want to add a child element or attribute. Choose Edit.
2. Choose Add and select whether you wish to add Element or Attribute. If you wish to add multiple row of element or attributes, choose Rows. Specify the number of rows to be added and choose Add.

However, below mentioned are few conditions, which apply for such additions:

Deleting Nodes

You can also delete nodes from the data type. To do so follow these steps:

1. Use the checkboxes to select the rows that you want to delete. Only editable nodes can be deleted.
2. Choose Delete just above the table. Following rules apply for node deletion:

Note: When you assign a user-defined data type to an element, the child nodes populated from that user-defined data type can only be deleted from the referenced data type only. So, from the current data type’s structure, you can delete the parent element only.
For example, in ‘xyz’ data type ‘Element1’ is a child element, which refers to ‘tutorial_test’ data type. Here, you will only be allowed to delete the parent element ‘Element1’ and not its child nodes (the checkboxes are disabled). To delete the child nodes, you must do it from ‘tutorial_test’ data type.

Once you edit the data types, you can then save the data types directly or save the data types as a new version. You can do so even if you have errors in your data type structure.

Using Cut, Copy, Paste, Drag, Drop, Up, and Down

You can change the positions of the nodes by using quick actions like drag, and drop, move up and down.
Use cut, copy, paste actions to modify the data type structure and reuse existing node formats respectively.
None of these actions can be performed on the root node. Multi-select is not allowed for any of these actions.

Cut, Copy, Paste

1. Use the checkbox to select the node to be cut, copied.

1. Select the node below which you wish to paste the cut or copied node.

Note: All the rules for deleting and adding the node will apply when you cut and paste the nodes respectively.

Drag and Drop

Use drag and drop to change the positions of the nodes.

Note: The nodes re always added below the target drop node. All the rules for adding and deleting nodes will apply while placing the nodes at the desired location. If dropping of the node is not possible at the selected target location, the node retains its older position.

Move Up and Down

Use the up and down arrows (above the table) to change the positions of the nodes.

1. Use the checkbox to select the node to be moved.

2. Use the up or down action buttons to change the position of the selected node.

Note: You cannot move up an immediate child node(first node under a parent) at all hierarchies. And, you cannot move last node in a hierarchy down.

Message Types comprises a data type that describes the structure of a message. You can find the following details.

Following details you see as soon as you land on the Structure tab.

When you select a row you see additional details in view only mode. The Restrictions are non editable and depend upon the used user-defined data type.

For message types, you can only edit the Data Type Used from both Overview and Structure tabs.

From Structure & Overview tab:

1. Choose Edit.

1. Select a row to view the additional details.
2. Following fields can be edited in the right hand-panel of Structure tab or from Overview tab:

• Data Type Used: Choose Select. Select the integration packages from which you wish to list the data types. Select the data type to be assigned. The structure of the selected data type gets loaded in the tree table.

> Note: You can edit the referenced data type of the root node only.

• Namespace (Only editable from Overview tab): If the namespace is not mentioned, you can enter a new one or modify the existing one.
  

  Note:
  - XMLNamespace should begin with an alphabet and cannot contain tilde (~), back-quote (`), and caret(^).
  - The XMLNamespace ‘http://www.w3.org/2001/XMLSchema’ is dedicated to schema components and cannot be used.