Table of Contents

Search

  1. Preface
  2. Overview, Downloading, and Installing
  3. Administration API
  4. Identity Service API
  5. Screenflow Programming and SDK
  6. ActiveVOS WSHT API
  7. Embedding Request Forms in Standalone Web Pages
  8. XML-JSON for Process Central

7. APIs, SDKs, and Services

7. APIs, SDKs, and Services

Permissions

Permissions

Permissions determine who can see guides when information within the Forms, Designs, and Report panes. (Reports are not available in Process Designer.) Each is set independently; that is, the permissions that you set for one pane do not affect the permissions in the other. An application configuration file sets permissions for the Designs pane and an
.avcconfig
file sets them for the Forms pane. For example, if you set permissions for access in the Designs pane, these settings do not affect what users can see in the Forms pane.
Setting Permissions in an Application Configuration file
When you create an application configuration file with a screenflowConfig element, setting
globalPermissions
to
true
tells Guide Designer to display a Permissions tab within the guide designer's
Settings
dialog. Here is an example of setting the
globalPermissions
feature:
<screenflowConfig ...>    <
global
...>       <
features
>          <feature name="guidePermissions" enabled="true"/>          ...       </features>       ...
Now that this is set, users will see the following dialog when displaying the
Settings
dialog from the guide designer's toolbar.
Any user who has access to Process Designer will then be able to make changes here that affect the privileges that a user has for guides.
The permissions allow the following access:
  • Administrator
    : Has full access to guides; that is, an administrator can create and run guides, and can see and use this Permissions tab. Only administrators can see and use the
    Terminate Running Guides
    button that appears when a guide is selected in the upper-right panel displayed when the Designs pane is being displayed.
  • Guide Creator
    : Can create and run guides; however, users in this role do not see the Permissions tab.
  • Guide User
    : Can only run guides.
The settings made by users in this dialog do not affect permissions for accessing guides in the Forms pane.
Setting Permissions in an .avcconfig File
When you add an
.avcconfig
file that is associated with forms, you can set roles for who can access information. Here's an example that allows users in the three named roles to access forms.
<tns:requestCategoryDefs> <tns:requestCategoryDef id="requestcategory_guides_launchpad" name="${requestcategory_guides_launchpad}"> <avccom:requestDef id="hello-world" name="Guide In Form"> <avccom:allowedRoles> <avccom:role>abAdmin</avccom:role> <avccom:role>abDeveloper</avccom:role> <avccom:role>loanreps</avccom:role> </avccom:allowedRoles> ...
The settings made by users in this dialog do not affect permissions for accessing guides in the Forms pane.
An application can have more than one
.avcconfig
file. For example, you may have a second one that defines permissions for information in the Reports pane.
The order in which the Process Server uses the information in
.avcconfig
files is alphabetical. This means that the elements in one file can overwrite elements in another. You can see this order by selecting
Catalog | Resources | Central Configs
from within the Process Console. If one of your files is inadvertently overriding another, you will need to change the file's name to change the execution order.