Advanced Editor Functionality
FCSI has created functionality that allows you to enhance the usability of the Object Editor.
Features
Dynamic Grouping
You can dynamically group your fields and dynamically change the name of the group. This is especially desired when you have data that may not be applicable to the current object and you can hide the data from view or group the data so the editor presents only the information that is useful. As seen in the image to the right, the OSM Data label changes depending if the data is set or not.
External Enumeration
With the advanced editor functionality from FCSI, you can now use a completely external data source to support enumeration. In the example to the right, the DIGEST data is not derived from any Smallworld static or dynamic enumerators. The enumeration data (Masonry, Permanent, Shed) are being read from an external Access MDB file. The data stored in is simply the key that is associated with the enumerated data. The data can be in any format as long as it is programmically available to Magik, including directly from a website. This ensures the enumeration data is as accurate and up to date as possible.
Dynamic and Derived Data Display
FCSI's advanced Object Editor functionality gives you the ability to view (and edit) data that is external to the object or external to Smallworld. For example the fcsi_dyn1 field is a simple read only attribute that is derived from the object's ID. This could easily be changed to support referenced object outside Smallworld.
- For example, if you have additional Asset Management (AM) data that is stored outside Smallworld like pole manufacturer, year manufactured, material, and last inspection, it can be displayed in the pole's object editor. This does not require any synchronization between databases. It reads the data from the external source when the object is brought up into the editor.
- Another example would be the ability to show fields that are part of joined record on this editor. This is perfect if you store cataloged data and want to show that data within the parent object editor.
The XML Fields group contains fields that are not part of the object directly. The XML Fields attributes are derived from a text join that is attached to the object. The fields are editable! When you update the field listed under XML Fields, the text join, XML Properties, is updated with the new value. These fields are not only viewable (and editable) in the editor, but the fields can be used in the browser for queries.
