Difference between revisions of "PEC-REP/Current/GIMPEGuide/GSPConfigOptions"

Latest revision as of 19:31, September 28, 2022

This topic is part of the manual Genesys Info Mart Private Edition Guide for version Current of Reporting.

1 adjust-vq-time-by-strategy-time
2 canceled-queues
3 completed-queues
4 interaction-type-ignore-list
5 max-ixn-duration-days
- 5.1 Artificial termination of long-living interactions
6 max-msfs-per-irf
7 populate-ixnqueue-facts
8 populate-workbin-as-hold
9 populate-workbin-facts
10 q-answer-threshold
11 q-short-abandoned-threshold
12 short-abandoned-threshold
13 show-non-queue-mediation
- 13.1 Example
14 stop-ixn-queues

Options you can use to control GSP behavior.

adjust-vq-time-by-strategy-time

Default value: false
Valid values: true, false
Configuration level: standard

Specifies whether GSP adjusts the mediation duration in mediation segment facts (MSFs) for virtual queues to include time spent in strategies but not in associated virtual queues — for example, if an interaction spends 3 minutes in a strategy and is in a virtual queue for 2 of those minutes, whether the MSF for the virtual queue reports the duration as 3 minutes or 2 minutes.

true — GSP includes strategy time that is outside the virtual queue in the mediation duration in MSFs for virtual queues.
false — GSP never includes strategy time that is outside the virtual queue in the mediation duration. This setting means that there might be gaps between the end time of the MSF for a virtual queue that is used by a strategy and the interaction resource fact (IRF) that follows the strategy’s routing, or between the start time of the MSF for a virtual queue and the end time of a previous MSF (for example, the MSF for an Interaction Workbin).

In digital scenarios in which an interaction is bounced between a mediation resource (for example, an Interaction Queue or a Workbin) and a strategy as the strategy repeatedly retries busy agents, this option comes into effect only for the virtual queue that is associated with the last strategy party, before the interaction is routed successfully or else terminated. Genesys Info Mart does not report on virtual-queue activity that overlaps the repeated interim mediations.

>> Back to list

canceled-queues

Default value: iWD_Canceled
Valid values: A comma-separated list of queue names
Configuration level: standard

In digital deployments that use archive queues in their business processes, specifies the Interaction Queues that are used as archives for canceled interactions. When an interaction is placed into one of these queues, GSP considers the interaction to be terminated. The transformation job assigns the technical result/reason combination of COMPLETED/CANCELED in the IRF of the handling resource that placed the interaction in the queue, and GSP excludes the interaction from further processing.

The option parallels the completed-queues configuration option available in Interaction Server. The default value of the GSP option matches the archive queue for canceled interactions in the default business process for the Genesys intelligent Workload Distribution (iWD) solution.

>> Back to list

completed-queues

Default value: iWD_Completed
Valid values: A comma-separated list of queue names
Configuration level: standard

In digital deployments that use archive queues in their business processes, specifies the Interaction Queues that are used as archives for completed interactions. When an interaction is placed into one of these queues, GSP considers the interaction to be terminated. The transformation job assigns the technical result/reason combination of COMPLETED/ARCHIVED in the IRF of the handling resource that placed the interaction in the queue, and GSP excludes the interaction from further processing.

The option parallels the completed-queues configuration option available in Interaction Server. The default value of the GSP option matches the archive queue for completed interactions in the default business process for the Genesys iWD solution.

>> Back to list

interaction-type-ignore-list

Default value: InboundReport, InboundDisposition
Valid values: A comma-separated list of interaction types
Configuration level: standard

In digital deployments, specifies the interaction types or subtypes you want to exclude from reporting. GSP does not transform any interactions with the interaction type(s) or subtype(s) you specify. No records are generated in fact tables for interactions of this type.

If you disable a subtype, the parent interactions of that subtype as well as any child interactions of those parent interactions are disabled, even if the child interactions themselves are of a different subtype, one that is configured to be transformed.

>> Back to list

max-ixn-duration-days

Default value: 30
Valid values: Any positive integer
Configuration level: standard

Specifies the maximum duration, in days, of interactions in the deployed environment.

For long-living digital interactions, specifies the maximum number of days to process active interactions, after which the interactions become eligible for artificial termination. Consider using a value that is consistent with the value of the option days-to-keep-active-facts.

Artificial termination of long-living interactions

This functionality is intended primarily to prevent problems with aggregation — for example, when updates to long-living digital interactions trigger unnecessary re-aggregation, which results in overflow errors.

If an interaction is still active when the max-ixn-duration-days period expires, the transformation job terminates the interaction artificially in fact tables. Any activity that is related to this interaction that occurs after termination is discarded.

>> Back to list

max-msfs-per-irf

Default value: 50
Valid values: 10-10000
Configuration level: standard

Specifies the maximum number of MSF records associated with a given digital interaction that are represented in the Info Mart database. When the number of MSF records associated with a single IRF record exceeds the limit, the transformation job processes only the first n mediation DNs and the last n mediation DNs in the interaction, where n = max-msfs-per-irf/2. In this way, ETL performance avoids being degraded by huge numbers of MSF records for unsuccessful routing attempts for "stuck strategy" scenarios.

The first n mediation records for a given interaction are processed by the transformation job and populated in the MSF table as they occur. The last n records are postponed until an associated IRF record has been created.

The option does not affect the mediation durations that are reported in the IRF (QUEUE_DURATION, ROUTING_POINT_DURATION, MEDIATION_DURATION, and PREVIOUS_MEDIATION_DURATION); all these metrics correctly report the full overall mediation time.

Log message number 55-20120 is generated when the max-msfs-per-irf limit is exceeded, triggering the behavior to abbreviate the representation of unsuccessful routing attempts in the Info Mart database. You can set an alarm on the log message, to prompt you to investigate strategies that might be inappropriate for your deployment.

>> Back to list

populate-ixnqueue-facts

Default value: true
Valid values: true, false
Configuration level: standard, script: standard

Enables or disables the population of digital Interaction Queue activity to the MSF table. GSP uses the value configured at the standard level for all configured Interaction Queues, but you can override that value for specific Interaction Queues by configuring a different value for those Interaction Queues at the script: standard level.

true — The placement of an interaction in an Interaction Queue is represented in the MSF table.
false — The placement of an interaction in an Interaction Queue is not represented in the MSF table.

GSP always creates an MSF record for the first Interaction Queue that an inbound interaction enters, regardless of the setting of this option.

Strategy time is not included in the mediation duration, with the following exceptions:

