Agentry PreBuilt Client Usage and challenges

[former_member587017]

Hello ,

I have custom prebuilt client that is working fine but as soon as a new agentry app verison is pushed by developers - for example : making changes in Java file by adding new structure /POJO class or a rule change to manage date for region - the prebuilt client goes in a initial sync. For the most changes on Agentry layer this is not a issue.

Could you please share if any changes on application warrants ( ex: Structure chane m Rule chnage ) a new prebuilt client built.Or Am I doing something wrong .

Recent example - Rule was chnaged to incorporate date format for US region devices - After the deployment ( ver2) I could see new version once I login to Prebuilt client .- but this trigger a download of CTEquipment table .

aftre I logoff n reset client - I see the older version of app (ver1) again in info icon.

PS- We are restarting the SMP after changes are deployed.

[mark_pe · Accepted solution]

Sandeep,

Hello. The rule of thumb on any changes in Agentry is as follows (As Expected):

• Each change is a definition change in an XML or Agentry.zip file (.agzx)
• Each of those changes will have a time stamp
• If a change is on a rule that touches any definition that could have touch a constant, a screen, a table and others then the likelihood of that part of the definition will also be reloaded
• The timestamp of the agzx file when uploaded to SMP 3.0 will be saved
• This will be compared to the timestamp of the definition loaded into the pre-built client or production client
• If the time of the SMP 3.0 server is newer than the definition of the client then a rebuilt of that item is mandated and therefore that part of the logic is reloaded

Let us compare this with your question:

"Recent example - Rule was chnaged to incorporate date format for US region devices - After the deployment ( ver2) I could see new version once I login to Prebuilt client .- but this trigger a download of CTEquipment table ."

If your rule touch a constant, a logic or anything tied to CTEquipment table and this would be the primary cause of it loading again.

One other thing that all need to know:

If you import a zip file to the Eclipse editor then normally the Eclipse editor wipes out all the timestamp on each definition. So if you do a new publish to the SMP 3.0 server then the production clients will now get compared to this new timestamp. They would do a full rebuild.

For any Java file update, this is the reference of all the definition of your code so it will be better if you rebuilt the client as it may be referring to an older library which you would not want that to occur (basically in any web design or mobile design if your app uses an older library you would need to reset your client or clear your browser).

Another thing could be based on a data issue tied to a bug in Equipment table: See: Work Manager Equipment table issue: https://launchpad.support.sap.com/#/notes/2672023 - Equipment/Functional Location Characteristic Value not deleted in delta sync of Equipment/Functional Location List Set Complex Table (and causes a reload of the Agentry client).

This is what I know based on experience tied to this same question.

Hope this helps.

Regards,

Mark