In this article you will find FAQ's related to OData.
For creating user profiles, we have a list of users in a Database can it be mapped and added under User Profiles? Because only those users should have access to any information. Is there a way to do it or do we need to add those users manually under User Profiles?
We currently have two methods of user authentication, the first is direct user creation on the Xalt Mobility Cloud, the second is to utilize Microsoft Active Directory Authentication. Soon we will expand our authentication methods to include OAuth
While adding data objects, can we perform business logic while picking the data objects?
You can create workflows with conditional options, so criteria can be presented based on a varied of different factors. In most cases
Do we need to add data source for each API?
If all the services are on one URL and listed in the metada doc then they will all be available, if they have segmented them on the odata services then they will need one for each.
Do we have an option to parse the data and show it in tree structure? (i.e.) Modules -> child Modules -> child modules
There are some conditional displays that we can implement based on user input.
Do we have option to list down all the already scanned information by the user without going back to backend DB /without storing it in DB?
All data is sent either back to a DB or API, we do not currently store data client side, in most cases, this is preferable due to security concerns. However; we are working to bring offline capabilities to our clients very soon.
Is there a way to find that the product is already processed in mobility? Is it possible to store this information on client side ?
-
One solution: Store the information in temp table at dB while scanning for a temporary use and when user say accept or reject for a weld, then delete/clear that from temp table
-
We may have more options when the XNA client is released (XNA includes some offline capabilities