The customer is trying to add the code field Reference No from Entity JT Task into a mobile screen. Currently the customer has already add multiple custom fields from JtTask into the target mobile screen, but for some reason the core field ReferenceNo is just not available in the drop down. - Open Solution Manager / Mobile Apps / Configuration / Apps for Page Designer.- Find page Service Engineer / My Work.- Click on a work task and button "..." / My Work Detail Page to take it to the Work Details Page.- Click on Page Designer to start changing that page.- Click on Contents / Task Information.- Scroll down to "Task Information Group".- Click on Contents + button to try to add Reference No.- Observe that Reference No is not in the drop down as it should. The entity is JTTask and it seems that all JtTask fields are available in the drop down except for Reference No.
The customer configured SSO using Azure AD and it works well for the client. When login in with the FSM Android mobile which runs on the Android Work Profile and is managed by Intune, it doesn't work. The user is able to go to the Azure AD login page and provide the password, which is accepted, but then a new dialog is prompted saying: "Are you trying to sign in to …? Only continue if you downloaded the app from a store or website that you trust”. When one clicks on continue, it says: "Action Blocked: this action is not allowed by your organization.”The customer believes this happens because this is not a managed app (integrated with the Intune SDK). I think it could also be something that is configured on the Azure Ad that can be changed, so it “trusts” the app and doesn't go through the whole "are you trying to sign in...”. Any ideas? Integrating the App with the Intune SDK sounds like a large amount of work and could also break things.
Google Play Store will no longer accept apps on SDKs targeting less than 33. Is there any plans to have the Android SDK updated to 33? Even though the Play Store is not supported, I am not sure if staying on a older SDK 30 is a good idea as well. Any customers that currently use the Play Store in order to deploy via InTune/MDM, will no longer be able to do so as of August 31 (fixes, new mods). Anyone has done a project specific update of SDK? I started trying with SKD31 but it is a good chunk of work. It new builds and launches, but there will be plenty of runtime issues to be fixed. PS.: Apparently there is an exception to extend it to November, but hasn’t been confirmed yet. There might be an option available to “ permanently private apps” as well, but hasn’t been confirmed yet.
I ran into something that was a pretty hard problem to diagnose: the FSM Android mobile app was not working with HTTPS, but it was working with HTTP. The app doesn't really show exceptions when it fails to establish a connection, it just says: Incorrect service URL or network connectivity, which is accurate, but not very useful. If it showed exceptions it would have said: javax.net.ssl.SSLHandshakeException:java.security.cert.CertPathValidatorException:Trust anchor for certificate path not found.It took quite a bit of VPN, Firewall and server TCP tracing in order to recognise the issue was likely the TLS handshake and that the customer was using self signed certificates.The solution involved adding trust anchors for self signed certificates in the code (network_security_config.xml), which is a modification.<trust-anchors> <certificates src="system" /> <certificates src="user" /></trust-anchors>Please note that the customer was already adding the CA into th
I am setting up a custom event type Rest Call and I have two different problems:Validate Payload is empty I set a validated payload field as {"status":"&NEW:ROWSTATE"}. I also set it as {"job_id":"1234"}, but in both cases I check the message generated under Application Messages / Notifications and it doesn't seem to have a payload at all. The contents of “Event_rest.txt” file under section Input Message Data is always empty. This is either a bug where Validated Payload is not being sent or I am missing something important… I couldn't make the Rest Attachment work either. It at least attaches the file I provide, but doesn't replace the custom event variables in the file such as {"status":"&NEW:ROWSTATE"}.PS.: The output message has contents for the server I am making the Rest Call to, which proves the outgoing HTTP call was made. Any information on what this might be is appreciated.
The customer is experiencing crashes on FSM 6u7 while synchronising messages. We applied a fix from R&D for that issue coming from u9, but it didn't fully solve the problem. The apps still crashes when there are a ton of messages to be syncd in the background. Please note that even without Push Notification, the background sync often works. For some users it seems to not work very much in the background. Sometimes it stops altogether and the following gets logged under Privacy / Analytics: Exception Type: EXC_CRASH (SIGKILL)Exception Codes: 0x0000000000000000, 0x0000000000000000Exception Note: EXC_CORPSE_NOTIFYTermination Reason: Namespace SPRINGBOARD, Code 0x8badf00dTermination Description: SPRINGBOARD, <RBSTerminateContext| domain:10 code:0x8BADF00D explanation:scene-update watchdog transgression: application<com.FSM.Mobile.Superior>:360 exhausted real (wall clock) time allowance of 10.00 seconds | ProcessVisibility: Background | ProcessState: Running | WatchdogEvent:
I am troubleshooting mobile messages stuck on FSM 6 iOS mobile. I have seen that error before where messages get stuck in Waiting or Ready in the device and the only solution is to reinitialize, which loses all the data that was stuck. Please note that this is not caused by messages in Error.In the past I have seen it happening two times. One was a mobile customization problem and the other one was a product bug. The latter was caused by buggy sync code that set some messages in a group in Waiting, but they were not really waiting for anything. Consequently they never got an answer and got stuck in Waiting.Have you seen any of that recently? The message getting stuck is always an attachment and it is stuck in Ready. I looked into the mobile and server logs and there are not exception matching that time stamp. The only thing strange about those messages is that they attachment_log.attachment file is NULL, which makes me think it is either a bug or they tried to attach a blank file. I am
Already have an account? Login
No account yet? Create an account
Enter your 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.
