What's the significance of param scope of TABLE_CHECK and TABLE_REFRESH parameter for a CT?

[sudhiranjan_lenka]

Hello Experts,

I work on SYCLO/Agentry mobile applications. I need your help to understand the significance of param scope(User/Application) of TABLE_CHECK and TABLE_REFRESH parameter for a CT.

Do they have any impact on the Transmit?

Appreciate your help!!

Thanks,

Sudhir.

[kevin_hu]

Param. Scope: The scope of the parameter value. There are two options:

• Mobile Application: Value for all users of the application
• Mobile User: Value that can be overridden for individual users. To override a user’s parameter value, see the Administration & Monitoring portal information on parameters.

So for complex tables, leaving the value as "application" is normally ok unless you have some different refresh logics for different users.

[sudhiranjan_lenka]

Thank you so much Kevin for the response.

Let me put my question in a different way.

Let's say I have a CT(A) and the check param scope is set to user with value as 0. I transmitted as X and it Transmitted successfully. then I changed the user to B and try to Transmit, so will it check the CT for the update?

And what will be the behavior for the same scenario If I set the param scope as Application.

Thanks,

Sudhir.