Scenarios in which an interaction is bounced between an Interaction Queue and a strategy while an available agent is being identified
When the show-non-queue-mediation option is set to true

Tip

Ideally, set populate-ixnqueue-facts to true only for Interaction Queues for which mediation reporting is meaningful, so that the MSF table does not become cluttered with unnecessary information. Some Interaction Queues are not useful for reporting, such as the Interaction Queues that are associated with Interaction Workbin objects only through a configured Interaction Queue View.

>> Back to list

populate-workbin-as-hold

Default value: true
Valid values: true, false
Configuration level: standard

Specifies whether the time that an interaction is in an Interaction Workbin is considered to be hold time or mediation.

true — Workbin time is considered to be hold if the handling resource places the interaction into its own personal workbin. The hold ends when any resource takes the interaction out of the workbin. Various hold metrics are reported in the IRF record that is associated with that handling resource.
false — Workbin time is considered to be mediation. Whether or not the workbin activity is represented by an MSF record depends on the value of the populate-workbin-facts option.

For time in an Interaction Workbin to be considered hold time, the Agent or Place resource must place the interaction into its own personal workbin. For example, if Agent1 places an email interaction into its personal workbin, the workbin time is considered to be hold; however, if another resource, such as another agent or a strategy, places the interaction into the workbin for Agent1 to handle, the workbin time is not considered to be hold.

If a handling resource places an interaction into more than one of its own personal workbins, all of the personal workbin time is considered to be hold, and there is no distinction between the hold time in the various workbins. For example, if Agent1 places an email interaction into a Drafts workbin, then pulls the interaction to continue handling it and subsequently places it into a FollowUp workbin, the hold duration that is reported in the IRF record for Agent1’s association with the interaction combines the time that is spent in both workbins.

The following table summarizes the results of different permutations of the populate-workbin-as-hold and populate-workbin-facts options, in combination with the specifics of the interaction flow. If the values of the populate-workbin-as-hold and populate-workbin-facts options are both set to false, the workbin activity is not represented in the dimensional model.

**Matrix of workbin reporting results**
Scenario	Reporting result for workbin activity
Scenario	populate-workbin-as-hold=false populate-workbin-facts=true	populate-workbin-as-hold=true populate-workbin-facts=true	populate-workbin-as-hold=true populate-workbin-facts=false
An Agent/Place resource places the interaction into its personal workbin.	MSF record.*	Hold metrics in the IRF record for the association of that Agent/Place with the interaction. This is the default behavior.
Another resource places the interaction into the personal workbin of an Agent/Place.		MSF record.* This is the default behavior.	Not represented in the dimensional model.
Any resource places the interaction into an AgentGroup or PlaceGroup workbin.		MSF record.* This is the default behavior.	Not represented in the dimensional model.
*The MSF record includes a `WORKBIN_KEY` value that identifies the workbin instance that is associated with the mediation.

>> Back to list

populate-workbin-facts

Default value: true
Valid values: true, false
Configuration level: standard, script: standard

Enables or disables the population of digital Interaction Workbin activity to the MSF table. For workbins that are associated with handling resources of type Agent or Place, this option comes into effect only if GSP has not been configured to consider workbin time as hold (populate-workbin-as-hold=false). For the circumstances under which GSP considers workbin time as hold, see the description of the populate-workbin-as-hold option.

GSP uses the value configured at the standard level for all configured Interaction Workbins, but you can override that value for specific Interaction Workbins by configuring a different value for those Interaction Workbins at the script: standard level.

true — Provided that GSP does not consider the workbin time as hold, the placement of an interaction in an Interaction Workbin is represented in the MSF table. The MSF record references a WORKBIN dimension, which identifies the type of resource that is associated with the workbin and the specific resource that is associated with the mediation. Strategy time is not included in the mediation duration, except for scenarios in which an interaction is bounced between an Interaction Workbin and a strategy as the strategy repeatedly retries busy agents. For more information, see the description of the MEDIATION_DURATION field in Populating mediation segments.
false — The placement of an interaction in an Interaction Workbin is not represented in the MSF table.

>> Back to list

q-answer-threshold

Default value: 60
Valid values: 1-600000 for digital, 1-10000 for voice.
Configuration level: media, dn: media, script: media

Specifies the default duration, in seconds, that is used on all configured queues as a target time to accept an interaction that entered a queue.

You can configure a different threshold for each media type.

GSP uses the value configured at the media level for all configured queues, but you can override the value for interactions of that media type that come through particular virtual queues, digital interaction queues, or workbins by configuring a different value:

For specific Virtual Queue DNs at the dn: media level
For specific digital Interaction Queues or Interaction Workbins at the script: media level

>> Back to list

q-short-abandoned-threshold

Default value: 10
Valid values: 1-1000
Configuration level: media, dn: media, script: media

Specifies the maximum duration of mediation, in seconds, that is used on all configured queues to indicate that an interaction that was abandoned while in a queue should be considered a “short” abandon. GSP uses this value to determine the state of SHORT_ABANDONED_FLAG in the MSF row for an interaction abandoned in a queue.

You can configure a different threshold for each media type.

GSP uses the value configured at the media level for all configured queues, but you can override the value for interactions of that media type that come through particular virtual queues, digital interaction queues, or workbins by configuring a different value:

For specific Virtual Queue DNs at the dn: media level
For specific digital Interaction Queues or Interaction Workbins at the script: media level

>> Back to list

short-abandoned-threshold

Default value: 10
Valid values: 0-100
Configuration level: media

Specifies the minimum duration, in seconds, of an abandoned interaction in order for it to be considered truly abandoned. GSP uses this value to determine the state of SHORT_ABANDONED_FLAG in the IRF row.

You can configure a different threshold for each media type.

>> Back to list

show-non-queue-mediation

Default value: false
Valid values: true, false
Configuration level: standard

Controls whether all mediation time for digital interactions, even mediation time that does not occur within a queue, is represented by an MSF.

true — Provided that there is an MSF for the first Interaction Queue in a mediation (which is true for mediation time of unhandled interactions), all mediation time for a digital interaction that occurs after the first Interaction Queue, even mediation time that does not occur within a queue, is represented by one or more MSFs. Additional, non-queue MSFs are created for multimedia interactions to represent mediation time that occurs outside an Interaction Queue MSF — for example, mediation time that occurs after an MSF for an Interaction Queue if a routing strategy is attempting to find a routing target without the use of a virtual queue.
false — MSFs for digital interactions are focused only on the portion of the mediation time that occurs in a queue, whether it is an Interaction Queue or a virtual queue. There may be gaps in time between MSFs, because the interaction may not be in a queue, or may not be in a queue that is represented by an MSF.

