The three main elements that are defined to support ObjectExtender applications are the model, the schema and the data store map. The information, sometimes referred to as metadata, for each of these is stored in a class in the repository. When a model, schema or map is first created it can be edited without requiring it to be saved. In this case all changes are recorded in the image and are only available to you in the image. To save the work and make it available to other users, use the Save option from each of the browsers. This will store the details of the model, map or schema into a class in the repository. If a model, map or schema requires saving the browser will indicate this in the text pane on the lower half of the browser.
After a model, map or schema has been saved it can be loaded by other users into their image by loading the storage class the same way any other class is loaded from the repository. (Note that to load a class it must either be a version or else if it is still an edition you must be the developer of the edition).
The browsers are not automatically refreshed when you load the metadata information for a model, schema, or map. This is done with the load available menu option. Selecting this option will hydrate the models, maps or schema in the image from the list of loaded classes that are holding the metadata information. As modifications are made to a model, schema, or map, the changes are recorded locally in the image. The browser will indicate that the class is out of sync with the image by indicating that it is dirty and requires saving. If you decide you do not want to keep your modifications you can revert the model, map or schema to the version last saved to its storage class by selecting the revert menu option. Once you are ready to store your work into the repository the Save option will take the definition of the model, map or schema from your image (which is always the ones the browsers display) and store it into the repository. From here the class can be versioned and then loaded and modified by another user.
It is good practice to version the class containing the metadata for the model, map or schema before another user loads it into their image. Once the storage class has been versioned it can be moved between repositories using the import and export menu options. When the class is exported it takes the metadata with it allowing ObjectExtender models, maps and schemas to be moved between repositories.
When creating a new object model using the ObjectExtender tools, the steps are as follows: