Skip to main content
Solved

Storage of context values in Mobile Work Order.

  • May 6, 2021
  • 1 reply
  • 89 views

Atheeq Maharoof
Superhero (Employee)
Forum|alt.badge.img+12

Hi All,

When we create a context filtered by USER_ID (For an example, in the newly created context we change the label value from "Site" to "TSite"). Following are some of the questions regarding this scenario.

  1. How will the changed context value("TSite") will be sent to the mobile device? Will it be stored in any table in the mobile device or is there any other mechanism?
  2. How can I confirm whether the changed context value has been transferred to the mobile device without viewing the UI?
  3. Is there any specific permission that should be granted to mobile user to get the newly created context value ?

Best Regards,

Atheeq Mahroof

Best answer by Dar

  1. The label is sent in meta data to the client. It’s stored in the local db but it’s not easy to check this in the table as it’s stored as a blob.
  2. Easiest way to check is by running the fiddler and observing the response json for the call to end point …/Downlink.svc/MaintEngApp/system/Metadata?ScopeId=global. You can check if the correct context has been resolved by observing the value for ScopeId parameter. If the ScopeId is correct check the response json. You should be able to figure out the label text in the clients node.
  3. No specific permission is required.
This topic has been closed for replies.

1 reply

Dar
Hero (Employee)
Forum|alt.badge.img+5
  • Hero (Employee)
  • Answer
  • May 6, 2021
  1. The label is sent in meta data to the client. It’s stored in the local db but it’s not easy to check this in the table as it’s stored as a blob.
  2. Easiest way to check is by running the fiddler and observing the response json for the call to end point …/Downlink.svc/MaintEngApp/system/Metadata?ScopeId=global. You can check if the correct context has been resolved by observing the value for ScopeId parameter. If the ScopeId is correct check the response json. You should be able to figure out the label text in the clients node.
  3. No specific permission is required.