text
stringlengths 65
20k
|
|---|
Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Get Started with the Mapper Review the following topics for an overview of how to use the mapper to map source data structures to target data structures.Topics About Mappings About Mapping Data Between Applications About the Expression Builder Access the Mapper About Mappings One of the key tasks to any integration is defining how data is transferred, or mapped , between two applications.In most cases, the messages you want to transfer between the applications in an integration have different data structures.A visual mapper enables you to map element nodes between applications by dragging source element nodes onto target element nodes. |
Access to Oracle Support Oracle customers that have purchased support have access to electronic support through My Oracle Support.For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Get Started with the Mapper Review the following topics for an overview of how to use the mapper to map source data structures to target data structures.Topics About Mappings About Mapping Data Between Applications About the Expression Builder Access the Mapper About Mappings One of the key tasks to any integration is defining how data is transferred, or mapped , between two applications.In most cases, the messages you want to transfer between the applications in an integration have different data structures.A visual mapper enables you to map element nodes between applications by dragging source element nodes onto target element nodes.When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections. |
For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Get Started with the Mapper Review the following topics for an overview of how to use the mapper to map source data structures to target data structures.Topics About Mappings About Mapping Data Between Applications About the Expression Builder Access the Mapper About Mappings One of the key tasks to any integration is defining how data is transferred, or mapped , between two applications.In most cases, the messages you want to transfer between the applications in an integration have different data structures.A visual mapper enables you to map element nodes between applications by dragging source element nodes onto target element nodes.When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections.You can expand and load data structure levels on demand to display additional levels. |
ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Get Started with the Mapper Review the following topics for an overview of how to use the mapper to map source data structures to target data structures.Topics About Mappings About Mapping Data Between Applications About the Expression Builder Access the Mapper About Mappings One of the key tasks to any integration is defining how data is transferred, or mapped , between two applications.In most cases, the messages you want to transfer between the applications in an integration have different data structures.A visual mapper enables you to map element nodes between applications by dragging source element nodes onto target element nodes.When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections.You can expand and load data structure levels on demand to display additional levels.There is no limit on the levels of display. |
Diversity and Inclusion Oracle is fully committed to diversity and inclusion.Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Get Started with the Mapper Review the following topics for an overview of how to use the mapper to map source data structures to target data structures.Topics About Mappings About Mapping Data Between Applications About the Expression Builder Access the Mapper About Mappings One of the key tasks to any integration is defining how data is transferred, or mapped , between two applications.In most cases, the messages you want to transfer between the applications in an integration have different data structures.A visual mapper enables you to map element nodes between applications by dragging source element nodes onto target element nodes.When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections.You can expand and load data structure levels on demand to display additional levels.There is no limit on the levels of display.The maps you create are called transformation maps, and use the eXtensible Stylesheet Language (XSL) to describe the data mappings, which let you perform complex data manipulation and transformation. |
Oracle respects and values having a diverse workforce that increases thought leadership and innovation.As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Get Started with the Mapper Review the following topics for an overview of how to use the mapper to map source data structures to target data structures.Topics About Mappings About Mapping Data Between Applications About the Expression Builder Access the Mapper About Mappings One of the key tasks to any integration is defining how data is transferred, or mapped , between two applications.In most cases, the messages you want to transfer between the applications in an integration have different data structures.A visual mapper enables you to map element nodes between applications by dragging source element nodes onto target element nodes.When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections.You can expand and load data structure levels on demand to display additional levels.There is no limit on the levels of display.The maps you create are called transformation maps, and use the eXtensible Stylesheet Language (XSL) to describe the data mappings, which let you perform complex data manipulation and transformation.A standard set of XSLT constructs are provided (for example, xsl:if , xsl:for-each , and others). |
As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation.We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Get Started with the Mapper Review the following topics for an overview of how to use the mapper to map source data structures to target data structures.Topics About Mappings About Mapping Data Between Applications About the Expression Builder Access the Mapper About Mappings One of the key tasks to any integration is defining how data is transferred, or mapped , between two applications.In most cases, the messages you want to transfer between the applications in an integration have different data structures.A visual mapper enables you to map element nodes between applications by dragging source element nodes onto target element nodes.When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections.You can expand and load data structure levels on demand to display additional levels.There is no limit on the levels of display.The maps you create are called transformation maps, and use the eXtensible Stylesheet Language (XSL) to describe the data mappings, which let you perform complex data manipulation and transformation.A standard set of XSLT constructs are provided (for example, xsl:if , xsl:for-each , and others).A specialized function is also provided for you to reference lookups directly from the mapper. |
We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve.Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Get Started with the Mapper Review the following topics for an overview of how to use the mapper to map source data structures to target data structures.Topics About Mappings About Mapping Data Between Applications About the Expression Builder Access the Mapper About Mappings One of the key tasks to any integration is defining how data is transferred, or mapped , between two applications.In most cases, the messages you want to transfer between the applications in an integration have different data structures.A visual mapper enables you to map element nodes between applications by dragging source element nodes onto target element nodes.When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections.You can expand and load data structure levels on demand to display additional levels.There is no limit on the levels of display.The maps you create are called transformation maps, and use the eXtensible Stylesheet Language (XSL) to describe the data mappings, which let you perform complex data manipulation and transformation.A standard set of XSLT constructs are provided (for example, xsl:if , xsl:for-each , and others).A specialized function is also provided for you to reference lookups directly from the mapper.1-1Note: The mapper supports XSL version 2.0. |
Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.vRelated Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Get Started with the Mapper Review the following topics for an overview of how to use the mapper to map source data structures to target data structures.Topics About Mappings About Mapping Data Between Applications About the Expression Builder Access the Mapper About Mappings One of the key tasks to any integration is defining how data is transferred, or mapped , between two applications.In most cases, the messages you want to transfer between the applications in an integration have different data structures.A visual mapper enables you to map element nodes between applications by dragging source element nodes onto target element nodes.When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections.You can expand and load data structure levels on demand to display additional levels.There is no limit on the levels of display.The maps you create are called transformation maps, and use the eXtensible Stylesheet Language (XSL) to describe the data mappings, which let you perform complex data manipulation and transformation.A standard set of XSLT constructs are provided (for example, xsl:if , xsl:for-each , and others).A specialized function is also provided for you to reference lookups directly from the mapper.1-1Note: The mapper supports XSL version 2.0.Version 1.0 is not supported. |
vRelated Resources See these Oracle resources: Oracle Cloud http://cloud.oracle.com Using Integrations in Oracle Integration Generation 2 Conventions The following text conventions are used in this document: Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Get Started with the Mapper Review the following topics for an overview of how to use the mapper to map source data structures to target data structures.Topics About Mappings About Mapping Data Between Applications About the Expression Builder Access the Mapper About Mappings One of the key tasks to any integration is defining how data is transferred, or mapped , between two applications.In most cases, the messages you want to transfer between the applications in an integration have different data structures.A visual mapper enables you to map element nodes between applications by dragging source element nodes onto target element nodes.When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections.You can expand and load data structure levels on demand to display additional levels.There is no limit on the levels of display.The maps you create are called transformation maps, and use the eXtensible Stylesheet Language (XSL) to describe the data mappings, which let you perform complex data manipulation and transformation.A standard set of XSLT constructs are provided (for example, xsl:if , xsl:for-each , and others).A specialized function is also provided for you to reference lookups directly from the mapper.1-1Note: The mapper supports XSL version 2.0.Version 1.0 is not supported.The mapper supports both qualified and unqualified schemas (that is, schemas without elementFormDefault=qualified ). |
italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Get Started with the Mapper Review the following topics for an overview of how to use the mapper to map source data structures to target data structures.Topics About Mappings About Mapping Data Between Applications About the Expression Builder Access the Mapper About Mappings One of the key tasks to any integration is defining how data is transferred, or mapped , between two applications.In most cases, the messages you want to transfer between the applications in an integration have different data structures.A visual mapper enables you to map element nodes between applications by dragging source element nodes onto target element nodes.When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections.You can expand and load data structure levels on demand to display additional levels.There is no limit on the levels of display.The maps you create are called transformation maps, and use the eXtensible Stylesheet Language (XSL) to describe the data mappings, which let you perform complex data manipulation and transformation.A standard set of XSLT constructs are provided (for example, xsl:if , xsl:for-each , and others).A specialized function is also provided for you to reference lookups directly from the mapper.1-1Note: The mapper supports XSL version 2.0.Version 1.0 is not supported.The mapper supports both qualified and unqualified schemas (that is, schemas without elementFormDefault=qualified ).Elements and attributes with and without namespace prefixes are also supported. |
monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.Preface vi1 Get Started with the Mapper Review the following topics for an overview of how to use the mapper to map source data structures to target data structures.Topics About Mappings About Mapping Data Between Applications About the Expression Builder Access the Mapper About Mappings One of the key tasks to any integration is defining how data is transferred, or mapped , between two applications.In most cases, the messages you want to transfer between the applications in an integration have different data structures.A visual mapper enables you to map element nodes between applications by dragging source element nodes onto target element nodes.When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections.You can expand and load data structure levels on demand to display additional levels.There is no limit on the levels of display.The maps you create are called transformation maps, and use the eXtensible Stylesheet Language (XSL) to describe the data mappings, which let you perform complex data manipulation and transformation.A standard set of XSLT constructs are provided (for example, xsl:if , xsl:for-each , and others).A specialized function is also provided for you to reference lookups directly from the mapper.1-1Note: The mapper supports XSL version 2.0.Version 1.0 is not supported.The mapper supports both qualified and unqualified schemas (that is, schemas without elementFormDefault=qualified ).Elements and attributes with and without namespace prefixes are also supported.Substitution groups in schemas are supported. |
Topics About Mappings About Mapping Data Between Applications About the Expression Builder Access the Mapper About Mappings One of the key tasks to any integration is defining how data is transferred, or mapped , between two applications.In most cases, the messages you want to transfer between the applications in an integration have different data structures.A visual mapper enables you to map element nodes between applications by dragging source element nodes onto target element nodes.When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections.You can expand and load data structure levels on demand to display additional levels.There is no limit on the levels of display.The maps you create are called transformation maps, and use the eXtensible Stylesheet Language (XSL) to describe the data mappings, which let you perform complex data manipulation and transformation.A standard set of XSLT constructs are provided (for example, xsl:if , xsl:for-each , and others).A specialized function is also provided for you to reference lookups directly from the mapper.1-1Note: The mapper supports XSL version 2.0.Version 1.0 is not supported.The mapper supports both qualified and unqualified schemas (that is, schemas without elementFormDefault=qualified ).Elements and attributes with and without namespace prefixes are also supported.Substitution groups in schemas are supported.You can see all the substitutable elements in a base element in the mapper, and select the one to use. |
In most cases, the messages you want to transfer between the applications in an integration have different data structures.A visual mapper enables you to map element nodes between applications by dragging source element nodes onto target element nodes.When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections.You can expand and load data structure levels on demand to display additional levels.There is no limit on the levels of display.The maps you create are called transformation maps, and use the eXtensible Stylesheet Language (XSL) to describe the data mappings, which let you perform complex data manipulation and transformation.A standard set of XSLT constructs are provided (for example, xsl:if , xsl:for-each , and others).A specialized function is also provided for you to reference lookups directly from the mapper.1-1Note: The mapper supports XSL version 2.0.Version 1.0 is not supported.The mapper supports both qualified and unqualified schemas (that is, schemas without elementFormDefault=qualified ).Elements and attributes with and without namespace prefixes are also supported.Substitution groups in schemas are supported.You can see all the substitutable elements in a base element in the mapper, and select the one to use.Extended data types are also supported. |
A visual mapper enables you to map element nodes between applications by dragging source element nodes onto target element nodes.When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections.You can expand and load data structure levels on demand to display additional levels.There is no limit on the levels of display.The maps you create are called transformation maps, and use the eXtensible Stylesheet Language (XSL) to describe the data mappings, which let you perform complex data manipulation and transformation.A standard set of XSLT constructs are provided (for example, xsl:if , xsl:for-each , and others).A specialized function is also provided for you to reference lookups directly from the mapper.1-1Note: The mapper supports XSL version 2.0.Version 1.0 is not supported.The mapper supports both qualified and unqualified schemas (that is, schemas without elementFormDefault=qualified ).Elements and attributes with and without namespace prefixes are also supported.Substitution groups in schemas are supported.You can see all the substitutable elements in a base element in the mapper, and select the one to use.Extended data types are also supported.Elements and attributes for which mapping is required are identified by a blue asterisk (*) to the left of their names. |
When you open the mapper for a request or response message in an integration, the data structures are automatically populated with the information pulled from the source and target connections.You can expand and load data structure levels on demand to display additional levels.There is no limit on the levels of display.The maps you create are called transformation maps, and use the eXtensible Stylesheet Language (XSL) to describe the data mappings, which let you perform complex data manipulation and transformation.A standard set of XSLT constructs are provided (for example, xsl:if , xsl:for-each , and others).A specialized function is also provided for you to reference lookups directly from the mapper.1-1Note: The mapper supports XSL version 2.0.Version 1.0 is not supported.The mapper supports both qualified and unqualified schemas (that is, schemas without elementFormDefault=qualified ).Elements and attributes with and without namespace prefixes are also supported.Substitution groups in schemas are supported.You can see all the substitutable elements in a base element in the mapper, and select the one to use.Extended data types are also supported.Elements and attributes for which mapping is required are identified by a blue asterisk (*) to the left of their names.To display only required fields, click the Filter icon in the mapper toolbar, select Required Fields , and click Apply . |
You can expand and load data structure levels on demand to display additional levels.There is no limit on the levels of display.The maps you create are called transformation maps, and use the eXtensible Stylesheet Language (XSL) to describe the data mappings, which let you perform complex data manipulation and transformation.A standard set of XSLT constructs are provided (for example, xsl:if , xsl:for-each , and others).A specialized function is also provided for you to reference lookups directly from the mapper.1-1Note: The mapper supports XSL version 2.0.Version 1.0 is not supported.The mapper supports both qualified and unqualified schemas (that is, schemas without elementFormDefault=qualified ).Elements and attributes with and without namespace prefixes are also supported.Substitution groups in schemas are supported.You can see all the substitutable elements in a base element in the mapper, and select the one to use.Extended data types are also supported.Elements and attributes for which mapping is required are identified by a blue asterisk (*) to the left of their names.To display only required fields, click the Filter icon in the mapper toolbar, select Required Fields , and click Apply .You can also right-click elements and attributes and select Node Info to show specific schema details such as the data type, if mapping is required, and so on. |
There is no limit on the levels of display.The maps you create are called transformation maps, and use the eXtensible Stylesheet Language (XSL) to describe the data mappings, which let you perform complex data manipulation and transformation.A standard set of XSLT constructs are provided (for example, xsl:if , xsl:for-each , and others).A specialized function is also provided for you to reference lookups directly from the mapper.1-1Note: The mapper supports XSL version 2.0.Version 1.0 is not supported.The mapper supports both qualified and unqualified schemas (that is, schemas without elementFormDefault=qualified ).Elements and attributes with and without namespace prefixes are also supported.Substitution groups in schemas are supported.You can see all the substitutable elements in a base element in the mapper, and select the one to use.Extended data types are also supported.Elements and attributes for which mapping is required are identified by a blue asterisk (*) to the left of their names.To display only required fields, click the Filter icon in the mapper toolbar, select Required Fields , and click Apply .You can also right-click elements and attributes and select Node Info to show specific schema details such as the data type, if mapping is required, and so on.Additional custom annotations can also be displayed. |
The maps you create are called transformation maps, and use the eXtensible Stylesheet Language (XSL) to describe the data mappings, which let you perform complex data manipulation and transformation.A standard set of XSLT constructs are provided (for example, xsl:if , xsl:for-each , and others).A specialized function is also provided for you to reference lookups directly from the mapper.1-1Note: The mapper supports XSL version 2.0.Version 1.0 is not supported.The mapper supports both qualified and unqualified schemas (that is, schemas without elementFormDefault=qualified ).Elements and attributes with and without namespace prefixes are also supported.Substitution groups in schemas are supported.You can see all the substitutable elements in a base element in the mapper, and select the one to use.Extended data types are also supported.Elements and attributes for which mapping is required are identified by a blue asterisk (*) to the left of their names.To display only required fields, click the Filter icon in the mapper toolbar, select Required Fields , and click Apply .You can also right-click elements and attributes and select Node Info to show specific schema details such as the data type, if mapping is required, and so on.Additional custom annotations can also be displayed.These annotations are currently only available with the Oracle Sales Cloud Adapter. |
A standard set of XSLT constructs are provided (for example, xsl:if , xsl:for-each , and others).A specialized function is also provided for you to reference lookups directly from the mapper.1-1Note: The mapper supports XSL version 2.0.Version 1.0 is not supported.The mapper supports both qualified and unqualified schemas (that is, schemas without elementFormDefault=qualified ).Elements and attributes with and without namespace prefixes are also supported.Substitution groups in schemas are supported.You can see all the substitutable elements in a base element in the mapper, and select the one to use.Extended data types are also supported.Elements and attributes for which mapping is required are identified by a blue asterisk (*) to the left of their names.To display only required fields, click the Filter icon in the mapper toolbar, select Required Fields , and click Apply .You can also right-click elements and attributes and select Node Info to show specific schema details such as the data type, if mapping is required, and so on.Additional custom annotations can also be displayed.These annotations are currently only available with the Oracle Sales Cloud Adapter.The Oracle Engagement Cloud Adapter obtains this information from the applications and annotates it in the integration WSDL. |
A specialized function is also provided for you to reference lookups directly from the mapper.1-1Note: The mapper supports XSL version 2.0.Version 1.0 is not supported.The mapper supports both qualified and unqualified schemas (that is, schemas without elementFormDefault=qualified ).Elements and attributes with and without namespace prefixes are also supported.Substitution groups in schemas are supported.You can see all the substitutable elements in a base element in the mapper, and select the one to use.Extended data types are also supported.Elements and attributes for which mapping is required are identified by a blue asterisk (*) to the left of their names.To display only required fields, click the Filter icon in the mapper toolbar, select Required Fields , and click Apply .You can also right-click elements and attributes and select Node Info to show specific schema details such as the data type, if mapping is required, and so on.Additional custom annotations can also be displayed.These annotations are currently only available with the Oracle Sales Cloud Adapter.The Oracle Engagement Cloud Adapter obtains this information from the applications and annotates it in the integration WSDL.This information is then read and made visible as annotations in the mapper (for example, title and description). |
1-1Note: The mapper supports XSL version 2.0.Version 1.0 is not supported.The mapper supports both qualified and unqualified schemas (that is, schemas without elementFormDefault=qualified ).Elements and attributes with and without namespace prefixes are also supported.Substitution groups in schemas are supported.You can see all the substitutable elements in a base element in the mapper, and select the one to use.Extended data types are also supported.Elements and attributes for which mapping is required are identified by a blue asterisk (*) to the left of their names.To display only required fields, click the Filter icon in the mapper toolbar, select Required Fields , and click Apply .You can also right-click elements and attributes and select Node Info to show specific schema details such as the data type, if mapping is required, and so on.Additional custom annotations can also be displayed.These annotations are currently only available with the Oracle Sales Cloud Adapter.The Oracle Engagement Cloud Adapter obtains this information from the applications and annotates it in the integration WSDL.This information is then read and made visible as annotations in the mapper (for example, title and description).This information can help you better understand what data is being mapped. |
Version 1.0 is not supported.The mapper supports both qualified and unqualified schemas (that is, schemas without elementFormDefault=qualified ).Elements and attributes with and without namespace prefixes are also supported.Substitution groups in schemas are supported.You can see all the substitutable elements in a base element in the mapper, and select the one to use.Extended data types are also supported.Elements and attributes for which mapping is required are identified by a blue asterisk (*) to the left of their names.To display only required fields, click the Filter icon in the mapper toolbar, select Required Fields , and click Apply .You can also right-click elements and attributes and select Node Info to show specific schema details such as the data type, if mapping is required, and so on.Additional custom annotations can also be displayed.These annotations are currently only available with the Oracle Sales Cloud Adapter.The Oracle Engagement Cloud Adapter obtains this information from the applications and annotates it in the integration WSDL.This information is then read and made visible as annotations in the mapper (for example, title and description).This information can help you better understand what data is being mapped.The mapper toolbar provides the following functionality. |
The mapper supports both qualified and unqualified schemas (that is, schemas without elementFormDefault=qualified ).Elements and attributes with and without namespace prefixes are also supported.Substitution groups in schemas are supported.You can see all the substitutable elements in a base element in the mapper, and select the one to use.Extended data types are also supported.Elements and attributes for which mapping is required are identified by a blue asterisk (*) to the left of their names.To display only required fields, click the Filter icon in the mapper toolbar, select Required Fields , and click Apply .You can also right-click elements and attributes and select Node Info to show specific schema details such as the data type, if mapping is required, and so on.Additional custom annotations can also be displayed.These annotations are currently only available with the Oracle Sales Cloud Adapter.The Oracle Engagement Cloud Adapter obtains this information from the applications and annotates it in the integration WSDL.This information is then read and made visible as annotations in the mapper (for example, title and description).This information can help you better understand what data is being mapped.The mapper toolbar provides the following functionality.Element Description Click to return to the mapping canvas when you are inside the Code, Test, or Recommend page. |
Elements and attributes with and without namespace prefixes are also supported.Substitution groups in schemas are supported.You can see all the substitutable elements in a base element in the mapper, and select the one to use.Extended data types are also supported.Elements and attributes for which mapping is required are identified by a blue asterisk (*) to the left of their names.To display only required fields, click the Filter icon in the mapper toolbar, select Required Fields , and click Apply .You can also right-click elements and attributes and select Node Info to show specific schema details such as the data type, if mapping is required, and so on.Additional custom annotations can also be displayed.These annotations are currently only available with the Oracle Sales Cloud Adapter.The Oracle Engagement Cloud Adapter obtains this information from the applications and annotates it in the integration WSDL.This information is then read and made visible as annotations in the mapper (for example, title and description).This information can help you better understand what data is being mapped.The mapper toolbar provides the following functionality.Element Description Click to return to the mapping canvas when you are inside the Code, Test, or Recommend page.You can view the XSLT code being created as you design your mappings. |
Substitution groups in schemas are supported.You can see all the substitutable elements in a base element in the mapper, and select the one to use.Extended data types are also supported.Elements and attributes for which mapping is required are identified by a blue asterisk (*) to the left of their names.To display only required fields, click the Filter icon in the mapper toolbar, select Required Fields , and click Apply .You can also right-click elements and attributes and select Node Info to show specific schema details such as the data type, if mapping is required, and so on.Additional custom annotations can also be displayed.These annotations are currently only available with the Oracle Sales Cloud Adapter.The Oracle Engagement Cloud Adapter obtains this information from the applications and annotates it in the integration WSDL.This information is then read and made visible as annotations in the mapper (for example, title and description).This information can help you better understand what data is being mapped.The mapper toolbar provides the following functionality.Element Description Click to return to the mapping canvas when you are inside the Code, Test, or Recommend page.You can view the XSLT code being created as you design your mappings.Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester. |
You can see all the substitutable elements in a base element in the mapper, and select the one to use.Extended data types are also supported.Elements and attributes for which mapping is required are identified by a blue asterisk (*) to the left of their names.To display only required fields, click the Filter icon in the mapper toolbar, select Required Fields , and click Apply .You can also right-click elements and attributes and select Node Info to show specific schema details such as the data type, if mapping is required, and so on.Additional custom annotations can also be displayed.These annotations are currently only available with the Oracle Sales Cloud Adapter.The Oracle Engagement Cloud Adapter obtains this information from the applications and annotates it in the integration WSDL.This information is then read and made visible as annotations in the mapper (for example, title and description).This information can help you better understand what data is being mapped.The mapper toolbar provides the following functionality.Element Description Click to return to the mapping canvas when you are inside the Code, Test, or Recommend page.You can view the XSLT code being created as you design your mappings.Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester.If you enable the recommendations engine, you can accept the target element recommendations of the engine when creating mappings. |
Extended data types are also supported.Elements and attributes for which mapping is required are identified by a blue asterisk (*) to the left of their names.To display only required fields, click the Filter icon in the mapper toolbar, select Required Fields , and click Apply .You can also right-click elements and attributes and select Node Info to show specific schema details such as the data type, if mapping is required, and so on.Additional custom annotations can also be displayed.These annotations are currently only available with the Oracle Sales Cloud Adapter.The Oracle Engagement Cloud Adapter obtains this information from the applications and annotates it in the integration WSDL.This information is then read and made visible as annotations in the mapper (for example, title and description).This information can help you better understand what data is being mapped.The mapper toolbar provides the following functionality.Element Description Click to return to the mapping canvas when you are inside the Code, Test, or Recommend page.You can view the XSLT code being created as you design your mappings.Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester.If you enable the recommendations engine, you can accept the target element recommendations of the engine when creating mappings.This eliminates the need to analyze and perform each individual source-to-target mapping.Chapter 1 About Mappings 1-2Element Description Click to disable user-friendly, source and target element names in the mapper. |
Elements and attributes for which mapping is required are identified by a blue asterisk (*) to the left of their names.To display only required fields, click the Filter icon in the mapper toolbar, select Required Fields , and click Apply .You can also right-click elements and attributes and select Node Info to show specific schema details such as the data type, if mapping is required, and so on.Additional custom annotations can also be displayed.These annotations are currently only available with the Oracle Sales Cloud Adapter.The Oracle Engagement Cloud Adapter obtains this information from the applications and annotates it in the integration WSDL.This information is then read and made visible as annotations in the mapper (for example, title and description).This information can help you better understand what data is being mapped.The mapper toolbar provides the following functionality.Element Description Click to return to the mapping canvas when you are inside the Code, Test, or Recommend page.You can view the XSLT code being created as you design your mappings.Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester.If you enable the recommendations engine, you can accept the target element recommendations of the engine when creating mappings.This eliminates the need to analyze and perform each individual source-to-target mapping.Chapter 1 About Mappings 1-2Element Description Click to disable user-friendly, source and target element names in the mapper.By default, user-friendly element names are shown. |
To display only required fields, click the Filter icon in the mapper toolbar, select Required Fields , and click Apply .You can also right-click elements and attributes and select Node Info to show specific schema details such as the data type, if mapping is required, and so on.Additional custom annotations can also be displayed.These annotations are currently only available with the Oracle Sales Cloud Adapter.The Oracle Engagement Cloud Adapter obtains this information from the applications and annotates it in the integration WSDL.This information is then read and made visible as annotations in the mapper (for example, title and description).This information can help you better understand what data is being mapped.The mapper toolbar provides the following functionality.Element Description Click to return to the mapping canvas when you are inside the Code, Test, or Recommend page.You can view the XSLT code being created as you design your mappings.Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester.If you enable the recommendations engine, you can accept the target element recommendations of the engine when creating mappings.This eliminates the need to analyze and perform each individual source-to-target mapping.Chapter 1 About Mappings 1-2Element Description Click to disable user-friendly, source and target element names in the mapper.By default, user-friendly element names are shown.Click to show the XSLT functions. |
You can also right-click elements and attributes and select Node Info to show specific schema details such as the data type, if mapping is required, and so on.Additional custom annotations can also be displayed.These annotations are currently only available with the Oracle Sales Cloud Adapter.The Oracle Engagement Cloud Adapter obtains this information from the applications and annotates it in the integration WSDL.This information is then read and made visible as annotations in the mapper (for example, title and description).This information can help you better understand what data is being mapped.The mapper toolbar provides the following functionality.Element Description Click to return to the mapping canvas when you are inside the Code, Test, or Recommend page.You can view the XSLT code being created as you design your mappings.Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester.If you enable the recommendations engine, you can accept the target element recommendations of the engine when creating mappings.This eliminates the need to analyze and perform each individual source-to-target mapping.Chapter 1 About Mappings 1-2Element Description Click to disable user-friendly, source and target element names in the mapper.By default, user-friendly element names are shown.Click to show the XSLT functions.You can select the following options: Select to show the namespace prefixes on source and target element nodes. |
Additional custom annotations can also be displayed.These annotations are currently only available with the Oracle Sales Cloud Adapter.The Oracle Engagement Cloud Adapter obtains this information from the applications and annotates it in the integration WSDL.This information is then read and made visible as annotations in the mapper (for example, title and description).This information can help you better understand what data is being mapped.The mapper toolbar provides the following functionality.Element Description Click to return to the mapping canvas when you are inside the Code, Test, or Recommend page.You can view the XSLT code being created as you design your mappings.Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester.If you enable the recommendations engine, you can accept the target element recommendations of the engine when creating mappings.This eliminates the need to analyze and perform each individual source-to-target mapping.Chapter 1 About Mappings 1-2Element Description Click to disable user-friendly, source and target element names in the mapper.By default, user-friendly element names are shown.Click to show the XSLT functions.You can select the following options: Select to show the namespace prefixes on source and target element nodes.Select to show the types (prefixes and data types) on source and target element nodes. |
These annotations are currently only available with the Oracle Sales Cloud Adapter.The Oracle Engagement Cloud Adapter obtains this information from the applications and annotates it in the integration WSDL.This information is then read and made visible as annotations in the mapper (for example, title and description).This information can help you better understand what data is being mapped.The mapper toolbar provides the following functionality.Element Description Click to return to the mapping canvas when you are inside the Code, Test, or Recommend page.You can view the XSLT code being created as you design your mappings.Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester.If you enable the recommendations engine, you can accept the target element recommendations of the engine when creating mappings.This eliminates the need to analyze and perform each individual source-to-target mapping.Chapter 1 About Mappings 1-2Element Description Click to disable user-friendly, source and target element names in the mapper.By default, user-friendly element names are shown.Click to show the XSLT functions.You can select the following options: Select to show the namespace prefixes on source and target element nodes.Select to show the types (prefixes and data types) on source and target element nodes.You can filter the display of element nodes, error messages, and warnings in the source or target data structures. |
The Oracle Engagement Cloud Adapter obtains this information from the applications and annotates it in the integration WSDL.This information is then read and made visible as annotations in the mapper (for example, title and description).This information can help you better understand what data is being mapped.The mapper toolbar provides the following functionality.Element Description Click to return to the mapping canvas when you are inside the Code, Test, or Recommend page.You can view the XSLT code being created as you design your mappings.Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester.If you enable the recommendations engine, you can accept the target element recommendations of the engine when creating mappings.This eliminates the need to analyze and perform each individual source-to-target mapping.Chapter 1 About Mappings 1-2Element Description Click to disable user-friendly, source and target element names in the mapper.By default, user-friendly element names are shown.Click to show the XSLT functions.You can select the following options: Select to show the namespace prefixes on source and target element nodes.Select to show the types (prefixes and data types) on source and target element nodes.You can filter the display of element nodes, error messages, and warnings in the source or target data structures.You can select to undo the previous action performed in the mapper. |
This information is then read and made visible as annotations in the mapper (for example, title and description).This information can help you better understand what data is being mapped.The mapper toolbar provides the following functionality.Element Description Click to return to the mapping canvas when you are inside the Code, Test, or Recommend page.You can view the XSLT code being created as you design your mappings.Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester.If you enable the recommendations engine, you can accept the target element recommendations of the engine when creating mappings.This eliminates the need to analyze and perform each individual source-to-target mapping.Chapter 1 About Mappings 1-2Element Description Click to disable user-friendly, source and target element names in the mapper.By default, user-friendly element names are shown.Click to show the XSLT functions.You can select the following options: Select to show the namespace prefixes on source and target element nodes.Select to show the types (prefixes and data types) on source and target element nodes.You can filter the display of element nodes, error messages, and warnings in the source or target data structures.You can select to undo the previous action performed in the mapper.For example, if you perform a mapping, then press this button, the mapping is removed. |
This information can help you better understand what data is being mapped.The mapper toolbar provides the following functionality.Element Description Click to return to the mapping canvas when you are inside the Code, Test, or Recommend page.You can view the XSLT code being created as you design your mappings.Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester.If you enable the recommendations engine, you can accept the target element recommendations of the engine when creating mappings.This eliminates the need to analyze and perform each individual source-to-target mapping.Chapter 1 About Mappings 1-2Element Description Click to disable user-friendly, source and target element names in the mapper.By default, user-friendly element names are shown.Click to show the XSLT functions.You can select the following options: Select to show the namespace prefixes on source and target element nodes.Select to show the types (prefixes and data types) on source and target element nodes.You can filter the display of element nodes, error messages, and warnings in the source or target data structures.You can select to undo the previous action performed in the mapper.For example, if you perform a mapping, then press this button, the mapping is removed.The link is disabled when all actions have been undone. |
The mapper toolbar provides the following functionality.Element Description Click to return to the mapping canvas when you are inside the Code, Test, or Recommend page.You can view the XSLT code being created as you design your mappings.Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester.If you enable the recommendations engine, you can accept the target element recommendations of the engine when creating mappings.This eliminates the need to analyze and perform each individual source-to-target mapping.Chapter 1 About Mappings 1-2Element Description Click to disable user-friendly, source and target element names in the mapper.By default, user-friendly element names are shown.Click to show the XSLT functions.You can select the following options: Select to show the namespace prefixes on source and target element nodes.Select to show the types (prefixes and data types) on source and target element nodes.You can filter the display of element nodes, error messages, and warnings in the source or target data structures.You can select to undo the previous action performed in the mapper.For example, if you perform a mapping, then press this button, the mapping is removed.The link is disabled when all actions have been undone.You can redo the action that was undone. |
Element Description Click to return to the mapping canvas when you are inside the Code, Test, or Recommend page.You can view the XSLT code being created as you design your mappings.Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester.If you enable the recommendations engine, you can accept the target element recommendations of the engine when creating mappings.This eliminates the need to analyze and perform each individual source-to-target mapping.Chapter 1 About Mappings 1-2Element Description Click to disable user-friendly, source and target element names in the mapper.By default, user-friendly element names are shown.Click to show the XSLT functions.You can select the following options: Select to show the namespace prefixes on source and target element nodes.Select to show the types (prefixes and data types) on source and target element nodes.You can filter the display of element nodes, error messages, and warnings in the source or target data structures.You can select to undo the previous action performed in the mapper.For example, if you perform a mapping, then press this button, the mapping is removed.The link is disabled when all actions have been undone.You can redo the action that was undone.You can maximize the size of the mapper. |
You can view the XSLT code being created as you design your mappings.Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester.If you enable the recommendations engine, you can accept the target element recommendations of the engine when creating mappings.This eliminates the need to analyze and perform each individual source-to-target mapping.Chapter 1 About Mappings 1-2Element Description Click to disable user-friendly, source and target element names in the mapper.By default, user-friendly element names are shown.Click to show the XSLT functions.You can select the following options: Select to show the namespace prefixes on source and target element nodes.Select to show the types (prefixes and data types) on source and target element nodes.You can filter the display of element nodes, error messages, and warnings in the source or target data structures.You can select to undo the previous action performed in the mapper.For example, if you perform a mapping, then press this button, the mapping is removed.The link is disabled when all actions have been undone.You can redo the action that was undone.You can maximize the size of the mapper.This is useful when working with large schemas. |
Once you complete designing your mappings, you can test them by entering sample content of the message to process in the mapping tester.If you enable the recommendations engine, you can accept the target element recommendations of the engine when creating mappings.This eliminates the need to analyze and perform each individual source-to-target mapping.Chapter 1 About Mappings 1-2Element Description Click to disable user-friendly, source and target element names in the mapper.By default, user-friendly element names are shown.Click to show the XSLT functions.You can select the following options: Select to show the namespace prefixes on source and target element nodes.Select to show the types (prefixes and data types) on source and target element nodes.You can filter the display of element nodes, error messages, and warnings in the source or target data structures.You can select to undo the previous action performed in the mapper.For example, if you perform a mapping, then press this button, the mapping is removed.The link is disabled when all actions have been undone.You can redo the action that was undone.You can maximize the size of the mapper.This is useful when working with large schemas.You can add functions, operators, and XSLT expressions to your mappings. |
If you enable the recommendations engine, you can accept the target element recommendations of the engine when creating mappings.This eliminates the need to analyze and perform each individual source-to-target mapping.Chapter 1 About Mappings 1-2Element Description Click to disable user-friendly, source and target element names in the mapper.By default, user-friendly element names are shown.Click to show the XSLT functions.You can select the following options: Select to show the namespace prefixes on source and target element nodes.Select to show the types (prefixes and data types) on source and target element nodes.You can filter the display of element nodes, error messages, and warnings in the source or target data structures.You can select to undo the previous action performed in the mapper.For example, if you perform a mapping, then press this button, the mapping is removed.The link is disabled when all actions have been undone.You can redo the action that was undone.You can maximize the size of the mapper.This is useful when working with large schemas.You can add functions, operators, and XSLT expressions to your mappings.About Mapping Data Between Applications Once you create an integration and have the source and target connections in place, you can define how data is mapped between the element nodes in the two data structures. |
This eliminates the need to analyze and perform each individual source-to-target mapping.Chapter 1 About Mappings 1-2Element Description Click to disable user-friendly, source and target element names in the mapper.By default, user-friendly element names are shown.Click to show the XSLT functions.You can select the following options: Select to show the namespace prefixes on source and target element nodes.Select to show the types (prefixes and data types) on source and target element nodes.You can filter the display of element nodes, error messages, and warnings in the source or target data structures.You can select to undo the previous action performed in the mapper.For example, if you perform a mapping, then press this button, the mapping is removed.The link is disabled when all actions have been undone.You can redo the action that was undone.You can maximize the size of the mapper.This is useful when working with large schemas.You can add functions, operators, and XSLT expressions to your mappings.About Mapping Data Between Applications Once you create an integration and have the source and target connections in place, you can define how data is mapped between the element nodes in the two data structures.The mapper appears with the element nodes of the source data structure on the left and the target data structure on the right. |
By default, user-friendly element names are shown.Click to show the XSLT functions.You can select the following options: Select to show the namespace prefixes on source and target element nodes.Select to show the types (prefixes and data types) on source and target element nodes.You can filter the display of element nodes, error messages, and warnings in the source or target data structures.You can select to undo the previous action performed in the mapper.For example, if you perform a mapping, then press this button, the mapping is removed.The link is disabled when all actions have been undone.You can redo the action that was undone.You can maximize the size of the mapper.This is useful when working with large schemas.You can add functions, operators, and XSLT expressions to your mappings.About Mapping Data Between Applications Once you create an integration and have the source and target connections in place, you can define how data is mapped between the element nodes in the two data structures.The mapper appears with the element nodes of the source data structure on the left and the target data structure on the right.1.To map fields directly, click a source element nodes and drag it to the corresponding field in the target element node.Chapter 1 About Mapping Data Between Applications 1-3A blue line connects the two nodes. |
Click to show the XSLT functions.You can select the following options: Select to show the namespace prefixes on source and target element nodes.Select to show the types (prefixes and data types) on source and target element nodes.You can filter the display of element nodes, error messages, and warnings in the source or target data structures.You can select to undo the previous action performed in the mapper.For example, if you perform a mapping, then press this button, the mapping is removed.The link is disabled when all actions have been undone.You can redo the action that was undone.You can maximize the size of the mapper.This is useful when working with large schemas.You can add functions, operators, and XSLT expressions to your mappings.About Mapping Data Between Applications Once you create an integration and have the source and target connections in place, you can define how data is mapped between the element nodes in the two data structures.The mapper appears with the element nodes of the source data structure on the left and the target data structure on the right.1.To map fields directly, click a source element nodes and drag it to the corresponding field in the target element node.Chapter 1 About Mapping Data Between Applications 1-3A blue line connects the two nodes.An Expression Builder below the mapper is displayed to show the XPath expression. |
You can select the following options: Select to show the namespace prefixes on source and target element nodes.Select to show the types (prefixes and data types) on source and target element nodes.You can filter the display of element nodes, error messages, and warnings in the source or target data structures.You can select to undo the previous action performed in the mapper.For example, if you perform a mapping, then press this button, the mapping is removed.The link is disabled when all actions have been undone.You can redo the action that was undone.You can maximize the size of the mapper.This is useful when working with large schemas.You can add functions, operators, and XSLT expressions to your mappings.About Mapping Data Between Applications Once you create an integration and have the source and target connections in place, you can define how data is mapped between the element nodes in the two data structures.The mapper appears with the element nodes of the source data structure on the left and the target data structure on the right.1.To map fields directly, click a source element nodes and drag it to the corresponding field in the target element node.Chapter 1 About Mapping Data Between Applications 1-3A blue line connects the two nodes.An Expression Builder below the mapper is displayed to show the XPath expression.2.To use functions, operators, or XSLT statements in your mapping, see Work with Functions, Operators, and XSLT Statements . |
Select to show the types (prefixes and data types) on source and target element nodes.You can filter the display of element nodes, error messages, and warnings in the source or target data structures.You can select to undo the previous action performed in the mapper.For example, if you perform a mapping, then press this button, the mapping is removed.The link is disabled when all actions have been undone.You can redo the action that was undone.You can maximize the size of the mapper.This is useful when working with large schemas.You can add functions, operators, and XSLT expressions to your mappings.About Mapping Data Between Applications Once you create an integration and have the source and target connections in place, you can define how data is mapped between the element nodes in the two data structures.The mapper appears with the element nodes of the source data structure on the left and the target data structure on the right.1.To map fields directly, click a source element nodes and drag it to the corresponding field in the target element node.Chapter 1 About Mapping Data Between Applications 1-3A blue line connects the two nodes.An Expression Builder below the mapper is displayed to show the XPath expression.2.To use functions, operators, or XSLT statements in your mapping, see Work with Functions, Operators, and XSLT Statements .3.When you are done mapping data, click Close , then click Apply to save your changes when prompted. |
You can filter the display of element nodes, error messages, and warnings in the source or target data structures.You can select to undo the previous action performed in the mapper.For example, if you perform a mapping, then press this button, the mapping is removed.The link is disabled when all actions have been undone.You can redo the action that was undone.You can maximize the size of the mapper.This is useful when working with large schemas.You can add functions, operators, and XSLT expressions to your mappings.About Mapping Data Between Applications Once you create an integration and have the source and target connections in place, you can define how data is mapped between the element nodes in the two data structures.The mapper appears with the element nodes of the source data structure on the left and the target data structure on the right.1.To map fields directly, click a source element nodes and drag it to the corresponding field in the target element node.Chapter 1 About Mapping Data Between Applications 1-3A blue line connects the two nodes.An Expression Builder below the mapper is displayed to show the XPath expression.2.To use functions, operators, or XSLT statements in your mapping, see Work with Functions, Operators, and XSLT Statements .3.When you are done mapping data, click Close , then click Apply to save your changes when prompted.You can also click Validate to save your changes. |
You can select to undo the previous action performed in the mapper.For example, if you perform a mapping, then press this button, the mapping is removed.The link is disabled when all actions have been undone.You can redo the action that was undone.You can maximize the size of the mapper.This is useful when working with large schemas.You can add functions, operators, and XSLT expressions to your mappings.About Mapping Data Between Applications Once you create an integration and have the source and target connections in place, you can define how data is mapped between the element nodes in the two data structures.The mapper appears with the element nodes of the source data structure on the left and the target data structure on the right.1.To map fields directly, click a source element nodes and drag it to the corresponding field in the target element node.Chapter 1 About Mapping Data Between Applications 1-3A blue line connects the two nodes.An Expression Builder below the mapper is displayed to show the XPath expression.2.To use functions, operators, or XSLT statements in your mapping, see Work with Functions, Operators, and XSLT Statements .3.When you are done mapping data, click Close , then click Apply to save your changes when prompted.You can also click Validate to save your changes.View User-Friendly Element Names You can view user-friendly display names instead of technical names for source and target elements in the mapper tree and for expressions in the Expression Builder. |
For example, if you perform a mapping, then press this button, the mapping is removed.The link is disabled when all actions have been undone.You can redo the action that was undone.You can maximize the size of the mapper.This is useful when working with large schemas.You can add functions, operators, and XSLT expressions to your mappings.About Mapping Data Between Applications Once you create an integration and have the source and target connections in place, you can define how data is mapped between the element nodes in the two data structures.The mapper appears with the element nodes of the source data structure on the left and the target data structure on the right.1.To map fields directly, click a source element nodes and drag it to the corresponding field in the target element node.Chapter 1 About Mapping Data Between Applications 1-3A blue line connects the two nodes.An Expression Builder below the mapper is displayed to show the XPath expression.2.To use functions, operators, or XSLT statements in your mapping, see Work with Functions, Operators, and XSLT Statements .3.When you are done mapping data, click Close , then click Apply to save your changes when prompted.You can also click Validate to save your changes.View User-Friendly Element Names You can view user-friendly display names instead of technical names for source and target elements in the mapper tree and for expressions in the Expression Builder.This eliminates the need to try and understand the technical, often cryptic, names that are difficult to correlate to the user-friendly display names you see in the endpoint application's user interface. |
The link is disabled when all actions have been undone.You can redo the action that was undone.You can maximize the size of the mapper.This is useful when working with large schemas.You can add functions, operators, and XSLT expressions to your mappings.About Mapping Data Between Applications Once you create an integration and have the source and target connections in place, you can define how data is mapped between the element nodes in the two data structures.The mapper appears with the element nodes of the source data structure on the left and the target data structure on the right.1.To map fields directly, click a source element nodes and drag it to the corresponding field in the target element node.Chapter 1 About Mapping Data Between Applications 1-3A blue line connects the two nodes.An Expression Builder below the mapper is displayed to show the XPath expression.2.To use functions, operators, or XSLT statements in your mapping, see Work with Functions, Operators, and XSLT Statements .3.When you are done mapping data, click Close , then click Apply to save your changes when prompted.You can also click Validate to save your changes.View User-Friendly Element Names You can view user-friendly display names instead of technical names for source and target elements in the mapper tree and for expressions in the Expression Builder.This eliminates the need to try and understand the technical, often cryptic, names that are difficult to correlate to the user-friendly display names you see in the endpoint application's user interface.User-friendly names are displayed by default, but you can also toggle to the technical names. |
You can redo the action that was undone.You can maximize the size of the mapper.This is useful when working with large schemas.You can add functions, operators, and XSLT expressions to your mappings.About Mapping Data Between Applications Once you create an integration and have the source and target connections in place, you can define how data is mapped between the element nodes in the two data structures.The mapper appears with the element nodes of the source data structure on the left and the target data structure on the right.1.To map fields directly, click a source element nodes and drag it to the corresponding field in the target element node.Chapter 1 About Mapping Data Between Applications 1-3A blue line connects the two nodes.An Expression Builder below the mapper is displayed to show the XPath expression.2.To use functions, operators, or XSLT statements in your mapping, see Work with Functions, Operators, and XSLT Statements .3.When you are done mapping data, click Close , then click Apply to save your changes when prompted.You can also click Validate to save your changes.View User-Friendly Element Names You can view user-friendly display names instead of technical names for source and target elements in the mapper tree and for expressions in the Expression Builder.This eliminates the need to try and understand the technical, often cryptic, names that are difficult to correlate to the user-friendly display names you see in the endpoint application's user interface.User-friendly names are displayed by default, but you can also toggle to the technical names.Toggle Between User-Friendly Names and Technical Names Adapter Names Root Elements in Source and Target Trees Child Elements in Source and Target Trees Search For Data in the Source and Target Trees User-Friendly Expression for Mapping Expression Builder Other Sections of the User Interface Toggle Between User-Friendly Names and Technical Names By default, user-friendly names are displayed in the source and target mapper trees when you open the mapper. |
You can maximize the size of the mapper.This is useful when working with large schemas.You can add functions, operators, and XSLT expressions to your mappings.About Mapping Data Between Applications Once you create an integration and have the source and target connections in place, you can define how data is mapped between the element nodes in the two data structures.The mapper appears with the element nodes of the source data structure on the left and the target data structure on the right.1.To map fields directly, click a source element nodes and drag it to the corresponding field in the target element node.Chapter 1 About Mapping Data Between Applications 1-3A blue line connects the two nodes.An Expression Builder below the mapper is displayed to show the XPath expression.2.To use functions, operators, or XSLT statements in your mapping, see Work with Functions, Operators, and XSLT Statements .3.When you are done mapping data, click Close , then click Apply to save your changes when prompted.You can also click Validate to save your changes.View User-Friendly Element Names You can view user-friendly display names instead of technical names for source and target elements in the mapper tree and for expressions in the Expression Builder.This eliminates the need to try and understand the technical, often cryptic, names that are difficult to correlate to the user-friendly display names you see in the endpoint application's user interface.User-friendly names are displayed by default, but you can also toggle to the technical names.Toggle Between User-Friendly Names and Technical Names Adapter Names Root Elements in Source and Target Trees Child Elements in Source and Target Trees Search For Data in the Source and Target Trees User-Friendly Expression for Mapping Expression Builder Other Sections of the User Interface Toggle Between User-Friendly Names and Technical Names By default, user-friendly names are displayed in the source and target mapper trees when you open the mapper.Name display is controlled by the button at the top of the mapper. |
This is useful when working with large schemas.You can add functions, operators, and XSLT expressions to your mappings.About Mapping Data Between Applications Once you create an integration and have the source and target connections in place, you can define how data is mapped between the element nodes in the two data structures.The mapper appears with the element nodes of the source data structure on the left and the target data structure on the right.1.To map fields directly, click a source element nodes and drag it to the corresponding field in the target element node.Chapter 1 About Mapping Data Between Applications 1-3A blue line connects the two nodes.An Expression Builder below the mapper is displayed to show the XPath expression.2.To use functions, operators, or XSLT statements in your mapping, see Work with Functions, Operators, and XSLT Statements .3.When you are done mapping data, click Close , then click Apply to save your changes when prompted.You can also click Validate to save your changes.View User-Friendly Element Names You can view user-friendly display names instead of technical names for source and target elements in the mapper tree and for expressions in the Expression Builder.This eliminates the need to try and understand the technical, often cryptic, names that are difficult to correlate to the user-friendly display names you see in the endpoint application's user interface.User-friendly names are displayed by default, but you can also toggle to the technical names.Toggle Between User-Friendly Names and Technical Names Adapter Names Root Elements in Source and Target Trees Child Elements in Source and Target Trees Search For Data in the Source and Target Trees User-Friendly Expression for Mapping Expression Builder Other Sections of the User Interface Toggle Between User-Friendly Names and Technical Names By default, user-friendly names are displayed in the source and target mapper trees when you open the mapper.Name display is controlled by the button at the top of the mapper.Chapter 1 View User-Friendly Element Names 1-4 1.Click to switch to technical names. |
You can add functions, operators, and XSLT expressions to your mappings.About Mapping Data Between Applications Once you create an integration and have the source and target connections in place, you can define how data is mapped between the element nodes in the two data structures.The mapper appears with the element nodes of the source data structure on the left and the target data structure on the right.1.To map fields directly, click a source element nodes and drag it to the corresponding field in the target element node.Chapter 1 About Mapping Data Between Applications 1-3A blue line connects the two nodes.An Expression Builder below the mapper is displayed to show the XPath expression.2.To use functions, operators, or XSLT statements in your mapping, see Work with Functions, Operators, and XSLT Statements .3.When you are done mapping data, click Close , then click Apply to save your changes when prompted.You can also click Validate to save your changes.View User-Friendly Element Names You can view user-friendly display names instead of technical names for source and target elements in the mapper tree and for expressions in the Expression Builder.This eliminates the need to try and understand the technical, often cryptic, names that are difficult to correlate to the user-friendly display names you see in the endpoint application's user interface.User-friendly names are displayed by default, but you can also toggle to the technical names.Toggle Between User-Friendly Names and Technical Names Adapter Names Root Elements in Source and Target Trees Child Elements in Source and Target Trees Search For Data in the Source and Target Trees User-Friendly Expression for Mapping Expression Builder Other Sections of the User Interface Toggle Between User-Friendly Names and Technical Names By default, user-friendly names are displayed in the source and target mapper trees when you open the mapper.Name display is controlled by the button at the top of the mapper.Chapter 1 View User-Friendly Element Names 1-4 1.Click to switch to technical names.The button changes colors to blue and technical names for the source and target elements are displayed. |
About Mapping Data Between Applications Once you create an integration and have the source and target connections in place, you can define how data is mapped between the element nodes in the two data structures.The mapper appears with the element nodes of the source data structure on the left and the target data structure on the right.1.To map fields directly, click a source element nodes and drag it to the corresponding field in the target element node.Chapter 1 About Mapping Data Between Applications 1-3A blue line connects the two nodes.An Expression Builder below the mapper is displayed to show the XPath expression.2.To use functions, operators, or XSLT statements in your mapping, see Work with Functions, Operators, and XSLT Statements .3.When you are done mapping data, click Close , then click Apply to save your changes when prompted.You can also click Validate to save your changes.View User-Friendly Element Names You can view user-friendly display names instead of technical names for source and target elements in the mapper tree and for expressions in the Expression Builder.This eliminates the need to try and understand the technical, often cryptic, names that are difficult to correlate to the user-friendly display names you see in the endpoint application's user interface.User-friendly names are displayed by default, but you can also toggle to the technical names.Toggle Between User-Friendly Names and Technical Names Adapter Names Root Elements in Source and Target Trees Child Elements in Source and Target Trees Search For Data in the Source and Target Trees User-Friendly Expression for Mapping Expression Builder Other Sections of the User Interface Toggle Between User-Friendly Names and Technical Names By default, user-friendly names are displayed in the source and target mapper trees when you open the mapper.Name display is controlled by the button at the top of the mapper.Chapter 1 View User-Friendly Element Names 1-4 1.Click to switch to technical names.The button changes colors to blue and technical names for the source and target elements are displayed.2.Click to switch back to user-friendly names. |
The mapper appears with the element nodes of the source data structure on the left and the target data structure on the right.1.To map fields directly, click a source element nodes and drag it to the corresponding field in the target element node.Chapter 1 About Mapping Data Between Applications 1-3A blue line connects the two nodes.An Expression Builder below the mapper is displayed to show the XPath expression.2.To use functions, operators, or XSLT statements in your mapping, see Work with Functions, Operators, and XSLT Statements .3.When you are done mapping data, click Close , then click Apply to save your changes when prompted.You can also click Validate to save your changes.View User-Friendly Element Names You can view user-friendly display names instead of technical names for source and target elements in the mapper tree and for expressions in the Expression Builder.This eliminates the need to try and understand the technical, often cryptic, names that are difficult to correlate to the user-friendly display names you see in the endpoint application's user interface.User-friendly names are displayed by default, but you can also toggle to the technical names.Toggle Between User-Friendly Names and Technical Names Adapter Names Root Elements in Source and Target Trees Child Elements in Source and Target Trees Search For Data in the Source and Target Trees User-Friendly Expression for Mapping Expression Builder Other Sections of the User Interface Toggle Between User-Friendly Names and Technical Names By default, user-friendly names are displayed in the source and target mapper trees when you open the mapper.Name display is controlled by the button at the top of the mapper.Chapter 1 View User-Friendly Element Names 1-4 1.Click to switch to technical names.The button changes colors to blue and technical names for the source and target elements are displayed.2.Click to switch back to user-friendly names.Adapter Names In user-friendly mode, adapter names are displayed along with the adapter's associated icon and the type of payload (request/response). |
1.To map fields directly, click a source element nodes and drag it to the corresponding field in the target element node.Chapter 1 About Mapping Data Between Applications 1-3A blue line connects the two nodes.An Expression Builder below the mapper is displayed to show the XPath expression.2.To use functions, operators, or XSLT statements in your mapping, see Work with Functions, Operators, and XSLT Statements .3.When you are done mapping data, click Close , then click Apply to save your changes when prompted.You can also click Validate to save your changes.View User-Friendly Element Names You can view user-friendly display names instead of technical names for source and target elements in the mapper tree and for expressions in the Expression Builder.This eliminates the need to try and understand the technical, often cryptic, names that are difficult to correlate to the user-friendly display names you see in the endpoint application's user interface.User-friendly names are displayed by default, but you can also toggle to the technical names.Toggle Between User-Friendly Names and Technical Names Adapter Names Root Elements in Source and Target Trees Child Elements in Source and Target Trees Search For Data in the Source and Target Trees User-Friendly Expression for Mapping Expression Builder Other Sections of the User Interface Toggle Between User-Friendly Names and Technical Names By default, user-friendly names are displayed in the source and target mapper trees when you open the mapper.Name display is controlled by the button at the top of the mapper.Chapter 1 View User-Friendly Element Names 1-4 1.Click to switch to technical names.The button changes colors to blue and technical names for the source and target elements are displayed.2.Click to switch back to user-friendly names.Adapter Names In user-friendly mode, adapter names are displayed along with the adapter's associated icon and the type of payload (request/response).For this example, the source REST Adapter and Oracle Commerce Cloud Adapter and the target REST Adapter are displayed. |
An Expression Builder below the mapper is displayed to show the XPath expression.2.To use functions, operators, or XSLT statements in your mapping, see Work with Functions, Operators, and XSLT Statements .3.When you are done mapping data, click Close , then click Apply to save your changes when prompted.You can also click Validate to save your changes.View User-Friendly Element Names You can view user-friendly display names instead of technical names for source and target elements in the mapper tree and for expressions in the Expression Builder.This eliminates the need to try and understand the technical, often cryptic, names that are difficult to correlate to the user-friendly display names you see in the endpoint application's user interface.User-friendly names are displayed by default, but you can also toggle to the technical names.Toggle Between User-Friendly Names and Technical Names Adapter Names Root Elements in Source and Target Trees Child Elements in Source and Target Trees Search For Data in the Source and Target Trees User-Friendly Expression for Mapping Expression Builder Other Sections of the User Interface Toggle Between User-Friendly Names and Technical Names By default, user-friendly names are displayed in the source and target mapper trees when you open the mapper.Name display is controlled by the button at the top of the mapper.Chapter 1 View User-Friendly Element Names 1-4 1.Click to switch to technical names.The button changes colors to blue and technical names for the source and target elements are displayed.2.Click to switch back to user-friendly names.Adapter Names In user-friendly mode, adapter names are displayed along with the adapter's associated icon and the type of payload (request/response).For this example, the source REST Adapter and Oracle Commerce Cloud Adapter and the target REST Adapter are displayed.1.Click to switch to technical names. |
2.To use functions, operators, or XSLT statements in your mapping, see Work with Functions, Operators, and XSLT Statements .3.When you are done mapping data, click Close , then click Apply to save your changes when prompted.You can also click Validate to save your changes.View User-Friendly Element Names You can view user-friendly display names instead of technical names for source and target elements in the mapper tree and for expressions in the Expression Builder.This eliminates the need to try and understand the technical, often cryptic, names that are difficult to correlate to the user-friendly display names you see in the endpoint application's user interface.User-friendly names are displayed by default, but you can also toggle to the technical names.Toggle Between User-Friendly Names and Technical Names Adapter Names Root Elements in Source and Target Trees Child Elements in Source and Target Trees Search For Data in the Source and Target Trees User-Friendly Expression for Mapping Expression Builder Other Sections of the User Interface Toggle Between User-Friendly Names and Technical Names By default, user-friendly names are displayed in the source and target mapper trees when you open the mapper.Name display is controlled by the button at the top of the mapper.Chapter 1 View User-Friendly Element Names 1-4 1.Click to switch to technical names.The button changes colors to blue and technical names for the source and target elements are displayed.2.Click to switch back to user-friendly names.Adapter Names In user-friendly mode, adapter names are displayed along with the adapter's associated icon and the type of payload (request/response).For this example, the source REST Adapter and Oracle Commerce Cloud Adapter and the target REST Adapter are displayed.1.Click to switch to technical names.The adapter names are removed. |
3.When you are done mapping data, click Close , then click Apply to save your changes when prompted.You can also click Validate to save your changes.View User-Friendly Element Names You can view user-friendly display names instead of technical names for source and target elements in the mapper tree and for expressions in the Expression Builder.This eliminates the need to try and understand the technical, often cryptic, names that are difficult to correlate to the user-friendly display names you see in the endpoint application's user interface.User-friendly names are displayed by default, but you can also toggle to the technical names.Toggle Between User-Friendly Names and Technical Names Adapter Names Root Elements in Source and Target Trees Child Elements in Source and Target Trees Search For Data in the Source and Target Trees User-Friendly Expression for Mapping Expression Builder Other Sections of the User Interface Toggle Between User-Friendly Names and Technical Names By default, user-friendly names are displayed in the source and target mapper trees when you open the mapper.Name display is controlled by the button at the top of the mapper.Chapter 1 View User-Friendly Element Names 1-4 1.Click to switch to technical names.The button changes colors to blue and technical names for the source and target elements are displayed.2.Click to switch back to user-friendly names.Adapter Names In user-friendly mode, adapter names are displayed along with the adapter's associated icon and the type of payload (request/response).For this example, the source REST Adapter and Oracle Commerce Cloud Adapter and the target REST Adapter are displayed.1.Click to switch to technical names.The adapter names are removed.Chapter 1 View User-Friendly Element Names 1-5 Root Elements in Source and Target Trees User-friendly names for the root elements of the different payloads enable you to easily correlate them with the associated invoke/trigger connection, the adapter used, and the type of payload (request/response). |
You can also click Validate to save your changes.View User-Friendly Element Names You can view user-friendly display names instead of technical names for source and target elements in the mapper tree and for expressions in the Expression Builder.This eliminates the need to try and understand the technical, often cryptic, names that are difficult to correlate to the user-friendly display names you see in the endpoint application's user interface.User-friendly names are displayed by default, but you can also toggle to the technical names.Toggle Between User-Friendly Names and Technical Names Adapter Names Root Elements in Source and Target Trees Child Elements in Source and Target Trees Search For Data in the Source and Target Trees User-Friendly Expression for Mapping Expression Builder Other Sections of the User Interface Toggle Between User-Friendly Names and Technical Names By default, user-friendly names are displayed in the source and target mapper trees when you open the mapper.Name display is controlled by the button at the top of the mapper.Chapter 1 View User-Friendly Element Names 1-4 1.Click to switch to technical names.The button changes colors to blue and technical names for the source and target elements are displayed.2.Click to switch back to user-friendly names.Adapter Names In user-friendly mode, adapter names are displayed along with the adapter's associated icon and the type of payload (request/response).For this example, the source REST Adapter and Oracle Commerce Cloud Adapter and the target REST Adapter are displayed.1.Click to switch to technical names.The adapter names are removed.Chapter 1 View User-Friendly Element Names 1-5 Root Elements in Source and Target Trees User-friendly names for the root elements of the different payloads enable you to easily correlate them with the associated invoke/trigger connection, the adapter used, and the type of payload (request/response).The icon of the root element corresponds to the associated adapter. |
View User-Friendly Element Names You can view user-friendly display names instead of technical names for source and target elements in the mapper tree and for expressions in the Expression Builder.This eliminates the need to try and understand the technical, often cryptic, names that are difficult to correlate to the user-friendly display names you see in the endpoint application's user interface.User-friendly names are displayed by default, but you can also toggle to the technical names.Toggle Between User-Friendly Names and Technical Names Adapter Names Root Elements in Source and Target Trees Child Elements in Source and Target Trees Search For Data in the Source and Target Trees User-Friendly Expression for Mapping Expression Builder Other Sections of the User Interface Toggle Between User-Friendly Names and Technical Names By default, user-friendly names are displayed in the source and target mapper trees when you open the mapper.Name display is controlled by the button at the top of the mapper.Chapter 1 View User-Friendly Element Names 1-4 1.Click to switch to technical names.The button changes colors to blue and technical names for the source and target elements are displayed.2.Click to switch back to user-friendly names.Adapter Names In user-friendly mode, adapter names are displayed along with the adapter's associated icon and the type of payload (request/response).For this example, the source REST Adapter and Oracle Commerce Cloud Adapter and the target REST Adapter are displayed.1.Click to switch to technical names.The adapter names are removed.Chapter 1 View User-Friendly Element Names 1-5 Root Elements in Source and Target Trees User-friendly names for the root elements of the different payloads enable you to easily correlate them with the associated invoke/trigger connection, the adapter used, and the type of payload (request/response).The icon of the root element corresponds to the associated adapter.The format of user-friendly names for the root elements differs based on the variable type or the associated adapter. |
This eliminates the need to try and understand the technical, often cryptic, names that are difficult to correlate to the user-friendly display names you see in the endpoint application's user interface.User-friendly names are displayed by default, but you can also toggle to the technical names.Toggle Between User-Friendly Names and Technical Names Adapter Names Root Elements in Source and Target Trees Child Elements in Source and Target Trees Search For Data in the Source and Target Trees User-Friendly Expression for Mapping Expression Builder Other Sections of the User Interface Toggle Between User-Friendly Names and Technical Names By default, user-friendly names are displayed in the source and target mapper trees when you open the mapper.Name display is controlled by the button at the top of the mapper.Chapter 1 View User-Friendly Element Names 1-4 1.Click to switch to technical names.The button changes colors to blue and technical names for the source and target elements are displayed.2.Click to switch back to user-friendly names.Adapter Names In user-friendly mode, adapter names are displayed along with the adapter's associated icon and the type of payload (request/response).For this example, the source REST Adapter and Oracle Commerce Cloud Adapter and the target REST Adapter are displayed.1.Click to switch to technical names.The adapter names are removed.Chapter 1 View User-Friendly Element Names 1-5 Root Elements in Source and Target Trees User-friendly names for the root elements of the different payloads enable you to easily correlate them with the associated invoke/trigger connection, the adapter used, and the type of payload (request/response).The icon of the root element corresponds to the associated adapter.The format of user-friendly names for the root elements differs based on the variable type or the associated adapter.The following table lists the format of user-friendly names for the root elements for different variable types. |
User-friendly names are displayed by default, but you can also toggle to the technical names.Toggle Between User-Friendly Names and Technical Names Adapter Names Root Elements in Source and Target Trees Child Elements in Source and Target Trees Search For Data in the Source and Target Trees User-Friendly Expression for Mapping Expression Builder Other Sections of the User Interface Toggle Between User-Friendly Names and Technical Names By default, user-friendly names are displayed in the source and target mapper trees when you open the mapper.Name display is controlled by the button at the top of the mapper.Chapter 1 View User-Friendly Element Names 1-4 1.Click to switch to technical names.The button changes colors to blue and technical names for the source and target elements are displayed.2.Click to switch back to user-friendly names.Adapter Names In user-friendly mode, adapter names are displayed along with the adapter's associated icon and the type of payload (request/response).For this example, the source REST Adapter and Oracle Commerce Cloud Adapter and the target REST Adapter are displayed.1.Click to switch to technical names.The adapter names are removed.Chapter 1 View User-Friendly Element Names 1-5 Root Elements in Source and Target Trees User-friendly names for the root elements of the different payloads enable you to easily correlate them with the associated invoke/trigger connection, the adapter used, and the type of payload (request/response).The icon of the root element corresponds to the associated adapter.The format of user-friendly names for the root elements differs based on the variable type or the associated adapter.The following table lists the format of user-friendly names for the root elements for different variable types.Adapter/Variable Type Format of User-Friendly NameExample Application Adapter trigger/invoke_action_name payload_type (request/ response) (Associated_Adapter_Name )SendInventoryAdjustments Request (SOAP) System Adapter See the Example column. |
Toggle Between User-Friendly Names and Technical Names Adapter Names Root Elements in Source and Target Trees Child Elements in Source and Target Trees Search For Data in the Source and Target Trees User-Friendly Expression for Mapping Expression Builder Other Sections of the User Interface Toggle Between User-Friendly Names and Technical Names By default, user-friendly names are displayed in the source and target mapper trees when you open the mapper.Name display is controlled by the button at the top of the mapper.Chapter 1 View User-Friendly Element Names 1-4 1.Click to switch to technical names.The button changes colors to blue and technical names for the source and target elements are displayed.2.Click to switch back to user-friendly names.Adapter Names In user-friendly mode, adapter names are displayed along with the adapter's associated icon and the type of payload (request/response).For this example, the source REST Adapter and Oracle Commerce Cloud Adapter and the target REST Adapter are displayed.1.Click to switch to technical names.The adapter names are removed.Chapter 1 View User-Friendly Element Names 1-5 Root Elements in Source and Target Trees User-friendly names for the root elements of the different payloads enable you to easily correlate them with the associated invoke/trigger connection, the adapter used, and the type of payload (request/response).The icon of the root element corresponds to the associated adapter.The format of user-friendly names for the root elements differs based on the variable type or the associated adapter.The following table lists the format of user-friendly names for the root elements for different variable types.Adapter/Variable Type Format of User-Friendly NameExample Application Adapter trigger/invoke_action_name payload_type (request/ response) (Associated_Adapter_Name )SendInventoryAdjustments Request (SOAP) System Adapter See the Example column.Schedule - Schedule $self (for technical mode) or Integration Metadata (for user- friendly mode) Tracking Variables If a user-friendly name is entered for the tracking variable in the Business Identifiers For Tracking page, that becomes the user-friendly name for the variable in the mapper. |
Name display is controlled by the button at the top of the mapper.Chapter 1 View User-Friendly Element Names 1-4 1.Click to switch to technical names.The button changes colors to blue and technical names for the source and target elements are displayed.2.Click to switch back to user-friendly names.Adapter Names In user-friendly mode, adapter names are displayed along with the adapter's associated icon and the type of payload (request/response).For this example, the source REST Adapter and Oracle Commerce Cloud Adapter and the target REST Adapter are displayed.1.Click to switch to technical names.The adapter names are removed.Chapter 1 View User-Friendly Element Names 1-5 Root Elements in Source and Target Trees User-friendly names for the root elements of the different payloads enable you to easily correlate them with the associated invoke/trigger connection, the adapter used, and the type of payload (request/response).The icon of the root element corresponds to the associated adapter.The format of user-friendly names for the root elements differs based on the variable type or the associated adapter.The following table lists the format of user-friendly names for the root elements for different variable types.Adapter/Variable Type Format of User-Friendly NameExample Application Adapter trigger/invoke_action_name payload_type (request/ response) (Associated_Adapter_Name )SendInventoryAdjustments Request (SOAP) System Adapter See the Example column.Schedule - Schedule $self (for technical mode) or Integration Metadata (for user- friendly mode) Tracking Variables If a user-friendly name is entered for the tracking variable in the Business Identifiers For Tracking page, that becomes the user-friendly name for the variable in the mapper.If the Tracking Name field in the Business Identifiers For Tracking page is not populated for the variable, the system constructs the user-friendly name for the tracking variable in the format of Tracking Variable 1/2/3.My Business Identifier Tracking Variable 1 Tracking Variable 2 Tracking Variable 3 Other Variables For all other variables (that is, simple variables and the root element of the complex variables), the user-friendly name is automatically constructed using the name with which the variable was created (without the $ prefix).counter studentNameChapter 1 View User-Friendly Element Names 1-6Child Elements in Source and Target Trees The user-friendly names for the child elements in the source and target trees are derived from the associated schema files. |
Chapter 1 View User-Friendly Element Names 1-4 1.Click to switch to technical names.The button changes colors to blue and technical names for the source and target elements are displayed.2.Click to switch back to user-friendly names.Adapter Names In user-friendly mode, adapter names are displayed along with the adapter's associated icon and the type of payload (request/response).For this example, the source REST Adapter and Oracle Commerce Cloud Adapter and the target REST Adapter are displayed.1.Click to switch to technical names.The adapter names are removed.Chapter 1 View User-Friendly Element Names 1-5 Root Elements in Source and Target Trees User-friendly names for the root elements of the different payloads enable you to easily correlate them with the associated invoke/trigger connection, the adapter used, and the type of payload (request/response).The icon of the root element corresponds to the associated adapter.The format of user-friendly names for the root elements differs based on the variable type or the associated adapter.The following table lists the format of user-friendly names for the root elements for different variable types.Adapter/Variable Type Format of User-Friendly NameExample Application Adapter trigger/invoke_action_name payload_type (request/ response) (Associated_Adapter_Name )SendInventoryAdjustments Request (SOAP) System Adapter See the Example column.Schedule - Schedule $self (for technical mode) or Integration Metadata (for user- friendly mode) Tracking Variables If a user-friendly name is entered for the tracking variable in the Business Identifiers For Tracking page, that becomes the user-friendly name for the variable in the mapper.If the Tracking Name field in the Business Identifiers For Tracking page is not populated for the variable, the system constructs the user-friendly name for the tracking variable in the format of Tracking Variable 1/2/3.My Business Identifier Tracking Variable 1 Tracking Variable 2 Tracking Variable 3 Other Variables For all other variables (that is, simple variables and the root element of the complex variables), the user-friendly name is automatically constructed using the name with which the variable was created (without the $ prefix).counter studentNameChapter 1 View User-Friendly Element Names 1-6Child Elements in Source and Target Trees The user-friendly names for the child elements in the source and target trees are derived from the associated schema files.If the schema files are generated with user-friendly names for the elements, the elements get rendered with those names in user-friendly mode in the mapper. |
The button changes colors to blue and technical names for the source and target elements are displayed.2.Click to switch back to user-friendly names.Adapter Names In user-friendly mode, adapter names are displayed along with the adapter's associated icon and the type of payload (request/response).For this example, the source REST Adapter and Oracle Commerce Cloud Adapter and the target REST Adapter are displayed.1.Click to switch to technical names.The adapter names are removed.Chapter 1 View User-Friendly Element Names 1-5 Root Elements in Source and Target Trees User-friendly names for the root elements of the different payloads enable you to easily correlate them with the associated invoke/trigger connection, the adapter used, and the type of payload (request/response).The icon of the root element corresponds to the associated adapter.The format of user-friendly names for the root elements differs based on the variable type or the associated adapter.The following table lists the format of user-friendly names for the root elements for different variable types.Adapter/Variable Type Format of User-Friendly NameExample Application Adapter trigger/invoke_action_name payload_type (request/ response) (Associated_Adapter_Name )SendInventoryAdjustments Request (SOAP) System Adapter See the Example column.Schedule - Schedule $self (for technical mode) or Integration Metadata (for user- friendly mode) Tracking Variables If a user-friendly name is entered for the tracking variable in the Business Identifiers For Tracking page, that becomes the user-friendly name for the variable in the mapper.If the Tracking Name field in the Business Identifiers For Tracking page is not populated for the variable, the system constructs the user-friendly name for the tracking variable in the format of Tracking Variable 1/2/3.My Business Identifier Tracking Variable 1 Tracking Variable 2 Tracking Variable 3 Other Variables For all other variables (that is, simple variables and the root element of the complex variables), the user-friendly name is automatically constructed using the name with which the variable was created (without the $ prefix).counter studentNameChapter 1 View User-Friendly Element Names 1-6Child Elements in Source and Target Trees The user-friendly names for the child elements in the source and target trees are derived from the associated schema files.If the schema files are generated with user-friendly names for the elements, the elements get rendered with those names in user-friendly mode in the mapper.If the schema files do not contain user-friendly names for the elements defined, the child elements are displayed with the technical name in both user-friendly mode and technical mode. |
2.Click to switch back to user-friendly names.Adapter Names In user-friendly mode, adapter names are displayed along with the adapter's associated icon and the type of payload (request/response).For this example, the source REST Adapter and Oracle Commerce Cloud Adapter and the target REST Adapter are displayed.1.Click to switch to technical names.The adapter names are removed.Chapter 1 View User-Friendly Element Names 1-5 Root Elements in Source and Target Trees User-friendly names for the root elements of the different payloads enable you to easily correlate them with the associated invoke/trigger connection, the adapter used, and the type of payload (request/response).The icon of the root element corresponds to the associated adapter.The format of user-friendly names for the root elements differs based on the variable type or the associated adapter.The following table lists the format of user-friendly names for the root elements for different variable types.Adapter/Variable Type Format of User-Friendly NameExample Application Adapter trigger/invoke_action_name payload_type (request/ response) (Associated_Adapter_Name )SendInventoryAdjustments Request (SOAP) System Adapter See the Example column.Schedule - Schedule $self (for technical mode) or Integration Metadata (for user- friendly mode) Tracking Variables If a user-friendly name is entered for the tracking variable in the Business Identifiers For Tracking page, that becomes the user-friendly name for the variable in the mapper.If the Tracking Name field in the Business Identifiers For Tracking page is not populated for the variable, the system constructs the user-friendly name for the tracking variable in the format of Tracking Variable 1/2/3.My Business Identifier Tracking Variable 1 Tracking Variable 2 Tracking Variable 3 Other Variables For all other variables (that is, simple variables and the root element of the complex variables), the user-friendly name is automatically constructed using the name with which the variable was created (without the $ prefix).counter studentNameChapter 1 View User-Friendly Element Names 1-6Child Elements in Source and Target Trees The user-friendly names for the child elements in the source and target trees are derived from the associated schema files.If the schema files are generated with user-friendly names for the elements, the elements get rendered with those names in user-friendly mode in the mapper.If the schema files do not contain user-friendly names for the elements defined, the child elements are displayed with the technical name in both user-friendly mode and technical mode.Figure 1-1 Child Elements Shown with User-Friendly Names Chapter 1 View User-Friendly Element Names 1-7Figure 1-2 Child Elements Shown with Technical Names The attributes of the schema elements are rendered with the @ prefix followed by the attribute name in the mapper. |
Adapter Names In user-friendly mode, adapter names are displayed along with the adapter's associated icon and the type of payload (request/response).For this example, the source REST Adapter and Oracle Commerce Cloud Adapter and the target REST Adapter are displayed.1.Click to switch to technical names.The adapter names are removed.Chapter 1 View User-Friendly Element Names 1-5 Root Elements in Source and Target Trees User-friendly names for the root elements of the different payloads enable you to easily correlate them with the associated invoke/trigger connection, the adapter used, and the type of payload (request/response).The icon of the root element corresponds to the associated adapter.The format of user-friendly names for the root elements differs based on the variable type or the associated adapter.The following table lists the format of user-friendly names for the root elements for different variable types.Adapter/Variable Type Format of User-Friendly NameExample Application Adapter trigger/invoke_action_name payload_type (request/ response) (Associated_Adapter_Name )SendInventoryAdjustments Request (SOAP) System Adapter See the Example column.Schedule - Schedule $self (for technical mode) or Integration Metadata (for user- friendly mode) Tracking Variables If a user-friendly name is entered for the tracking variable in the Business Identifiers For Tracking page, that becomes the user-friendly name for the variable in the mapper.If the Tracking Name field in the Business Identifiers For Tracking page is not populated for the variable, the system constructs the user-friendly name for the tracking variable in the format of Tracking Variable 1/2/3.My Business Identifier Tracking Variable 1 Tracking Variable 2 Tracking Variable 3 Other Variables For all other variables (that is, simple variables and the root element of the complex variables), the user-friendly name is automatically constructed using the name with which the variable was created (without the $ prefix).counter studentNameChapter 1 View User-Friendly Element Names 1-6Child Elements in Source and Target Trees The user-friendly names for the child elements in the source and target trees are derived from the associated schema files.If the schema files are generated with user-friendly names for the elements, the elements get rendered with those names in user-friendly mode in the mapper.If the schema files do not contain user-friendly names for the elements defined, the child elements are displayed with the technical name in both user-friendly mode and technical mode.Figure 1-1 Child Elements Shown with User-Friendly Names Chapter 1 View User-Friendly Element Names 1-7Figure 1-2 Child Elements Shown with Technical Names The attributes of the schema elements are rendered with the @ prefix followed by the attribute name in the mapper.With user-friendly names, the @ prefix is not appended to the front of the name or in user-friendly mode. |
For this example, the source REST Adapter and Oracle Commerce Cloud Adapter and the target REST Adapter are displayed.1.Click to switch to technical names.The adapter names are removed.Chapter 1 View User-Friendly Element Names 1-5 Root Elements in Source and Target Trees User-friendly names for the root elements of the different payloads enable you to easily correlate them with the associated invoke/trigger connection, the adapter used, and the type of payload (request/response).The icon of the root element corresponds to the associated adapter.The format of user-friendly names for the root elements differs based on the variable type or the associated adapter.The following table lists the format of user-friendly names for the root elements for different variable types.Adapter/Variable Type Format of User-Friendly NameExample Application Adapter trigger/invoke_action_name payload_type (request/ response) (Associated_Adapter_Name )SendInventoryAdjustments Request (SOAP) System Adapter See the Example column.Schedule - Schedule $self (for technical mode) or Integration Metadata (for user- friendly mode) Tracking Variables If a user-friendly name is entered for the tracking variable in the Business Identifiers For Tracking page, that becomes the user-friendly name for the variable in the mapper.If the Tracking Name field in the Business Identifiers For Tracking page is not populated for the variable, the system constructs the user-friendly name for the tracking variable in the format of Tracking Variable 1/2/3.My Business Identifier Tracking Variable 1 Tracking Variable 2 Tracking Variable 3 Other Variables For all other variables (that is, simple variables and the root element of the complex variables), the user-friendly name is automatically constructed using the name with which the variable was created (without the $ prefix).counter studentNameChapter 1 View User-Friendly Element Names 1-6Child Elements in Source and Target Trees The user-friendly names for the child elements in the source and target trees are derived from the associated schema files.If the schema files are generated with user-friendly names for the elements, the elements get rendered with those names in user-friendly mode in the mapper.If the schema files do not contain user-friendly names for the elements defined, the child elements are displayed with the technical name in both user-friendly mode and technical mode.Figure 1-1 Child Elements Shown with User-Friendly Names Chapter 1 View User-Friendly Element Names 1-7Figure 1-2 Child Elements Shown with Technical Names The attributes of the schema elements are rendered with the @ prefix followed by the attribute name in the mapper.With user-friendly names, the @ prefix is not appended to the front of the name or in user-friendly mode.In technical mode, the attributes are shown appended with the @ prefix. |
1.Click to switch to technical names.The adapter names are removed.Chapter 1 View User-Friendly Element Names 1-5 Root Elements in Source and Target Trees User-friendly names for the root elements of the different payloads enable you to easily correlate them with the associated invoke/trigger connection, the adapter used, and the type of payload (request/response).The icon of the root element corresponds to the associated adapter.The format of user-friendly names for the root elements differs based on the variable type or the associated adapter.The following table lists the format of user-friendly names for the root elements for different variable types.Adapter/Variable Type Format of User-Friendly NameExample Application Adapter trigger/invoke_action_name payload_type (request/ response) (Associated_Adapter_Name )SendInventoryAdjustments Request (SOAP) System Adapter See the Example column.Schedule - Schedule $self (for technical mode) or Integration Metadata (for user- friendly mode) Tracking Variables If a user-friendly name is entered for the tracking variable in the Business Identifiers For Tracking page, that becomes the user-friendly name for the variable in the mapper.If the Tracking Name field in the Business Identifiers For Tracking page is not populated for the variable, the system constructs the user-friendly name for the tracking variable in the format of Tracking Variable 1/2/3.My Business Identifier Tracking Variable 1 Tracking Variable 2 Tracking Variable 3 Other Variables For all other variables (that is, simple variables and the root element of the complex variables), the user-friendly name is automatically constructed using the name with which the variable was created (without the $ prefix).counter studentNameChapter 1 View User-Friendly Element Names 1-6Child Elements in Source and Target Trees The user-friendly names for the child elements in the source and target trees are derived from the associated schema files.If the schema files are generated with user-friendly names for the elements, the elements get rendered with those names in user-friendly mode in the mapper.If the schema files do not contain user-friendly names for the elements defined, the child elements are displayed with the technical name in both user-friendly mode and technical mode.Figure 1-1 Child Elements Shown with User-Friendly Names Chapter 1 View User-Friendly Element Names 1-7Figure 1-2 Child Elements Shown with Technical Names The attributes of the schema elements are rendered with the @ prefix followed by the attribute name in the mapper.With user-friendly names, the @ prefix is not appended to the front of the name or in user-friendly mode.In technical mode, the attributes are shown appended with the @ prefix.User-friendly names do not include the namespace prefix. |
The adapter names are removed.Chapter 1 View User-Friendly Element Names 1-5 Root Elements in Source and Target Trees User-friendly names for the root elements of the different payloads enable you to easily correlate them with the associated invoke/trigger connection, the adapter used, and the type of payload (request/response).The icon of the root element corresponds to the associated adapter.The format of user-friendly names for the root elements differs based on the variable type or the associated adapter.The following table lists the format of user-friendly names for the root elements for different variable types.Adapter/Variable Type Format of User-Friendly NameExample Application Adapter trigger/invoke_action_name payload_type (request/ response) (Associated_Adapter_Name )SendInventoryAdjustments Request (SOAP) System Adapter See the Example column.Schedule - Schedule $self (for technical mode) or Integration Metadata (for user- friendly mode) Tracking Variables If a user-friendly name is entered for the tracking variable in the Business Identifiers For Tracking page, that becomes the user-friendly name for the variable in the mapper.If the Tracking Name field in the Business Identifiers For Tracking page is not populated for the variable, the system constructs the user-friendly name for the tracking variable in the format of Tracking Variable 1/2/3.My Business Identifier Tracking Variable 1 Tracking Variable 2 Tracking Variable 3 Other Variables For all other variables (that is, simple variables and the root element of the complex variables), the user-friendly name is automatically constructed using the name with which the variable was created (without the $ prefix).counter studentNameChapter 1 View User-Friendly Element Names 1-6Child Elements in Source and Target Trees The user-friendly names for the child elements in the source and target trees are derived from the associated schema files.If the schema files are generated with user-friendly names for the elements, the elements get rendered with those names in user-friendly mode in the mapper.If the schema files do not contain user-friendly names for the elements defined, the child elements are displayed with the technical name in both user-friendly mode and technical mode.Figure 1-1 Child Elements Shown with User-Friendly Names Chapter 1 View User-Friendly Element Names 1-7Figure 1-2 Child Elements Shown with Technical Names The attributes of the schema elements are rendered with the @ prefix followed by the attribute name in the mapper.With user-friendly names, the @ prefix is not appended to the front of the name or in user-friendly mode.In technical mode, the attributes are shown appended with the @ prefix.User-friendly names do not include the namespace prefix.The option to view element names with the prefix Show prefixes available in the View menu of the mapper is disabled when the mapper is in user-friendly mode. |
Chapter 1 View User-Friendly Element Names 1-5 Root Elements in Source and Target Trees User-friendly names for the root elements of the different payloads enable you to easily correlate them with the associated invoke/trigger connection, the adapter used, and the type of payload (request/response).The icon of the root element corresponds to the associated adapter.The format of user-friendly names for the root elements differs based on the variable type or the associated adapter.The following table lists the format of user-friendly names for the root elements for different variable types.Adapter/Variable Type Format of User-Friendly NameExample Application Adapter trigger/invoke_action_name payload_type (request/ response) (Associated_Adapter_Name )SendInventoryAdjustments Request (SOAP) System Adapter See the Example column.Schedule - Schedule $self (for technical mode) or Integration Metadata (for user- friendly mode) Tracking Variables If a user-friendly name is entered for the tracking variable in the Business Identifiers For Tracking page, that becomes the user-friendly name for the variable in the mapper.If the Tracking Name field in the Business Identifiers For Tracking page is not populated for the variable, the system constructs the user-friendly name for the tracking variable in the format of Tracking Variable 1/2/3.My Business Identifier Tracking Variable 1 Tracking Variable 2 Tracking Variable 3 Other Variables For all other variables (that is, simple variables and the root element of the complex variables), the user-friendly name is automatically constructed using the name with which the variable was created (without the $ prefix).counter studentNameChapter 1 View User-Friendly Element Names 1-6Child Elements in Source and Target Trees The user-friendly names for the child elements in the source and target trees are derived from the associated schema files.If the schema files are generated with user-friendly names for the elements, the elements get rendered with those names in user-friendly mode in the mapper.If the schema files do not contain user-friendly names for the elements defined, the child elements are displayed with the technical name in both user-friendly mode and technical mode.Figure 1-1 Child Elements Shown with User-Friendly Names Chapter 1 View User-Friendly Element Names 1-7Figure 1-2 Child Elements Shown with Technical Names The attributes of the schema elements are rendered with the @ prefix followed by the attribute name in the mapper.With user-friendly names, the @ prefix is not appended to the front of the name or in user-friendly mode.In technical mode, the attributes are shown appended with the @ prefix.User-friendly names do not include the namespace prefix.The option to view element names with the prefix Show prefixes available in the View menu of the mapper is disabled when the mapper is in user-friendly mode.The option is enabled once you switch to technical mode. |
The icon of the root element corresponds to the associated adapter.The format of user-friendly names for the root elements differs based on the variable type or the associated adapter.The following table lists the format of user-friendly names for the root elements for different variable types.Adapter/Variable Type Format of User-Friendly NameExample Application Adapter trigger/invoke_action_name payload_type (request/ response) (Associated_Adapter_Name )SendInventoryAdjustments Request (SOAP) System Adapter See the Example column.Schedule - Schedule $self (for technical mode) or Integration Metadata (for user- friendly mode) Tracking Variables If a user-friendly name is entered for the tracking variable in the Business Identifiers For Tracking page, that becomes the user-friendly name for the variable in the mapper.If the Tracking Name field in the Business Identifiers For Tracking page is not populated for the variable, the system constructs the user-friendly name for the tracking variable in the format of Tracking Variable 1/2/3.My Business Identifier Tracking Variable 1 Tracking Variable 2 Tracking Variable 3 Other Variables For all other variables (that is, simple variables and the root element of the complex variables), the user-friendly name is automatically constructed using the name with which the variable was created (without the $ prefix).counter studentNameChapter 1 View User-Friendly Element Names 1-6Child Elements in Source and Target Trees The user-friendly names for the child elements in the source and target trees are derived from the associated schema files.If the schema files are generated with user-friendly names for the elements, the elements get rendered with those names in user-friendly mode in the mapper.If the schema files do not contain user-friendly names for the elements defined, the child elements are displayed with the technical name in both user-friendly mode and technical mode.Figure 1-1 Child Elements Shown with User-Friendly Names Chapter 1 View User-Friendly Element Names 1-7Figure 1-2 Child Elements Shown with Technical Names The attributes of the schema elements are rendered with the @ prefix followed by the attribute name in the mapper.With user-friendly names, the @ prefix is not appended to the front of the name or in user-friendly mode.In technical mode, the attributes are shown appended with the @ prefix.User-friendly names do not include the namespace prefix.The option to view element names with the prefix Show prefixes available in the View menu of the mapper is disabled when the mapper is in user-friendly mode.The option is enabled once you switch to technical mode.Search For Data in the Source and Target Trees The source and target trees can be searched with the element name in either user- friendly mode or technical mode. |
The format of user-friendly names for the root elements differs based on the variable type or the associated adapter.The following table lists the format of user-friendly names for the root elements for different variable types.Adapter/Variable Type Format of User-Friendly NameExample Application Adapter trigger/invoke_action_name payload_type (request/ response) (Associated_Adapter_Name )SendInventoryAdjustments Request (SOAP) System Adapter See the Example column.Schedule - Schedule $self (for technical mode) or Integration Metadata (for user- friendly mode) Tracking Variables If a user-friendly name is entered for the tracking variable in the Business Identifiers For Tracking page, that becomes the user-friendly name for the variable in the mapper.If the Tracking Name field in the Business Identifiers For Tracking page is not populated for the variable, the system constructs the user-friendly name for the tracking variable in the format of Tracking Variable 1/2/3.My Business Identifier Tracking Variable 1 Tracking Variable 2 Tracking Variable 3 Other Variables For all other variables (that is, simple variables and the root element of the complex variables), the user-friendly name is automatically constructed using the name with which the variable was created (without the $ prefix).counter studentNameChapter 1 View User-Friendly Element Names 1-6Child Elements in Source and Target Trees The user-friendly names for the child elements in the source and target trees are derived from the associated schema files.If the schema files are generated with user-friendly names for the elements, the elements get rendered with those names in user-friendly mode in the mapper.If the schema files do not contain user-friendly names for the elements defined, the child elements are displayed with the technical name in both user-friendly mode and technical mode.Figure 1-1 Child Elements Shown with User-Friendly Names Chapter 1 View User-Friendly Element Names 1-7Figure 1-2 Child Elements Shown with Technical Names The attributes of the schema elements are rendered with the @ prefix followed by the attribute name in the mapper.With user-friendly names, the @ prefix is not appended to the front of the name or in user-friendly mode.In technical mode, the attributes are shown appended with the @ prefix.User-friendly names do not include the namespace prefix.The option to view element names with the prefix Show prefixes available in the View menu of the mapper is disabled when the mapper is in user-friendly mode.The option is enabled once you switch to technical mode.Search For Data in the Source and Target Trees The source and target trees can be searched with the element name in either user- friendly mode or technical mode.For example, assume the mapper is in user-friendly mode and an element exists whose user-friendly name is BEG: Beginning Segment for Purchase Order and technical name is BegSegPO . |
The following table lists the format of user-friendly names for the root elements for different variable types.Adapter/Variable Type Format of User-Friendly NameExample Application Adapter trigger/invoke_action_name payload_type (request/ response) (Associated_Adapter_Name )SendInventoryAdjustments Request (SOAP) System Adapter See the Example column.Schedule - Schedule $self (for technical mode) or Integration Metadata (for user- friendly mode) Tracking Variables If a user-friendly name is entered for the tracking variable in the Business Identifiers For Tracking page, that becomes the user-friendly name for the variable in the mapper.If the Tracking Name field in the Business Identifiers For Tracking page is not populated for the variable, the system constructs the user-friendly name for the tracking variable in the format of Tracking Variable 1/2/3.My Business Identifier Tracking Variable 1 Tracking Variable 2 Tracking Variable 3 Other Variables For all other variables (that is, simple variables and the root element of the complex variables), the user-friendly name is automatically constructed using the name with which the variable was created (without the $ prefix).counter studentNameChapter 1 View User-Friendly Element Names 1-6Child Elements in Source and Target Trees The user-friendly names for the child elements in the source and target trees are derived from the associated schema files.If the schema files are generated with user-friendly names for the elements, the elements get rendered with those names in user-friendly mode in the mapper.If the schema files do not contain user-friendly names for the elements defined, the child elements are displayed with the technical name in both user-friendly mode and technical mode.Figure 1-1 Child Elements Shown with User-Friendly Names Chapter 1 View User-Friendly Element Names 1-7Figure 1-2 Child Elements Shown with Technical Names The attributes of the schema elements are rendered with the @ prefix followed by the attribute name in the mapper.With user-friendly names, the @ prefix is not appended to the front of the name or in user-friendly mode.In technical mode, the attributes are shown appended with the @ prefix.User-friendly names do not include the namespace prefix.The option to view element names with the prefix Show prefixes available in the View menu of the mapper is disabled when the mapper is in user-friendly mode.The option is enabled once you switch to technical mode.Search For Data in the Source and Target Trees The source and target trees can be searched with the element name in either user- friendly mode or technical mode.For example, assume the mapper is in user-friendly mode and an element exists whose user-friendly name is BEG: Beginning Segment for Purchase Order and technical name is BegSegPO .If SegPO is the search string used to search for the element, the search highlights the element irrespective of your current mode.Chapter 1 View User-Friendly Element Names 1-8User-Friendly Expression for Mapping Just as the source and target element technical names are simplified by their user-friendly names, the mapping expression created is represented in a simplified form. |
Adapter/Variable Type Format of User-Friendly NameExample Application Adapter trigger/invoke_action_name payload_type (request/ response) (Associated_Adapter_Name )SendInventoryAdjustments Request (SOAP) System Adapter See the Example column.Schedule - Schedule $self (for technical mode) or Integration Metadata (for user- friendly mode) Tracking Variables If a user-friendly name is entered for the tracking variable in the Business Identifiers For Tracking page, that becomes the user-friendly name for the variable in the mapper.If the Tracking Name field in the Business Identifiers For Tracking page is not populated for the variable, the system constructs the user-friendly name for the tracking variable in the format of Tracking Variable 1/2/3.My Business Identifier Tracking Variable 1 Tracking Variable 2 Tracking Variable 3 Other Variables For all other variables (that is, simple variables and the root element of the complex variables), the user-friendly name is automatically constructed using the name with which the variable was created (without the $ prefix).counter studentNameChapter 1 View User-Friendly Element Names 1-6Child Elements in Source and Target Trees The user-friendly names for the child elements in the source and target trees are derived from the associated schema files.If the schema files are generated with user-friendly names for the elements, the elements get rendered with those names in user-friendly mode in the mapper.If the schema files do not contain user-friendly names for the elements defined, the child elements are displayed with the technical name in both user-friendly mode and technical mode.Figure 1-1 Child Elements Shown with User-Friendly Names Chapter 1 View User-Friendly Element Names 1-7Figure 1-2 Child Elements Shown with Technical Names The attributes of the schema elements are rendered with the @ prefix followed by the attribute name in the mapper.With user-friendly names, the @ prefix is not appended to the front of the name or in user-friendly mode.In technical mode, the attributes are shown appended with the @ prefix.User-friendly names do not include the namespace prefix.The option to view element names with the prefix Show prefixes available in the View menu of the mapper is disabled when the mapper is in user-friendly mode.The option is enabled once you switch to technical mode.Search For Data in the Source and Target Trees The source and target trees can be searched with the element name in either user- friendly mode or technical mode.For example, assume the mapper is in user-friendly mode and an element exists whose user-friendly name is BEG: Beginning Segment for Purchase Order and technical name is BegSegPO .If SegPO is the search string used to search for the element, the search highlights the element irrespective of your current mode.Chapter 1 View User-Friendly Element Names 1-8User-Friendly Expression for Mapping Just as the source and target element technical names are simplified by their user-friendly names, the mapping expression created is represented in a simplified form.This is a user interface-only entity. |
Schedule - Schedule $self (for technical mode) or Integration Metadata (for user- friendly mode) Tracking Variables If a user-friendly name is entered for the tracking variable in the Business Identifiers For Tracking page, that becomes the user-friendly name for the variable in the mapper.If the Tracking Name field in the Business Identifiers For Tracking page is not populated for the variable, the system constructs the user-friendly name for the tracking variable in the format of Tracking Variable 1/2/3.My Business Identifier Tracking Variable 1 Tracking Variable 2 Tracking Variable 3 Other Variables For all other variables (that is, simple variables and the root element of the complex variables), the user-friendly name is automatically constructed using the name with which the variable was created (without the $ prefix).counter studentNameChapter 1 View User-Friendly Element Names 1-6Child Elements in Source and Target Trees The user-friendly names for the child elements in the source and target trees are derived from the associated schema files.If the schema files are generated with user-friendly names for the elements, the elements get rendered with those names in user-friendly mode in the mapper.If the schema files do not contain user-friendly names for the elements defined, the child elements are displayed with the technical name in both user-friendly mode and technical mode.Figure 1-1 Child Elements Shown with User-Friendly Names Chapter 1 View User-Friendly Element Names 1-7Figure 1-2 Child Elements Shown with Technical Names The attributes of the schema elements are rendered with the @ prefix followed by the attribute name in the mapper.With user-friendly names, the @ prefix is not appended to the front of the name or in user-friendly mode.In technical mode, the attributes are shown appended with the @ prefix.User-friendly names do not include the namespace prefix.The option to view element names with the prefix Show prefixes available in the View menu of the mapper is disabled when the mapper is in user-friendly mode.The option is enabled once you switch to technical mode.Search For Data in the Source and Target Trees The source and target trees can be searched with the element name in either user- friendly mode or technical mode.For example, assume the mapper is in user-friendly mode and an element exists whose user-friendly name is BEG: Beginning Segment for Purchase Order and technical name is BegSegPO .If SegPO is the search string used to search for the element, the search highlights the element irrespective of your current mode.Chapter 1 View User-Friendly Element Names 1-8User-Friendly Expression for Mapping Just as the source and target element technical names are simplified by their user-friendly names, the mapping expression created is represented in a simplified form.This is a user interface-only entity.That is, the user friendly expression for a mapping is displayed in the mapper. |
If the Tracking Name field in the Business Identifiers For Tracking page is not populated for the variable, the system constructs the user-friendly name for the tracking variable in the format of Tracking Variable 1/2/3.My Business Identifier Tracking Variable 1 Tracking Variable 2 Tracking Variable 3 Other Variables For all other variables (that is, simple variables and the root element of the complex variables), the user-friendly name is automatically constructed using the name with which the variable was created (without the $ prefix).counter studentNameChapter 1 View User-Friendly Element Names 1-6Child Elements in Source and Target Trees The user-friendly names for the child elements in the source and target trees are derived from the associated schema files.If the schema files are generated with user-friendly names for the elements, the elements get rendered with those names in user-friendly mode in the mapper.If the schema files do not contain user-friendly names for the elements defined, the child elements are displayed with the technical name in both user-friendly mode and technical mode.Figure 1-1 Child Elements Shown with User-Friendly Names Chapter 1 View User-Friendly Element Names 1-7Figure 1-2 Child Elements Shown with Technical Names The attributes of the schema elements are rendered with the @ prefix followed by the attribute name in the mapper.With user-friendly names, the @ prefix is not appended to the front of the name or in user-friendly mode.In technical mode, the attributes are shown appended with the @ prefix.User-friendly names do not include the namespace prefix.The option to view element names with the prefix Show prefixes available in the View menu of the mapper is disabled when the mapper is in user-friendly mode.The option is enabled once you switch to technical mode.Search For Data in the Source and Target Trees The source and target trees can be searched with the element name in either user- friendly mode or technical mode.For example, assume the mapper is in user-friendly mode and an element exists whose user-friendly name is BEG: Beginning Segment for Purchase Order and technical name is BegSegPO .If SegPO is the search string used to search for the element, the search highlights the element irrespective of your current mode.Chapter 1 View User-Friendly Element Names 1-8User-Friendly Expression for Mapping Just as the source and target element technical names are simplified by their user-friendly names, the mapping expression created is represented in a simplified form.This is a user interface-only entity.That is, the user friendly expression for a mapping is displayed in the mapper.However, it does not get saved in the XSL file. |
If the schema files are generated with user-friendly names for the elements, the elements get rendered with those names in user-friendly mode in the mapper.If the schema files do not contain user-friendly names for the elements defined, the child elements are displayed with the technical name in both user-friendly mode and technical mode.Figure 1-1 Child Elements Shown with User-Friendly Names Chapter 1 View User-Friendly Element Names 1-7Figure 1-2 Child Elements Shown with Technical Names The attributes of the schema elements are rendered with the @ prefix followed by the attribute name in the mapper.With user-friendly names, the @ prefix is not appended to the front of the name or in user-friendly mode.In technical mode, the attributes are shown appended with the @ prefix.User-friendly names do not include the namespace prefix.The option to view element names with the prefix Show prefixes available in the View menu of the mapper is disabled when the mapper is in user-friendly mode.The option is enabled once you switch to technical mode.Search For Data in the Source and Target Trees The source and target trees can be searched with the element name in either user- friendly mode or technical mode.For example, assume the mapper is in user-friendly mode and an element exists whose user-friendly name is BEG: Beginning Segment for Purchase Order and technical name is BegSegPO .If SegPO is the search string used to search for the element, the search highlights the element irrespective of your current mode.Chapter 1 View User-Friendly Element Names 1-8User-Friendly Expression for Mapping Just as the source and target element technical names are simplified by their user-friendly names, the mapping expression created is represented in a simplified form.This is a user interface-only entity.That is, the user friendly expression for a mapping is displayed in the mapper.However, it does not get saved in the XSL file.Click the Code tab of the mapper after creating a mapping. |
If the schema files do not contain user-friendly names for the elements defined, the child elements are displayed with the technical name in both user-friendly mode and technical mode.Figure 1-1 Child Elements Shown with User-Friendly Names Chapter 1 View User-Friendly Element Names 1-7Figure 1-2 Child Elements Shown with Technical Names The attributes of the schema elements are rendered with the @ prefix followed by the attribute name in the mapper.With user-friendly names, the @ prefix is not appended to the front of the name or in user-friendly mode.In technical mode, the attributes are shown appended with the @ prefix.User-friendly names do not include the namespace prefix.The option to view element names with the prefix Show prefixes available in the View menu of the mapper is disabled when the mapper is in user-friendly mode.The option is enabled once you switch to technical mode.Search For Data in the Source and Target Trees The source and target trees can be searched with the element name in either user- friendly mode or technical mode.For example, assume the mapper is in user-friendly mode and an element exists whose user-friendly name is BEG: Beginning Segment for Purchase Order and technical name is BegSegPO .If SegPO is the search string used to search for the element, the search highlights the element irrespective of your current mode.Chapter 1 View User-Friendly Element Names 1-8User-Friendly Expression for Mapping Just as the source and target element technical names are simplified by their user-friendly names, the mapping expression created is represented in a simplified form.This is a user interface-only entity.That is, the user friendly expression for a mapping is displayed in the mapper.However, it does not get saved in the XSL file.Click the Code tab of the mapper after creating a mapping.The Code tab shows the XSL file that is generated behind the scenes. |
Figure 1-1 Child Elements Shown with User-Friendly Names Chapter 1 View User-Friendly Element Names 1-7Figure 1-2 Child Elements Shown with Technical Names The attributes of the schema elements are rendered with the @ prefix followed by the attribute name in the mapper.With user-friendly names, the @ prefix is not appended to the front of the name or in user-friendly mode.In technical mode, the attributes are shown appended with the @ prefix.User-friendly names do not include the namespace prefix.The option to view element names with the prefix Show prefixes available in the View menu of the mapper is disabled when the mapper is in user-friendly mode.The option is enabled once you switch to technical mode.Search For Data in the Source and Target Trees The source and target trees can be searched with the element name in either user- friendly mode or technical mode.For example, assume the mapper is in user-friendly mode and an element exists whose user-friendly name is BEG: Beginning Segment for Purchase Order and technical name is BegSegPO .If SegPO is the search string used to search for the element, the search highlights the element irrespective of your current mode.Chapter 1 View User-Friendly Element Names 1-8User-Friendly Expression for Mapping Just as the source and target element technical names are simplified by their user-friendly names, the mapping expression created is represented in a simplified form.This is a user interface-only entity.That is, the user friendly expression for a mapping is displayed in the mapper.However, it does not get saved in the XSL file.Click the Code tab of the mapper after creating a mapping.The Code tab shows the XSL file that is generated behind the scenes.Note that the file contains only the technical mapping, and not the user- friendly expression. |
With user-friendly names, the @ prefix is not appended to the front of the name or in user-friendly mode.In technical mode, the attributes are shown appended with the @ prefix.User-friendly names do not include the namespace prefix.The option to view element names with the prefix Show prefixes available in the View menu of the mapper is disabled when the mapper is in user-friendly mode.The option is enabled once you switch to technical mode.Search For Data in the Source and Target Trees The source and target trees can be searched with the element name in either user- friendly mode or technical mode.For example, assume the mapper is in user-friendly mode and an element exists whose user-friendly name is BEG: Beginning Segment for Purchase Order and technical name is BegSegPO .If SegPO is the search string used to search for the element, the search highlights the element irrespective of your current mode.Chapter 1 View User-Friendly Element Names 1-8User-Friendly Expression for Mapping Just as the source and target element technical names are simplified by their user-friendly names, the mapping expression created is represented in a simplified form.This is a user interface-only entity.That is, the user friendly expression for a mapping is displayed in the mapper.However, it does not get saved in the XSL file.Click the Code tab of the mapper after creating a mapping.The Code tab shows the XSL file that is generated behind the scenes.Note that the file contains only the technical mapping, and not the user- friendly expression.The mappings work as they always have at runtime. |
In technical mode, the attributes are shown appended with the @ prefix.User-friendly names do not include the namespace prefix.The option to view element names with the prefix Show prefixes available in the View menu of the mapper is disabled when the mapper is in user-friendly mode.The option is enabled once you switch to technical mode.Search For Data in the Source and Target Trees The source and target trees can be searched with the element name in either user- friendly mode or technical mode.For example, assume the mapper is in user-friendly mode and an element exists whose user-friendly name is BEG: Beginning Segment for Purchase Order and technical name is BegSegPO .If SegPO is the search string used to search for the element, the search highlights the element irrespective of your current mode.Chapter 1 View User-Friendly Element Names 1-8User-Friendly Expression for Mapping Just as the source and target element technical names are simplified by their user-friendly names, the mapping expression created is represented in a simplified form.This is a user interface-only entity.That is, the user friendly expression for a mapping is displayed in the mapper.However, it does not get saved in the XSL file.Click the Code tab of the mapper after creating a mapping.The Code tab shows the XSL file that is generated behind the scenes.Note that the file contains only the technical mapping, and not the user- friendly expression.The mappings work as they always have at runtime.At design time, the mapper displays the mappings as user-friendly expressions in user-friendly mode and as technical expressions in technical mode. |
User-friendly names do not include the namespace prefix.The option to view element names with the prefix Show prefixes available in the View menu of the mapper is disabled when the mapper is in user-friendly mode.The option is enabled once you switch to technical mode.Search For Data in the Source and Target Trees The source and target trees can be searched with the element name in either user- friendly mode or technical mode.For example, assume the mapper is in user-friendly mode and an element exists whose user-friendly name is BEG: Beginning Segment for Purchase Order and technical name is BegSegPO .If SegPO is the search string used to search for the element, the search highlights the element irrespective of your current mode.Chapter 1 View User-Friendly Element Names 1-8User-Friendly Expression for Mapping Just as the source and target element technical names are simplified by their user-friendly names, the mapping expression created is represented in a simplified form.This is a user interface-only entity.That is, the user friendly expression for a mapping is displayed in the mapper.However, it does not get saved in the XSL file.Click the Code tab of the mapper after creating a mapping.The Code tab shows the XSL file that is generated behind the scenes.Note that the file contains only the technical mapping, and not the user- friendly expression.The mappings work as they always have at runtime.At design time, the mapper displays the mappings as user-friendly expressions in user-friendly mode and as technical expressions in technical mode.The user-friendly expression for a mapping is created when a mapping is constructed in the mapper. |
The option to view element names with the prefix Show prefixes available in the View menu of the mapper is disabled when the mapper is in user-friendly mode.The option is enabled once you switch to technical mode.Search For Data in the Source and Target Trees The source and target trees can be searched with the element name in either user- friendly mode or technical mode.For example, assume the mapper is in user-friendly mode and an element exists whose user-friendly name is BEG: Beginning Segment for Purchase Order and technical name is BegSegPO .If SegPO is the search string used to search for the element, the search highlights the element irrespective of your current mode.Chapter 1 View User-Friendly Element Names 1-8User-Friendly Expression for Mapping Just as the source and target element technical names are simplified by their user-friendly names, the mapping expression created is represented in a simplified form.This is a user interface-only entity.That is, the user friendly expression for a mapping is displayed in the mapper.However, it does not get saved in the XSL file.Click the Code tab of the mapper after creating a mapping.The Code tab shows the XSL file that is generated behind the scenes.Note that the file contains only the technical mapping, and not the user- friendly expression.The mappings work as they always have at runtime.At design time, the mapper displays the mappings as user-friendly expressions in user-friendly mode and as technical expressions in technical mode.The user-friendly expression for a mapping is created when a mapping is constructed in the mapper.The user-friendly expression is created based on the user-friendly name for the components in the mapping. |
The option is enabled once you switch to technical mode.Search For Data in the Source and Target Trees The source and target trees can be searched with the element name in either user- friendly mode or technical mode.For example, assume the mapper is in user-friendly mode and an element exists whose user-friendly name is BEG: Beginning Segment for Purchase Order and technical name is BegSegPO .If SegPO is the search string used to search for the element, the search highlights the element irrespective of your current mode.Chapter 1 View User-Friendly Element Names 1-8User-Friendly Expression for Mapping Just as the source and target element technical names are simplified by their user-friendly names, the mapping expression created is represented in a simplified form.This is a user interface-only entity.That is, the user friendly expression for a mapping is displayed in the mapper.However, it does not get saved in the XSL file.Click the Code tab of the mapper after creating a mapping.The Code tab shows the XSL file that is generated behind the scenes.Note that the file contains only the technical mapping, and not the user- friendly expression.The mappings work as they always have at runtime.At design time, the mapper displays the mappings as user-friendly expressions in user-friendly mode and as technical expressions in technical mode.The user-friendly expression for a mapping is created when a mapping is constructed in the mapper.The user-friendly expression is created based on the user-friendly name for the components in the mapping.Consider the following mapping: concat( $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ ns31:translation-status, $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking- info) This mapping refers to a concat function whose parameters are two elements from the payload. |
Search For Data in the Source and Target Trees The source and target trees can be searched with the element name in either user- friendly mode or technical mode.For example, assume the mapper is in user-friendly mode and an element exists whose user-friendly name is BEG: Beginning Segment for Purchase Order and technical name is BegSegPO .If SegPO is the search string used to search for the element, the search highlights the element irrespective of your current mode.Chapter 1 View User-Friendly Element Names 1-8User-Friendly Expression for Mapping Just as the source and target element technical names are simplified by their user-friendly names, the mapping expression created is represented in a simplified form.This is a user interface-only entity.That is, the user friendly expression for a mapping is displayed in the mapper.However, it does not get saved in the XSL file.Click the Code tab of the mapper after creating a mapping.The Code tab shows the XSL file that is generated behind the scenes.Note that the file contains only the technical mapping, and not the user- friendly expression.The mappings work as they always have at runtime.At design time, the mapper displays the mappings as user-friendly expressions in user-friendly mode and as technical expressions in technical mode.The user-friendly expression for a mapping is created when a mapping is constructed in the mapper.The user-friendly expression is created based on the user-friendly name for the components in the mapping.Consider the following mapping: concat( $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ ns31:translation-status, $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking- info) This mapping refers to a concat function whose parameters are two elements from the payload.The user-friendly expression for this mapping is as follows: concat( translation-status, tracking-info) where: translation-status is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:translation-status tracking-info is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking-info Expression Builder When you navigate to the mapper, the Expression Builder launches in user-friendly mode by default when you select a target element. |
For example, assume the mapper is in user-friendly mode and an element exists whose user-friendly name is BEG: Beginning Segment for Purchase Order and technical name is BegSegPO .If SegPO is the search string used to search for the element, the search highlights the element irrespective of your current mode.Chapter 1 View User-Friendly Element Names 1-8User-Friendly Expression for Mapping Just as the source and target element technical names are simplified by their user-friendly names, the mapping expression created is represented in a simplified form.This is a user interface-only entity.That is, the user friendly expression for a mapping is displayed in the mapper.However, it does not get saved in the XSL file.Click the Code tab of the mapper after creating a mapping.The Code tab shows the XSL file that is generated behind the scenes.Note that the file contains only the technical mapping, and not the user- friendly expression.The mappings work as they always have at runtime.At design time, the mapper displays the mappings as user-friendly expressions in user-friendly mode and as technical expressions in technical mode.The user-friendly expression for a mapping is created when a mapping is constructed in the mapper.The user-friendly expression is created based on the user-friendly name for the components in the mapping.Consider the following mapping: concat( $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ ns31:translation-status, $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking- info) This mapping refers to a concat function whose parameters are two elements from the payload.The user-friendly expression for this mapping is as follows: concat( translation-status, tracking-info) where: translation-status is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:translation-status tracking-info is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking-info Expression Builder When you navigate to the mapper, the Expression Builder launches in user-friendly mode by default when you select a target element.The Expression Builder shows the mapping for the target element selected. |
If SegPO is the search string used to search for the element, the search highlights the element irrespective of your current mode.Chapter 1 View User-Friendly Element Names 1-8User-Friendly Expression for Mapping Just as the source and target element technical names are simplified by their user-friendly names, the mapping expression created is represented in a simplified form.This is a user interface-only entity.That is, the user friendly expression for a mapping is displayed in the mapper.However, it does not get saved in the XSL file.Click the Code tab of the mapper after creating a mapping.The Code tab shows the XSL file that is generated behind the scenes.Note that the file contains only the technical mapping, and not the user- friendly expression.The mappings work as they always have at runtime.At design time, the mapper displays the mappings as user-friendly expressions in user-friendly mode and as technical expressions in technical mode.The user-friendly expression for a mapping is created when a mapping is constructed in the mapper.The user-friendly expression is created based on the user-friendly name for the components in the mapping.Consider the following mapping: concat( $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ ns31:translation-status, $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking- info) This mapping refers to a concat function whose parameters are two elements from the payload.The user-friendly expression for this mapping is as follows: concat( translation-status, tracking-info) where: translation-status is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:translation-status tracking-info is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking-info Expression Builder When you navigate to the mapper, the Expression Builder launches in user-friendly mode by default when you select a target element.The Expression Builder shows the mapping for the target element selected.As with the mapper, the Expression Builder also has two modes. |
This is a user interface-only entity.That is, the user friendly expression for a mapping is displayed in the mapper.However, it does not get saved in the XSL file.Click the Code tab of the mapper after creating a mapping.The Code tab shows the XSL file that is generated behind the scenes.Note that the file contains only the technical mapping, and not the user- friendly expression.The mappings work as they always have at runtime.At design time, the mapper displays the mappings as user-friendly expressions in user-friendly mode and as technical expressions in technical mode.The user-friendly expression for a mapping is created when a mapping is constructed in the mapper.The user-friendly expression is created based on the user-friendly name for the components in the mapping.Consider the following mapping: concat( $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ ns31:translation-status, $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking- info) This mapping refers to a concat function whose parameters are two elements from the payload.The user-friendly expression for this mapping is as follows: concat( translation-status, tracking-info) where: translation-status is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:translation-status tracking-info is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking-info Expression Builder When you navigate to the mapper, the Expression Builder launches in user-friendly mode by default when you select a target element.The Expression Builder shows the mapping for the target element selected.As with the mapper, the Expression Builder also has two modes.User-friendly mode shows the mapping as a user-friendly expression. |
That is, the user friendly expression for a mapping is displayed in the mapper.However, it does not get saved in the XSL file.Click the Code tab of the mapper after creating a mapping.The Code tab shows the XSL file that is generated behind the scenes.Note that the file contains only the technical mapping, and not the user- friendly expression.The mappings work as they always have at runtime.At design time, the mapper displays the mappings as user-friendly expressions in user-friendly mode and as technical expressions in technical mode.The user-friendly expression for a mapping is created when a mapping is constructed in the mapper.The user-friendly expression is created based on the user-friendly name for the components in the mapping.Consider the following mapping: concat( $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ ns31:translation-status, $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking- info) This mapping refers to a concat function whose parameters are two elements from the payload.The user-friendly expression for this mapping is as follows: concat( translation-status, tracking-info) where: translation-status is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:translation-status tracking-info is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking-info Expression Builder When you navigate to the mapper, the Expression Builder launches in user-friendly mode by default when you select a target element.The Expression Builder shows the mapping for the target element selected.As with the mapper, the Expression Builder also has two modes.User-friendly mode shows the mapping as a user-friendly expression.Figure 1-3 User-Friendly Names in Expression Builder Chapter 1 View User-Friendly Element Names 1-9To toggle the Expression Builder between the two modes, click the toggle button available on the right side of the Expression Builder. |
However, it does not get saved in the XSL file.Click the Code tab of the mapper after creating a mapping.The Code tab shows the XSL file that is generated behind the scenes.Note that the file contains only the technical mapping, and not the user- friendly expression.The mappings work as they always have at runtime.At design time, the mapper displays the mappings as user-friendly expressions in user-friendly mode and as technical expressions in technical mode.The user-friendly expression for a mapping is created when a mapping is constructed in the mapper.The user-friendly expression is created based on the user-friendly name for the components in the mapping.Consider the following mapping: concat( $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ ns31:translation-status, $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking- info) This mapping refers to a concat function whose parameters are two elements from the payload.The user-friendly expression for this mapping is as follows: concat( translation-status, tracking-info) where: translation-status is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:translation-status tracking-info is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking-info Expression Builder When you navigate to the mapper, the Expression Builder launches in user-friendly mode by default when you select a target element.The Expression Builder shows the mapping for the target element selected.As with the mapper, the Expression Builder also has two modes.User-friendly mode shows the mapping as a user-friendly expression.Figure 1-3 User-Friendly Names in Expression Builder Chapter 1 View User-Friendly Element Names 1-9To toggle the Expression Builder between the two modes, click the toggle button available on the right side of the Expression Builder.You can manually edit the existing mapping in the Expression Builder. |
Click the Code tab of the mapper after creating a mapping.The Code tab shows the XSL file that is generated behind the scenes.Note that the file contains only the technical mapping, and not the user- friendly expression.The mappings work as they always have at runtime.At design time, the mapper displays the mappings as user-friendly expressions in user-friendly mode and as technical expressions in technical mode.The user-friendly expression for a mapping is created when a mapping is constructed in the mapper.The user-friendly expression is created based on the user-friendly name for the components in the mapping.Consider the following mapping: concat( $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ ns31:translation-status, $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking- info) This mapping refers to a concat function whose parameters are two elements from the payload.The user-friendly expression for this mapping is as follows: concat( translation-status, tracking-info) where: translation-status is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:translation-status tracking-info is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking-info Expression Builder When you navigate to the mapper, the Expression Builder launches in user-friendly mode by default when you select a target element.The Expression Builder shows the mapping for the target element selected.As with the mapper, the Expression Builder also has two modes.User-friendly mode shows the mapping as a user-friendly expression.Figure 1-3 User-Friendly Names in Expression Builder Chapter 1 View User-Friendly Element Names 1-9To toggle the Expression Builder between the two modes, click the toggle button available on the right side of the Expression Builder.You can manually edit the existing mapping in the Expression Builder.Figure 1-4 Technical Names in the Expression Builder Other Sections of the User Interface Other sections of the mapper in which the source and target elements are displayed all show the names in synchronization with the mode that is selected for the mapper (user-friendly or technical). |
The Code tab shows the XSL file that is generated behind the scenes.Note that the file contains only the technical mapping, and not the user- friendly expression.The mappings work as they always have at runtime.At design time, the mapper displays the mappings as user-friendly expressions in user-friendly mode and as technical expressions in technical mode.The user-friendly expression for a mapping is created when a mapping is constructed in the mapper.The user-friendly expression is created based on the user-friendly name for the components in the mapping.Consider the following mapping: concat( $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ ns31:translation-status, $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking- info) This mapping refers to a concat function whose parameters are two elements from the payload.The user-friendly expression for this mapping is as follows: concat( translation-status, tracking-info) where: translation-status is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:translation-status tracking-info is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking-info Expression Builder When you navigate to the mapper, the Expression Builder launches in user-friendly mode by default when you select a target element.The Expression Builder shows the mapping for the target element selected.As with the mapper, the Expression Builder also has two modes.User-friendly mode shows the mapping as a user-friendly expression.Figure 1-3 User-Friendly Names in Expression Builder Chapter 1 View User-Friendly Element Names 1-9To toggle the Expression Builder between the two modes, click the toggle button available on the right side of the Expression Builder.You can manually edit the existing mapping in the Expression Builder.Figure 1-4 Technical Names in the Expression Builder Other Sections of the User Interface Other sections of the mapper in which the source and target elements are displayed all show the names in synchronization with the mode that is selected for the mapper (user-friendly or technical).For example: The Test button (where the root elements of each source are displayed as the headers of the tabs) The Filter button (where one of the options to filter the tree data is by source name, which shows the root elements of the different sources) This means that if the mapper is in user-friendly mode, these sections of the user interface also show the user-friendly names of the elements. |
Note that the file contains only the technical mapping, and not the user- friendly expression.The mappings work as they always have at runtime.At design time, the mapper displays the mappings as user-friendly expressions in user-friendly mode and as technical expressions in technical mode.The user-friendly expression for a mapping is created when a mapping is constructed in the mapper.The user-friendly expression is created based on the user-friendly name for the components in the mapping.Consider the following mapping: concat( $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ ns31:translation-status, $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking- info) This mapping refers to a concat function whose parameters are two elements from the payload.The user-friendly expression for this mapping is as follows: concat( translation-status, tracking-info) where: translation-status is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:translation-status tracking-info is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking-info Expression Builder When you navigate to the mapper, the Expression Builder launches in user-friendly mode by default when you select a target element.The Expression Builder shows the mapping for the target element selected.As with the mapper, the Expression Builder also has two modes.User-friendly mode shows the mapping as a user-friendly expression.Figure 1-3 User-Friendly Names in Expression Builder Chapter 1 View User-Friendly Element Names 1-9To toggle the Expression Builder between the two modes, click the toggle button available on the right side of the Expression Builder.You can manually edit the existing mapping in the Expression Builder.Figure 1-4 Technical Names in the Expression Builder Other Sections of the User Interface Other sections of the mapper in which the source and target elements are displayed all show the names in synchronization with the mode that is selected for the mapper (user-friendly or technical).For example: The Test button (where the root elements of each source are displayed as the headers of the tabs) The Filter button (where one of the options to filter the tree data is by source name, which shows the root elements of the different sources) This means that if the mapper is in user-friendly mode, these sections of the user interface also show the user-friendly names of the elements.If the mapper is in technical mode, these sections show the technical names of the elements. |
The mappings work as they always have at runtime.At design time, the mapper displays the mappings as user-friendly expressions in user-friendly mode and as technical expressions in technical mode.The user-friendly expression for a mapping is created when a mapping is constructed in the mapper.The user-friendly expression is created based on the user-friendly name for the components in the mapping.Consider the following mapping: concat( $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ ns31:translation-status, $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking- info) This mapping refers to a concat function whose parameters are two elements from the payload.The user-friendly expression for this mapping is as follows: concat( translation-status, tracking-info) where: translation-status is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:translation-status tracking-info is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking-info Expression Builder When you navigate to the mapper, the Expression Builder launches in user-friendly mode by default when you select a target element.The Expression Builder shows the mapping for the target element selected.As with the mapper, the Expression Builder also has two modes.User-friendly mode shows the mapping as a user-friendly expression.Figure 1-3 User-Friendly Names in Expression Builder Chapter 1 View User-Friendly Element Names 1-9To toggle the Expression Builder between the two modes, click the toggle button available on the right side of the Expression Builder.You can manually edit the existing mapping in the Expression Builder.Figure 1-4 Technical Names in the Expression Builder Other Sections of the User Interface Other sections of the mapper in which the source and target elements are displayed all show the names in synchronization with the mode that is selected for the mapper (user-friendly or technical).For example: The Test button (where the root elements of each source are displayed as the headers of the tabs) The Filter button (where one of the options to filter the tree data is by source name, which shows the root elements of the different sources) This means that if the mapper is in user-friendly mode, these sections of the user interface also show the user-friendly names of the elements.If the mapper is in technical mode, these sections show the technical names of the elements.About the Expression Builder Use the Expression Builder to view and edit your XPath expressions. |
At design time, the mapper displays the mappings as user-friendly expressions in user-friendly mode and as technical expressions in technical mode.The user-friendly expression for a mapping is created when a mapping is constructed in the mapper.The user-friendly expression is created based on the user-friendly name for the components in the mapping.Consider the following mapping: concat( $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ ns31:translation-status, $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking- info) This mapping refers to a concat function whose parameters are two elements from the payload.The user-friendly expression for this mapping is as follows: concat( translation-status, tracking-info) where: translation-status is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:translation-status tracking-info is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking-info Expression Builder When you navigate to the mapper, the Expression Builder launches in user-friendly mode by default when you select a target element.The Expression Builder shows the mapping for the target element selected.As with the mapper, the Expression Builder also has two modes.User-friendly mode shows the mapping as a user-friendly expression.Figure 1-3 User-Friendly Names in Expression Builder Chapter 1 View User-Friendly Element Names 1-9To toggle the Expression Builder between the two modes, click the toggle button available on the right side of the Expression Builder.You can manually edit the existing mapping in the Expression Builder.Figure 1-4 Technical Names in the Expression Builder Other Sections of the User Interface Other sections of the mapper in which the source and target elements are displayed all show the names in synchronization with the mode that is selected for the mapper (user-friendly or technical).For example: The Test button (where the root elements of each source are displayed as the headers of the tabs) The Filter button (where one of the options to filter the tree data is by source name, which shows the root elements of the different sources) This means that if the mapper is in user-friendly mode, these sections of the user interface also show the user-friendly names of the elements.If the mapper is in technical mode, these sections show the technical names of the elements.About the Expression Builder Use the Expression Builder to view and edit your XPath expressions.This section provides an overview of the Expression Builder. |
The user-friendly expression for a mapping is created when a mapping is constructed in the mapper.The user-friendly expression is created based on the user-friendly name for the components in the mapping.Consider the following mapping: concat( $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ ns31:translation-status, $EDI-Translate/nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking- info) This mapping refers to a concat function whose parameters are two elements from the payload.The user-friendly expression for this mapping is as follows: concat( translation-status, tracking-info) where: translation-status is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:translation-status tracking-info is the user-friendly name of the element $EDI-Translate/ nsmpr0:executeResponse/ns31:TranslateOutput/ns31:tracking-info Expression Builder When you navigate to the mapper, the Expression Builder launches in user-friendly mode by default when you select a target element.The Expression Builder shows the mapping for the target element selected.As with the mapper, the Expression Builder also has two modes.User-friendly mode shows the mapping as a user-friendly expression.Figure 1-3 User-Friendly Names in Expression Builder Chapter 1 View User-Friendly Element Names 1-9To toggle the Expression Builder between the two modes, click the toggle button available on the right side of the Expression Builder.You can manually edit the existing mapping in the Expression Builder.Figure 1-4 Technical Names in the Expression Builder Other Sections of the User Interface Other sections of the mapper in which the source and target elements are displayed all show the names in synchronization with the mode that is selected for the mapper (user-friendly or technical).For example: The Test button (where the root elements of each source are displayed as the headers of the tabs) The Filter button (where one of the options to filter the tree data is by source name, which shows the root elements of the different sources) This means that if the mapper is in user-friendly mode, these sections of the user interface also show the user-friendly names of the elements.If the mapper is in technical mode, these sections show the technical names of the elements.About the Expression Builder Use the Expression Builder to view and edit your XPath expressions.This section provides an overview of the Expression Builder.Displaying the Expression Builder 1.Click a target element node. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.