- Model Diagram Rules This page last changed on Nov 28, 2008. .stickable, h1, h2, h3, h4, h5 false true Show Sticky notes Hide Sticky notes Save Cancel Oracle Data Service Integrator Documentation > Data Services Developer's Guide # Rules Governing Model Diagrams Model diagrams follow a set of rules: Each entity in the model has a title which is the local name of the data service (the fully-qualified name is visible as a mouse-over). Associated Read functions can be displayed, with or without signatures. Model diagrams do not "own" data services, but simply reference them. Multiple models can, without limit, contain representations of the same data service or relationships between data services. Models are not nested. That is, a model diagram cannot reference another. Multiple models can be defined and located anywhere in your project. Changes made to a model diagram can be reversed using the Edit Undo command. However it is important to keep in mind that changes to any underlying files such as schemas (XML types) or data services made through the model will not be undone. Instead, edit the data service directly or close and reopen your application before saving your changes.
  | Changes to a model diagram that affect data services such as when a new relationship is created are only made permanent in Workshop for WebLogic after you do a File > Save All

Document generated by Confluence on Jan 13, 2009 15:57