Browse Page is working in XMPro Act (Mobile) but not in XMWorkspace

How Can We Help?

Browse Page is working in XMPro Act (Mobile) but not in XMWorkspace

< Back

Scenario

A browse page (Asset) has been configured using the integration wizard. The Asset browse page connects to a stored procedure that takes one input parameter (Section). The parameter is selected from another browse page (Section) which is functioning as expected on the page.

 

 Issue

XMPro Act (Mobile): When opening the browse page in the mobile app, the browse page opens with the correct values.

XMWorkspace (Browser): When opening the browse page in a browser, the browse page opens with no values being displayed.

 

Explanation

There are two possible causes to the issue experienced. XMWorkspace and XMPro Act do not always function the same – different technologies will have some slight differences as in this case.

  1. In XMWorkspace (browser) browse pages only support returning values to a Text Box. Values will not be returned to a reference label. In the mobile app this restriction is not there, and a value can be returned to a reference label. XMPro recommends that values from a browse page always be returned to a Text Box.
  2. In XMWorkspace a postback is required for the value to be correctly applied to the field before it can be used as a parameter in a separate integration. In this case a post back is required on the Section Browse Page that will apply the value to the parameter field before being used in the Asset browse page. The mobile app works differently, in the way that the values are applied immediately to the field without a post back being necessary, thereby allowing for returned values to be used without the need of a postback.
Comments are closed.

This is the legacy version of the XMPro Documentation site. For the latest XMPro documentation, please visit documentation.xmpro.com

X