You can also define the value for a Source or Destination directly in the node's Properties pane. If you do this, you do not need to map Source data to the node.
|
|
|
|
General
|
|
Node Type
|
This property indicates whether the node is simple or compound. This is an informational display and cannot be edited.
|
|
Name
|
This property displays the name of the node. The name of the node is the name of the element in the Source or Destination data. This is an informational display and cannot be edited.
|
|
Description
|
Enter a description of the node.
|
|
External Data Type
|
The data type of an element received from an external system. This is an informational display and cannot be edited.
|
|
Path
|
This property displays the path where the node is located, including fictive elements that were created to display the schema properly. Fictive elements are not part of the actual path. This is an informational display and cannot be edited.
|
|
Actual Path
|
The JSON schema node path shown without fictive elements, as it will be used during runtime. This is an informational display and cannot be edited.
|
Note:
|
This property is available for JSON schema files only.
|
|
|
Single Instance Filter
|
The single instance filter takes the first record that matches the condition that you set in this property.
Click  to open the Expression Editor, and enter a single instance filter condition.
|
Note:
|
This property is relevant for Source compound nodes only.
|
|
|
Replication
|
Determines whether to enable the replication of Data Mapper compound nodes. Select one of the following from the drop-down list:
For more information on how to do this, click here.
|
|
Condition
|
You can define a condition to decide when this mapping directive will be executed in deployment. If there is no condition, it will always be executed. This is only relevant when the Destination type is XML.
Click to open the Expression Editor, and enter a condition.
|
|
Multi Updates
|
Multi update functionality lets you update any variable while looping a Destination compound. During deployment, the updates are executed according to their sequence.
Click to open the Multi Updates dialog box. Then, click Add to open a new line. Create the required computation, then click OK.
Multi updates run before conditions on node properties.
|
Note:
|
This property is relevant for compound nodes only. It is not displayed when you park on simple nodes.
|
|
|
Internal Data Type
|
This describes the attribute used when you want to convert the data type into a Magic xpi internal type. This property will override the default set in the Default Data Format repository. This is an informational display and cannot be edited.
|
|
String Date
|
If you select Yes, the internal attribute (below) becomes an Alpha type. This enables the property to contain both the date and the time. If you select this option, you will need to make some changes to the data_types.xml file, which is located in the <Magic xpi installation>\Studio folder. To learn how to do this, click here.
|
Note:
|
This property is relevant for the datetime field in databases only.
|
|
|
Calculated Value
|
Often, the result that you want to place in a variable cannot be fetched from a single value, but needs to be fetched from a number of different parameters. This is where calculated values need to be used. These are variables that are updated using an expression to determine the actual value.
Click to open the Expression Editor. Use this to enter an expression or a fixed value.
This is available for Destination data only.
|
|
Picture
|
The length of the data. For example, if the digit 9 is entered the node can have nine or less characters.
-
For Source nodes, this is an informational display and cannot be edited.
-
For Destination nodes only. You can change the picture value if the Always Use Custom Picture property is set to Yes and the node is mapped to a Source or a value is entered in the Calculated Value property.
For DateTime type nodes, you can choose between StringDate format and Date format:
-
When the String Date property is set to Yes, the Picture property is enabled and set to 19 by default.
-
When the String Date property is set to No, the Data Mapper will use a Date format. YYYY/MM/DD is selected by default. Change the Always Use Custom Picture property to Yes, in order to edit the Date format.
For Numeric pictures, the picture can only contain numbers, decimal points and the letter N for negatives, such as N12.4.
|
|
Always Use Custom Picture
|
If you want to change the picture in the Picture property and you want to be sure that the value you enter is always used, select Yes from the drop-down list.
This property is available for a mapped element in:
For DateTime types, this property is disabled:
-
When the String Date property is set to Yes, the Always Use Custom Picture property is set to Yes.
-
When the String Date property is set to No, the Always Use Custom Picture property is set to No by default.
|
|
Log Error (this is enabled only when working with databases)
|
Click to select the variables that will accept the input data in the Error Handling Flow.
|
Note:
|
You should make sure that you have previously defined the variables that will accept the input data in the Error Handling Flow.
|
|
|
Additional XML Properties
|
|
Namespace Prefix
|
The node's namespace prefix, which can be used as an alias for the node's namespace. This is an informational display and cannot be edited.
|
|
Namespace
|
The node's namespace. A namespace is a collection of names, identified by a URI reference, that are used in XML documents as element types and attribute names. This helps to differentiate XML documents from different Sources so they can be read by the Data Mapper. This is an informational display and cannot be edited.
|
|
Max Length
|
The number of characters for alphanumeric field types.
|
|
Total Digits
|
The total number of digits before and after the decimal point.
|
|
Fraction Digits
|
The number of digits after the decimal point.
|
|
Max Occurrences
|
This property is retrieved from the schema. It refers to the maximum number of node occurrences that are allowed.
For example, if the schema's Max occurrences=3, the XML that is based on that schema can include up to three occurrences at the most.
|
|
Min Occurrences
|
This property is retrieved from the schema. It refers to the minimum number of node occurrences that are allowed.
For example, a valid XML schema can be generated only if Min occurrences=1 (at least).
|
|
Default/Fixed Value
|
The default or fixed value for the field.
|
|
Documentation
|
The documentation that is relevant to the specific field.
|
|
Enumeration
|
This read-only entry displays a predefined list of available values for this node.
|
|
Nillable
|
If this property is set to True, it means that the element has a Nillable attribute set to True in the XSD and/or XML. These elements can then read Null values from an XML element and write Null values to an XML element.
This property appears for simple elements only.
|
|
Additional JSON Properties
|
|
Max Length
|
The maximum allowable length of a string in the JSON schema.
|
|
Max Items
|
The maximum length of an array in the JSON schema.
|
|
Min Items
|
The minimum length of an array in the JSON schema.
|
|
Default
|
The default value for an item.
|
|
Enum Values
|
Restricts a specific value to fixed set of values.
|
|
Nillable
|
If this property is set to True, it means that the element has a Nillable attribute set to True in the JSON file. These elements can then read Null values from a JSON element and write Null values to a JSON element.
This property appears for simple elements only.
|
