Document toolboxDocument toolbox

Pub Name Change Policy and Procedures

Summary / TL:DR: This article will show you the process for changing the name of a publication.

Step by step guide

Upon receipt of a Pub Name Change ticket, please take the following steps:

If not already provided, confirm the new name of the pub, as well as the due date for the change.

The ticket will sit with Global Support until requested due date.

We will want to add the below parties as watchers and pass the ticket to other teams once the change is ready to be made. Important - All PubSvs employees involved with ticket need to set as “Watchers” to see internal comments. “Participants” will only see public replies.

Team order -

  • JSD Renewals: Unassigned when passed; Michael Ward as watcher

  • JSD Global Support: Add yourself as a watcher and Ashley Stevens as watcher to check Advantage portion

  • 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

  • Accounting: Pam Comegys as a watcher

For international clients only: Ticket does not need to go to Accounting or TCC/ECC. They are only added to the ticket to be made aware of the changes taking place. Note from EPP:
“In the past, we only worked domestic ones but that was because we just didn't get international requests OR it was when there was an international EPP. But when we did name changes, we only needed sign off from the support team, IRIS, renewals, and e-comm. the other people (TCC, Accounting) were just added to the ticket as FYI's”

When passing the ticket to each team, please use the below script:

“Hey (team name) / @TSP,

Any changes needed on your end for (pub code)?

Thanks”

Once everyone’s signed off, let the affiliate know that everything is good to go.


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.

Click here to open a ticket


 

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'html-macro' is unknown.