--- title: "Mapping Rules" slug: "mapping-rules" description: "This is a description of what the Mapping Rules are in RapidIdentity Connect." tags: ["RapidIdentity ", "Connect", "Mapping", "Policy", "Actions"] updated: 2022-06-03T13:36:24Z published: 2022-06-03T13:36:24Z canonical: "help.rapididentity.com/mapping-rules" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.rapididentity.com/llms.txt > Use this file to discover all available pages before exploring further. # Mapping Rules ## Mapping Rules - Namespaces, namespace prefixes, comments, and processing instructions are all ignored. - Elements with no attributes and no content or whitespace-only content become null. - Elements with no subelements and no attributes become the text, numeric, or boolean value of the element content.ActionScript ```actionscript Hello becomes "Hello" ``` - Elements with attributes or child elements become a record. - Nested element names (sans any namespace prefix) become record fieldsActionScript ```actionscript Hello becomes { "y": "Hello" } ``` - Attributes become record fields prefixed with @.ActionScript ```actionscript becomes { "y": { "@z": 1 } } ``` - If an element has attributes and non-empty text-only content, then the text content becomes a record field named value.ActionScript ```actionscript Hello becomes { "y": { "@z": 1, "value": "Hello" } } ``` - Multiple elements with the same name at the same level become multiple values of the same field.ActionScript ```actionscript Hello Goodbye becomes { "y": ["Hello", "Goodbye"] } ``` - If an element has mixed content (intermixed text and elements), then the text is ignored.ActionScript ```actionscript Hello Something in between Goodbye becomes { "y": ["Hello", "Goodbye"] } ```