Accessibility Skip to content
  • Add the translated asset in specific product/services folder
  • Keep the filename same as of EN except for last country code (example: tc8-ds-ko.pdf)
  • Our system automatically will pick up the KO version if named correctly

Workfront Reference Request: https://poly.my.workfront.com/issue/view?ID=5ee9dc380212831134076256093c323c

 

There are 3 areas that PIDs are stored/used.

  1. The PIM model record. this is used to drive automation to send a customer to product marketing pages (https://www.poly.com/product/?pid=xxxx) or product support pages (https://docs.plantronics.com/?pid=xxxx)
  2. A content fragment that maps PID to a release note KB article (https://www.poly.com/firmware-release-notes?pid=xxxx). The content fragments are located at https://author.poly.com/assets.html/content/dam > www > content-fragments > support > Release Notes > Hub Desktop
  3. A content fragment that returns a JSON of release notes for mobile devices (https://www.poly.com/catalog/firmware?prodId=xxxx&version=134&locale=en_US). The content fragments are located at 
    https://author.poly.com/assets.html/content/dam > www > content-fragments > support > Release Notes > Hub Mobile

Page 1 of the document received in request refers to the hub desktop release notes and usually, Karla Zamarripa manages that.

Page 2 of the document received in request refers to the hub mobile release notes and we usually handle that.

 

Create Desktop Release Notes:

  • Navigate to
    https://author.poly.com/assets.html/content/dam > www > content-fragments > support > Release Notes > Hub Desktop
  • Create > Content Fragment > Release-Notes
  • Add title & name
  • On the release note page, add name again
  • Add the reference URLs on the specific country boxes as per document provided in the request
  • Add "PID" as per the request
  • Save and Publish

Create Mobile Release Notes:

  • Navigate to
    https://author.poly.com/assets.html/content/dam > www > content-fragments > support > Release Notes > Hub Mobile
  • Go to EN country
  • Create > Content Fragment > Firmware
  • Add title and name
  • Fill Name as "PID Reference:" from request document
  • Fill Lang Locale. eg: en_US
  • Add release note URL: https://www.poly.com/software
  • Add version attributes: They are mentioned in "Release Note Copy" in the requested document
  • Add Version (mentioned as "Firmware version" in the document)
  • Save and Publish

 

 

We should NEVER post any event.on24.com web link on Poly.com. e.g. https://event.on24.com/wcc/r/2384717/AE61BF487AA39148978F5B4E19E213FE

These registration pages are created for a different use case when somebody creates a webinar (whether live or on-demand webinar)… but should never be used for any explicit marketing activity (linking in social, emails, web, etc). There will (should) always be a corresponding connect.poly.com registration page… and that is the page we should post.

So if you ever see any request to add a link to “event.on24.com”, tell them, ‘I need to connect.poly.com registration page”.

  • Navigate to Events section:
    https://author.poly.com/sites.html/content/www/events
  • Navigate to event year (2020/2021)
  • Create "Poly Event Detail Page"
  • Add Title, Name, Page Title, Navigation Title
  • Edit the "Event Detail" component
  • Add Event Title
  • Select "Tradeshow" as Event Type
  • Add Start Date & End Date
  • Select the Region
  • Add location (Virtual/or address of event)
  • Add Ticket link (Event webpage link)
  • Event Tier = 1
  • Go to "Event Landing Page Reference"
  • Add Event Webpage link in "Event Landing Page Reference"
  • Save and Publish