Merge pull request #9707 from mendix/qt-screenshots

Restructure Integration attachments

Author: quinntracy

content/en/docs/marketplace/platform-supported-content/modules/external-database-connector.md

@@ -95,7 +95,7 @@ For free apps, make sure to add the default values to the constant in Studio Pro
 
 When the connection is successful and saved, you can search the **Browse database** tab for Tables, Views, Procedures, and Functions.
 
-{{< figure src="/attachments/refguide/modeling/integration/use-the-external-database-connector/3.png" width="700" >}}
+{{< figure src="http://attachments/refguide/modeling/integration/use-platform-supported-content/use-the-external-database-connector/3.png" width="700" >}}
 
 ## Querying a Database {#query-database}
 

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

@@ -20,7 +20,7 @@ Import mappings are used to define how incoming XML or JSON is converted into Me
 
 This is an example of an import mapping document that maps an **Order** from a web service to a **ReceivedOrder** entity:
 
-{{< figure src="/attachments/refguide/modeling/integration/mapping-documents/16843933.png" class="no-border" >}}
+{{< figure src="/attachments/refguide/modeling/integration/mapping-documents/import-mapping.png" class="no-border" >}}
 
 For more details, see [Import Mappings](/refguide/import-mappings/).
 
@@ -33,7 +33,7 @@ Export mappings are used to define how Mendix objects can be converted to XML ac
 
 This is an example of an export mapping document:
 
-{{< figure src="/attachments/refguide/modeling/integration/mapping-documents/16843940.png" class="no-border" >}}
+{{< figure src="/attachments/refguide/modeling/integration/mapping-documents/export-mapping.png" class="no-border" >}}
 
 In this example, a **Cheesecake** entity will be passed when the export mapping is called. Subsequently, the **Topping** entities will be fetched by following the **Topping_Cheesecake** association from the passed Cheesecake Mendix object. The result is passed to an XML document or sent to a web service.
 

content/en/docs/refguide/modeling/integration/mapping-documents/select--elements.md

@@ -11,7 +11,7 @@ aliases:
 
 For both [import](/refguide/import-mappings/) and [export mappings](/refguide/export-mappings/), you need to specify the elements structure you want to map. You do this in the **Select schema elements** window. An example of this screen is shown below:
 
-{{< figure src="/attachments/refguide/modeling/integration/mapping-documents/select--elements/19399143.png" class="no-border" >}}
+{{< figure src="/attachments/refguide/modeling/integration/mapping-documents/select--elements/schema-elements-window.png" class="no-border" >}}
 
 Perform the following steps in the **Select schema elements** window:
 

content/en/docs/refguide/modeling/integration/mapping-documents/xml-documents/xml-inheritance-and-choice.md

@@ -19,7 +19,7 @@ In Mendix, both inheritance and choice are mapped by entity specialization.
 
 In the image below, an example of an Export Mapping with inheritance is shown. For Import Mappings, the structure is the same, only the direction of the arrows is reversed. One Persons object has a one-to-many association to Person. The person can be either a Customer or Employee.
 
-{{< figure src="/attachments/refguide/modeling/integration/mapping-documents/xml-inheritance-and-choice/16843946.png" class="no-border" >}}
+{{< figure src="/attachments/refguide/modeling/integration/mapping-documents/xml-inheritance-and-choice/inheritance.png" class="no-border" >}}
 
 For Import Mappings, mapping the incoming XML to a specific XSD type is defined by the attribute *xsi:type*. However, this attribute is optional. When the *xsi:type* attribute is not present and the base type of the element is not abstract, that type will be used (in the example, that is Person). If the base type does not have a mapping defined in the import mapping document, it will be skipped. When the base type is abstract, an error will be thrown.
 
@@ -35,6 +35,6 @@ When the root element is an inheritance element, you can only maps the entire bo
 
 The image below shows an Export Mapping with a choice element. The schema specifies a choice with two alternatives: an employee id or member ID. In this image, a base entity Person is mapped to the choice element to serve as a generalization for the choice options. 
 
-{{< figure src="/attachments/refguide/modeling/integration/mapping-documents/xml-inheritance-and-choice/16843945.png" class="no-border" >}}
+{{< figure src="/attachments/refguide/modeling/integration/mapping-documents/xml-inheritance-and-choice/choice.png" class="no-border" >}}
 
 For exporting objects, optionality on choice elements is handled differently than for other elements because they do not explicitly occur in XML. There are two cases in which it is valid to export an empty object for a choice element: first, when the choice element itself is **Optional** and second, when at least one of the choice options is **Optional**. In these cases, no element will be created, otherwise an error is thrown. When one or more options of a choice element are **Nillable** and at the choice element you export an empty object, Mendix throws an **Unsupported** error because it is impossible to determine which XML element should be sent with the *xsi:nil* attribute.