Skip to content

Commit 7565683

Browse files
authored
Merge pull request #9749 from mendix/qt-restructure
Restructure Mx10 Integration attachment files
2 parents d7c59fc + 40ebc93 commit 7565683

File tree

498 files changed

+432
-434
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

498 files changed

+432
-434
lines changed

content/en/docs/refguide/modeling/integration/mapping-documents/xml-documents/xml-schemas.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ weight: 15
88

99
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/).
1010

11-
{{< figure src="/attachments/refguide/modeling/integration/xml-schemas/18582294.png" alt="Figure 1" class="no-border" >}}
11+
{{< figure src="/attachments/refguide/modeling/integration/mapping-documents/xml-schemas/schema.png" alt="Figure 1" class="no-border" >}}
1212

1313
## XSD File Support
1414

@@ -33,7 +33,7 @@ In the mapping editor for import mappings, you can check elements that can occur
3333

3434
### XSD Constraints
3535

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" >}}
3737

3838
* This will be next to each unsupported element or attribute. Checking any of such elements or attributes will result in consistency errors.
3939

content/en/docs/refguide/modeling/integration/use-excel-documents/export-to-excel.md

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -29,12 +29,12 @@ To download the modules, follow these steps:
2929
1. Open the **Mendix Marketplace** from within Studio Pro.
3030
2. Search for the keyword *reflection* and select **Mx Model reflection**:
3131

32-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/18581166.png" class="no-border" >}}
32+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/mx-model-reflection.png" class="no-border" >}}
3333

3434
3. Click **Download** to include the module in your app. It will be imported into **App** > **Marketplace modules** in the **App Explorer**.
3535
4. Search for the keyword *Excel*, select **Excel exporter**, and download that module into your app:
3636

37-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/exporter.png" class="no-border" >}}
37+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/exporter.png" class="no-border" >}}
3838

3939
{{% alert color="warning" %}}
4040
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
4747
1. In the [App Explorer](/refguide/app-explorer/), go to **Navigation**.
4848
2. Add a **New item** to the navigation to open the page **MxModelReflection.MxObjects_Overview**:
4949

50-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/new-menu-item-mxreflection.png" alt="new-menu-item-mxreflection" class="no-border" >}}
50+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/new-menu-item-mxreflection.png" alt="new-menu-item-mxreflection" class="no-border" >}}
5151

5252
3. Add a new item to the Navigation to open the page **XLSReport.Excel_Document_Overview**:
5353

54-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/new-menu-item-excel-exporter.png" alt="new-menu-item-excel-exporter" class="no-border" >}}
54+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/new-menu-item-excel-exporter.png" alt="new-menu-item-excel-exporter" class="no-border" >}}
5555

5656
4. Open **App Security** and assign these two modules to the Administrator user role:
5757

58-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/security.png" class="no-border" >}}
58+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/security.png" class="no-border" >}}
5959

6060
## Creating an Input Object Entity
6161

@@ -64,7 +64,7 @@ In this section, you will create an entity which will be used to export the Exce
6464
1. Open the domain model for your app and add an entity to serve as a "primary export" entity that is a specialization of **FileDocument**.
6565
2. Create an association between the newly created entity and the entity (or entities) that you will want to serve as a base for the Excel export.
6666

67-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/18581908.png" class="no-border" >}}
67+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/create-association.png" class="no-border" >}}
6868

6969
## Configuring Mx Model Reflection {#configure-mx-model-reflection}
7070

@@ -104,7 +104,7 @@ To set up a template, follow these steps:
104104

105105
7. Provide a **Description** for identifying and documenting what this template is for:
106106

107-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/new-excel-template.png" class="no-border" >}}
107+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/new-excel-template.png" class="no-border" >}}
108108

109109
8. Specify the **Date time export format** which defines how the dates and times should appear in the Excel file once exported.
110110

@@ -116,7 +116,7 @@ To upload an Excel file as a template, perform the following steps:
116116

