In this section:


Note

The SBC does not support Lync/Skype.


A Configuration Workflows and Templates object is a sample configuration that guides you through the process of data entry for a particular scenario. The sample configuration includes default values for some of the settings, which you can accept or override these settings before loading the workflow onto the SBC. A Configuration Wizard may include steps that contain text, images, or user-configurable settings and attributes, repeat specific steps that need multiple entries, or commit configuration updates to the SBC either after every step, or at the end of the workflow. Additionally, you can include new Ribbon workflows as they are made available in the Ribbon Support Portal, create and upload customized workflows to the EMA, and customize existing workflows for specific needs.

Opening a Workflow

From the EMA main screen, navigate to Configuration > Configuration Wizards. The Configuration Workflows and Templates window is displayed.

There are two types of EMA workflows. The type is indicated by the Source column in Configuration Template Workflows.

  • Ribbon Workflows – Ribbon workflows are attached along with the SBC, which is indicated by Ribbon in the Source column. You cannot delete a Ribbon workflow.
  • User-added Workflows – Workflows that are downloaded from the Ribbon Support Portal, customized by you, and uploaded back to EMA using the File Upload screen. This type is indicated by User in the Source column.

To launch or delete a custom workflow, click the associated button in the Launch/Delete column for that workflow.

Note

You can only delete user-added workflows.

Navigating A Workflow

This section describes the navigation of workflow and commands associated with it. After launching the template workflow, a new screen opens with the workflow title and the steps associated with it.



Navigation Buttons

The side panel indicates the current step and is not a selectable user interface. The workflow steps are displayed in a vertical list and you can navigate through the steps using the Next and Back buttons. Navigation is sequential - you can navigate to the next step or previous step only; you cannot skip a step.

Navigation ButtonsDescription
Previous
Select the Previous button to navigate to the previous step in the workflow. When you return to a previous page, later work is saved and does not need to be re-entered when you return to the page.
View Config Details
The View Config Details button is displayed in every step with user entries. Click the View Config Details button to view:
  • CLI commands for non-tokenized workflow step.
  • CLI commands with all the tokens filled for tokenized workflow step.
Submit 
The Submit button is displayed in every step. You can perform the following using the Submit button.
  • Validate and check all the tokenized CLI fields in complete state. If any required fields are incomplete, an error message is displayed.
  • Submit the tokenized CLI values to the SBC.
    • The Submit button is not visible for the static workflow steps.
    • The Submit button is always enabled for the template workflow steps.
Next 
Select the Next button to navigate to the next step in the workflow. The Next button is disabled on the mandatory steps until you submit the configuration. Once you submit the configuration, the Next button is enabled so you can navigate to the next step.
Show only required fieldsThis option displays only the mandatory fields required for configuration in each template workflow steps that do not have default values provided.

Additional Interfaces

The template workflow steps are linked to CLI commands. Once you select the Submit button for a particular step, the EMA loads the CLI commands to the SBC. You can view the CLI commands that will be submitted to the SBC in the Configuration Details dialog, which is generated after you select View Config Details.

The CLI commands for a template step are categorized into:

  • Tokenized CLI – You must input the value for the tokenized CLIs before submitting the configuration step. The workflow template identifies fields that can be customized through "tokens" in the CLI. The tokens in the CLI are replaced with the values you enter. You must complete all input fields before the tokens in tokenized CLIs can be updated. For example, if a CLI command includes a token for an IP address, the IP address input field is presented to you, and the value entered in this field replaces the corresponding token in the CLI command before submitting it to the SBC.

  • Non-Tokenized CLI Steps – Steps with CLI commands that do not require any input from you.