@thilinaweliwita Thank you for this verydescriptive answer.
Thank you @Charith Fernando and @Atheeq Maharoof for your valuable input on this.
@Charith Fernando Thank you very much for the explanation!Cheers.
Apparently you have checked all the possible reasons. What FSM UPD version is used by the customer? /Sanjeewa @SanjeewaJ Customer has faced this issue in UPD12 and after upgrading to UPD13 as well.
Thanks @Lee Pinchbeck Apart from that, is there a way to accomplish this from the drop down called ‘Applicable device type’? It already shows "2 selected". but this is greyed out and the customer cannot change it. Customer is already using FSM Mobile on iPhones and iPads. They want to limit this only to iPads.
@Lee Pinchbeck Thank you for the knowledge shared. That screenshot has been taken from customer’s MDM where we apparently don’t have any control through the FSM Application. This issue is solved now 🙂
Thanks @Atheeq Maharoof for this. With further work on this it was found that the <create_request_contact> MPM, called by the baseline-policy when creating a request_contact form Request screen is not called in customer’s environment. This could be because the custom-policy, and its DLL is having a different implementation for creating new request contacts.
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.
