Draft:RN/Recording QM and Interaction Analytics/8.5.512.33 - Revision history

WikiSysop: Redirected page to Draft:RN/Recording QM and Interaction Analytics/8.5.512.34

2022-10-20T05:15:38Z

Redirected page to Draft:RN/Recording QM and Interaction Analytics/8.5.512.34

WikiSysop at 09:30, October 11, 2022

2022-10-11T09:30:57Z

WikiSysop at 06:45, October 7, 2022

2022-10-07T06:45:34Z

WikiSysop at 07:45, October 3, 2022

2022-10-03T07:45:40Z

WikiSysop at 09:30, September 30, 2022

2022-09-30T09:30:47Z

WikiSysop at 08:30, September 30, 2022

2022-09-30T08:30:50Z

WikiSysop at 08:15, September 30, 2022

2022-09-30T08:15:52Z

WikiSysop at 08:00, September 30, 2022

2022-09-30T08:00:48Z

WikiSysop at 07:45, September 30, 2022

2022-09-30T07:45:48Z

WikiSysop at 19:16, September 29, 2022

2022-09-29T19:16:14Z

← Older revision		Revision as of 05:15, October 20, 2022
Line 1:		Line 1:
−	~~{{ComponentRN~~	+	#REDIRECT [[Draft:RN/Recording QM and Interaction Analytics/8.5.512.34]]
−	~~\|ComponentId=c6d90412-17a5-4d3b-b822-060c75731775~~
−	~~\|JQL=issuekey in (PRSM-28856)~~
−	~~\|DeploymentTypeId=5439f1be-1868-4091-b058-1667389b6ce1~~
−	~~\|ReleaseDate=2022-09-30~~
−	~~\|Highlight=Includes support for SMS interaction and resolved issues.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=PRSM-28856~~
−	~~\|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72~~
−	~~\|Content=SpeechMiner now supports processing of SMS interactions. You can now filter, evaluate, and create a report for these interactions.~~
−	~~\|LocalContent=SpeechMiner now supports processing of SMS interactions. You can now filter, evaluate, and create a report for these interactions.~~
−	~~\|SupportingDocumentation={{Link-AnywhereElse\|product=PEC-REC\|version=Current\|manual=User\|topic=createanewsearch~~#~~interaction-properties}}~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=WFOAZURE-2113~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	\|LocalContent=A search performed with more than one term in the search filter now returns the required interactions. Previously, the search performed with multiple terms didn’t return any interactions.
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=WFOAZURE-1971~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	~~\|LocalContent=If a topic has terms with a single word, then the single word term is now recognized only as a complete word~~ and not as part of other words. For example, the term “age" doesn’t recognize and match the words such as “coverage”, ”package”, and so on. Previously, the single word term in the topic recognized similar terms even if the term was part of the words.
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=WFOAZURE-1903~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	~~\|LocalContent=When a digital interaction has only an open HTML tag and the text content type is not set to HTML, the text after the open HTML tag now appears in the UI~~. Also, if the custom tag is within the HTML tag, and if the text content type is not set to HTML, the custom tag now appears in the UI. Previously, in such scenarios, the text after the open HTML tag and the custom tag didn’t appear in the UI.
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=PRSM-28895~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	~~\|LocalContent=The metadata fields for the '''Metadata Frequency''' report now appear in alphabetical order.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=PRSM-28844~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	~~\|LocalContent=SpeechMiner now displays the system recorded or automated or IVR segments of an interaction with a new icon in the '''Transcription''' section.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=PRSM-28818~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	~~\|LocalContent=Free Form answer can now handle up to 4000 characters. Previously, Free Form supported only up to 2000 characters.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=WFOAZURE-2193~~
−	~~\|IssueCategoryId=7677e764-86f7-44e3-92bc-f13b59c71260~~
−	~~\|LocalContent=If your '''Free form''' answer has 4000 characters, the last character in the '''Free form''' answer does not appear when you export it to PDF.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=PRSM-28644~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	~~\|LocalContent=If an interaction is sent with multiple segments tagged to different programs, the whole interaction is now tagged to the latest program and the search no longer fails.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=WFOAZURE-2035~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	~~\|LocalContent=The '''Usage Tracking''' report execution is now optimized to improve its performance.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=PRSM-28836~~
−	~~\|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72~~
−	~~\|LocalContent=Interaction metadata that are marked as key metadata items now appear on top of the form in an evaluation session in ''key:value'' pairs.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=WFOAZURE-2195~~
−	~~\|IssueCategoryId=7677e764-86f7-44e3-92bc-f13b59c71260~~
−	~~\|LocalContent=When an evaluation is exported to PDF, '''Free form''' answer is displayed after a blank page and the first line of the answer is not aligned properly~~.
−	}}

@@ Line 16: / Line 16: @@
 |TicketNumber=WFOAZURE-2113
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|LocalContent=A search performed with more than one term in the Search Filter now returns the required interactions. Previously, the search performed with multiple terms didn’t return any interactions.
+|LocalContent=A search performed with more than one term in the search filter now returns the required interactions. Previously, the search performed with multiple terms didn’t return any interactions.
 }}
 {{Issue
@@ Line 31: / Line 31: @@
 |TicketNumber=PRSM-28895
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|LocalContent=The metadata fields for the Metadata Frequency report now appear in alphabetical order.
+|LocalContent=The metadata fields for the '''Metadata Frequency''' report now appear in alphabetical order.
 }}
 {{Issue
 |TicketNumber=PRSM-28844
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|LocalContent=SpeechMiner now displays the system recorded or automated or IVR segments of an interaction with a new icon in the Transcription section.
+|LocalContent=SpeechMiner now displays the system recorded or automated or IVR segments of an interaction with a new icon in the '''Transcription''' section.
 }}
 {{Issue
@@ Line 46: / Line 46: @@
 |TicketNumber=WFOAZURE-2193
 |IssueCategoryId=7677e764-86f7-44e3-92bc-f13b59c71260
-|LocalContent=If your Free Form answer has 4000 characters, the last character in the Free Form answer does not appear when you export it to PDF.
+|LocalContent=If your '''Free form''' answer has 4000 characters, the last character in the '''Free form''' answer does not appear when you export it to PDF.
 }}
 {{Issue
@@ Line 56: / Line 56: @@
 |TicketNumber=WFOAZURE-2035
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|LocalContent=The Usage Tracking report execution is now optimized to improve its performance.
+|LocalContent=The '''Usage Tracking''' report execution is now optimized to improve its performance.
 }}
 {{Issue
 |TicketNumber=PRSM-28836
 |IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
-|LocalContent=Interaction metadata that are marked as key metadata items now appear on top of the form in an Evaluation Session in key:value pairs.
+|LocalContent=Interaction metadata that are marked as key metadata items now appear on top of the form in an evaluation session in ''key:value'' pairs.
 }}
 {{Issue
 |TicketNumber=WFOAZURE-2195
 |IssueCategoryId=7677e764-86f7-44e3-92bc-f13b59c71260
-|LocalContent=When an evaluation is exported to PDF, Free Form answer is displayed after a blank page and the first line of the answer is not aligned properly.
+|LocalContent=When an evaluation is exported to PDF, '''Free form''' answer is displayed after a blank page and the first line of the answer is not aligned properly.
 }}

