|
|
| (4 intermediate revisions by the same user not shown) |
| 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=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.
| |
| − | }}
| |
| − | {{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.
| |
| − | }}
| |
| − | {{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.
| |
| − | }}
| |
| − | {{Issue
| |
| − | |TicketNumber=PRSM-28895
| |
| − | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
| |
| − | |LocalContent=Metadata fields for the Metadata Frequency report now appears 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 programs tagged, then the interaction is 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.
| |
| − | }}
| |
| − | {{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.
| |
| − | }}
| |
This is a draft page; it has not yet been published.
