Workflows

www.altova.com Expand/Collapse All Print this Topic Previous Page Up One Level Next page

Home >  Web UI Reference >

Workflows

The Workflows tab (screenshot below) provides an interface for managing the container structure of the root folder of MobileTogether Server and the access rights (permissions) for each container. Containers are folders that contain sub-containers and/or solutions (also called design files or .mtd files). MTD files cannot be added to a container via the server's Web UI, but are deployed to the server from MobileTogether Designer. At deployment, the exact path to a container must be specified; this is facilitated by being able to browse, in MobileTogether Designer, to the required container.

Click to expand/collapse

The Workflows tab initially displays the root container, which is denoted by the "/" character.
Click the Down arrows next to a container's name to display the sub-containers of that container; click a sub-container in the pop-up list to go to that sub-container.
To go to a container, click it.
Every level that you descend in the hierarchy of containers is displayed at the top of the window as a "breadcrumbs" path. The Down arrow of each level displays the sub-containers of that container, so you can navigate easily to different containers.

MTSWorkflowsBreadcrumbs

To select a container, click the container's check box. Selections are used for renaming, moving, and deleting containers (see Functionality below).

 

 

Click to expand/collapseFunctionality

The buttons of the tab provide the following functionality:

Create Container

Creates a container in the current folder. Click a container to open it

Save

Saves changes such as a modification of descriptions

Move or Rename Selected Objects

If one object is selected, opens the Rename and Move dialog, in which you can (i) rename and/or (ii) move the object to a new container that you select. If multiple objects are selected, opens the Move dialog, in which you can select the container to move to.

Delete Selected Objects

Deletes the selected container or file

Lock Selected

A locked solution cannot be overwritten by a new deployment. If attempted, an error message is displayed in MobileTogether Designer

Unlock Selected

Unlocks a locked solution

Permissions

Sets which users/roles can access individual containers, and their level of access

Search

Searches for the term submitted. Check Recursive to search in descendant containers

 

Other available actions:

To navigate up the container hierarchy, click the required ancestor folder in the path at the top of the Workflows tab
To navigate down the container hierarchy, click a container to open it
Click a solution file's URL to run the solution

 

 

Click to expand/collapseThe container /public/

Clicking the public container opens the container and displays its contents. public is a predefined container containing sample design files (solutions) that are delivered with the program. Click a solution's URL to run it.

mtsworkflowspublic_zoom45

 

Click to expand/collapseThe display of a container's contents

A container contains sub-containers and/or solutions (aka design files or .mtd files). The contents of each container are displayed as a tabular list. The columns of the table display the properties of solutions:

 

Name: Name of the solution file as saved in MobileTogether Designer.
App, App version: The App and App Ver columns appear only if at least one AppStore App (see the MobileTogether Designer user manual) has been deployed to the server. They display, respectively, the name of the AppStore App and its version.
Description: Short description of the solution, which can be entered by clicking in the field.
Design Version: Version of MobileTogether Designer in which the solution was created.
Last Deployed On: The date and time of the solution's last deployment.
Global Resource Configuration: The global resource that has been defined for that solution and deployed to the server. If no global resource is specified, Default is displayed.
Persistent Data: A Clear Data button appears in this column if data has been changed while running the solution. Click the button if you wish to undo the changes.
Automated Test: A blue wheel indicates that at least one test run for automated testing of that solution is available, but is not active. A red wheel indicates that at least one test run of the available test runs is active. To activate a design's test run or configure how the test run is played back on the client, click the solution's wheel icon (shown in the screenshot above). This displays a page showing the automated tests of that solution (see next section below). For information about Automated Testing, see the MobileTogether Designer documentation.
Run in Browser: The server URL where the solution file is deployed. Click to run the solution. (For AppStore Apps, no URL is displayed because the AppStore App cannot be opened in a web browser.)

 

 

Click to expand/collapseAutomated testing

When you click the wheel icon in a solution's Automated Test column, a page is displayed that shows the automated tests of that solution (screenshot below).

Click to expand/collapse

