[Index]
To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com
VOSS-4-UC allows for flow through provisioning, in other words, for auto-provisioning users and services during user sync from devices.
Auto-provisioning typically references user attributes such as a user's department, division or city address. This filter is set up as Model Filter Criteria.
When setting up a Flow Through Provisioning Criteria instance, this initial Model filter criteria definition of user attributes is then further associated with additional properties for the user in VOSS-4-UC:
An instance of Flow Through Provisioning Criteria that can be selected in the Subscriber Criteria drop down list of the Global Settings, Flow Through Provisioning Criteria tab. See: Global Settings.
Related Topics
Microsoft Overview in the Core Feature Guide
Sync with Flow Through in the Core Feature Guide
Subscriber Profiles in the Core Feature Guide
User Roles in the Core Feature Guide
Overview
VOSS Automate's flow through provisioning feature allows auto-provisioning of users and services during user sync from devices.
Note
Related Topics
LDAP Integration in the Core Feature Guide
Add CUCM Server in the Core Feature Guide
CUCM Configuration in the Core Feature Guide
Microsoft Overview in the Core Feature Guide
Sync with Flow Through for Microsoft in the Core Feature Guide
Subscriber Profiles in the Core Feature Guide
Model Filter Criteria in the Core Feature Guide
Global Settings in the Core Feature Guide
Site Defaults in the Core Feature Guide
User Roles in the Core Feature Guide
This topic describes the steps for setting up your system to enable a seamless sync in of users to VOSS Automate from the hierarchy where the sync source device is set up (typically, Customer level), and the flow through provisioning of services to subscribers at your sites.
To move users to sites, the flow through provisioning references move filter criteria, and attributes set up as Model Filter Criteria (such as a user's department, division or city address).
Note
The flow through provisioning uses the move filter criteria in the site defaults (SDD) to determine whether to move users to site. FTP will not run if the user is not moved to the site.
To create a subscriber and provision resources and services, the flow through provisioning references subscriber profiles. See Subscriber Profiles.
Note
Flow through provisioning (FTP) uses subscriber profiles for provisioning, so you will need a subscriber profile and Quick Add Group (QAG) with device configuration templates (CFTs) set up before using FTP.
Each flow through provisioning criteria (one per customer) consists of one or more pairs of model filter criteria and a subscriber profile combinations.
Flow Through Provisioning Workflow
To access the flowcharts, view the topic via the release documentation at: https://documentation.voss-solutions.com/automate.html
Before you Start: Add a Server as Sync Source
Users are imported from the server sync source to the Customer level in VOSS Automate. The flow through provisioning is generic functionality and supports a number of scenarios, including Microsoft, LDAP, CUCM, and other models (depending on predefined model criteria).
Note
See the Core Feature Guide for details around adding and setting up a server for your flow through provisioning scenario. For example, see Microsoft Quick Start, Set up an LDAP Server, Set Up Cisco Unified Communications Manager Servers
Step 1: Add Model Filter Criteria
Flow through provisioning references model filter criteria set up for each user type (for example, Microsoft, LDAP, or CUCM).
When setting up the model filter criteria, you will specify usage, either flow through provisioning, or move user:
To move a user to the site on import, configure model filter criteria with Move User selected as the value for the Usage field.
To provision a user once they're at the site, configure model filter criteria with Flow Through Provisioning selected as the value for the Usage field.
Note
The flow through provisioning process only runs if the user is at the site.
For details around adding the model filter criteria, see Model Filter Criteria
Step 2: Add Subscriber Profiles
Flow through provisioning uses the subscriber profile to determine the services to be assigned to a subscriber once they're moved to the site.
For details around adding subscriber profiles, see Subscriber Profiles
Step 3: Add Flow Through Provisioning Criteria
Flow through provisioning criteria is a type of model filter criteria used for provisioning. One named flow through provisioning criteria can be added at each Customer level.
Each flow through provisioning criteria is a collection of one or more pairs of model filter criteria and subscriber profile combinations. The flow through provisioning criteria defines how users are matched to both sites and subscriber profiles, allowing the tool to seamlessly move users to the sites (based on model filter criteria) and to create a subscriber and assign services from the subscriber profile.
Flow through provisioning uses the first match to execute the move and service assignment operation.
You can use a single flow through provisioning criteria to match any number of subscriber profiles for this customer and its sites. For example, if you have ten different subscriber profiles, you can add ten pairs of model filter criteria and subscriber profile combinations.
Note
Flow through provisioning criteria is configured via either of the following menu options (default menus):
Before setting up the flow through provisioning criteria, configure the following:
Step 4: Choose Move Criteria
To allow users to be moved in a flow through provisioning, you need to choose move filter criteria for the user type (Microsoft, LDAP, and/or CUCM). The move filter criteria defines how the system moves users to the correct site once they're synced in; that is, it matches each user to the relevant site.
Note
The system uses the existence of the move filter criteria from the site defaults to determine if the user must be moved. Flow through provisioning will not work if a user is not moved to a site.
Prerequisites:
To choose move criteria ...
Step 5: Enable Flow Through Provisioning
Enabling your system for flow through provisioning in the Global Settings allows VOSS Automate to perform a seamless sync in, to move users to the correct site (based on move filter criteria) as subscribers (based on the model filter criteria), and to provision these subscribers with appropriate services (based on the subscriber profile).
Prerequisites:
To enable flow through provisioning ...
Log in to the Admin Portal as Provider admin or higher.
Set the hierarchy to the level where the sync source device is installed. Typically, this is at the customer.
Go to (default menus) Customizations > Global Settings, and select the Flow Through Provisioning tab.
Note
Alternative menu: Flow Through Provisioning Configuration > Global Settings.
At Enable Move & Flow Through Provisioning, select Yes.
At Enable Move & Provisioning after Add Sync, select Yes.
At Flow Through Provisioning Criteria, choose the flow through provisioning criteria to use at the customer level (for all sites at the customer).
Save.
Step 6: Sync with Flow Through Provisioning
This section describes the general workflow in a generic sync with flow through provisioning.
You can run the sync directly, or via a schedule.
Ensure you have the following set up before a sync:
Sync with Flow Through Provisioning Workflow Steps
The flow through provisioning workflow is executed per user and runs in parallel:
Imports user.
Creates a corresponding LDAP user (for LDAP scenario), and a local VOSS user.
Moves users to the sites (based on model filter criteria). If no criteria in place, user remains at Customer level.
Updates the user's role for the site.
Executes Add Subscriber from Profile to create the subscriber, and checks the flow through provisioning criteria to match it to a subscriber profile.
Provisions the subscribers with appropriate services, from the subscriber profile.
Sends a welcome email to subscribers if the following applies:
See also Email HTML Templates.
You can monitor the progress of the transaction via the Transaction Log. When complete, verify the user's move and provisioning status:
Flow Through Provisioning Criteria is a model where user criteria is stored for FTP. When a user is synced into the system and FTP is configured this data will be checked to see if the user that is synced in matches the criteria or not. If it matches the appropriate Subscriber from Profile mechanism is called to automatically provision the user.
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name | Name of the flow through provisioning criteria |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Description | Description of the flow through provisioning criteria |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Criteria Order | Ordered list a criteria to math on. The first criteria that matches will be used. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Model filter criteria | Model Filter Criteria |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Subscriber Profile | Profile of the Subscriber to use. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
User Role | Role to assign to the user. |
|