IFC Model Properties (Magic xpi 3.x)
To use this type of Source or data, select IFC Model from the drop-down list in the main Source/Destination dialog box. This dialog box lets you select a predefined XSD to use as XML data. This provides an easy way of using the XML Schema Definition (XSD) for any flow component. When you use this as a Destination, you can pass parameters to an XML file to configure any flow component. When you use the IFC Model Properties dialog box you should:
-
Select the XSD from any flow component in your project's Component Repository. You just need to select the component from a list and the component's XSD file is used for you schema definition.
-
Indicate the location of the XML file that you are using for the Source or location of the XML file used to pass the component's configuration parameters.
|
Note:
|
By default, the Destination IFC Models do not load to a DOM. If you want the Destinations to always load to a DOM, you need to close the Magic xpi Studio, set the XMLDomMapper special setting to N, open the Studio, and then rebuild the project. However, when the Append Data check box is selected, the Destination IFC Models will always be loaded to a DOM.
|
The IFC Model Source and Destination properties dialog boxes have the following properties:
|
|
|
|
Name
|
Enter a name for the schema.
|
|
Description
|
Enter a description for the schema.
|
|
Flow Component
|
Click  to select a component from the Component List, which is a list of all the components that are available for the flow.
|
|
Schema
|
This is available only when you select one of the SAPB1 connectors in the Flow Component field (above).
Click to select a predefined schema from the Schema List.
|
|
Data Source/Destination
|
Select where the Source information is located, or where to create the Destination file.
-
File: If you select File, a field is available to add the name and location of the XML file with the Source data or the Destination of the file you are creating.
Click  to open the Expression Editor. Use the Expression Editor to create an expression or condition that will locate the file. This allows you to define a dynamic location for the file. If you want to work with a static location, enter the full path to the file in the field or create a (flow, context, or global) variable that holds the full path to the file and select the variable from the Expression Editor.
-
Variable: Select a variable that contains the XML file with the data you want to use. Only variables of the BLOB type are available. The XML data must be contained in the BLOB.
|
|
XML Validation (Destination only)
|
Select this check box if you want to validate the created XML against the schema file that is set in the XSD file during runtime. If you select this check box, make sure that in runtime the XSD file that you set will be located where you defined it.
The XML validation output is available in the C.sys.LastErrorInfo system variable, and the C.sys.ErrorDescription variable contains the relevant Source or Destination details.
|
Note:
|
XML validation is executed prior to the mapping. If the validation fails, the mapping will abort.
|
Since version: V3.1
|
|
Append Data (Destination only)
|
Select this check box to append the new mapping to work with existing XML files.
|
Note:
|
You need to map at least one compound node when you select the Append Data check box.
|
|
|
XML File Encoding (Destination only)
|
Select the language encoding (the language and character set) that is used for the Destination XML file. You can create several Destinations with different language encoding in the same Data Mapper. Click here to see the languages that are supported. See also the Project Data Encoding property in the Project Properties dialog box.
|
|
Always Create Nodes (Destination only)
|
Select this check box to create the mapped Destination nodes.
When this property is not selected (default), an XML Destination node is not created if the Alpha expression returns one of the following:
The Condition expression on the node overrides this behavior.
Since version: V3.1 SP1
|
