In the CRM Enterprise Search Workbench (trx. CRM_ES_WB) you can model templates and associate them with each other. In release WEBCUIF 7.0 SP01, only certain fields of linked external templates are taken automatically into account. These are:
- Fields of technical templates are automatically added as request and response fields, if they are directly linked to the business template.
- All request fields of external templates are merged into the requests of a template. This is obviously too much.
- Only the first level of external template links is included. This is too little.
In WEBCUIF 7.0 EhP1 the CRM Enterprise Search Workbench has been enhanced so as to cater for the above mentioned points. The template owner will be able to include request and response attributes of external templates into his model. The automatic mapping described under point 1 will be discontinued. The modeling will provide:
- The ability to add attributes of external templates (one-by-one) as request or response attributes. Therefore the template owner can decide which fields of external templates are required for the business case.
- The ability to include external template attributes regardless of the nesting level. Therefore the template owner can navigate, say, from his template, A, to template C via template B so as to include certain attributes of template C to A.
The following diagram illustrates both points: Template A is linked to template B with a external relation; template B is linked to template C with another external relation.
This development is valid from release WEBCUIF 7.0 EhP1.
The WEBCUIF component enables the application developer to model Enterprise Search Templates (i.e. search objects) directly from BOL. Here is a screenshot from the CRM Enterprise Search Workbench (trx. CRM_ES_WB).
Internal relations connect two nodes of the same template. In the following screenshot BOL relation CarrierConnectionRel is modeled. It connects nodes UIFCarrier and UIFConnection.
External Relations - Implicit Attribute Modeling
External relations connect two nodes of different templates. In the following example BOL relation ConnectionCarrierRel is modelled. It connects node UIFConnection with external node UIFCarrier. UIFCarrier corresponds to two templates AT and UW. The effect is as follows:
- All request attributes of business templates are taken over to template AT_ULI_SET3.
- All request and response attributes of technical templates are taken over to template AT_ULI_SET3.
This is termed implicit external attribute modelling (WEBCUIF 7.0).
External Relations - Explicit Attribute Modelling
With WEBCUIF EhP1 it is possible to explicitly select the attributes of templates modelled with a external relation. In the following example the same BOL relation ConnectionCarrierRel is modelled with the difference that the attributes of template 'AT' are explicitly selected. The effect is that only the selected request attributes and all response attributes are taken over to template AT_ULI_SET3. This is termed explicit external attribute modelling.
Defining Modeling Depth of External Relations
Using the Customizing activity 'Define Modeling Depth of External Relations' you specify the level of depth by which you can reference external templates. The following example shows the underlying database view (CRMD_ES_ACT_FUNC) in which the level of depth is set to 2 for template AT_ULI_SET3. Note that setting the level to greater than 1 is subject to authorization. For further details see view documentation in IMG.