Generic Integration Framework to Support ASB Interface - Revision history

WikiSysop at 14:11, 16 February 2022

2022-02-16T14:11:53Z

Show changes

IDT-1 at 08:02, 21 December 2021

2021-12-21T08:02:48Z

WikiSysop at 04:15, 21 December 2021

2021-12-21T04:15:17Z

Show changes

IDT-1 at 12:18, 15 December 2021

2021-12-15T12:18:32Z

Show changes

IDT-1 at 12:15, 15 December 2021

2021-12-15T12:15:00Z

IDT-1 at 09:27, 18 September 2020

2020-09-18T09:27:57Z

WikiSysop at 12:41, 12 September 2020

2020-09-12T12:41:19Z

IDT-1 at 04:07, 22 July 2020

2020-07-22T04:07:16Z

IDT-1 at 04:06, 22 July 2020

2020-07-22T04:06:41Z

IDT-1 at 04:04, 22 July 2020

2020-07-22T04:04:55Z

@@ Line 2: / Line 2: @@
 = Generic Integration Framework to Support ASB Interface =
-Azure Service Bus (ASB) is a fully managed enterprise integration message broker. Data is transferred between different applications and services using messages. The ICM-ASB adapter considers the approach based on REST and OData principles that exposes a uniform, stateless interface which communicates using HTTP(S) and JSON payloads.
+Azure Service Bus (ASB) is a fully managed enterprise integration message broker. Data is transferred between different applications and services using messages. The ICI-ASB adapter considers the approach based on REST and OData principles that exposes a uniform, stateless interface which communicates using HTTP(S) and JSON payloads.
 == Configuring ASB adapter to load Masterdata&nbsp; ==
-The ICM support for generic integration provides the ability to synchronize ICM Masterdata tables using the input from ASB. Through a technical configuration, you can specify the attributes to be used for this generic integration.
+The ICI support for generic integration provides the ability to synchronize ICI Masterdata tables using the input from ASB. Through a technical configuration, you can specify the attributes to be used for this generic integration.
 === Create Masterdata Contract Type ===
-To enable synchronization between ICM and ASB, a Masterdata Contract Type should first be configured in ICM, with specific attributes for the integration. To create a Masterdata Contract Type:
+To enable synchronization between ICI and ASB, a Masterdata Contract Type should first be configured in ICI, with specific attributes for the integration. To create a Masterdata Contract Type:
 #'''Click '''Contract Type&nbsp; menu from the Configure&nbsp;tile. The Select Contract Type page opens.
@@ Line 31: / Line 31: @@
 === Client App Cross Reference ===
-The Client App Cross Reference mapping maps ICM entities (for example, ICM attributes) to client app entities.
+The Client App Cross Reference mapping maps ICI entities (for example, ICI attributes) to client app entities.
-#Navigate to the Create Masterdata page in ICM. This page contains the following tabs:
+#Navigate to the Create Masterdata page in ICI. This page contains the following tabs:
 <div class="image-green-border">[[File:GIF 4.png|600px|GIF 4.png]]</div> <div class="image-green-border">&nbsp;</div>
 ==== Masterdata Details ====
 .&nbsp;&nbsp; &nbsp;Select the Category from the drop-down. For example, Default.<br/> 2.&nbsp;&nbsp; &nbsp;Select the Masterdata Contract Type.
-<div class="note-box">'''Note''': In order to map ICM entities with entities in the file uploaded through ASB, you must select Client App Cross Reference from the drop-down.</div>
+<div class="note-box">'''Note''': In order to map ICI entities with entities in the file uploaded through ASB, you must select Client App Cross Reference from the drop-down.</div>
 .&nbsp;&nbsp; &nbsp;Click Next. The Attributes page opens.
 ==== Attributes ====
-#Enter the relevant attribute values. For example, enter ICM Entity Name as ICMSupplierMaster and Client Entity Name as SupplierMaster. The Payload Type can be selected as JSON.
+#Enter the relevant attribute values. For example, enter ICI Entity Name as ICISupplierMaster and Client Entity Name as SupplierMaster. The Payload Type can be selected as JSON.
-<div class="note-box">'''Note''': The Client Name GenerICMntegration must be selected. To create mapping using ASB, select Messaging in the Integration Mode drop-down. You need to select a Task Category for Messaging, either Scheduled or EventBased as required.</div> <ol start="2">
+<div class="note-box">'''Note''': The Client Name GenerICIntegration must be selected. To create mapping using ASB, select Messaging in the Integration Mode drop-down. You need to select a Task Category for Messaging, either Scheduled or EventBased as required.</div> <ol start="2">
 <li>'''Click '''Save to save the entity mapping.</li>
 </ol>
@@ Line 50: / Line 50: @@
 === Client App Entity Mapping ===
-The Client App Entity Mapping maps ICM attributes (for example, attribute names used in Supplier Master) to attributes in the file uploaded through ASB.
+The Client App Entity Mapping maps ICI attributes (for example, attribute names used in Supplier Master) to attributes in the file uploaded through ASB.
-#Navigate to theCreate Masterdata page in ICM. This page contains the following tabs:
+#Navigate to theCreate Masterdata page in ICI. This page contains the following tabs:
 <div class="image-green-border">[[File:GIF 7.png|600px|GIF 7.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div>
 ==== Masterdata Details ====
@@ Line 58: / Line 58: @@
 #Select the Category from the drop-down. For example, Default.
 #Select the Masterdata Contract Type.
-<div class="note-box">'''Note''': In order to map ICM attributes with attributes uploaded through ASB, Client App Entity Mapping must be selected from the drop-down.</div> <ol start="3">
+<div class="note-box">'''Note''': In order to map ICI attributes with attributes uploaded through ASB, Client App Entity Mapping must be selected from the drop-down.</div> <ol start="3">
 <li>Click Next. The Attributes page opens.</li>
 </ol>
@@ Line 64: / Line 64: @@
 ==== Attributes ====
-#'''Enter''' the relevant attribute values. For example, enter ICM&nbsp;Entity Name as ICMSupplierMaster and Client Entity Name as SupplierMaster.&nbsp;
+#'''Enter''' the relevant attribute values. For example, enter ICI&nbsp;Entity Name as ICISupplierMaster and Client Entity Name as SupplierMaster.&nbsp;
-To create mapping using ASB, select Messaging in the Integration Mode drop-down. The Client Name selected must be GenerICMntegration.
+To create mapping using ASB, select Messaging in the Integration Mode drop-down. The Client Name selected must be GenerICIntegration.
-In case of lookup and non-lookup attributes: The ICM Relationship Key should be set for lookup attributes and kept blank for non-lookup attributes. The Relationship Key framing should be <Master Contract Type Name> Double Underscore<ICM Attribute Name>. For example, in case of Supplier Master the ICM attribute name will be ICMSupplierCountry and the Masterdata Contract Type for this attribute will be ICMCountryMaster. Hence, relationship key will be ICMCountryMaster__ICMSupplierCountry.
+In case of lookup and non-lookup attributes: The ICI Relationship Key should be set for lookup attributes and kept blank for non-lookup attributes. The Relationship Key framing should be <Master Contract Type Name> Double Underscore<ICI Attribute Name>. For example, in case of Supplier Master the ICI attribute name will be ICISupplierCountry and the Masterdata Contract Type for this attribute will be ICICountryMaster. Hence, relationship key will be ICICountryMaster__ICISupplierCountry.
 <ol start="2">
 <li>'''Click&nbsp;&nbsp;'''CREATE&nbsp; to save the entity mapping.</li>
@@ Line 77: / Line 77: @@
 === Download Payload ===
-#Navigate to the Masterdata page in ICM.
+#Navigate to the Masterdata page in ICI.
 #'''Click''' the View Record icon next to the Client App Cross Reference entity you have created. The Masterdata Details page opens.
 <div class="image-green-border">[[File:GIF 9.png|600px|GIF 9.png]]</div> <div class="image-green-border">&nbsp;</div> <ol start="3">
@@ Line 103: / Line 103: @@
 === Updating Transaction Data&nbsp; ===
-To update transaction data from ICM using generic integration framework:
+To update transaction data from ICI using generic integration framework:
-#'''Edit''' the agreement in ICM with the desired values.
+#'''Edit''' the agreement in ICI with the desired values.
 #'''Click''' Update.
-'''Note''': For transaction data outbound, it is mandatory to select Data Flow Type as ICM to Client in the Client App Entity Mapping. The workflow action selected in Publish Transaction Data in Client App Cross Reference Mapping is the event at which transaction data will be updated. For example, if the values selected in this field are Approved and Updated, then the transaction data will be updated when these actions are taken on the agreement.
+'''Note''': For transaction data outbound, it is mandatory to select Data Flow Type as ICI to Client in the Client App Entity Mapping. The workflow action selected in Publish Transaction Data in Client App Cross Reference Mapping is the event at which transaction data will be updated. For example, if the values selected in this field are Approved and Updated, then the transaction data will be updated when these actions are taken on the agreement.
 &nbsp;
@@ Line 117: / Line 117: @@
 #'''Open''' Service Bus Explorer and go to the Service Bus Namespace.
-#Go to the generICMntegrationoutbound topic. Right-click and '''select '''Refresh Subscription from the drop-down.
+#Go to the generICIntegrationoutbound topic. Right-click and '''select '''Refresh Subscription from the drop-down.
 #'''Click '''Messages. The Retrieve messages from subscription window opens.
 #'''Select '''Peek radio button in the Receive Mode section.
@@ Line 124: / Line 124: @@
 The updated values are displayed in the Message Text.
 <ol start="6">
-<li>Check the Notifications Dashboard in ICM to view the success, failure and update notifications for outbound transaction data.</li>
+<li>Check the Notifications Dashboard in ICI to view the success, failure and update notifications for outbound transaction data.</li>
 </ol>

@@ Line 13: / Line 13: @@
 #'''Click '''''Create Contract Type'' sub menu from the ''Configuration ''tile. The ''Select Contract Type'' page opens.
-<div class="image-green-border">[[File:Generic Integration Framework ASB 01.png|620px|Generic Integration Framework ASB 01.png]]</div> <ol start="2">
+<div class="image-green-border">[[File:GIF1.png|500px]]</div> <ol start="2">
 <li>'''Select''' ''Masterdata''.</li>
 </ol>
-<div class="image-green-border">[[File:Generic Integration Framework ASB 02.png|420px|Generic Integration Framework ASB 02.png]]</div> <ol start="3">
+<div class="image-green-border">[[File:GIF 2.png|500px]]</div> <ol start="3">
 <li>'''Click '''the ''Next ''button. The ''Create Contract Type Wizard'' page opens.</li>
 </ol>
-<div class="image-green-border">[[File:Generic Integration Framework SFTP 03.png|520px|Generic Integration Framework SFTP 03.png]]</div> <ol start="3">
+<div class="image-green-border">[[File:GIF 3.png|550px]]</div> <ol start="3">
 <li>The ''Create Contract Type ''page has the following sections:</li>
 </ol>
@@ Line 34: / Line 34: @@
 #Navigate to the ''Create Masterdata'' page in ICI. This page contains the following tabs:
-<div class="image-green-border">[[File:Generic Integration Framework ASB 04.png|520px|Generic Integration Framework ASB 04.png]]</div>
+<div class="image-green-border">[[File:GIF 4.png|600px]]</div>
 ==== Masterdata Details ====
@@ Line 47: / Line 47: @@
 <li>'''Click '''''Save'' to save the entity mapping.</li>
 </ol>
-<div class="image-green-border">[[File:Generic Integration Framework ASB 05.png|520px|Generic Integration Framework ASB 05.png]]</div>
+<div class="image-green-border">[[File:GIF 5.png|600px]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">[[File:GIF 6.png|600px]]</div> <div class="image-green-border">&nbsp;</div>
 === Client App Entity Mapping ===
@@ Line 53: / Line 53: @@
 #Navigate to the''Create Masterdata'' page in ICI. This page contains the following tabs:
-<div class="image-green-border">[[File:Generic Integration Framework ASB 06.png|520px|Generic Integration Framework ASB 06.png]]</div>
+<div class="image-green-border">[[File:GIF 7.png|600px]]</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div> <div class="image-green-border">&nbsp;</div>
 ==== Masterdata Details ====
@@ Line 72: / Line 72: @@
 <li>'''Click '''''Save'' to save the entity mapping.</li>
 </ol>
-<div class="image-green-border">[[File:Generic Integration Framework ASB 07.png|720px|Generic Integration Framework ASB 07.png]]</div>
+<div class="image-green-border">[[File:GIF 8.png|600px]]</div>
 == Using ASB Adapter to load/publish Masterdata ==
@@ Line 79: / Line 79: @@
 #Navigate to the Masterdata page in ICI.
 #'''Click''' the ''View Record'' icon next to the ''Client App Cross Reference'' entity you have created. The ''Masterdata Details'' page opens.
-<div class="image-green-border">[[File:Generic Integration Framework ASB 08.png|720px|Generic Integration Framework ASB 08.png]]</div> <ol start="3">
+<div class="image-green-border">[[File:GIF 9.png|600px]]</div> <div class="image-green-border">&nbsp;</div> <ol start="3">
 <li>Click the ''Download Payload'' button to download a template for the Masterdata.</li>
 </ol>
 '''Note''': The file format of the template will be according to the ''Payload Type'' selected in the attributes of the ''Client App Cross Reference'' entity.
-<div class="image-green-border">[[File:Generic Integration Framework ASB 09.png|720px|Generic Integration Framework ASB 09.png]]</div> <ol start="4">
+<div class="image-green-border">[[File:GIF 10.png|600px]]</div> <ol start="4">
 <li>Open the downloaded JSON file. This file will be used by third-party systems to push data to the ASB adapter.</li>
 </ol>
@@ Line 98: / Line 98: @@
 <div class="note-box">'''Note''': For any subsequent ''Masterdata'' changes, the user needs to click ''Publish Payload'' button again to update the empty payload.</div>
 A notification is displayed once the Payload is published successfully.
-<div class="image-green-border">[[File:Generic Integration Framework ASB 12.png|720px|Generic Integration Framework ASB 12.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="note-box">'''Note''': The user can create a subscription to the job status updates by using the standard in ''Notification Setting'' in the ''User Administration'' menu.</div>
+<div class="image-green-border">[[File:GIF 11.png|600px]]</div> <div class="image-green-border">&nbsp;</div> <div class="note-box">'''Note''': The user can create a subscription to the job status updates by using the standard in ''Notification Setting'' in the ''User Administration'' menu.</div>
 == Using ASB Adapter to load/publish Transaction Data&nbsp; ==
@@ Line 112: / Line 112: @@
 &nbsp;
 ==== Checking Data in Service Bus Explorer ====

@@ Line 111: / Line 111: @@
 &nbsp;
 ==== Checking Data in Service Bus Explorer ====
@@ Line 134: / Line 135: @@
 &nbsp;

@@ Line 2: / Line 2: @@
 = Generic Integration Framework to Support ASB Interface =
-Azure Service Bus (ASB) is a fully managed enterprise integration message broker. Data is transferred between different applications and services using messages. The ICM-ASB adapter considers the approach based on REST and OData principles that exposes a uniform, stateless interface which communicates using HTTP(S) and JSON payloads.
+Azure Service Bus (ASB) is a fully managed enterprise integration message broker. Data is transferred between different applications and services using messages. The ICI-ASB adapter considers the approach based on REST and OData principles that exposes a uniform, stateless interface which communicates using HTTP(S) and JSON payloads.
 == Configuring ASB adapter to load Masterdata&nbsp; ==
-The ICM support for generic integration provides the ability to synchronize ICM Masterdata tables using the input from ASB. Through a technical configuration, you can specify the attributes to be used for this generic integration.
+The ICI support for generic integration provides the ability to synchronize ICI Masterdata tables using the input from ASB. Through a technical configuration, you can specify the attributes to be used for this generic integration.
 === Create Masterdata Contract Type ===
-To enable synchronization between ICM and ASB, a Masterdata Contract Type should first be configured in ICM, with specific attributes for the integration. To create a Masterdata Contract Type:
+To enable synchronization between ICI and ASB, a Masterdata Contract Type should first be configured in ICI, with specific attributes for the integration. To create a Masterdata Contract Type:
 #'''Click '''''Create Contract Type'' sub menu from the ''Configuration ''tile. The ''Select Contract Type'' page opens.
@@ Line 31: / Line 31: @@
 === Client App Cross Reference ===
-The Client App Cross Reference mapping maps ICM entities (for example, ICM attributes) to client app entities.
+The Client App Cross Reference mapping maps ICI entities (for example, ICI attributes) to client app entities.
-#Navigate to the ''Create Masterdata'' page in ICM. This page contains the following tabs:
+#Navigate to the ''Create Masterdata'' page in ICI. This page contains the following tabs:
 <div class="image-green-border">[[File:Generic Integration Framework ASB 04.png|520px|Generic Integration Framework ASB 04.png]]</div>
 ==== Masterdata Details ====
 .&nbsp;&nbsp; &nbsp;Select the ''Category ''from the drop-down. For example, ''Default''.<br/> 2.&nbsp;&nbsp; &nbsp;Select the Masterdata Contract Type.
-<div class="note-box">'''Note''': In order to map ICM entities with entities in the file uploaded through ASB, you must select ''Client App Cross Reference'' from the drop-down.</div>
+<div class="note-box">'''Note''': In order to map ICI entities with entities in the file uploaded through ASB, you must select ''Client App Cross Reference'' from the drop-down.</div>
 .&nbsp;&nbsp; &nbsp;Click ''Next''. The ''Attributes ''page opens.
 ==== Attributes ====
-#Enter the relevant attribute values. For example, enter ''ICM Entity Name'' as ''ICMSupplierMaster'' and ''Client Entity Name'' as ''SupplierMaster''. The ''Payload Type'' can be selected as ''JSON''.
+#Enter the relevant attribute values. For example, enter ''ICI Entity Name'' as ''ICISupplierMaster'' and ''Client Entity Name'' as ''SupplierMaster''. The ''Payload Type'' can be selected as ''JSON''.
 <div class="note-box">'''Note''': The ''Client Name'' ''GenericIntegration'' must be selected. To create mapping using ASB, select ''Messaging'' in the ''Integration Mode'' drop-down. You need to select a ''Task Category for Messaging'', either ''Scheduled'' or ''EventBased'' as required.</div> <ol start="2">
 <li>'''Click '''''Save'' to save the entity mapping.</li>
@@ Line 50: / Line 50: @@
 === Client App Entity Mapping ===
-The Client App Entity Mapping maps ICM attributes (for example, attribute names used in Supplier Master) to attributes in the file uploaded through ASB.
+The Client App Entity Mapping maps ICI attributes (for example, attribute names used in Supplier Master) to attributes in the file uploaded through ASB.
-#Navigate to the''Create Masterdata'' page in ICM. This page contains the following tabs:
+#Navigate to the''Create Masterdata'' page in ICI. This page contains the following tabs:
 <div class="image-green-border">[[File:Generic Integration Framework ASB 06.png|520px|Generic Integration Framework ASB 06.png]]</div>
 ==== Masterdata Details ====
@@ Line 58: / Line 58: @@
 #Select the ''Category ''from the drop-down. For example, ''Default''.
 #Select the Masterdata Contract Type.
-<div class="note-box">'''Note''': In order to map ICM attributes with attributes uploaded through ASB, ''Client App Entity Mapping'' must be selected from the drop-down.</div> <ol start="3">
+<div class="note-box">'''Note''': In order to map ICI attributes with attributes uploaded through ASB, ''Client App Entity Mapping'' must be selected from the drop-down.</div> <ol start="3">
 <li>Click ''Next''. The ''Attributes'' page opens.</li>
 </ol>
@@ Line 64: / Line 64: @@
 ==== Attributes ====
-#'''Enter''' the relevant attribute values. For example, enter ''ICM Entity Name'' as ''ICMSupplierMaster'' and ''Client Entity Name'' as ''SupplierMaster''.&nbsp;
+#'''Enter''' the relevant attribute values. For example, enter ''ICI&nbsp;Entity Name'' as ''ICISupplierMaster'' and ''Client Entity Name'' as ''SupplierMaster''.&nbsp;
 To create mapping using ASB, select ''Messaging'' in the ''Integration Mode'' drop-down. The ''Client Name'' selected must be ''GenericIntegration''.
-In case of lookup and non-lookup attributes: The ICM Relationship Key should be set for lookup attributes and kept blank for non-lookup attributes. The Relationship Key framing should be <''Master Contract Type Name''> Double Underscore<''ICM Attribute Name''>. For example, in case of Supplier Master the ICM attribute name will be ''ICMSupplierCountry'' and the Masterdata Contract Type for this attribute will be ''ICMCountryMaster''. Hence, relationship key will be ''ICMCountryMaster__ICMSupplierCountry.''
+In case of lookup and non-lookup attributes: The ICI Relationship Key should be set for lookup attributes and kept blank for non-lookup attributes. The Relationship Key framing should be <''Master Contract Type Name''> Double Underscore<''ICI Attribute Name''>. For example, in case of Supplier Master the ICI attribute name will be ''ICISupplierCountry'' and the Masterdata Contract Type for this attribute will be ''ICICountryMaster''. Hence, relationship key will be ''ICICountryMaster__ICISupplierCountry.''
 <ol start="2">
 <li>'''Click '''''Save'' to save the entity mapping.</li>
 </ol>
 <div class="image-green-border">[[File:Generic Integration Framework ASB 07.png|720px|Generic Integration Framework ASB 07.png]]</div>
 == Using ASB Adapter to load/publish Masterdata ==
 === Download Payload ===
-#Navigate to the Masterdata page in ICM.
+#Navigate to the Masterdata page in ICI.
 #'''Click''' the ''View Record'' icon next to the ''Client App Cross Reference'' entity you have created. The ''Masterdata Details'' page opens.
 <div class="image-green-border">[[File:Generic Integration Framework ASB 08.png|720px|Generic Integration Framework ASB 08.png]]</div> <ol start="3">
@@ Line 101: / Line 100: @@
 <div class="image-green-border">[[File:Generic Integration Framework ASB 12.png|720px|Generic Integration Framework ASB 12.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="note-box">'''Note''': The user can create a subscription to the job status updates by using the standard in ''Notification Setting'' in the ''User Administration'' menu.</div>
 == Using ASB Adapter to load/publish Transaction Data&nbsp; ==
 === Updating Transaction Data&nbsp; ===
-To update transaction data from ICM using generic integration framework:
+To update transaction data from ICI using generic integration framework:
-#'''Edit''' the agreement in ICM with the desired values.
+#'''Edit''' the agreement in ICI with the desired values.
 #'''Click''' ''Update''.
-'''Note''': For transaction data outbound, it is mandatory to select ''Data Flow Type'' as ''ICM to Client'' in the Client App Entity Mapping. The workflow action selected in ''Publish Transaction Data'' in Client App Cross Reference Mapping is the event at which transaction data will be updated. For example, if the values selected in this field are ''Approved ''and ''Updated'', then the transaction data will be updated when these actions are taken on the agreement.
+'''Note''': For transaction data outbound, it is mandatory to select ''Data Flow Type'' as ''ICI to Client'' in the Client App Entity Mapping. The workflow action selected in ''Publish Transaction Data'' in Client App Cross Reference Mapping is the event at which transaction data will be updated. For example, if the values selected in this field are ''Approved ''and ''Updated'', then the transaction data will be updated when these actions are taken on the agreement.
 &nbsp;
@@ Line 126: / Line 124: @@
 The updated values are displayed in the ''Message Text''.
 <ol start="6">
-<li>Check the ''Notifications Dashboard'' in ICM to view the success, failure and update notifications for outbound transaction data.</li>
+<li>Check the ''Notifications Dashboard'' in ICI to view the success, failure and update notifications for outbound transaction data.</li>
 </ol>

@@ Line 102: / Line 102: @@
 == Using ASB Adapter to load/publish Transaction Data&nbsp; ==
-=== Updating Transaction Data – Outbound ===
 To update transaction data from ICM using generic integration framework:
@@ Line 111: / Line 112: @@
 '''Note''': For transaction data outbound, it is mandatory to select ''Data Flow Type'' as ''ICM to Client'' in the Client App Entity Mapping. The workflow action selected in ''Publish Transaction Data'' in Client App Cross Reference Mapping is the event at which transaction data will be updated. For example, if the values selected in this field are ''Approved ''and ''Updated'', then the transaction data will be updated when these actions are taken on the agreement.
 ==== Checking Data in Service Bus Explorer ====
@@ Line 121: / Line 123: @@
 #'''Select '''''Peek ''radio button in the ''Receive Mode'' section.
 #'''Click '''''Ok''.
-<div class="image-green-border">[[File:7.12 ASB adapter.png|720px]]</div>
+<div class="image-green-border">[[File:7.12 ASB adapter.png|720px|7.12 ASB adapter.png]]</div>
 The updated values are displayed in the ''Message Text''.
 <ol start="6">