Rename files

Author: quinntracy

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

@@ -8,7 +8,7 @@ weight: 15
 
 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/).
 
-{{< figure src="/attachments/refguide/modeling/integration/xml-schemas/18582294.png" alt="Figure 1" class="no-border" >}}
+{{< figure src="/attachments/refguide/modeling/integration/mapping-documents/xml-schemas/schema.png" alt="Figure 1" class="no-border" >}}
 
 ## XSD File Support
 
@@ -33,7 +33,7 @@ In the mapping editor for import mappings, you can check elements that can occur
 
 ### XSD Constraints
 
-* 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" >}}
+* 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" >}}
 
 * This will be next to each unsupported element or attribute. Checking any of such elements or attributes will result in consistency errors. 
 

content/en/docs/refguide10/modeling/integration/mapping-documents/import-mappings.md

@@ -10,15 +10,15 @@ Please refer to [Mapping Documents](/refguide10/mapping-documents/) for an intro
 
 Figure 1 depicts an example of an Import Mapping document in which two elements from an XML Schema have been selected using the **Select elements...** dialog. Then, the ReceivedPartners and ReceivedClient entities were added and mapped to the Result and Client schema elements. Each time the Import Mapping is invoked, a new ReceivedPartners object is obtained.
 
-{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/import-mappings/16843942.png" class="no-border" >}}
+{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/import-mappings/im-example.png" class="no-border" >}}
 
 **Figure 1**
 
 ### Obtaining an Object
 
 For each XML or JSON object, a Mendix object needs to be obtained. You can create one or find an existing object in the database. Alternatively, you can use a custom microflow that returns an object. You can define how a Mendix object is obtained in the window depicted in Figure 2, which is shown after double-clicking a specific mapping element.
 
-{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/import-mappings/16843943.png" class="no-border" >}}
+{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/import-mappings/mapping-entity.png" class="no-border" >}}
 
 **Figure 2**
 
@@ -42,8 +42,6 @@ In each case, if the object is found or created, mapped attributes will be given
 
 This is the action that the runtime will perform when an error occurred in the specified **Obtain Mendix Object** action.
 
-{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/import-mappings/no-object-found.png" class="no-border" >}}
-
 | Property | Description |
 | --- | --- |
 | **Create** | Create an object of the correct entity to map to and process as in **Create an object**, above. |
@@ -66,13 +64,13 @@ Be aware that lists are not stored ordered in the Mendix database. The XML schem
 
 Each schema value in a selected XML or JSON schema object needs to be mapped to an attribute of an entity to be used in your app. If you don't want to map certain values, uncheck them in the **Select elements...** dialog box. Configuring how to map the attributes is done in the screen depicted in Figure 3, which is shown after double-clicking a specific mapping element.
 
-{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/import-mappings/16843943.png" class="no-border" >}}
+{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/import-mappings/no-object-found.png" class="no-border" >}}
 
 **Figure 3**
 
 Having defined the mappings for the attributes, these mappings are also shown in the mapping document. When a specific attribute is selected, the schema element is also selected. This works the other way around too. An example of this is shown in Figure 4, where the **dati** attribute is selected in both the entity and the schema element (in this case, dati is mapped to dati).
 
-{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/import-mappings/16843944.png" class="no-border" >}}
+{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/import-mappings/schema-example.png" class="no-border" >}}
 
 **Figure 4**
 

content/en/docs/refguide10/modeling/integration/mapping-documents/map-automatically.md

@@ -7,11 +7,11 @@ url: /refguide10/map-automatically/
 
 After you have selected a schema source for the mapping document, you need to connect it to entities, associations, and attributes. When you do not yet have suitable entities available in your domain model, creating new ones by hand can be difficult, especially in large mappings. The **Map automatically** button does the majority of the work for you. Based on the selected schema elements, it creates domain model entities and uses them in the mapping.
 
-{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/map-automatically/18579457.png" class="no-border" >}}
+{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/map-automatically/domain-model-mapping.png" class="no-border" >}}
 
 In the above picture, no entities are connected to the schema elements and the domain model in the module is empty. After clicking **Map automatically**, the situation is as follows:
 
-{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/map-automatically/18579459.png" class="no-border" >}}
+{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/map-automatically/auto-map-example.png" class="no-border" >}}
 
 The following actions will be applied:
 
@@ -21,13 +21,13 @@ The following actions will be applied:
 
 A dialog is shown with the changes that have been applied to the domain model and mapping document (click **Details**"** to expand the dialog).
 
-{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/map-automatically/18579458.png" class="no-border" >}}
+{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/map-automatically/change-dialog.png" class="no-border" >}}
 
 ## Using Existing Entities, Attributes and Associations
 
 If the domain model already contains entities that map to schema elements, they are reused in the mapping. By default, an entity with the same name of the schema type is used. New attributes may be added, or a generalization may be set if the entity did not already have one. New associations may be created as well if they do not yet exist. The result dialog reports if it reuses existing domain model elements:
 
-{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/map-automatically/18579460.png" class="no-border" >}}
+{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/map-automatically/change-dialog-reuse.png" class="no-border" >}}
 
 ## Limitations
 

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

@@ -11,7 +11,7 @@ aliases:
 
 For both [import](/refguide10/import-mappings/) and [export mappings](/refguide10/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/refguide10/modeling/integration/mapping-documents/select--elements/19399143.png" class="no-border" >}}
+{{< figure src="/attachments/refguide10/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/refguide10/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/refguide10/modeling/integration/mapping-documents/xml-documents/xml-inheritance-and-choice/16843946.png" class="no-border" >}}
+{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/xml-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/refguide10/modeling/integration/mapping-documents/xml-documents/xml-inheritance-and-choice/16843945.png" class="no-border" >}}
+{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/xml-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.

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

@@ -8,7 +8,7 @@ weight: 15
 
 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](/refguide10/import-mappings/) and [Export Mappings](/refguide10/export-mappings/).
 
-{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/xml-schemas/18582294.png" alt="Figure 1" class="no-border" >}}
+{{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/xml-schemas/schema.png" alt="Figure 1" class="no-border" >}}
 
 ## XSD File Support
 
@@ -33,7 +33,7 @@ In the mapping editor for import mappings, you can check elements that can occur
 
 ### XSD Constraints
 
-* If the XSD contains any of the unsupported constructs, they will be highlighted in the mapping editor with this warning icon: {{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/xml-schemas/16843903.png" class="no-border" >}}
+* If the XSD contains any of the unsupported constructs, they will be highlighted in the mapping editor with this warning icon: {{< figure src="/attachments/refguide10/modeling/integration/mapping-documents/xml-schemas/warning.png" class="no-border" >}}
 
 * This will be next to each unsupported element or attribute. Checking any of such elements or attributes will result in consistency errors.