The Automated Tests page shows all the test runs that have been deployed for the selected solution. You can set up individual test runs for playback on client devices as follows:

 

1.In the Active column, check the test runs that you want to make active. These test runs will be played back on the client when the user starts a solution. If multiple test runs are selected, then all the selected test runs will be played back. If any one of a solution's test runs has been activated, then, on the Workflows page, the wheel in the design's Automated Test column is displayed in red.
2.Set the speed of the test run in the Run Type column. You can set the speed for all test runs at once by selecting the speed in the dropdown list of the column header.
3.Set the logging details you want during playback. Do this by checking the columns you want. See the Automated Testing section in the MobileTogether Designer documentation for information about these options.
4.Click Save to finish.

 

If you wish to delete a test run, select its check box in the leftmost column and click Delete Selected.

 

Permissions

In the lower part of the Automated Tests page (screenshot below), you can specify: (i) what users and roles can run automated tests for the selected solution (in the Security tab), and (ii) the devices on which test runs can be carried out (selected in the Devices tab).

 

MTSAutoTestSecurity

 

Users and roles are selected in the Security tab, devices are selected in the Devices tab (see screenshot above).
To assign a user/role or device to the Allowed list, select it in the left pane and click Assign (see screenshot above).
Remove a user/role or device from the Allowed list by selecting it and clicking Remove.
You can assign or remove multiple selections at a time.
If no device is assigned to the Allowed list, then test runs for that solution can be run on all devices.

 

Note:    All automated tests that were deployed prior to an upgrade of the server to version 4.1 (released 27 February 2018) or later will get security permissions for all users/roles; that is, all users/roles can run automated tests, which is the same behavior as that prior to the upgrade. For automated tests that are deployed subsequent to an upgrade to version 4.1, security permissions are set for no user/role; that is, any user or role that may run automated tests must be explicitly specified.

 

 

Click to expand/collapsePermissions

Permissions are access rights, and they can be set for each container individually. Permissions determine which users or roles have access to that container, and what kind of access each user/role has (read, write, use). These access rights can be set for the container, its workflows (or solutions), and read/write security.

Click to expand/collapse

For containers, permissions are inherited from parent containers.
For users, permissions are inherited from all roles the user is a member of, as well as from permissions directly assigned to the user.
Inheritance rules for users take precedence over container hierarchy rules.
If a permission is redefined for any role the user is a member of, container hierarchy inheritance for this particular permission is overridden.

 

 

Permissions are checked for every user interaction. A user can only successfully access and/or edit when all required permissions are granted. Permissions are set for the following groups:

 

Container

Read: The user can list the contents and find an object in the container.
Read-Write: Additional to read, can create new (and delete existing) objects, depending on other permissions that may apply.

 

Workflow

Read: The user can run solutions.
Read-Write: The user can additionally write to solution data. To modify file data, write access must also be granted for the container.

 

Security

Read: The user is permitted to read the permission list of any child object of the container.
Read-Write: The user can additionally change the permissions list of any child object of the container.
By default a user is permitted to read only permissions assigned to it or a role it is a member of. If the Read Users and Roles privilege is granted (see Users and Roles), users can read all permission entries.

 

 

1.Click the Permissions button of the container. This takes you to the container's Permissions page (screenshot below).

Click to expand/collapse

2.To edit the access rights of an already permitted user/role, click its Change button (see screenshot above). To add permissions for a new user/role, click Add Permissions. Both these buttons open the Edit Permissions pane.

Click to expand/collapse

3.In the Edit Permissions pane, select a user/role by checking its check box. If you are editing existing permissions, permissions will be inherited from this user/role. If you are adding permissions, this user/role will be added to the permitted users/roles list of this container. In the Search At combo box, you can select users and roles that have been defined for MobileTogether Server or for all enabled domains (by selecting, respectively, MobileTogether Server or Windows in the combo box). A domain's users and roles are defined by the domain's administrator. They will be available in the pane only if the Active Directory Login setting has been enabled in the Settings tab.
4.Change the permissions as required. The Inherit option causes permissions to be inherited from the parent container.

 

 


© 2019 Altova GmbH