Hi,
I am following the instructions for updating our SAAS implementation of QuickShip to use the ‘OAuth’ security in the UPS API.
The Epicor instructions state:
However, when I click on 'Register
Has anyone else done this successfully.
If so, please can you post the steps.
Thanks,
Andrew.
I used this KB KB0134527 in 2024.1 On Prem. I even found the user and password for the user that was made during our initial install.
I only found the control id on the paper or pdf copy of the invoice not in the UPS invoice download.
I did not get the UPS site to launch until I cleared my browser cache which was after the the step where you run index.html.
Thanks Greg.
Do I still need to fill out the registration details, even though I am already connecting to UPS via the old authentication method already?
I completed this last Friday and encountered the same issue, but only when I attempted to register in QuickShip from my PC. If I logged into QuickShip on the server and clicked Register, I was taken to the UPS login page as the KB article states.
EDIT; Scratch that. it goes to the site for login.
and I am too chicken on my dev site to go further. 
Hi,
We are running Quickship in the cloud so there is no server to log onto.
Cheers,
Andrew.
Support will walk you through it if you open a ticket. I pointed out some issues in the instructions when I went through this but I don’t think its been updated. Nothing like waiting till the last minute!
Thanks Alisa - I find it amazing that people can write wrong instructions. You would think it would be harder to write wrong instructions than right ones.
However, I’ll take the comment about ‘last minute’. Certainly missed this when it landed in my inbox.
There is a distinction to be made between writing wrong instructions, and the instructions being outdated.
No they are just wrong, the tech agreed with me.
A story about “the last minute”…
A long, long time ago (early 90s)
in a galaxy far, far away (Scotts Valley, CA)…
I was a telephone tech support rep for a tape drive manufacturer. I also wrote the user manuals for the QIC-40 products.
It was a relatively small company, and I knew the developers personally. I’d get a heads-up that a new product/version/feature needed some documentation, and I’d go over there and they’d walk me through how it worked, and I’d have a couple of days to write it up all nice and tidy. SOMETIMES I’d have already been able to play with it, SOMETIMES I (or one of my colleagues) had suggested the feature, so SOMETIMES I had a little prep. But not very often.
And then SOMETIMES I’d get a frantic call at the last might, after my nice tidy write-up was done, saying “YOU HAVE TO TAKE OUT THE PARAGRAPH(S) ABOUT zzz FEATURE IT GOT PULLED”.
This was a small company. Epicor is a BIG company. @timshuwy has written PLENTY of times about how features get included/excluded at the last minute. The folks who write the software are NOT the folks who write the documentation (and THANK GOODNESS for that). “The Last Minute” is literally the FIRST minute that the documentation crew knows for sure what’s there.
Most frequently, the revenue side of the house will have the loudest voice on when updates get released. “Docs not ready yet” typically isn’t going to delay it. @karihagedorn and her team are doing the best they can!
We had this issue and I had to use a Incognito / InPrivate window to complete the process. QS Support said it was something with cookie cache or a extension.
When I had to install QuickShip last year the documentation was almost non existent and I suspect it is a case of playing catch up.
The good news is, certainly for SaaS based QuickShip, is the Epicare support is excellent.
And sometimes, instructions were 100% correct at the time of release, but something outside of our control changes… one example of this is when Several years ago, Google Chrome did an unannounced change the way that some inner workings of Chrome worked, and resulted in Epicor being required to change our software, AND also the documentation.
So, at any point in time, someone might look at documentation and say “it is wrong”… it was most likely not developed wrong at the time is was written.
