What the Heck Happened to July and August? |
![]() |
|
At first, we thought this article would be about how quickly July and August seemed to disappear. One minute summer was getting started, and suddenly September was here. But if you used XenDirect R3 during parts of August, you probably have a very different answer to the question, “What the heck happened to July and August?” We do too. During the summer, our development team was completing a major update to an underlying component of the R3 Admin module. The technology we had been using was being deprecated by its vendor, which meant replacing it was no longer optional. We had been working on the transition for some time and intentionally completed the work in phases to reduce the impact and allow us to test each stage along the way. Unfortunately, the final phase proved far more troublesome than expected. We conducted extensive testing before deployment. In fact, after initially deploying the final update, we encountered an issue significant enough that we rolled the release back and spent another four days testing and making corrections before trying again. Even after that additional testing, once the update was deployed into the full production environment, additional problems surfaced that had not appeared during testing. And there were too many of them. Some affected relatively small areas of R3, while others interfered with important day-to-day functions. Unlike the earlier deployment, this final stage involved changes that could not simply be rolled back, so our development team had to work forward—identifying, correcting, testing, and deploying fixes as quickly as possible. For several weeks, that became our primary focus. We worked through reported issues every day, prioritized those having the greatest impact, and released corrections as soon as we were confident they were ready. We know that none of that changes the disruption these issues caused. We sincerely apologize. You rely on XenDirect to run important parts of your operation, and during portions of August, R3 did not perform at the level you should expect from us. We appreciate the customers who reported issues, provided examples, answered our questions, and worked with our Support team while we resolved them. The good news is that we are now back on track. The major transition is behind us, the significant issues identified during and following the conversion have been addressed, and R3 is once again operating on a much more stable footing. We also came away from the experience with additional lessons about testing a change of this size and about how we manage major underlying technology transitions. Those lessons will be applied to future development and deployment work. July and August certainly went by quickly—but not always for the reasons we would have preferred. Thank you for your patience, your feedback, and for sticking with us through a difficult stretch. |
|
![]() |
WebReg 3.0: All the Latest Details |
|
The migration process from WebReg 2.0 to WebReg 3.0 is in full swing! As we have continued through the first few weeks of the migration process, we have identified and resolved a number of issues based on beta-site testing and customer feedback. We are also completing the final work and validation for payment gateway connections. Because of this additional work, our originally planned Go-Live dates have been postponed. However, we are on schedule with all preview/beta sites and will continue to remain on schedule for that phase of the migration process. Tentative Go-Live DateIf your Go-Live date is already past or is close, we will contact you with a new tentative date for your approval. Please keep in mind that this date remains tentative until we successfully complete our final testing and confirm that your site is ready for production use. Before Go-Live, our team will perform a more extensive review of your WebReg 3.0 preview site. This will include testing various registration, account, payment, and other site functions. As part of that testing, we will also complete an actual $1.00 course purchase using your payment gateway. This allows us to verify that the payment is successfully transmitted through the gateway and processed as expected. The first set of Go-Live migrations are organizations using Authorize.Net as their payment gateway. If you have not already provided us with your Authorize.Net Client Key, we will also need that information before we can complete the final payment gateway testing. Please send it to us through a support ticket if it is still outstanding. Successful completion of this testing, particularly the payment gateway verification, will be one of the final requirements before we confirm your Go-Live date. Client LoginAbout a week ago, we disabled the test Client login on the beta sites to make some changes related to the login process. We expect to have client login available within a few days. Once it is restored, you will again be able to test the client login and account-related functions as part of your beta-site review. WebReg 3.0 Beta UpdatesWe have also updated our Help Center page that tracks WebReg 3.0 beta fixes, changes, and additions. This works much like the update information we provide for the XenDirect Admin module and gives you a central location to see what has changed during the beta period. https://xenegrade.kayako.com/article/792-updates-webreg-release-3-2026 We recommend checking this page periodically, particularly if you previously reported an issue or noticed something that did not appear to be working as expected. WebReg 3.0 CommunicationsWe also use Mailchimp to communicate important Xenegrade news and WebReg 3.0 updates, and we want to make sure the primary WebReg 3.0 contacts at your organization are subscribed. Many contacts are already subscribed. However, some users may currently be listed as unsubscribed. Because Mailchimp requires the individual user to manage that preference, Xenegrade cannot resubscribe someone who has previously unsubscribed. If you are not currently receiving our news emails, or want to confirm your subscription, you can subscribe or update your preference using Subscribe to News from your XenDirect user menu. We recommend that each of your primary WebReg 3.0 contacts confirm that they are subscribed so they do not miss important announcements as we move closer to Go-Live. Continue Reporting IssuesAs you continue reviewing and testing your beta site, please continue to submit a separate support ticket for each issue you discover. Keeping each issue in its own ticket allows our support and development teams to immediately identify the specific problem, track its status, and work on it without having to separate multiple issues from a single ticket. Please continue testing as much of the site as possible. The feedback we receive during this stage is helping us identify and resolve issues before WebReg 3.0 is deployed more broadly. We will continue to keep you updated as we complete the remaining work and move closer to confirming your Go-Live date. |
|
TIP: Do You Have a Broken Image? |
![]() |
|
If you have an image in a report, WebReg, or some other location where the image URL is coming from within XenDirect, here is the solution to fix that. First, the issue is related to a server change. A portion of the recent migration effort to WebReg 3.0 required us to make a server storage change to match the newer technology. That means that we also had to move images and files. But the change also required a change to the URL path. This fix is easy. You literally only need to add one character to the URL. |
|
![]() |
The XenDirect
|
|
Welcome to the Add-on Marketplace, your quick look at features and services that can extend the value of XenDirect. Add-ons can help you streamline processes, improve efficiency, add new capabilities, and tailor the system more closely to the way your operation works. Whether you are looking for automation, specialized tools, training, or other enhancements, add-ons offer practical ways to expand what your system can do. If you have questions or would like more information about any add-on, please submit a support ticket through the Help Center. We will be glad to discuss options and help you determine what may be the best fit for your needs. |
|
|
|
|
|
|
2026 Holiday
|
![]() |
|
Xenegrade will be closed on the following days in 2026:
If XenDirect is unavailable during a closure, use the emergency process outlined in the Help Center. |
|
![]() |
Helpful Reminders |
|
|





