Best Practices Menus

In addition to a default set of menus, VOSS-4-UC also provides best practice menus for provider and customer administrators, including the associated access profiles and landing pages. The names of these items can be identified by the word Enhanced in the model name.

These menus have a more business-oriented structure and include additional options based on best practice adaptations that may also be included in VOSS-4-UC.

The best practice menus have the following features:

  • A menu order, nesting and naming convention according to common business use.

    The top-down order of the menus follow the logical order of tasks and system hierarchies that are used to carry out these tasks.

    For example, for provider administrators, the Cisco UC App Management menu provides menus only for these Cisco devices, while SMTP server and other settings carried out by providers are arranged under Provider Configuration. Similarly, the Cisco Subscriber Services menu has sub-menus for all the functionality associated with these subscribers in VOSS-4-UC.

  • Additional naming conventions that identify the menu type:

    • Where a menu refers to an adaptation, the menu name indicates this with an asterisk (*) appended, for example Move Phone and Services *.
    • Where a menu is for a form view (input or edit), the first word in the menu name is in capitals, for example ADD Internal Number Inventory. Note that this does not apply to menu names that start with abbreviations and acronyms like E164, HCS, LDAP and so on. In this case, the capital rule will apply to the next word in the menu item name.

  • Menus for URLs:

    • Menus are provided for VOSS-4-UC portals so that is easy to launch into another portal.

    Important

    In the case of menus that use URLs, you need to update the URLs to match your configuration.

To modify and to assign your modification of a best practice menu to a user role, consider the following:

  • Managing menu layouts - see: Create a Menu Layout. Also consider using the Menu Diff Tool to easily modify menus - see the Advanced Configuration Guide for details.
  • Field Display Policies associated with menu items are available. For further configuration, see: Add or Edit a Field Display Policy.
  • Configuration Templates associated with menu items are available. For further configuration, see: Workflow for Creating Configuration Templates.
  • Access Profiles for the best practices menus are provided - see the list under the Access Profiles menu. If any access profiles need to be modified to align with a modified menu, see: Access Profile Permissions and Operations.
  • Landing Pages for the best practices menus are provided - see the list under the Landing Pages menu.