OK Phil because what we have observered on our environment is that if we import custom A from test environment to production environnent we don’t find our changes in production even after publishing perhaps we have then an issue with our mobilecustomizer release (or else) we will investigate more Thanks
HI Phil for our V15.1 or 15.2 we have applied the fix for the DC but we still have an issue on the address finder it’s not working we have an error and can’t use it. Do you have a workaround for this module ?
Hi Phil thanks for the info we have the first customer case reported this morning on V15.2 and V15.4
Hi Phil I have published again the customization but the release number on my mobile is still 15.4.0.0 (note that if i set up on Asteamobile apps the std asteamobile URL \asteamobileedge\ i cans see the 15.4.0.1)
It looks like there was an issue on the customer process flow endpoint , the error message was not clear and we didn’t know if the message was effectivly sent or not
yes as the back office to be consistent
Hi Ugo , if we do that this ok but that’s mean a user which is customizer in the back office can modify screens. We want for some environments like training/ production only import / export customization
In the service level template we cant’ use the “minutes before coverage end to start” field with the next day service function ?
We have here the same phone company so the issue is very strange as directly using Chrome on the mobile this is working but using the APP not i will open a case to support thanks all for you help
we have asked the tech to uninstall the latest android webview - same error message
I will open a case. there is no change on Alliance or on windows. i guess but i’am not sure at all ,there is a change in azure/office 365 on TLS protocol but i’m not an expertRgdsChristophe
hi Ugo : the tech is on a samsung android 10 with mobileedge 3.3.0 when he performs the login he has the network issue with chrome this is ok . when i test this on my mobile device (xiaomi) same android release same mobile app release with the technicien credential this is working. we have tested on an other samsung no error. The tech as tested with an other device too he has the issue - very strange problem
When we have this kind of display issue on our side, this is due to the fact that the Alliance URL is not defined in the trusted site zone. Dont’ know if this can help
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.