| | Re: BES 10.1.2 Custom IT Policy Rules?
Thanks for the replies.
Good point re the import tool, but what seems to happen is that it strips the custom policies (and really anything that doesn't have a direct equivalent in BES 10.1)
Our reason behind wanting to use custom IT Policies is that some apps can be fed commands to pre-populate or lock certain fields etc. on deployment using Custom IT Policy Rules.
So a usage scenario might be that a published app might have a web-service address (or something else) that needs to be populated. Rather than have end-users manually type in a complex URL (or other value), some developers have included a hook to allow this to be pre-populated by a custom IT Policy Rule Names and Values.
Rule Name: SomeMobileAppName
All this helps ensure that end-users aren't fat-fingering URLs and helpdesks aren't getting called saying that the XYZ service is broken.