Introduction to the Admin Portal User Interface¶
This topic describes the user interface for the VOSS Automate Admin Portal.
Note
VOSS Automate v21.2 ships with a new logo and an updated look and feel, including additional options for customized themes. Additionally, VOSS-4-UC is now VOSS Automate. As at v21.2, you may still see some references to VOSS-4-UC. These will be replaced in future versions.
Related Topics
Button Bar¶
For certain models, such as Roles or Credential Policy, the list view or detail view of the Admin Portal shows a button bar with a number of controls. The buttons displayed depend on the Access Profile of the user.
Button |
Description |
---|---|
Add |
When viewing a list, the button opens an Add form to create a new item. |
Save |
On the Add form, the button is used to save a newly created item. On the detail view, the button is used to save changes made to the specific item. |
Delete |
From a list, remove an entry or the selected entries. |
Cancel |
Used to cancel triggered events such as transactions, bulk loads, and so on. |
Back |
On the detail view, the button returns to the original list page position. The browser’s back button also carries out this task. |
Help |
Open the on-line help page for the current model. |
Move |
For selected model instances, move them from the current hierarchy to another hierarchy. By default only device models have a Move button. This button is available on list and instance Admin Portal screens. When moving device models, checks are built in to disallow moving a device model instance to a hierarchy node with a different device. For Data Models, Move is allowed by editing the Data Model’s definition in the Operations section. |
The Action menu provides actions applicable to the specific view.
List View Action |
Description |
---|---|
Bulk Load File |
Only used in Administration Tools > Bulk Load, when bulk loading a preselected file. |
Bulk Modify |
On the list view of certain items, the button displays a form to enter modifications to any selected list items and carries out a Bulk Modify. This is only available if your administrator has given you. the required permissions. |
Configuration Template |
For a form, create a Configuration Template for a model or carry out a task such as an advanced search. |
List View Action |
Description |
---|---|
Export |
From search results or any list view in the system, it is possible to select the entities required and export them with all attributes. The selected data can be exported to:
|
Export Bulk Load Template |
Export a model structure to a MS Excel bulk load file format. The file can be used as a template to bulk load instances of the model. Refer to the Bulk Load topic help. |
Field Display Policy |
Add a Field Display policy to a selected model. The detail view of a Transaction displays this button to show sub-transactions. |
Move |
For selected model instances, move them from the current hierarchy to another hierarchy. By default only device models have a Move button, which is available on list and instance Admin Portal screens. When moving device models, checks are built in to disallow moving a device model instance to a hierarchy node with a different device. For Data Models, Move is allowed by editing the Data Model’s definition in the Operations section. |
Clone |
Make a copy of the current item. An option is available to rename the copied item. |
Execute |
For an executable model such as a Provisioning Workflow, Macro, Wizard or for a script, run the execution. |
Import |
For supported Network Devices, carry out an import of data from the device. |
Export |
Export a specific item with all its attributes. |
Package |
Create a package containing selected search results. |
Refresh |
Click this button on the Transaction list to refresh the list of transactions. This would for example update the Progress of the transaction. |
Replay |
Transactions that have failed can, under certain circumstances, be replayed. This means that the transaction is re-submitted with the original request parameters. |
Edit and Replay |
Available for completed transactions. Similar to the Replay button, but allows you to first make changes to the previously submitted form before the transaction is resubmitted. |
Reset Phone |
Reset a phone. |
Return |
Return - From the detail display of a selected instance of a model, select this button to return to the list display of the model instances. |
Tag |
For a selected model instance, add a tag to it. |
Tag Version |
For a selected model instance, add a version tag to it. |
Test Connection |
For instances of models representing connection parameters such as connections to devices, click the button to test the connection. |
Visualize |
Deprecated. |
On the Admin Portal GUI, buttons and icons to carry out actions - according to the form contents, e.g. Phone.
Save
Delete
Clone
Move
Help
Purge
Export
JSON Editor
Apply
Lock
Reset
Restart
Vendor Config
Wipe
On-line Help¶
Press the Help button on both the Main Menu button bar as well as the Button bar to open a new browser tab to show on-line help for your system. The new browser tab shows the following menu options:
General Help: General help information for the application.
Model Detail Help: Model (Item) specific help, for example data/GeneralHelp. This content may vary according to the Field Display Policy that is applied to the item.
Model API Help: the API reference for the item.
When the Help button (?) is pressed on the Main Menu button bar, only the three menu options are shown. When the Help button is pressed on the Button bar, context sensitive help specific to the associated form is also shown.
If a Field on the context sensitive help for an item is marked with an asterisk next to the field name, it is mandatory and must be filled out in order for the subsequent transaction to be successful.
A user’s view of the available on-line help depends on hierarchy level, role-based access, and field display policies.
Main Page Controls¶
The following controls are available on the Admin Portal.
Icon |
Description |
---|---|
These icons are used to access the hierarchy. |
|
This icon is used to return to the main application page. |
Form Controls¶
The following controls are available from a form.
Icon |
Description |
---|---|
Open another instance of the current form field or open a pop-up screen to add an item. |
|
Delete the current instance of a field from a form or open a pop-up screen to confirm. |
|
Move the selected instance on a form down in the order of field entries. In the case where a Position field is available, for example for Lines, the entered value determines the order in the object. |
|
Move the selected instance on a form up in the order of field entries. In the case where a Position field is available, for example for Lines, the entered value determines the order in the object. |
|
Collapse or expand all array items, for form arrays with multiple items. Arrays are collapsed by default. You can expand or collapse selected array items in a form array, or expand/collapse all from the form array header. |
Icon |
Description |
---|---|
|
On multi-tabbed forms, navigate to the previous or next tab. |
A warning icon, for example if a mandatory field is not filled in. |
|
* |
Next to an input control on a form, the asterisk indicates that the field is mandatory. |
[Browse] |
Next to an input control on a form, a button to open a file selection dialog. |
[ V] |
Drop-down input box. Typing into the box filters the drop-down list choices. |
Note
On some parts of the user interface, when adding or deleting items via pop-up screens, clicking the OK button typically completes the update; that is, you won’t need to also click Save on the main form.
About¶
The About menu provides details for your system, including version, patches, and adaptations.
Version¶
Release: Installed product release version.
The version naming convention is:
new: <YY>.<num>, for example: 19.3 is the 3rd release of 2019.
legacy: <major>.<minor>.<revision>, where major=YY,minor=num,revision=revision of num.
Patch Bundle: The installed Patch Bundle (PB) number, if any.
Build Number: Product build number.
Release Date: Date when this version was released.
Deployed Mode: Current deployment mode type, for example:
Provider with HCMF
Provider Decoupled
Enterprise
Note
You can use the toolbar Copy icon to copy version release text to the clipboard.
Patches¶
If any patches have been installed on the system, these are listed under the Patches menu. Details of installed patches are also provided for reference and enquiries, for example:
Version: in this context, the patch version (there can be multiple versions of the same patch).
Defect IDs: VOSS Automate internal IDs for reference
Models: any models and model Instances added or affected by the patch
Adaptations¶
If any adaptations are installed on the system, these are listed. Select an adaptation from the list to see more details, for example:
Adaptation Tag(s): the tags can be used to find all models that are a part of the adaptation, using a search query such as
(tag IS <tag1>) or (tag IS <tag2>)
where
<tag1>
and<tag2>
are the names of tags.Note
The search for models is carried out from the user hierarchy and down.
Upgrade Risk: an indication of the impact of an adaptation on an existing system:
High: Core changes
Medium: Standalone adaptation using core workflows
Low: Standalone feature