Hello Federico,

Hope you're doing well.

This is default mobile application behavior. Empty fields always remain invisible in case they are not filled in. This logic can be changed with the help of development only. It would be necessary to override the Terrasoft.controller.BasePreviewPage of the method doChangeField in all pages like this:

doChangeField: function(field, newValue, executeRulesCallback) {
                       this.callParent(arguments);
                       field.show();
}

Best regards,

Roman

Roman Rak, Thanks, that can be apply only for a specific object?

I just create a new controller for the specific schema and works. Thanks

Hi Francois,

This usually happens if there are more than 1 workplace set for the Mobile App. The best way is to check your Mobile wizard and see if any of those sections linked to any of the workplaces.

I double checked and nothing is refering to the order. (I only kept Account/Contact/Activity/Lead.  The data that I'm showing does not call ORDERs or Products in Orders) 

But I still see :  Importing data (OrderProduct) = over 2 Millions records.

 

Can we limit the amount of Order records  (Today's data ONLY) ?

Hello Federico,

Hope you're doing well.

At the moment, the mobile application doesn't support interaction with virtual columns. We have created a request to the R&D team so they could review the possibility of further implementation of this functionality in the future versions of the mobile application. 

Thank you for helping us to provide better services!

Best regards,

Roman

Hello Federico,

There is an onSaveButtonTap method in the base edit page controller schema that is triggered when the record is saved. There is no async validator there, but in case you need to check something for the saved record upon saving then you need to look at that method call.

Best regards,

Oscar

Oscar Dylan,

 Thanks Oscar. I need to create a page controller for a custom section? There is some documentation about that?

Federico Buffa ...,

No we don't have such an instruction unfortunately.

Best regards,

Oscar

Oscar Dylan,

 Thank you so much. Just wondering if that method can be use in the module config or needs to be in another schema. I don't have much information about mobile structure.

Hello Federico, 

We performed some tests in order to achieve your requirement, but it seems like such implementation is not possible for now. The only one business rule will be active in this case. We already informed our Core R&D team and we will work to add such functionality in our next releases. Thank you for understanding!

Best Regards, 

Bogdan L.

Hello Sarika, 

Unfortunately, the pre-configured pages and the dialog boxes (modal windows) are not presented in the default configuration of the mobile application yet. 

Detailed information about the mobile application interface (as well as information on how the edit data option works there) can be found in the Get started with the mobile app UI Academy article. 

Best regards, 

Olga. 

Hello Daniel,

The mobile application UI doesn't support working with business processes and processes are only triggered on the server side in real-time once the record is modified in the mobile application or record is added (and correspondent start signals are present in some process).

Our core R&D team already has a task to make it possible to work with business processes from the UI directly and I will also let them know about your post so to prioritize the task for them.

Thank you for helping us in making the app better!

Best regards,

Oscar

Thank You Oscar.

I think it is a important feature for the application, so that the actions of the buttons can be dynamic and don't just give it "Message Alerts".

Best Regards,

Daniel Longo

Hello Maher,

Once you sync the mobile app with the main app all lookup values are being saved in the cache of the mobile app and will be available for selection in offline mode. In case you've added new lookup values to the main app and need them to appear in the mobile app please sync the mobile app with the main app and new values will appear as needed.

Best regards,

Oscar

Oscar Dylan,

Hello Oscar,

Thank you for the reply.

I am not able to see the list of values in offline mode for some reason, are there any steps to do or configurations?

I did synchronize before disconnecting from the network.

Maher.

maher daher, maybe our steps to reproduce the behavior are different. Can you please specify the value for the system setting with the "MobileApplicationMode" code (try setting the value as "Offline")? Have I understood you right that you perform synchronization, then disconnect your device from the network and then try to edit the record, select the lookup, but you don't have any values there? Is this a custom lookup or some out-of-the-box lookup?

Please also make sure that your lookup is present in the SyncOptions property -> SysLookupsImportConfig attribute in the mobile application manifest (as described here). Because your lookup may simply not sync with the mobile application.

Best regards,

Oscar

Hello Luka,

Have you tried calling the this.reloadEntity(); method on custom button click? What was the result?

Best regards,

Oscar

reloadEntity is for web app. in mobile app, record instance doesn't have reloadEntity :( 

Hello Luka,

To solve your business task you need to add visible value to the field and bind it to the method:

"visible": {"bindTo": "visibleMethodName"}
and create an attribute 
"hideFieldAttribute": {
        "dataValueType": Terrasoft.DataValueType.BOOLEAN,
        "value": true
      },

This method will be triggered by a button click and should set an attribute:

buttonAction: function() {
        this.set("hideFieldAttribute", false);
      },

This method is bound to the visible property of the field:

 visibleMethodName: function() {
        var result = this.get("hideFieldAttribute");
        return result;
      },

Please let us know if it helps!

Best regards,

Bogdan S.

I resolved it, using business rule. Thanks a lot, you gave me good point.

record.changeProperty("UsrGeneralAgreementUrl", {
    hidden: false
});