For digital interactions, mediation that occurs in a virtual queue is always represented in Genesys Info Mart by an MSF. However, depending on the setting for populate-ixnqueue-facts, mediation that occurs in an Interaction Queue might not be represented by an MSF; in fact, often it is not. When show-non-queue-mediation is set to true, the additional MSFs that are created occur between MSFs for Interaction Queues (in other words, when an interaction moves during mediation from one Interaction Queue that is represented by an MSF to another that is represented by an MSF), or between the MSF for an Interaction Queue and a routing target (agent). The additional, non-queue MSFs may overlap with MSFs for virtual queues, since an interaction may also be in a virtual queue for some (or all) of the mediation time that occurs outside of an Interaction Queue MSF. Furthermore, the additional MSFs may include time that the interaction spent in Interaction Queues that are not represented by an MSF.

Example

Consider the scenario in which a digital interaction enters the contact center at time t0 and, after mediation involving various queues and routing strategies, is routed for handling at time t4. Following first handling, there is additional mediation before the interaction is routed for further handling.
t0–t1: InteractionQueue1
t1–t2: Strategy1
t2–t3: InteractionQueue2 (not the same queue as InteractionQueue1)
t3–t4: Strategy2
t4–t5: Agent1
t5–t6: InteractionQueue3
t6–t7: Strategy3
t7–t8: InteractionQueue4
t8–t9: Strategy4
t9–t10: Agent2

The following table summarizes the mediation reporting results, depending on configuration option settings.

populate-ixnqueue-facts=`false`, show-non-queue-mediation=`false`	populate-ixnqueue-facts=`true`, show-non-queue-mediation=`false`	populate-ixnqueue-facts=`false`, show-non-queue-mediation=`true`	populate-ixnqueue-facts=`true`, show-non-queue-mediation=`true`
Without virtual queues
MSF1 (InteractionQueue1)* IRF1 (Agent1) IRF2 (Agent2) *If the second InteractionQueue in the scenario is actually the same as InteractionQueue1, then MSF1 would cover t0–t3, and there would be a gap of t3–t4.	MSF1 (InteractionQueue1) MSF2 (InteractionQueue2) IRF1 (Agent1) MSF3 (InteractionQueue3) MSF4 (InteractionQueue4) IRF2 (Agent2)	MSF1 (InteractionQueue1) MSF2 (Strategy1) IRF1 (Agent1) IRF2 (Agent2) Spans t1–t4, including time for InteractionQueue2 and Strategy2.	MSF1 (InteractionQueue1) MSF2 (Strategy1) MSF3 (InteractionQueue2) MSF4 (Strategy2) IRF1 (Agent1) MSF5 (InteractionQueue3) MSF6 (Strategy3) MSF7 (InteractionQueue4) MSF8 (Strategy4) IRF2 (Agent2)
Gaps: t1–t4, t5–t9	Gaps: t1–t2, t3–t4, t6–t7, t8–t9	Gaps: None up to first handling; t5–t9	Gaps: None
If the strategies use virtual queues, there are also separate MSFs for the virtual queues, which might eliminate gaps, even when show-non-queue-mediation=`false`, and which overlap with the MSF for the Strategy party when show-non-queue-mediation=`true`.

Important

There are other scenarios, not controlled by this option, where non-queue time might be incorporated into an MSF for a queue, such as when a digital interaction bounces back and forth between the same queue and a strategy. In such cases, the repeated bounce-backs are collapsed into a single MSF, which might include non-queue time when the routing strategy was attempting to find a routing target before returning the interaction to the same queue. For more information, see the description of the MEDIATION_DURATION field in Populating mediation segments.

>> Back to list

stop-ixn-queues

Default value: No default value
Valid values: A comma-separated list of queue names
Configuration level: standard

In digital deployments that use stop-interaction queues in their business processes, this option specifies the Interaction Queues that are used to handle stopping an interaction (for example, Twitter_StopIxn). When an interaction is placed into one of these queues, GSP considers the interaction to be terminated:

The transformation job assigns the technical result/reason combination of COMPLETED/UNSPECIFIED in the IRF of the handling resource that placed the interaction in the queue, and GSP excludes the interaction from further processing.
The agent who placed the interaction in the queue is represented as the party that stopped the interaction, and the strategy that actually stops the interaction and performs any associated post-processing is not represented in Genesys Info Mart reporting.

If you do not specify a value for this option, GSP handles these situations as transfers to a queue.

>> Back to list

Genesys Info Mart Private Edition Guide

Overview

Configure and deploy GSP

Configure and deploy GIM

Configure and deploy GCA

Upgrade, roll back, or uninstall

Observability

Difference between revisions of "PEC-REP/Current/GIMPEGuide/GSPConfigOptions"

Latest revision as of 19:31, September 28, 2022

Contents

adjust-vq-time-by-strategy-time

canceled-queues

completed-queues

interaction-type-ignore-list

max-ixn-duration-days

Artificial termination of long-living interactions

max-msfs-per-irf

populate-ixnqueue-facts

populate-workbin-as-hold

populate-workbin-facts

q-answer-threshold

q-short-abandoned-threshold

short-abandoned-threshold

show-non-queue-mediation

Example

stop-ixn-queues

@@ Line 3: / Line 3: @@
 |Context=Options you can use to control GSP behavior.
 }}
