Siebel Field Service Guide > Release Management > Process of Managing Release Manager >

Managing Technical Publications Work for Release Manager (End User)

When users enter design, development, and test data in Release Manager, technical writers can begin recording the progress and results of documentation efforts in Siebel Field Service. Their managers can monitor the information that they enter.

This topic contains the following related information:

• Creating Technical Documents and Linking Features
• Adding Activity Plans to Technical Documents

This task is a step in Process of Managing Release Manager.

Creating Technical Documents and Linking Features

After they identify release features, Technical Publications can begin revising existing documentation or developing new documents to describe new product functionality.

Technical Publications can track documentation development in Release Manager. The document available as an attachment to the record. Technical Publications links the document with associated features. Product marketers who are associated with the development of the document are linked to the record, and they can record their approvals. For each document, Technical Publications logs the portion completed and the target completion date so that they can address potential issues before they are critical.

To create a technical document

1. Navigate to the Release screen, then the Technical Documents view.
2. Create a new technical document record, and complete the fields as appropriate.

   Some fields are described in the following table.

   Field	Comments
   Target Date	Select the expected date of the document completion.
   Complete %	Type the percentage of the document that is completed to date.
   Release	Select the name or number of the product release associated with the document.
   Est Pages	Type the estimated number of pages for the completed document.
   New %	Type the percentage of the document that is new in this version of the document.
   Associated Parties	Select the individuals associated with development of the document. Set the author as Primary.

Adding Activity Plans to Technical Documents

An activity plan comes from a predefined activity template. An activity template contains multiple predefined activities to associate with a release item. Users can use activity templates instead of manually entering each activity, and activity templates help to standardize activities for technical publications teams.

To add an activity plan to a technical document

1. Navigate to the Release screen, then the Technical Document Activity Plans view.
2. Select a technical document record.
3. In the Activity Plans view, create a new activity plan record, and complete the fields as appropriate.

   When you associate the activity plan with the technical document, all the activities in the activity plan are associated with the technical document and appear in the Activities view.