WikiSysop at 00:00, July 31, 2022

2022-07-31T00:00:54Z

Margarethe.nitzsche@softphone.it: Published

2021-04-06T07:35:19Z

Published

New page

{{Article
|Standalone=No
|DisplayName=Screen pops configuration
|TocName=Configuration
|Context=Steps to configure screen-pops in Microsoft Dynamics 365 with CIF versions 1.0 or 2.0 or Microsoft USD.
|ComingSoon=No
|Section={{Section
|alignment=Vertical
|structuredtext=Customization can be deployed as an '''unmanaged solution'''. According to the Microsoft environment you are using, it is based on different JavaScript files.
|Status=No
}}{{Section
|sectionHeading=Configuring screen pops in Microsoft Dynamics 365 with CIF version 1.0
|alignment=Vertical
|structuredtext=In Microsoft Dynamics 365 with CIF version 1.0, screen pop configuration is based on the following JavaScript files, which implement the out-of-the-box scenario for different fields:

#'''<prefix>_iwscriptCIFWWE.js_custom.js:''' Computer Telephony Integration (CTI) events that the Adapter can capture
#'''<prefix>_utilCIFWWE_custom.js:''' implementation of the events mentioned in the previous point
#'''<prefix>_iwsconfigCIFWWE.js_custom.js:''' parameters necessary to customize the Adapter
#'''<prefix>_translations_custom.js:''' switch to other languages

An extra file must be handled to customize the outbound-call scenario:

#'''<prefix>_CustomMakeCallCIFWWE.js:''' wanted flow in case of outgoing interactions
{{NoteFormat|<prefix> is an example of how the file is named. Once you generate your unmanaged solution, your organization name takes the place of <prefix>.|}}

For customization, follow the procedure presented in {{Link-SomewhereInThisVersion|manual=Admin|topic=CustomSP}}.
|Status=No
}}{{Section
|sectionHeading=Configuring screen pops in Microsoft Dynamics 365 with CIF version 2.0
|alignment=Vertical
|structuredtext=In Microsoft Dynamics 365 with CIF version 2.0, screen pop configuration is based on the following JavaScript files, which implement the out-of-the-box scenario for different fields:

#'''<prefix>_iwscriptCIFWWEv2.js_custom.js:''' Computer Telephony Integration (CTI) events that the Adapter can capture
#'''<prefix>_utilCIFWWEv2_custom.js:''' implementation of the events mentioned in the previous point
#'''<prefix>_iwsconfigCIFWWEv2.js_custom.js:''' parameters necessary to customize the Adapter
#'''<prefix>_translations_custom.js:''' switch to other languages

An extra file must be handled to customize the outbound-call scenario:

#'''<prefix>_CustomMakeCallCIFWWEv2.js:''' wanted flow in case of outgoing interactions
{{NoteFormat|<prefix> is an example of how the file is named. Once you generate your unmanaged solution, your organization name takes the place of <prefix>.|}}

To proceed with the customization, follow the procedure presented in {{Link-SomewhereInThisVersion|manual=Admin|topic=CustomSP}}.
|Status=No
}}{{Section
|sectionHeading=Configuring screen pops in Microsoft Unified Service Desk (USD)
|alignment=Vertical
|structuredtext=In Microsoft USD, screen pop configuration is based on the following JavaScript files, which implement the out-of-the-box scenario for different fields:

#'''<prefix>_iwscriptCIFUSDWWE.js_custom.js:''' Computer Telephony Integration (CTI) events that the Adapter can capture
#'''<prefix>_utilCIFUSDWWE_custom.js:''' implementation of the events mentioned in the previous point
#'''<prefix>_iwsconfigCIFUSDWWE.js_custom.js:''' parameters necessary to customize the Adapter
#'''<prefix>_translations_custom.js:''' switch to other languages

An extra file must be handled to customize the outbound-call scenario:

#'''<prefix>_CustomMakeCallCIFUSDWWE.js:''' wanted flow in case of outgoing interactions
{{NoteFormat|<prefix> is an example of how the file is named. Once you generate your unmanaged solution, your organization name takes the place of <prefix>.|}}

For customization, follow the procedure presented in {{Link-SomewhereInThisVersion|manual=Admin|topic=CustomSP}}.
|Status=No
}}
}}

@@ Line 6: / Line 6: @@
 |ComingSoon=No
 |Section={{Section
 |alignment=Vertical
 |structuredtext=Customization can be deployed as an '''unmanaged solution'''. According to the Microsoft environment you are using, it is based on different JavaScript files.
 |Status=No
 }}{{Section
@@ Line 14: / Line 17: @@
 |structuredtext=In Microsoft Dynamics 365 with CIF version 1.0, screen pop configuration is based on the following JavaScript files, which implement the out-of-the-box scenario for different fields:
-#'''&lt;prefix&gt;_iwscriptCIFWWE.js_custom.js:''' Computer Telephony Integration (CTI) events that the Adapter can capture
+#'''softphon_iwscriptCIFWWE.js_custom.js:''' Computer Telephony Integration (CTI) events that the Adapter can capture
-#'''&lt;prefix&gt;_utilCIFWWE_custom.js:''' implementation of the events mentioned in the previous point
+#'''softphon_utilCIFWWE_custom.js:''' implementation of the events mentioned in the previous point
-#'''&lt;prefix&gt;_iwsconfigCIFWWE.js_custom.js:''' parameters necessary to customize the Adapter
+#'''softphon_iwsconfigCIFWWE.js_custom.js:''' parameters necessary to customize the Adapter
-#'''&lt;prefix&gt;_translations_custom.js:''' switch to other languages
+#'''softphon_translations_custom.js:''' switch to other languages
 An extra file must be handled to customize the outbound-call scenario:
-#'''&lt;prefix&gt;_CustomMakeCallCIFWWE.js:''' wanted flow in case of outgoing interactions
+#'''softphon_CustomMakeCallCIFWWE.js:''' wanted flow in case of outgoing interactions
-{{NoteFormat|&lt;prefix&gt; is an example of how the file is named. Once you generate your unmanaged solution, your organization name takes the place of &lt;prefix&gt;.|}}
 For customization, follow the procedure presented in {{Link-SomewhereInThisVersion|manual=Admin|topic=CustomSP}}.
@@ Line 31: / Line 36: @@
 |structuredtext=In Microsoft Dynamics 365 with CIF version 2.0, screen pop configuration is based on the following JavaScript files, which implement the out-of-the-box scenario for different fields:
-#'''&lt;prefix&gt;_iwscriptCIFWWEv2.js_custom.js:''' Computer Telephony Integration (CTI) events that the Adapter can capture
+#'''softphon_iwscriptCIFWWEv2.js_custom.js:''' Computer Telephony Integration (CTI) events that the Adapter can capture
-#'''&lt;prefix&gt;_utilCIFWWEv2_custom.js:''' implementation of the events mentioned in the previous point
+#'''softphon_utilCIFWWEv2_custom.js:''' implementation of the events mentioned in the previous point
-#'''&lt;prefix&gt;_iwsconfigCIFWWEv2.js_custom.js:''' parameters necessary to customize the Adapter
+#'''softphon_iwsconfigCIFWWEv2.js_custom.js:''' parameters necessary to customize the Adapter
-#'''&lt;prefix&gt;_translations_custom.js:''' switch to other languages
+#'''softphon_translations_custom.js:''' switch to other languages
 An extra file must be handled to customize the outbound-call scenario:
-#'''&lt;prefix&gt;_CustomMakeCallCIFWWEv2.js:''' wanted flow in case of outgoing interactions
+#'''softphon_CustomMakeCallCIFWWEv2.js:''' wanted flow in case of outgoing interactions
-{{NoteFormat|&lt;prefix&gt; is an example of how the file is named. Once you generate your unmanaged solution, your organization name takes the place of &lt;prefix&gt;.|}}
 To proceed with the customization, follow the procedure presented in {{Link-SomewhereInThisVersion|manual=Admin|topic=CustomSP}}.
@@ Line 48: / Line 54: @@
 |structuredtext=In Microsoft USD, screen pop configuration is based on the following JavaScript files, which implement the out-of-the-box scenario for different fields:
-#'''&lt;prefix&gt;_iwscriptCIFUSDWWE.js_custom.js:''' Computer Telephony Integration (CTI) events that the Adapter can capture
+#'''softphon_iwscriptCIFUSDWWE.js_custom.js:''' Computer Telephony Integration (CTI) events that the Adapter can capture
-#'''&lt;prefix&gt;_utilCIFUSDWWE_custom.js:''' implementation of the events mentioned in the previous point
+#'''softphon_utilCIFUSDWWE_custom.js:''' implementation of the events mentioned in the previous point
-#'''&lt;prefix&gt;_iwsconfigCIFUSDWWE.js_custom.js:''' parameters necessary to customize the Adapter
+#'''softphon_iwsconfigCIFUSDWWE.js_custom.js:''' parameters necessary to customize the Adapter
-#'''&lt;prefix&gt;_translations_custom.js:''' switch to other languages
+#'''softphon_translations_custom.js:''' switch to other languages
 An extra file must be handled to customize the outbound-call scenario:
-#'''&lt;prefix&gt;_CustomMakeCallCIFUSDWWE.js:''' wanted flow in case of outgoing interactions
+#'''softphon_CustomMakeCallCIFUSDWWE.js:''' wanted flow in case of outgoing interactions
-{{NoteFormat|&lt;prefix&gt; is an example of how the file is named. Once you generate your unmanaged solution, your organization name takes the place of &lt;prefix&gt;.|}}
 For customization, follow the procedure presented in {{Link-SomewhereInThisVersion|manual=Admin|topic=CustomSP}}.

GAMD/Current/Admin/ConfigSP - Revision history

WikiSysop at 00:00, July 31, 2022

Margarethe.nitzsche@softphone.it: Published