We then escalate the case to the IPS who reviews it and concludes that we are good to go ahead and use the solution. A fascinating kill-the-messenger strategy.From August 2022 IPS Support reduces its support to us down to zero, thereby being in breach of the service agreement. What happens is that IPS Support recommends us to look for an alternative community solution since they seem to think that we are to blame for their frustrating workload. As you might guess by now, this does not happen. You might expect that this would render an excuse from IPS due to a software having more bugs than a stray dog. The stalling issue was never resolved.August 2022IPS Support does a ticket count and notes that we have filed 145 support tickets since May 2021. In August 2022 Stripe Support asks for specific information from IPS but this is never provided despite reminders. Again IPS Support points towards our environment, despite us once again presenting a solid test battery showing the same stalling issue no matter what environment we use. May 2022During our tests, a large portion of new members’ Stripe payments stalls which (once again) effectively stops new members’ registrations. We estimate that the 18-month-long process would have taken us about 6 months with a stable and fully documented software, and an open-minded Support. The site was plagued by quite a few issues. The application was used by two admins configuring and testing multiple use case scenarios and front-end designs. We used the SAAS “Invison Power Board” from May 2021 to October 2022. This explains why we stayed on board through an 18-month-long orgy of bug reports. The software had also been around for 10-20 years (depending on how you count a major version upgrade) and could be expected to be stable. We chose “Invison Power Board” (IPB) from Invision Power Systems (IPS) as the tool for this since it had one for our offering critical functionality. We are two information technology managers and consultants both having 20+ years of experience who decided to launch a community directed towards executives. Within two weeks of testing and analysis, the error was found - in the IPS environment (the service worker). ![]() But not until a senior IPS developer was engaged the IPS Support blame game stopped. Quite the contrary, during three frustrating months we did hundreds of user registration tests on all kinds of hardware, three different browsers, and two separate networks. According to IPS Support everything points towards that our environment is to blame. Autumn 2021During our tests a large portion of new members’ registrations stalls. A critical mistake by us when viewed in the mirror. No excuse was given, but we decided to return to IPS due to all the hours invested. A Support staff then, but not until then, manually checked the code and concluded that we had not changed a single letter. We then communicated that we had decided to leave IPS. Since we had not changed any program code there was nothing to reverse. “Our flag shows that you have changed the code.” End of discussion. ![]() The Support was, as always, very confident and not open to arguments. ![]() A few IPB issue samples:Autumn 2021IPS support suddenly communicates that we had changed the program code, effectively leaving us without support – if we did not reverse the change.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |