
with Tags:
mainrecord
X

Marking Main Record as Modified while Modifying Related (Child) Records via Automation Scripts (v7.6)
When you modify, i.e. add/update/delete, child records (MBOs) related to a main record, the parent object might not always require saving, in other words it might not always get marked as "Modified". For default applications, the application forces the user to SAVE the main record because this functionality is implemented in the original MBO classes of Maximo. Unfortunately, when you have your custom objects used in your custom applications, you can face such use cases that you modify the child records and the main record is not... [More]
Tags:  controldesk+7.5 modified parent maximo modify mainrecord related child update save add maximo+7.6 delete maximo+7.5 controldesk+7.6 controldesk |
Object in LIBRARY.xml file will not show in the screen when adding a new sigoption to it
When adding a new sigoption to the LIBRARY.xml file, the object will only show in the screen if the Security Group has access to all sites . If the sigoptiondatasrc is not set to MAINRECORD in a sigoption located in the LIBRARY.xml file, then the option will only work for Security Groups with access to all sites. MAXADMIN group is marked to have access to all sites, and this is the reason why only administrators could see the new object. To resolve the problem do the following: From: <textbox id="MYNEWATTID" label="My... [More]
Tags:  sites ibm-blog library all mainrecord |