New directory (beta)

Disclaimer: this is a beta feature, meaning it still undergoing final testing before official release. The
feature is provided on an “as is” and “as available” basis. Pexip does not give any warranties to the usability of the feature.

We are currently testing out a new folder-based phonebook that should replace the default "flat file" we currently use on the Pexip Service.

A folder-based phonebook will be particularly useful for large enterprises with maybe hundreds or thousands of systems. For example, a structure based on country names can make it easy to quickly find the right system when scrolling through the phone book.

This is (currently) how it works:

1. Once a company would like to start using folder-based directory, they should define a structure (e.g. country-based) they would like to use. This is a simple 'pen and paper' exercise, no technology needed 🙂The folders will be on a single level.

2. Once a structure is in place, the Pexip partner can add systems to the different folders using portal.pexip.com. A system in this context is either a user, a team VMR or an endpoint. To add a system to a folder, go to "edit" for that particular system and find the "Phonebook folder" dropdown under 'Privacy and Tags'. This contains all the created folders under that company so far. You can then either select an already existing folder or create a new one.

mceclip0.png

3. After adding folders, the directory is still shown as a flat file like before. This is to ensure migration is handled in a controlled way. One can then start to override on the endpoints that should display the new folder structure: select the "wrench" next to the endpoint and select "Overrides":

mceclip1.png

...then set DIRECTORY_TYPE value to 'tags' ('flat' keeps the old style directory):

mceclip0.png

The endpoint should then display the folder-based directory about one hour after submitting.

If 15 or more entries in a particular folder, a second level is added. This new level displays the first letter of the entries alphabetically.

Example

Top level:

01-Touch8-Root.png

In folder 'Amer'. As this folder contains 15 or more entries, a second level is introduced, based on the first letter of the device name:

03-Touch8-AMER.png

In folder 'M': all entries starting with the letter 'M' in the 'Amer' folder:

04-Touch8-AMER-M.png

What about static entries?

Static entries can also be assigned a folder, similar to the other systems. Simply enter the folder name and submit:

mceclip0.png

(Note that the list of "Company static phonebook" by default lists all team VMRs and personal VMRs, as well as the manually entered static systems. Only the static systems can be assigned a folder via this list. To assign folders to personal and team VMRs, see step 2 above.)

Notes:

  1. The new folder structure will be viewable on certain hardware endpoints (Cisco and Poly). Hardware endpoints that do not support folders will default to the standard flat directory.
  2. Any systems with no folder will be put in an 'untagged' folder.
  3. The next version of this will have the following improvements:
    1. Untagged systems will be in the top level entry list, without any folder.
    2. Time to display changes will be significantly reduced from today's one hour timeframe.
Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments

1 comment
  • Nice.

    0
    Comment actions Permalink

Please sign in to leave a comment.