Query program listens for the signals from UF_TRVRS for the types of object it is interested in, and stores information about the objects.
The query program can store the object information any way it chooses: It can store object references in a collection, or in a List or grid (using the .RelatedReference property of the current item). Or it can get the object property information at the time it receives the signal, and store it in fields in an ordinary list.
There are two kinds of Framework object:
- Normal objects with names like VF_FPnnn (e.g. VF_FP003). There are multiple instances of these objects, and if you have the object reference, it is a reference to a particular instance. You automatically have access to all the properties of the instance.
- Member objects with names like VF_FPMnn (e.g. VF_FPM09). These objects were designed this way for performance reasons. In this case there is only one actual instance, and the properties of all instances are stored internally inside the single object instance. To get the properties of a particular instance, you must first set a property called CurrentMemberGUID to the value for that instance.
The main Framework objects in these examples are:
VF_FP001 | The Framework |
VF_FP002 | Application |
VF_FP003 | Business Object |
VF_FPM08 | Application/Business Object link |
VF_FPM09 | Command Definition |
VF_FPM10 | Command Reference (link between a command and a business object or application or Framework) This contains command handler information. |
VF_FPM14 | Filter |
The main RAMP objects are:
VF_FP025 | RAMP Container |
VF_FP026 | Session |
VF_FPM27 | Destination |
VF_FPM28 | Junction |
VF_FPM29 | Special |
VF_FPM30 | Script |
By exploring these objects using the Visual LANSAFeature Help option you can discover the properties that they contain. If you have questions about the properties please post a message to the VLF forum.