Jdruker/RebrandingTest
Exclude?
- VCC product, Premier Edition Cloud -- prodshort is PEC
- "Genesys Cloud - Premier Edition"
- Should "Genesys Cloud API Driver" for Twitter, etc. change?
- GVP version 85something draft -- or ignore issues because these versions are throwaway?
- What is happening with https://help.mypurecloud.com?
Contents
Exclusions/Exceptions
URL parts of internal or external links
Links to wiki pages should not be a problem because topic names will be changed. But mypurecloud.com is a potential problem.
- Using the Genesys Engage Adapter
- Genesys Engage cloud Support for GDPR
- For an overview of short-term forecasting, see Work with short-term forecasts. (Source page)
Products/components
With "Genesys Engage cloud":
- Cloud iWD or Genesys Engage cloud intelligent...
- Example: What does Cloud iWD do?...Cloud iWD features and functions (Source page)
- Genesys Cloud - Premier Edition -- should not change?
- Example: Genesys Cloud - Premier Edition: CTI Adapter enables you to handle interactions and work with your team (https://docs.genesys.com/Documentation/CCTI). Also https://docs.genesys.com/Documentation/CXB
- Genesys Cloud API Driver for Twitter -- should this change or not? RN: Genesys Cloud API Driver for Twitter Release Notes (Also in SOE link, Options link)
Issues with "PEC" because some instances need to change and some don't:
- Premier Edition Cloud (PEC) -- https://docs.genesys.com/Documentation/PEC/Current/Solution/Welcome
- This is the initial release of WebRTC Media Service on the Genesys Engage cloud (PEC) platform. Agents can handle both inbound and outbound voice calls through WebRTC-capable devices like Genesys Softphone by communicating with the PEC platform through the WebRTC Media Service. The WebRTC Media Service supports Genesys Softphone version 9.0.003.04+. (WebRTC RN)
- Prodshort in VCC doc URLs -- e.g., Documentation:PEC:Solution:Welcome:Current
- Template:PEC_Migrated
File names in repository links + titles of PDFs
Add examples -- Ed can find them?
Graphics file names
Other forecasting methods available in Genesys Engage cloud include:
- Weighted Historical Index—Uses previously captured historical Genesys Cloud data and specifies a historical index weighting.
- Import —Uses forecast data from an imported CSV file.
Find information and procedures that describe this method in the article Add a short-term forecast.
(Source page)
Once all the necessary configuration details are entered, click on the Launch button to launch Widgets.
- Cloud_banner_450x293.png used on https://docs.genesys.com/Documentation/GH/GH/Supervisor/Welcome
- Genesys Engage-Icon-with-text-Portrait-rgb-Full-color@4x.png but used only on Richard's User pages?
Potential false positives because s/w hasn't caught up
Starting in the 9.0.008.03 version, WebChat supports Genesys Engage v3 API via transports configuration section. The same can be tested In the launcher tool using the WebChat [with Transport only] section under GenesysEngage-cloud tab.
(Configuring Genesys Widgets)
Easy revisits
- This section contains the Enterprise Manager and Account Manager help documentation for Outbound for Genesys Engage (Cloud). (Outbound for Genesys Engage cloud Help)
- Genesys provides streamlined, lightweight, extensible, and mobile optimized widgets. By embedding widgets on your website, you can obtain great customer experiences powered by Genesys Engage cloud or Premise. (Genesys Widgets)
- Genesys's cloud architecture... (standard "About Genesys Engage cloud" intro in PSAAS guides, e.g.: Supervisor's Guide).
- "Genesys Engage cloud" in PDNA -- reconfirm or afterwards revert this: "As of March 2019, Performance DNA (PDNA) is only available as a Genesys Engage cloud product supporting hybrid architectures....If you are an existing Genesys Engage on-premises customer and are looking to add PDNA functionality, you can now use PDNA through a hybrid architecture with PDNA hosted on standalone cloud....If you are interested in migrating from the on-premises version of PDNA to the Genesys Engage cloud version,..." (Documentation/PDNA and Documentation/GSA)
- Might be worth revisiting "portal" pages like [[1]] for now-deprecated usage (e.g., "For other documentation for our Cloud products...").
Glossary entries
Genesys Customer Interaction Management (CIM) Platform is the base product bundle for Genesys Engage, and is a pre-requisite for most other Genesys Engage products. CIM Platform captures, processes, routes, manages and reports the life cycle of customer interaction or activity type across any contact center environment. Each CIM Platform seat requires at least one Interaction seat or Gplus Routing Interaction. (CIM Platform)
Not a problem
Usage we don't need to consider because we're not worrying about "genesyscloud" (e.g., in provider URLs like api-usw1.genesyscloud.com) or "[C|c]loud" when it's standalone. But there might be potential false positives because the s/w hasn't caught up.
- Code samples and prescribed input — Markup to exclude would be within <pre>, <source>, or <tt> tags or within URLs
- Jira refs (GCLOUD)
- Options default/valid values — References to "Genesys Social Analytics cloud" are not a problem (e.g., gsa-api-key)
- External products/concepts — Firebase Cloud Messaging (FCM)
- "Genesys" not part of "Genesys Engage cloud"
- "hybrid" because generic usage OK
Problems we're ignoring
- "platform" because we're ignoring this for pending further guidance from Nancy.
- Note undesirable usage as well.
- "product" and "application" that are contrary to new guidelines
- Undesirable usage
- If not specified, works like "on-prem" installation. (Source page)
- The extract and transform stages pertain to BDS running on premise. Platform and cloud interact using HTTPS protocol. BDS generates billing data files in the transform stage, saves them into local folder on Docker host, and (in online mode only) uploads them to S3....The loader stage pertains to BDS running on the Cloud. Here, generated files are validated and transferred to the IT department through Secure File Transfer Protocol (SFTP). (Source BDS page
- Possessive Genesys.
Standard replacements
Some random links to check:
- WFM supports integration with Genesys Cloud API for Forecasting using the Genesys Cloud upload service, which supports payloads greater than 3 MB. (wm-svr8521509)
- GAX no longer supports Cloud mode (no relation to Genesys cloud architecture) in the Agent Management dashboard. (https://docs.genesys.com/Documentation/RN/8.5.x/gax85rn/gax8525015)
- Genesys Engage cloud documentation