117117
1. Click the following icon:
118118

119-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/upload-excel-file.png" alt="upload-excel-file" class="no-border" >}}
119+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/upload-excel-file.png" alt="upload-excel-file" class="no-border" >}}
120120

121121
2. For **File**, click **Browse** and navigate to the Excel file that you want to use as a template.
122122

@@ -132,7 +132,7 @@ To create the worksheet layout, follow these steps:
132132

133133
1. Under the **Worksheets** section for the template, select **New** to create a new sheet template:
134134

135-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/18581907.png" class="no-border" >}}
135+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/new-sheet-template.png" class="no-border" >}}
136136

137137
2. Specify the **Name** that will be given to the sheet when the file is exported.
138138

@@ -144,11 +144,11 @@ To create the worksheet layout, follow these steps:
144144

145145
The following figure shows a template where worksheet has **Reference to the template input object** and **Sheet input Object** configured:
146146

147-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/worksheet-with-input-object.png" class="no-border" >}}
147+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/worksheet-with-input-object.png" class="no-border" >}}
148148

149149
The following figure shows a template where worksheet does not have **Reference to the template input object** and **Sheet input Object** configured:
150150

151-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/worksheet-without-input-object.png" class="no-border" >}}
151+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/worksheet-without-input-object.png" class="no-border" >}}
152152

153153
5. Configure the **Start retrieved data at row** to set the ordinal number in which the data should be exported.
154154

@@ -180,15 +180,15 @@ To create the worksheet layout, follow these steps:
180180

181181
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.
182182

183-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/multiple-sheets.png" class="no-border" >}}
183+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/multiple-sheets.png" class="no-border" >}}
184184

185185
### Configuring Dynamic Column Data {#dynamic-column-data}
186186

187187
To configure the dynamic column data, follow these steps:
188188

189189
1. On the **Column Data** tab, select **New** to create a new export column:
190190

191-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/18581905.png" class="no-border" >}}
191+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/new-export-column.png" class="no-border" >}}
192192

193193
2. The **Column number** will be set automatically, but can be overwritten to the desired ordinal number.
194194
3. Define a **Name** for the column. This will be the **Column Header** when exported.
@@ -205,7 +205,7 @@ To configure the static data in the sheet, follow these steps:
205205

206206
1. Open the **Static Data tab** and select **New** to create a new export column.
207207

208-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/18581903.png" class="no-border" >}}
208+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/static-data-tab.png" class="no-border" >}}
209209

210210
2. Specify the **Row** and **Column** that the static value should be placed.
211211
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
218218

219219
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:
220220

221-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/18581900.png" class="no-border" >}}
221+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/styles.png" class="no-border" >}}
222222

223223
2. Specify the properties of the style that will be applied to the cells.
224224

@@ -234,17 +234,17 @@ In this section, you will learn how to call the newly created Excel export templ
234234

235235
2. In the microflow, retrieve a single object which is the template you set up earlier to use for the export.
236236

237-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/retrieve-template.png" class="no-border" >}}
237+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/retrieve-template.png" class="no-border" >}}
238238

239239
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.
240240

241-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/java-action.png" class="no-border" >}}
241+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/java-action.png" class="no-border" >}}
242242

243243
4. In your microflow, download the resulting FileDocument object.
244244

245245
Your microflow should look similar to this:
246246

247-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/microflow-for-generate.png" class="no-border" >}}
247+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/microflow-for-generate.png" class="no-border" >}}
248248

249249
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.
250250

@@ -272,7 +272,7 @@ To run the microflow you created above, you will need to create another microflo
272272

273273
Your new microflow should look similar to this:
274274

275-
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/using-the-excel-exporter/associating-objects.png" class="no-border" >}}
275+
{{< figure src="/attachments/refguide/modeling/integration/use-excel-documents/export-to-excel/associating-objects.png" class="no-border" >}}
276276

277277
{{% alert color="info" %}}
278278
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

Comments
 (0)