Bookshelf Home | Contents | Index | PDF |
Using Siebel Tools > Managing Repositories > Managing Modifications That Multiple Developers Make > Tagging Objects That You Do Not ModifyTouch is a feature in Siebel Tools that allows you to tag an object that Siebel Tools has not tagged as a result of you importing an SIF file, checking in or checking out an object, or doing a manual update. It uses this tag information to identify the objects it extracts from an SDF file during a repository merge. If you touch an object, then you cannot remove the tag that Touch adds. Siebel Tools automatically tags the objects that it imports or checks in. If Siebel Tools requires an object during an SDF export, and if this object is not tagged, then you can touch the object to make it available to the export. For information about exporting the objects that a developer tags, see Exporting Modified Objects. For more information about SDF files, see How Siebel Tools Minimizes the Data it Processes during Exports and Imports. To tag objects that you do not modify
Using a Batch Operation to Tag Objects That You Do Not ModifyThis topic describes how to tag objects that you do not modify in batch. To use a batch operation to tag objects that you do not modify
Example of an Object List FileThe Object List file is a text file that includes a list of the objects that Siebel Tools must tag. You can use any file name that meets Windows file name requirements. You can locate this file anywhere on the computer where Siebel Tools resides. The Object List file uses the following format: object hierarchy,object type
The file must not include any empty lines. For example, you use the following format to tag the control user property of a control that resides in an applet: applet_name||control_name||control_user_property_name,Control User Prop For example, the following code specifies the control user property named Url of the CancelQuery control that resides in the ABO Bulk Request Component Product Pick Applet: ABO Bulk Request Component Product Pick Applet||CancelQuery||Url,Control User Prop If you specify an object in the TouchObjList.txt file, and if this object does not exist in the SRF, then Siebel Tools creates an error message in the log file. Examples of Specifying Objects That Do Not Include the Name PropertyYou use the Name property to specify most objects. If an object does not include a Name property, then you can use the next significant property. For example, you use the following Field property for a pick map: business_component_name||field_name||pick_map_field_property,Pick Map The following code specifies the Account Status pick map of the Account Status field that resides in the Account business component: Account||Account Status||Account Status,Pick Map For another example, you use the following Table property for a join: business_component_name||table,Join The following code specifies the S_CONTACT table of a join that resides in the Account business component: |
Using Siebel Tools | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |