Restrict use of output types by role or object type

If you want certain output types to be unavailable to certain roles in the Generate Output dialog, you can remove these output types from the Output Format drop-down menu for those roles.

1. In the TEXTML Administration perspective, connect to your server.
2. Locate the accessrights.xml file in the repository's /system/conf collection.
3. Check out and open accessrights.xml with a text editor.
4. Locate the section that begins with:
   <!-- ********************** OUTPUT TYPES ********************** -->

   The entries that follow specifically control the visibility of the output types for specified roles, but they can also serve as templates for additional entries.

   If an output type does not appear in accessrights.xml at all, it is visible to all users in the Generate Output drop-down.

5. Copy an entry , such as the entire <method name="Dita2Pdf"> element, and then paste the copy below the original.
6. Make the appropriate changes in the copied entry for your scenario.

   For example, you might have a PDF-Final output type. You allow users with the Information Architect role to create the final PDF output for snapshots, maps, topics, and images, but you allow only users with the Translation Manager role to create final PDF output for localized content for those objects.

     <method name="PDF-Final" type="outputtype">
       <notify enabled="false"/>
       <conditionset operator="any">
         <condition>
           <current>
             <type name="snapshot">
               <statuses>
                 <status>Authoring:*</status>              
               </statuses>
             </type>
             <type name="map">
               <statuses>
                 <status>Authoring:*</status>              
                 <status>Published:*</status>
               </statuses>
             </type>
             <type name="topic">
               <statuses>
                 <status>Authoring:*</status>
                 <status>Published:*</status>
               </statuses>
             </type>
             <type name="image">
               <statuses>
                 <status>Authoring:*</status>
                 <status>Published:*</status>
               </statuses>
             </type>
           </current>
           <users>
             <roles/>
             <groups>
               <group name="System Administrators"/>
             </groups>
             <roles>
               <role name="Information Architect"/>
             </roles>
           </users>
         </condition>
   	  <condition>
           <current>
             <type name="snapshot">
               <statuses>
                 <status>Localization:*</status>
               </statuses>
             </type>
             <type name="map">
               <statuses>
                 <status>Localization:*</status>
               </statuses>
             </type>
             <type name="topic">
               <statuses>
                 <status>Localization:*</status>
               </statuses>
             </type>
             <type name="image">
               <statuses>
                 <status>Localization:*</status>
               </statuses>
             </type>
           </current>
           <users>
             <roles/>
             <groups>
                 <group name="System Administrators"/>
             </groups>
             <roles>
                 <role name="Localization Manager"/>
             </roles>
           </users>
         </condition>
       </conditionset>
     </method>

7. Create additional methods as necessary to define your output type permissions.

   Output types cannot be restricted by object status, such as for maps at done. However, you can disable an output type for an object type altogether. From the example above, you could delete the following lines to disable the PDF-Final output type for snapshots:

   <type name="snapshot">
   	<statuses>
   		<status>Localization:*</status>
   	</statuses>
   </type>

8. Save, close, and check in the accessrights.xml file.
9. Inform users of the changes.
   The changes will be applied automatically once users close and then reopen their CCMS Desktop. Users can also apply the changes without restarting their CCMS Desktop by clicking IXIA CCMS > Synchronize Configuration. Additionally, refresh IXIA CCMS Web so that users will see the change reflected there.