Token Conversion Processes

As of June 1st, 2023, we are retiring our legacy registration server, meaning most offices running XV4, DCV, or DG will need to be converted to token. However, there are some caveats to this as described later in this article.

We are not allowing customers to install the token themselves, however resellers will be handling the token installation for their clients (see “Resellers" section below).

XV3, XVLite, and non-Tuxedo TWAIN reset requests

We will no longer being offering registration resets to users of these softwares. If you receive a request to reset a XV3, XVLite, or non-Tux TWAIN registration code, please use the Common Issues::Legacy Product Registration Reset Denial macro.

XrayVision 4 (NON-RESELLER):

If a client or a client’s IT requests a registration reset for XrayVision 4, we will need to convert them to token. If request came from a reseller, please see “XV4 Reseller Registration requests” section below. This is done free of charge, and does not need to go to sales or accounts.

• Take ticket normally, then apply Common Issues::Reg Reset Request > Convert Registration to Token macro - do not send/set status until below steps are followed

• Use this article to create an XV4 token using their current registration numbers: Replacing XrayVision 4 Standard Registration with Token If the client did not provide registration numbers, they will need to obtain them from Help > Display Registration Information and send them to you first

• Attach the XrayVision 4 upgrader () and ApteryxINI.ini containing their new token registration info to the body of the ticket, then paste the converted registration codes where it says “<primary TO BE FILLED BY TECH>” and “<addl TO BE FILLED BY TECH>” in the body of the ticket

• Set ticket status to Solved to send the macro and files to the client and close the ticket out

DataGrabber:

If a client or a client’s IT requests a registration reset for DataGrabber, we will need to convert them to token. This is done free of charge, and does not need to go to sales or accounts.

• Take ticket and use Common Issues::Reg Reset Request > Convert Registration to Token macro

• Reach out to customer/IT and remote into their server, or schedule a time if needed (program will need to be closed office-wide for the duration of the token conversion process)

• Use this article to create and install an DG token using their current registration numbers: Replacing DataGrabber Standard Registration with Token

• Once complete, use the DG Token::Token Registration Completed macro to tie Accounts into the ticket, paste the legacy registration number that was in use and converted to a token under the “The following codes were converted to token:” section of the comment body, and solve the ticket out.

XrayVision DCV:

DCV 3.4 without Web:

• Take ticket and use Common Issues::Reg Reset Request > Convert Registration to Token macro

• Reach out to customer/IT and remote into their server, or schedule a time if needed (program will need to be closed office-wide for the duration of the token conversion process)

• Use this article to create and install a DCV 3.4 token using their current registration numbers: Replacing DCV 3.4 Standard Registration with Token

• Once complete, use the DCV 3.4 Token::Token Registration Completed macro to tie Accounts into the ticket, paste all legacy codes that were in use and converted to token under the “The following codes were converted to token:” section of the comment body, and solve the ticket out.

DCV 3.5 without Web:

• Take ticket and use Common Issues::Reg Reset Request > Convert Registration to Token macro

• Reach out to customer/IT and remote into their server, or schedule a time if needed (program will need to be closed office-wide for the duration of the token conversion process)

• Use this article to create and install a DCV 3.5 token using their current registration numbers: Replacing DCV 3.5 Standard Registration with Token

• Once complete, use the DCV 3.5 Token::Token Registration Completed macro to tie Accounts into the ticket, paste all legacy codes that were in use and converted to token under the “The following codes were converted to token:” section of the comment body, and solve the ticket out.

DoD (Military, Navy, etc.), Corrections facilities, and hospitals that cannot reach out to our token server

For these types of offices ONLY, reset registration codes as normal.

Dental Care Alliance (DCA)

Reset reg as normal - this DSO is in the process of moving ALL offices to Apteryx.

XV4 Reseller Registration requests:

Our XV4 resellers have been given instructions on how to install token registration. The following resellers will be handling token registration installations themselves, with more to come:

Dental TI

XLDent

Patterson

Percsoft

Dentimax

Kapricorn

Jazz (for Jazz clients specifically, use Converting Jazz Imaging (Harmony) users to token)

Steps to handle their registration requests:

• Reseller will create ticket containing all registration codes needed

• Take ticket and create token INI file using “Token Setup Steps” section of Replacing XrayVision 4 Standard Registration with Token

• Use XV4 Token::Token Registration Conversion for Reseller macro, attach the XrayVision 4 Upgrader**and the INI file you have created for them, a paste all legacy codes that were in use and converted to token under the “The following codes were converted to token:” section of the comment body, and solve the ticket out.

**The XV4 Upgrader is found in Apteryx Legacy Upgraders > XV4 4.0.0.15 Upgraders, located in the Files tab of the Apteryx CX - Customer Support Teams channel

If a tech from a reseller needs help, the document that has been sent to our XV4 resellers is below and can be sent to them for reference:

Dentimax

For Dentimax, attach the DentiMaxAI4Upgrader.

Dentalaire

Dentalaire’s OEM version of DCV does not work with token at this time. If getting a registration reset request from a Dentalaire rep, reset code and do not convert to token.

Patterson (PIBridge):

Patterson will be handling the token registration installation for their customers.

• Reseller will create ticket containing all registration codes needed

• Take ticket and create token INI file using “Token Setup Steps” section of Replacing DataGrabber Standard Registration with Token

• Use DG Token::Token Registration Conversion for Patterson macro, attach the INI file you have created for them, paste the legacy registration number that was in use and converted to a token under the “The following codes were converted to token:” section of the comment body, and solve the ticket out.

If a Patterson rep needs help, the document that has been sent to Patterson regarding how to install the token themselves is below and can be sent to them for reference:

Attachments

• PDDS - XV4 Token Process.pdf
• PDDS - DG Token Process.docx