BizX in Stage is on b2111 while BizX Prod after b2105 upgrade is on b2105 which is different then Stage

[may_thang]

Hi,

Our Production BizX header did not change like in our Stage environment which we did UAT.  We noticed the BizX in Stage is on b2111 while BizX Prod after b2105 upgrade is on b2105.  Is it just us or other vSAAS customers have the same issue.  We have some automation tool that is sensitive to screen changes hence this cause a problem as it did not match our stage environment?  Does this mean that BizX b2111 has a different upgrade schedule?  I am trying to find out why is it different and when would BizX b2111 applied to our Prod environment or was it an error that our stage environment BizX was upgraded to b2111.  This has not been a smooth upgrade.  We are having issues with our custom e-signature as well whereby users are not able to sign off.  However after clearing browser cache or forcing user to actively type in password instead of the saved password on their browser and various other things, it eventually worked so we cannot pinpoint the root cause sigh.

Thanks,

May

[Maria_Consiglia]

I don't know why there s a differente upgrade window foe bizX, but the new bizX release will be upgraded in production environment on 19th november.

[may_thang]

Thanks for the info!  I guess I will have to prepare for it since we originally modified our bot runners to align with the new header then had to change it back so it looks like we have to change it again. sigh!

[PKetnouvong]

Hi May,

We had an eSignature issue prior to the upgrade because our eSignature extension needed to be updated.  Please make sure it's the same in all environments.  

[may_thang]

It is the same set up in all environments.  We did see the issue related to sign off but we were able to resolve it with workaround and submitted a case to SF however they did not resolve it and we were going back/forth trying to explain the issue and of course in Production is is worst since we have thousands of users vs the few testers in Stage.  

[MaryKatherineJ]

@may thang, we are also having issues with our custom e-signature extension requiring users to clear they browser cache before they can successfully enter their e-signature credentials.  Are you seeing it predominantly in users who have saved their password in their browser?  I am seeing the same issue regardless of browser; I have tested Edge (Chromium), Firefox, Chrome, and even good old IE11.  But closing/reopening the browser session or clearing the cache, or rebooting the computer seems to help. 

Very frustrating.  I just don't know why the release is causing this issue.  

Mary Katherine

[rorennie]

We also had the exact same issue with our e-signature and with 4500 people it is causing the helpdesk a major issue, despite comms going out detailing the problem, another issue is the alignment between Sailpoint AD, BizX and vLMS user names with LMS being case sensitive which once again cases issues for end users (at least we got away from having to use Employee Numbers)

Regards

Bob