-{{Editgrn_open}}<font color=red>Whole page is new.</font>{{Editgrn_close}}
+<!--Writer: "More info" links to the PDM use a template that currently links to the [https://docs.genesys.com/Documentation/PSAAS/draft/RPRT/GIMRef PSAAS cloud PDM]. You must update the link syntax in the template when the PE PDM is published, and then the links below should automatically resolve to the new PE PDM. (2) When the config option template for the suite is developed, remember to switch the entries on this page to use the new template, and modify the list query accordingly.
+-->
-{{JDNote|(1) "More info" links to the PDM use a template that currently links to the [https://docs.genesys.com/Documentation/PSAAS/draft/RPRT/GIMRef PSAAS cloud PDM]. You must update the link syntax in the template when the PE PDM is published, and then the links below should automatically resolve to the new PE PDM. (2) When the config option template for the suite is developed, remember to switch the entries on this page to use the new template, and modify the list query accordingly.}}
 GSP supports the configuration options described on this page. See {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=ConfigureGSP|anchor=Options|display text=Configure GSP behavior}} for information about how to change the option values in the Helm chart.
-GSP behavior affects data in the Info Mart database dimensional model. For full information about the Info Mart database tables and columns referenced in the descriptions below, see the ''{{PDMLinkForGIMPE|topic=GIMRef|linkText=Genesys Info Mart Historical Database Reference}}''.
+GSP behavior affects data in the Info Mart database dimensional model. For full information about the Info Mart database tables and columns referenced in the descriptions on this page, see the ''{{PDMLinkForGIMPE|topic=GIMRef|linkText=Genesys Info Mart Historical Database Reference}}''.
-{{Editgrn_open}}<font color=red>'''Writer's note:''' (1) Per Kostya, max-ixn-duration-seconds and max-segments should be hidden and are not included on this page. (2) In some cases, I left in instances of "Genesys Info Mart" instead of changing them to "GSP." Please pay attention to whether these are OK. The admittedly subtle convention I have adopted for PE/MC is to use "Genesys Info Mart" (never abbreviated) to refer to all three included services and "Genesys Info Mart (GIM)" (spelled out only on the very first {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=Overview|display text=overview}} page, otherwise always "GIM") to refer to the included service.</font>{{Editgrn_close}}
+<!-- '''Writer:'''
+(2) In some cases, I left in instances of "Genesys Info Mart" instead of changing them to "GSP." Please pay attention to whether these are OK. The admittedly subtle convention I have adopted for PE/MC is to use "Genesys Info Mart" (never abbreviated) to refer to all three included services and "Genesys Info Mart (GIM)" (spelled out only on the very first {{Link-SomewhereInThisVersion|manual=GIMPEGuide|topic=Overview|display text=overview}} page, otherwise always "GIM") to refer to the included service.
+-->
 {{AnchorDiv|OptionsList}}{{ColumnFormat|cols=3|content=
@@ Line 35: / Line 36: @@
 |ValidValues=true, false
 |ConfigLevel=standard
-|ShortDesc={{Editgrn_open}}<font color=red>Based on [https://docs.genesys.com/Documentation/Options/Current/GIM/GIM-gim-transformation#adjust-vq-time-by-strategy-time adjust-vq-time-by-strategy-time] in the gim-transformation section.</font>{{Editgrn_close}}
+|ShortDesc=
+Specifies whether GSP adjusts the mediation duration in mediation segment facts (MSFs) for virtual queues to include time spent in strategies but not in associated virtual queues — for example, if an interaction spends 3 minutes in a strategy and is in a virtual queue for 2 of those minutes, whether the MSF for the virtual queue reports the duration as 3 minutes or 2 minutes.
-Specifies whether GSP will adjust the mediation duration in mediation segment facts (MSFs) for virtual queues to include time that was spent in strategies but not in associated virtual queues — for example, if an interaction spends 3 minutes in a strategy and is in a virtual queue for 2 of those minutes, whether the MSF for the virtual queue will report the duration as 3 minutes or 2 minutes.
 * <tt>true</tt> — GSP includes strategy time that is outside the virtual queue in the mediation duration in MSFs for virtual queues.
 * <tt>false</tt> — GSP never includes strategy time that is outside the virtual queue in the mediation duration. This setting means that there might be gaps between the end time of the MSF for a virtual queue that is used by a strategy and the interaction resource fact (IRF) that follows the strategy’s routing, or between the start time of the MSF for a virtual queue and the end time of a previous MSF (for example, the MSF for an Interaction Workbin).
@@ Line 50: / Line 50: @@
 |ConfigLevel=standard
 |ValidValues=A comma-separated list of queue names
-|ShortDesc={{Editgrn_open}}<font color=red>Based on [https://docs.genesys.com/Documentation/Options/Current/GIM/GIM-gim-transformation#canceled-queues canceled-queues] in the gim-transformation section.</font>{{Editgrn_close}}
+|ShortDesc=
 In digital deployments that use archive queues in their business processes, specifies the Interaction Queues that are used as archives for canceled interactions. When an interaction is placed into one of these queues, GSP considers the interaction to be terminated. The transformation job assigns the technical result/reason combination of COMPLETED/CANCELED in the IRF of the handling resource that placed the interaction in the queue, and GSP excludes the interaction from further processing.
 |ExtendedDesc=The option parallels the '''completed-queues''' configuration option available in Interaction Server. The default value of the GSP option matches the archive queue for canceled interactions in the default business process for the Genesys intelligent Workload Distribution (iWD) solution.
@@ Line 63: / Line 62: @@
 |ConfigLevel=standard
 |ValidValues=A comma-separated list of queue names
-|ShortDesc={{Editgrn_open}}<font color=red>Based on [https://docs.genesys.com/Documentation/Options/Current/GIM/GIM-gim-transformation#completed-queues completed-queues] in the gim-transformation section.</font>{{Editgrn_close}}
+|ShortDesc=
 In digital deployments that use archive queues in their business processes, specifies the Interaction Queues that are used as archives for completed interactions. When an interaction is placed into one of these queues, GSP considers the interaction to be terminated. The transformation job assigns the technical result/reason combination of COMPLETED/ARCHIVED in the IRF of the handling resource that placed the interaction in the queue, and GSP excludes the interaction from further processing.
 |ExtendedDesc=The option parallels the '''completed-queues''' configuration option available in Interaction Server. The default value of the GSP option matches the archive queue for completed interactions in the default business process for the Genesys iWD solution.
@@ Line 74: / Line 72: @@
 |OptionName=interaction-type-ignore-list
 |DefaultValue=InboundReport, InboundDisposition
-|ValidValues={{Editgrn_open}}A comma-separated list of interaction types{{Editgrn_close}}
+|ValidValues=A comma-separated list of interaction types
 |ConfigLevel=standard
-|ShortDesc={{Editgrn_open}}<font color=red>Equivalent option not in GIM Classic. Confirm the description.</font>{{Editgrn_close}}
+|ShortDesc=
 In digital deployments, specifies the interaction types or subtypes you want to exclude from reporting. GSP does not transform any interactions with the interaction type(s) or subtype(s) you specify. No records are generated in fact tables for interactions of this type.
 If you disable a subtype, the parent interactions of that subtype as well as any child interactions of those parent interactions are disabled, even if the child interactions themselves are of a different subtype, one that is configured to be transformed.
 <!--
-'''Questions:'''
+Writer:
-#(1) Is the IGNORE column in the INTERACTION_TYPE table still populated, or do we need to change the column description in the Azure/PE PDMs? If it is populated based on this option value, <font color=red>ANSWER</font>: <KR> the IGNORE column in the INTERACTION_TYPE doesn’t affect GIM behavior in Azure. <font color=red>Action needed: none</font>
+#(3) Does the following still apply: "When a multimedia interaction subtype arrives that is new to Genesys Info Mart, the transformation job adds the new interaction subtype automatically to the INTERACTION_TYPE dimension table and includes it when transforming data. Genesys Info Mart generates a log event (message number 55-20151) to alert you about the addition." <font color=red>ANSWER</font><AT> For the documentation purposes (3) doesn’t apply to GSP. <font color=red>Action needed: '''PdM doc update'''</font>
-#(2) can customers manually add types/subtypes directly in the database to extend the ignore list during runtime? <font color=red>ANSWER</font>:  <KR> there is no reason for that.  <font color=red>Action needed: none</font>
+-->
-#(3) Does the following still apply: "When a multimedia interaction subtype arrives that is new to Genesys Info Mart, the transformation job adds the new interaction subtype automatically to the INTERACTION_TYPE dimension table and includes it when transforming data. Genesys Info Mart generates a log event (message number 55-20151) to alert you about the addition." <font color=red>ANSWER</font><AT> For the documentation purposes (3) doesn’t apply to GSP. <font color=red>Action needed: '''PdM doc update'''</font>-->
 |ExtendedDesc=
 |Introduced=
@@ Line 93: / Line 89: @@
 {{PEConfigOption
 |OptionName=max-ixn-duration-days
-|DefaultValue={{Editgrn_open}}30{{Editgrn_close}}
+|DefaultValue=30
-|ValidValues={{Editgrn_open}}Any positive integer{{Editgrn_close}}
+|ValidValues=Any positive integer
 |ConfigLevel=standard
-|ShortDesc=<!--<font color=red>Option not in GIM Classic. The following is a combination of [https://docs.genesys.com/Documentation/Options/Current/GIM/GIM-gim-etl#max-call-duration max-call-duration] and [https://docs.genesys.com/Documentation/Options/Current/GIM/GIM-gim-etl#days-to-keep-active-facts days-to-keep-active-facts].</font>-->
+|ShortDesc=
 Specifies the maximum duration, in days, of interactions in the deployed environment.
-For long-living digital interactions, specifies the maximum number of days to {{Editgrn_open}}process active interactions, after which the interactions become eligible for artificial termination. Consider using a value that is consistent with the value of the option '''days-to-keep-active-facts'''.{{Editgrn_close}}
+For long-living digital interactions, specifies the maximum number of days to process active interactions, after which the interactions become eligible for artificial termination. Consider using a value that is consistent with the value of the option '''days-to-keep-active-facts'''.
-|ExtendedDesc=<!--'''Questions:'''
+|ExtendedDesc=
-#(1) Is there a dependency between this option and days-to-keep-active-facts? Or if no actual dependency, should we recommend that they be consistent? <font color=red><KR> There is no dependency. I’m OK to recommend that.Action: added recommendation</font>
-#(2) max-call-duration in GIM Classic also controls the following timeouts -- do they apply here? (Presumably other timeouts to do with stuck thresholds for merge and with HA switchover definitely do not.)  <font color=red><KR> max-call-duration has no relation to max-ixn-duration-days and has no affect on digital transformation. Action:removed. </font>-->
-* <strike>The limit for waiting for After Call Work (ACW) before transforming voice interaction data.</strike>
-* <strike>For user data with propagation rules other than <tt>CALL</tt>, the limit for linking user data to IRFs for digital interactions. The option specifies the amount of time, starting from the beginning of the IRF, that the transformation job allows for user data to link to the IRF.</strike>
 ====Artificial termination of long-living interactions====
@@ Line 112: / Line 103: @@
 If an interaction is still active when the '''max-ixn-duration-days''' period expires, the transformation job terminates the interaction artificially in fact tables. Any activity that is related to this interaction that occurs after termination is discarded.
-<strike>GSP generates log message 55-20123 {{Editgrn_open}}<font color=red><KR> It’s not true. GSP has different log message system.</font>{{Editgrn_close}} when it terminates an interaction artificially. You can set an alarm on this message.</strike>
-<strike>Because this option affects a number of aspects of Genesys Info Mart functioning during extraction and transformation of voice and multimedia interactions, be aware that there are potential data implications if you change the option value.</strike>
 |Introduced=
 |Modified=
@@ Line 124: / Line 112: @@
 |ValidValues=10-10000
 |ConfigLevel=standard
-|ShortDesc={{Editgrn_open}}<font color=red>Based on [https://docs.genesys.com/Documentation/Options/Current/GIM/GIM-gim-etl/max-msfs-per-irf max-msfs-per-irf] in the gim-etl section</font>{{Editgrn_close}}
+|ShortDesc=
+Specifies the maximum number of MSF records associated with a given digital interaction that are represented in the Info Mart database. When the number of MSF records associated with a single IRF record exceeds the limit, the transformation job processes only the first n mediation DNs and the last n mediation DNs in the interaction, where n = max-msfs-per-irf/2. In this way, ETL performance avoids being degraded by huge numbers of MSF records for unsuccessful routing attempts for "stuck strategy" scenarios.
-Specifies the limit for the number of MSF records that are associated with a given digital interaction that will be represented in the Info Mart database. When the number of MSF records associated with a single IRF record exceeds the limit, the transformation job processes only the first n mediation DNs and the last n mediation DNs in the interaction, where n = max-msfs-per-irf/2. In this way, ETL performance avoids being degraded by huge numbers of MSF records for unsuccessful routing attempts for "stuck strategy" scenarios.
 |ExtendedDesc=The first n mediation records for a given interaction are processed by the transformation job and populated in the MSF table as they occur. The last n records are postponed until an associated IRF record has been created.
 The option does not affect the mediation durations that are reported in the IRF (QUEUE_DURATION, ROUTING_POINT_DURATION, MEDIATION_DURATION, and PREVIOUS_MEDIATION_DURATION); all these metrics correctly report the full overall mediation time.
-Log message number 55-20120 {{Editgrn_open}}<font color=red>Still true?</font>{{Editgrn_close}} is generated when the max-msfs-per-irf limit is exceeded, triggering the behavior to abbreviate the representation of unsuccessful routing attempts in the Info Mart database. You can set an alarm on the log message, to prompt you to investigate strategies that might be inappropriate for your deployment.
+Log message number 55-20120 is generated when the max-msfs-per-irf limit is exceeded, triggering the behavior to abbreviate the representation of unsuccessful routing attempts in the Info Mart database. You can set an alarm on the log message, to prompt you to investigate strategies that might be inappropriate for your deployment.
 |Introduced=
 |Modified=
@@ Line 138: / Line 125: @@
 {{PEConfigOption
 |OptionName=populate-ixnqueue-facts
-|DefaultValue={{Editgrn_open}}true{{Editgrn_close}}
+|DefaultValue=true
 |ValidValues=true, false
 |ConfigLevel=standard, script: standard
-|ShortDesc={{Editgrn_open}}<font color=red>Based on [https://docs.genesys.com/Documentation/Options/Current/GIM/GIM-gim-etl-populate/populate-mm-ixnqueue-facts populate-mm-ixnqueue-facts] in the gim-etl-populate section</font>{{Editgrn_close}}
+|ShortDesc=
+Enables or disables the population of digital Interaction Queue activity to the MSF table. GSP uses the value configured at the <tt>standard</tt> level for all configured Interaction Queues, but you can override that value for specific Interaction Queues by configuring a different value for those Interaction Queues at the <tt>script: standard</tt> level.
-Enables or disables the population of digital Interaction Queue activity to the MSF table. GSP uses the value {{Editgrn_open}}configured at the <tt>standard</tt> level{{Editgrn_close}} for all configured Interaction Queues, {{Editgrn_open}}but you can override that value for specific Interaction Queues by configuring a different value for those Interaction Queues at the <tt>script: standard</tt> level{{Editgrn_close}}.
+*<tt>true</tt> — The placement of an interaction in an Interaction Queue is represented in the MSF table.
+*<tt>false</tt> — The placement of an interaction in an Interaction Queue is not represented in the MSF table.
-*<tt>true</tt> — The placement of an interaction in an Interaction Queue will be represented in the MSF table.
+GSP always creates an MSF record for the first Interaction Queue that an inbound interaction enters, regardless of the setting of this option.
-*<tt>false</tt> — The placement of an interaction in an Interaction Queue will not be represented in the MSF table.
+<!-- writer: Per Kostya, there is an issue with this: has it been fixed?
+-->
-GSP always creates an MSF record for the first Interaction Queue that an inbound interaction enters, regardless of the setting of this option. {{Editgrn_open}}<font color=red>Per Kostya, there is an issue with this: has it been fixed?</font>{{Editgrn_close}}
 |ExtendedDesc=Strategy time is not included in the mediation duration, with the following exceptions:
 * Scenarios in which an interaction is bounced between an Interaction Queue and a strategy while an available agent is being identified
 * When the '''[[{{FULLPAGENAME}}#show-non-queue-mediation|show-non-queue-mediation]]''' option is set to <tt>true</tt>
-{{NoteFormat|Ideally, set '''populate-ixnqueue-facts''' to <tt>true</tt> only for Interaction Queues for which mediation reporting is {{Editgrn_open}}meaningful{{Editgrn_close}}, so that the MSF table does not become cluttered with unnecessary information. Some Interaction Queues are not useful for reporting, such as the Interaction Queues that are associated with Interaction Workbin objects only through a configured Interaction Queue View.|2}}
+{{NoteFormat|Ideally, set '''populate-ixnqueue-facts''' to <tt>true</tt> only for Interaction Queues for which mediation reporting is meaningful, so that the MSF table does not become cluttered with unnecessary information. Some Interaction Queues are not useful for reporting, such as the Interaction Queues that are associated with Interaction Workbin objects only through a configured Interaction Queue View.|2}}
 |Introduced=
 |Modified=
@@ Line 160: / Line 148: @@
 {{PEConfigOption
 |OptionName=populate-workbin-as-hold
-|DefaultValue={{Editgrn_open}}true{{Editgrn_close}}
+|DefaultValue=true
 |ValidValues=true, false
 |ConfigLevel=standard
-|ShortDesc={{Editgrn_open}}<font color=red>Based on [https://docs.genesys.com/Documentation/Options/Current/GIM/GIM-gim-etl-populate#populate-workbin-as-hold populate-workbin-as-hold] in the gim-etl-populate section.</font>{{Editgrn_close}}
+|ShortDesc=
 Specifies whether the time that an interaction is in an Interaction Workbin is considered to be hold time or mediation.
 * <tt>true</tt> — Workbin time is considered to be hold if the handling resource places the interaction into its own personal workbin. The hold ends when any resource takes the interaction out of the workbin. Various hold metrics are reported in the IRF record that is associated with that handling resource.
-* <tt>false</tt> — Workbin time is considered to be mediation. Whether or not the workbin activity will be represented by an MSF record depends on the value of the '''[[{{FULLPAGENAME}}#populate-workbin-facts|populate-workbin-facts]]''' option.
+* <tt>false</tt> — Workbin time is considered to be mediation. Whether or not the workbin activity is represented by an MSF record depends on the value of the '''[[{{FULLPAGENAME}}#populate-workbin-facts|populate-workbin-facts]]''' option.
 |ExtendedDesc=For time in an Interaction Workbin to be considered hold time, the Agent or Place resource must place the interaction into its own personal workbin. For example, if Agent1 places an email interaction into its personal workbin, the workbin time is considered to be hold; however, if another resource, such as another agent or a strategy, places the interaction into the workbin for Agent1 to handle, the workbin time is not considered to be hold.
@@ Line 187: / Line 174: @@
 {{!}} An Agent/Place resource places the interaction into its personal workbin.
 {{!}} rowspan=3 {{!}} MSF record.*
-{{Editgrn_open}}<strike>This is the default behavior.</strike>{{Editgrn_close}}
 {{!}} colspan=3 {{!}} Hold metrics in the IRF record for the association of that Agent/Place with the interaction.
-{{Editgrn_open}}This is the default behavior.{{Editgrn_close}}
+This is the default behavior.
 {{!}}-
 {{!}} Another resource places the interaction into the personal workbin of an Agent/Place.
 {{!}} rowspan=2 {{!}} MSF record.*
-{{Editgrn_open}}This is the default behavior.{{Editgrn_close}}
+This is the default behavior.
 {{!}} rowspan=2 {{!}} Not represented in the dimensional model.
 {{!}}-
@@ Line 211: / Line 197: @@
 |ValidValues=true, false
 |ConfigLevel=standard, script: standard
-|ShortDesc={{Editgrn_open}}<font color=red>Based on [https://docs.genesys.com/Documentation/Options/Current/GIM/GIM-gim-etl-populate/populate-mm-workbin-facts populate-mm-workbin-facts] in the gim-etl-populate section</font>{{Editgrn_close}}
+|ShortDesc=
 Enables or disables the population of digital Interaction Workbin activity to the MSF table. For workbins that are associated with handling resources of type Agent or Place, this option comes into effect only if GSP has not been configured to consider workbin time as hold (<tt>populate-workbin-as-hold=false</tt>). For the circumstances under which GSP considers workbin time as hold, see the description of the '''[[{{FULLPAGENAME}}#populate-workbin-as-hold|populate-workbin-as-hold]]''' option.
-GSP uses the value {{Editgrn_open}}configured at the <tt>standard</tt> level{{Editgrn_close}} for all configured Interaction Workbins, {{Editgrn_open}}but you can override that value for specific Interaction Workbins by configuring a different value for those Interaction Workbins at the <tt>script: standard</tt> level.{{Editgrn_close}}
+GSP uses the value configured at the <tt>standard</tt> level for all configured Interaction Workbins, but you can override that value for specific Interaction Workbins by configuring a different value for those Interaction Workbins at the <tt>script: standard</tt> level.
 |ExtendedDesc=
-* <tt>true</tt> — Provided that GSP does not consider the workbin time as hold, the placement of an interaction in an Interaction Workbin will be represented in the MSF table. The MSF record references a WORKBIN dimension, which identifies the type of resource that is associated with the workbin and the specific resource that is associated with the mediation. Strategy time is not included in the mediation duration, except for scenarios in which an interaction is bounced between an Interaction Workbin and a strategy as the strategy repeatedly retries busy agents. For more information, see the description of the MEDIATION_DURATION field in {{PDMLinkForGIMPE|topic=GIMPopMSF|linkText=Populating mediation segments}}.
+* <tt>true</tt> — Provided that GSP does not consider the workbin time as hold, the placement of an interaction in an Interaction Workbin is represented in the MSF table. The MSF record references a WORKBIN dimension, which identifies the type of resource that is associated with the workbin and the specific resource that is associated with the mediation. Strategy time is not included in the mediation duration, except for scenarios in which an interaction is bounced between an Interaction Workbin and a strategy as the strategy repeatedly retries busy agents. For more information, see the description of the MEDIATION_DURATION field in {{PDMLinkForGIMPE|topic=GIMPopMSF|linkText=Populating mediation segments}}.
-* <tt>false</tt> — The placement of an interaction in an Interaction Workbin will not be represented in the MSF table.
+* <tt>false</tt> — The placement of an interaction in an Interaction Workbin is not represented in the MSF table.
 |Introduced=
 |Modified=
@@ Line 227: / Line 212: @@
 |OptionName=q-answer-threshold
 |DefaultValue=60
-|ValidValues=1-600000 for digital, {{Editgrn_open}}1-10000 for voice.{{Editgrn_close}} <!--<font color=red>Confirm the valid range. In GIM Classic it's 1-1000 for voice. <KR> correct for digital, for voice = 1-10000</font>-->
+|ValidValues=1-600000 for digital, 1-10000 for voice.
 |ConfigLevel=media, dn: media, script: media
-|ShortDesc={{Editgrn_open}}<font color=red>Based on [https://docs.genesys.com/Documentation/Options/Current/GIM/GIM-gim-etl-media-chat#q-answer-threshold q-answer-threshold] in the gim-etl-media-chat section</font>{{Editgrn_close}}
+|ShortDesc=
 Specifies the default duration, in seconds, that is used on all configured queues as a target time to accept an interaction that entered a queue.
-{{Editgrn_open}}You can configure a different threshold for each media type.{{Editgrn_close}}
+You can configure a different threshold for each media type.
-GSP uses the value {{Editgrn_open}}configured at the <tt>media</tt> level for all configured queues, but you can override the value for interactions of that media type that come through particular virtual queues, digital interaction queues, or workbins by configuring a different value:{{Editgrn_close}}
+GSP uses the value configured at the <tt>media</tt> level for all configured queues, but you can override the value for interactions of that media type that come through particular virtual queues, digital interaction queues, or workbins by configuring a different value:
-* {{Editgrn_open}}For specific Virtual Queue DNs at the <tt>dn: media</tt> level{{Editgrn_open}}
+* For specific Virtual Queue DNs at the <tt>dn: media</tt> level
-* {{Editgrn_open}}For specific digital Interaction Queues or Interaction Workbins at the <tt>script: media</tt> level{{Editgrn_open}}
+* For specific digital Interaction Queues or Interaction Workbins at the <tt>script: media</tt> level
 |ExtendedDesc=
 |Introduced=
@@ Line 248: / Line 232: @@
 |ValidValues=1-1000
 |ConfigLevel=media, dn: media, script: media
-|ShortDesc={{Editgrn_open}}<font color=red>Based on [https://docs.genesys.com/Documentation/Options/Current/GIM/GIM-gim-etl#q-short-abandoned-threshold-voice q-short-abandoned-threshold-voice] for configobject=Application</font>{{Editgrn_close}}
+|ShortDesc=
+Specifies the maximum duration of mediation, in seconds, that is used on all configured queues to indicate that an interaction that was abandoned while in a queue should be considered a “short” abandon. GSP uses this value to determine the state of SHORT_ABANDONED_FLAG in the MSF row for an interaction abandoned in a queue.
-Specifies the maximum duration of mediation, in seconds, that is used on all configured queues to indicate that an interaction that was abandoned while in a queue should be considered a “short” abandon. GSP uses this value to determine the state of SHORT_ABANDONED_FLAG in the MSF row for {{Editgrn_open}}an interaction abandoned in a queue.{{Editgrn_close}}
+You can configure a different threshold for each media type.
-{{Editgrn_open}}You can configure a different threshold for each media type.{{Editgrn_close}}
+GSP uses the value configured at the <tt>media</tt> level for all configured queues, but you can override the value for interactions of that media type that come through particular virtual queues, digital interaction queues, or workbins by configuring a different value:
+* For specific Virtual Queue DNs at the <tt>dn: media</tt> level
-GSP uses the value {{Editgrn_open}}configured at the <tt>media</tt> level for all configured queues, but you can override the value for interactions of that media type that come through particular virtual queues, digital interaction queues, or workbins by configuring a different value:{{Editgrn_close}}
+* For specific digital Interaction Queues or Interaction Workbins at the <tt>script: media</tt> level
-* {{Editgrn_open}}For specific Virtual Queue DNs at the <tt>dn: media</tt> level{{Editgrn_open}}
-* {{Editgrn_open}}For specific digital Interaction Queues or Interaction Workbins at the <tt>script: media</tt> level{{Editgrn_open}}
 |ExtendedDesc=
 |Introduced=
@@ Line 265: / Line 248: @@
 |OptionName=short-abandoned-threshold
 |DefaultValue=10
-|ValidValues={{Editgrn_open}}0-100{{Editgrn_close}}
+|ValidValues=0-100
 |ConfigLevel=media
-|ShortDesc={{Editgrn_open}}<font color=red>Based on [https://docs.genesys.com/Documentation/Options/Current/GIM/GIM-gim-etl/short-abandoned-threshold short-abandoned-threshold] in the gim-etl section</font>{{Editgrn_close}}
+|ShortDesc=
 Specifies the minimum duration, in seconds, of an abandoned interaction in order for it to be considered truly abandoned. GSP uses this value to determine the state of SHORT_ABANDONED_FLAG in the IRF row.
-{{Editgrn_open}}You can configure a different threshold for each media type.{{Editgrn_close}}
+You can configure a different threshold for each media type.
 |ExtendedDesc=
 |Introduced=
@@ Line 282: / Line 264: @@
 |ValidValues=true, false
 |ConfigLevel=standard
-|ShortDesc={{Editgrn_open}}<font color=red>Based on [https://docs.genesys.com/Documentation/Options/Current/GIM/GIM-gim-transformation#show-non-queue-mediation-mm show-non-queue-mediation-mm] in the gim-transformation section.</font>{{Editgrn_close}}
+|ShortDesc=
 Controls whether all mediation time for digital interactions, even mediation time that does not occur within a queue, is represented by an MSF.
-* <tt>true</tt> — Provided that there is an MSF for the first Interaction Queue in a mediation (which is true for mediation time of unhandled interactions), all mediation time for a digital interaction that occurs after the first Interaction Queue, even mediation time that does not occur within a queue, is represented by one or more MSFs. Additional, non-queue MSFs are created {{Editgrn_open}}<tt>for multimedia interactions</tt>{{Editgrn_close}} to represent mediation time that occurs outside an Interaction Queue MSF — for example, mediation time that occurs after an MSF for an Interaction Queue{{Editgrn_open}}<strike>, when</strike> if{{Editgrn_close}} a routing strategy is attempting to find a routing target without the use of a virtual queue.
+* <tt>true</tt> — Provided that there is an MSF for the first Interaction Queue in a mediation (which is true for mediation time of unhandled interactions), all mediation time for a digital interaction that occurs after the first Interaction Queue, even mediation time that does not occur within a queue, is represented by one or more MSFs. Additional, non-queue MSFs are created <tt>for multimedia interactions</tt> to represent mediation time that occurs outside an Interaction Queue MSF — for example, mediation time that occurs after an MSF for an Interaction Queue if a routing strategy is attempting to find a routing target without the use of a virtual queue.
-* <tt>false</tt> — MSFs for digital interactions are focused only on the portion of the mediation time that occurs in a queue, whether it is an Interaction Queue or a virtual queue. There may be gaps in time between MSFs, because the interaction may not be in a queue, or may not be in a queue that is represented {{Editgrn_open}}<strike>in Genesys Info Mart with</strike> by{{Editgrn_close}} an MSF.
+* <tt>false</tt> — MSFs for digital interactions are focused only on the portion of the mediation time that occurs in a queue, whether it is an Interaction Queue or a virtual queue. There may be gaps in time between MSFs, because the interaction may not be in a queue, or may not be in a queue that is represented  by an MSF.
 For digital interactions, mediation that occurs in a virtual queue is always represented in Genesys Info Mart by an MSF. However, depending on the setting for '''[[{{FULLPAGENAME}}#populate-ixnqueue-facts|populate-ixnqueue-facts]]''', mediation that occurs in an Interaction Queue might not be represented by an MSF; in fact, often it is not. When '''show-non-queue-mediation''' is set to <tt>true</tt>, the additional MSFs that are created occur between MSFs for Interaction Queues (in other words, when an interaction moves during mediation from one Interaction Queue that is represented by an MSF to another that is represented by an MSF), or between the MSF for an Interaction Queue and a routing target (agent). The additional, non-queue MSFs may overlap with MSFs for virtual queues, since an interaction may also be in a virtual queue for some (or all) of the mediation time that occurs outside of an Interaction Queue MSF. Furthermore, the additional MSFs may include time that the interaction spent in Interaction Queues that are not represented by an MSF.
@@ Line 353: / Line 334: @@
 {{!}} '''Gaps:''' None
 {{!}}-
-{{!}} colspan="4" {{!}} If the strategies use virtual queues, there will also be separate MSFs for the virtual queues, which might eliminate gaps, even when '''show-non-queue-mediation'''=<tt>false</tt>, and which will overlap with the MSF for the Strategy party when '''show-non-queue-mediation'''=<tt>true</tt>.
+{{!}} colspan="4" {{!}} If the strategies use virtual queues, there are also separate MSFs for the virtual queues, which might eliminate gaps, even when '''show-non-queue-mediation'''=<tt>false</tt>, and which overlap with the MSF for the Strategy party when '''show-non-queue-mediation'''=<tt>true</tt>.
 {{!}}}
@@ Line 367: / Line 348: @@
 |ValidValues=A comma-separated list of queue names
 |ConfigLevel=standard
-|ShortDesc={{Editgrn_open}}<font color=red>Based on [https://docs.genesys.com/Documentation/Options/Current/GIM/GIM-gim-transformation#stop-ixn-queues stop-ixn-queues] in the gim-transformation section.</font>{{Editgrn_close}}
+|ShortDesc=
 In digital deployments that use stop-interaction queues in their business processes, this option specifies the Interaction Queues that are used to handle stopping an interaction (for example, Twitter_StopIxn). When an interaction is placed into one of these queues, GSP considers the interaction to be terminated:
 * The transformation job assigns the technical result/reason combination of COMPLETED/UNSPECIFIED in the IRF of the handling resource that placed the interaction in the queue, and GSP excludes the interaction from further processing.
 * The agent who placed the interaction in the queue is represented as the party that stopped the interaction, and the strategy that actually stops the interaction and performs any associated post-processing is not represented in Genesys Info Mart reporting.
-|ExtendedDesc={{Editgrn_open}}If you do not specify a value for this option{{Editgrn_close}}, GSP handles these situations as transfers to a queue.
+|ExtendedDesc=If you do not specify a value for this option, GSP handles these situations as transfers to a queue.
 |Introduced=
 |Modified=
 |Discontinued=
 }}