Jump to: navigation, search

Customization Manager


Use Customization Manager to store/manage various aspects of your Composer installation that you have customized.  You can store/manage the workflow and callflow diagram templates that you create as described in the Diagram Templates topic. topic.


The user interface takes the form of the Customization Manager view.  To display this view:

  1. Select Window > Show View > Other.
  2. In the resulting Show View dialog box, select Customization Manager and click OK. A Customization Manager view appears at the bottom of the Composer window listing registered plug-ins.  An example is shown below.


Managing Templates

You can use this view to manage the workflow and callflow diagram templates that you create as described in the Saving Diagrams as Templates topic. To manage diagram templates:

  1. Right-click a callflow or workflow diagram to bring up a menu.


  1. Select from the following:
  • Edit--Use to edit a selected diagram template.
  • Delete-Use to delete a selected diagram template
  • Add a New File--Use to import a callflow or workflow diagram.
  • Save Selected Item to Disk--Use to save a selected diagram to a disk.
  • Refresh

Customizer Preferences

To bring up Customizer Preferences:

  1. Click the Window menu.
  2. Select Preferences.
  3. Expand Composer.
  4. Select Customizer Preferences.  The Customizer Preferences dialog box opens.  The Callflow Diagram Editor and Workflow Diagram Editor customization plug-ins are display only and can be used for debugging.

CustomizerPref.gif The Customizer Preferences dialog box:

  • Reports on the location of the storage area (cstore directory) on disk. Diagrams that you save as templates are stored here.
  • Lists registered plug-ins as shown in the Customization Manager view.
  • Allows you to suppress confirmation dialogs associated with plug-ins. If checked, it suppresses the success/failure indicator message when you save a diagram as a template.
This page was last edited on July 24, 2013, at 12:23.
Comments or questions about this documentation? Contact us for support!