Object detail

Work with object details

• Sections
• Hints for developers
  • Defined field is not visible

AyMINE Framework uses universal class univDetail to open and manage details. It supports descendants (e.g. user settings is implemented as the descendant class derived from univDetail – use it as a reference class for the descendant implementation) or even using alternative view from the standalone java script implementation. Nevertheless, common AyMINE modules does not need it.

Detail uses common server counterpart library objRecord that loads data and manage update save. Server loads data according to the jsonc detail definition – client application does not define what data should be loaded but both server and client uses the same view definition from the object definition.

Sections

Slave object section describes, how detail (as well as list) manages the detail of the slave objects.

Detail descendants describes, how to created special detail class and manage detail behaviour programmatically.

Hints for developers

The section contains common problems that occurs during the development and new object definition. Recommendations are not useful for regular users of application based on the AyMINE Framework.

All recomendations here are somehow linked with object detail definition in the jsonc file:

Defined field is not visible

There are several reason, some are obvious, but others is often hard to find. Check properly:

• Mistyped character – simply field does not exist. Error is mostly easy to find, because application rasises a warning at the console
• Hidden field – field is set non-visible. Not common, because nonvisible are mostly only technical fiedls
• Readonly empty field – Field marked read only is invisible if it has no values. Be careful about that because it is correct behaviour and so system does not show any warning. Especially detail opened for new object does no show any read only field.
• Duplicity in field orders – When fields have explicitly defined order and tw fields have the same order, one of them becomes invisible. Be careful about that, because it mostly occurs for fields in different object definitions (abstract object overwritten by specific object). – This could be nice if a warning occurs, but it doesn't (yet).