Manifest File Migration Rules
The migration rules for this example are as follows. For each applet mapped to a manifest key in either of the following ways, an entry is made in the UI Objects applet.
By using the Presentation_Model and Physical_Renderer user properties under the Applet object in Siebel Tools.
By adding entries under the [Presentation Model] and [Physical Renderer] sections in the manifest_extensions.map file, in the SIEBSRVR_ROOT
\objects
folder on the Siebel Server.
Each time the manifest key is used in the legacy XML file, an entry is made in the new Manifest screen, and a record is also added to the Object Expression and Files views, using the rules shown in the following table.
Use of Keys in Legacy XML Files | Record Created in the Object Expression and Files Applets |
---|---|
Under a |
The record in the Object Expression applet with an expression value that evaluates to True only for the specified platform. The record also exists in the Files applet for any files associated with the record. |
Under the |
The record in the Object Expression applet with no entry in the Expression field. The record also exists the Files applet for any files associated with the record. |
Under a |
The following records are created in the Object Expression applet:
The records in the Files applet are associated with the Group Expression. |
Under the |
The record in the Object Expression applet with an Expression value that evaluates to True only for the given application and a record in the Files applet for the file associated with the record. |