You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/refguide/modeling/integration/mapping-documents/xml-documents/xml-schemas.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ weight: 15
8
8
9
9
An XML schema is defined in an XML Schema Definition (XSD) file and can be imported in your model. It describes what a certain XML document should look like. The schema can then be used in [Import Mappings](/refguide/import-mappings/) and [Export Mappings](/refguide/export-mappings/).
@@ -33,7 +33,7 @@ In the mapping editor for import mappings, you can check elements that can occur
33
33
34
34
### XSD Constraints
35
35
36
-
* If the XSD contains any of the unsupported constructs, they will be highlighted in the mapping editor with this warning icon: {{< figure src="/attachments/refguide/modeling/integration/xml-schemas/xml-schema-support/16843903.png" class="no-border" >}}
36
+
* If the XSD contains any of the unsupported constructs, they will be highlighted in the mapping editor with this warning icon: {{< figure src="/attachments/refguide/modeling/integration/mapping-documents/xml-schemas/warning.png" class="no-border" >}}
37
37
38
38
* This will be next to each unsupported element or attribute. Checking any of such elements or attributes will result in consistency errors.
Depending on the layout selected when the app was created, errors in Studio Pro may arise due to the new module's default layouts. To correct this, open each page that has an error and update the layout to the desired layout within the app.
@@ -47,15 +47,15 @@ In this section, you will learn how to add the required pages in the app's **Nav
47
47
1. In the [App Explorer](/refguide/app-explorer/), go to **Navigation**.
48
48
2. Add a **New item** to the navigation to open the page **MxModelReflection.MxObjects_Overview**:
5. Configure the **Start retrieved data at row** to set the ordinal number in which the data should be exported.
154
154
@@ -180,15 +180,15 @@ To create the worksheet layout, follow these steps:
180
180
181
181
Below you can find an example of the definition of a template and the corresponding exported Excel file: the two worksheets are defined as **Topic** and **PubMessage** in the template, and the corresponding Excel file has two sheets that have the same names.
2. Specify the **Row** and **Column** that the static value should be placed.
211
211
3. Enter a name for the cell in the **Name** field.
@@ -218,7 +218,7 @@ To configure the custom formatting and styling for the cells, follow these steps
218
218
219
219
1. Back on the main page for your new template, click **New** in the **Styles** section to create a new style that can be applied to any of the data in the Excel export:
3. In your microflow, call the **XLSReport.GenerateExcelDoc** Java action (available from the module's **JavaActions** folder) to pass the required objects to the module.
If your template definition does not have **Input Object**, your microflow can directly retrieve the template object and **Row Object** from the database for the export.
250
250
@@ -272,7 +272,7 @@ To run the microflow you created above, you will need to create another microflo
If you create a **PolicyDoc** with *no* associations to **Policy** objects, you will export an empty spreadsheet with the structure defined in the template.
0 commit comments