Summary / TL:DR: This article will show you the process for changing the name of a publication.
Upon receipt of a Pub Name Change ticket, please take the following steps:
Pub Name Change Policy and Procedure
If not already provided, confirm the new name of the pub, as well as the due date for the change.
Once the updates in Advantage have been completed, we will want to add the rest of the below parties as watchers and continue to pass the ticket to other teams in the following order- Renewals, Advantage, E-comm.
JSD Renewals: Unassigned when passed; Michael Ward as watcher
JSD Advantage Support: Unassigned when passed and as a watcher
JSD E-Comm: Sarah Smiley when passed; Patrick Nichols as watcher
JSD Electronic Processing: Joe Notari and Sam Hintz as watchers
TCC: Megan Gill and Kevin Davis as watcher
Middleware: Ryan Sturm as a watcher
Accounting: Pam Comegys as a watcher
*Important* All PubSvs employees involved with ticket need to set as “Watchers” to see internal comments. “Participants” will only see public replies.
3. When passing the ticket to each team, please use the below script:
“Hey (team name) Team,
Any changes needed on your end for (pub code)?
Thanks”
4. Once everyone’s signed off, let the affiliate know that everything is good to go.
a. *If a descriptor override needs to be completed in Advantage, this is up to EPP to complete after the advantage piece is completed.
i. For assistance on the descriptors, please use the new pub code guide: https://14westit.sharepoint.com/:w:/s/EPP/EeBrtTkbNTFDlt3xheUhV-kBYZbJot3gHZI0ZrLM5BhHEQ?e=g6BEgE
Wrap up
You should now know how to handle a pub name change ticket, and understand the process for completing the request.
Still need help?
We know this can be frustrating. To get further help please open a Support ticket.
Cannot find the article you’re looking for?
Suggest a new article here!