@@ Line 51: / Line 51: @@
 |TicketNumber=PRSM-28644
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|LocalContent=If an interaction is sent with multiple programs tagged, then the interaction is now tagged to the recent program.
+|LocalContent=If an interaction is sent with multiple segments tagged to different programs, the whole interaction is now tagged to the latest program and the search no longer fails.
 }}
 {{Issue

@@ Line 62: / Line 62: @@
 |IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
 |LocalContent=Interaction metadata that are marked as key metadata items now appear on top of the form in an Evaluation Session in key:value pairs.
 }}

@@ Line 16: / Line 16: @@
 |TicketNumber=WFOAZURE-2113
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|LocalContent=Search performed with more than one term in Search Filter now returns the required interactions. Previously, the search performed with multiple terms didn’t return any results.
+|LocalContent=A search performed with more than one term in the Search Filter now returns the required interactions. Previously, the search performed with multiple terms didn’t return any interactions.
 }}
 {{Issue
 |TicketNumber=WFOAZURE-1971
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|LocalContent=If a topic has terms with single word, then the single word term is now recognized only for the complete word and not part of the word. For example, the term “age“ doesn’t recognize and match the words such as “coverage”, ”package”, and so on. Previously, the single word term in the topic recognized the similar term even if the term was part of the word.
+|LocalContent=If a topic has terms with a single word, then the single word term is now recognized only as a complete word and not as part of other words. For example, the term “age" doesn’t recognize and match the words such as “coverage”, ”package”, and so on. Previously, the single word term in the topic recognized similar terms even if the term was part of the words.
 }}
 {{Issue
 |TicketNumber=WFOAZURE-1903
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|LocalContent=When a digital interaction only has an open HTML tag and the text content type is not set to HTML, the text after the open HTML tag still appears in the UI. Also, if the custom tag is within the HTML tag, and if the text content type is not set to HTML, the custom tag still appears in the UI.
+|LocalContent=When a digital interaction has only an open HTML tag and the text content type is not set to HTML, the text after the open HTML tag now appears in the UI. Also, if the custom tag is within the HTML tag, and if the text content type is not set to HTML, the custom tag now appears in the UI. Previously, in such scenarios, the text after the open HTML tag and the custom tag didn’t appear in the UI.
 }}
 {{Issue
 |TicketNumber=PRSM-28895
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|LocalContent=Metadata fields for the Metadata Frequency report now appears in alphabetical order.
+|LocalContent=The metadata fields for the Metadata Frequency report now appear in alphabetical order.
 }}
 {{Issue
@@ Line 51: / Line 51: @@
 |TicketNumber=PRSM-28644
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|LocalContent=If an interaction is sent with multiple programs tagged, then the interaction is tagged to the recent program.
+|LocalContent=If an interaction is sent with multiple programs tagged, then the interaction is now tagged to the recent program.
 }}
 {{Issue
 |TicketNumber=WFOAZURE-2035
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|LocalContent=Usage Tracking report execution is now optimized to improve its performance.
+|LocalContent=The Usage Tracking report execution is now optimized to improve its performance.
 }}
 {{Issue

@@ Line 11: / Line 11: @@
 |Content=SpeechMiner now supports processing of SMS interactions. You can now filter, evaluate, and create a report for these interactions.
 |LocalContent=SpeechMiner now supports processing of SMS interactions. You can now filter, evaluate, and create a report for these interactions.
-|SupportingDocumentation={{Link-AnywhereElse|product=PEC-REC|version=Current|manual=User|topic=createanewsearch}}
+|SupportingDocumentation={{Link-AnywhereElse|product=PEC-REC|version=Current|manual=User|topic=createanewsearch#interaction-properties}}
 }}
 {{Issue

@@ Line 40: / Line 40: @@
 |TicketNumber=PRSM-28818
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|LocalContent=Free Form question description can now handle up to 4000 characters. Previously, Free Form supported only up to 2000 characters.
+|LocalContent=Free Form answer can now handle up to 4000 characters. Previously, Free Form supported only up to 2000 characters.
 }}
 {{Issue