During initial installation, only the Administrator account is created (which cannot be removed). This account has full access to all BPA Platform features.From then on, any account with System Administrator or Security Administrator enabled can create, edit, or delete BPA Platform user accounts.

Types of User Account Authentication

BPA Platform supports two types of user authentication:

► Internal — Internal accounts are created in and for BPA Platform only.
► Windows — Windows accounts are initially created in your Microsoft® Active Directory® database. To allow your users to use their Windows credentials to access BPA Platform, you must add those credentials to BPA Platform as well.

Adding a New User

To add a new BPA Platform user account, do the following:

  1. From the Administration toolbar, click New User button.

    New User Properties - General Tab

    Click the image to view full size.

  2. If adding an internal user, enable BPA Authentication.
    1. Enter a Username and Password for this user, then re-enter the password in Confirm Password.
  3. If adding a Windows user, enable Windows Authentication. Windows administrator-level credentials are needed as BPA Platform queries Active Directory to complete this stage.
    1. Click Browse.
    2. If Select this object type does not say Users, click Object Types and select Users — you may be prompted for administrator-level credentials here.
    3. Click Locations. Expand the Active Directory tree and select Users — you may be prompted for administrator-level credentials here.
    4. In Enter the object name to select, enter a username and click Check Names. If a valid username is found, the full object name, including domain, is shown.
    5. Click OK.
  4. (Optional) An Email address is only required if this users is to receive server notifications and alerts.
  5. Go to the Server Roles tab and enable the applicable roles for this user. Use Select All to assign all roles to this user.

    Note: All user roles can access the Event Log.

    Server RoleFeature Access
    System Administrator

    This is the highest level of server role.

    System administrators have access to all features listed below.

    Security Administrator

    Security administrators create BPA Platform users.

    Note that only System administrator-level users can maintain existing user accounts.

    Server Administrator

    Server administrators maintain BPA Platform, including:

    ►Managing licences
    ►Managing server global options
    ►Running maintenance
    Tool Administrator

    Create and maintain global configuration for allowed tools (Tool Access tab), memory providers (Memory Access tab), and agents (Tool Access tab).

    Repository Administrators

    Create and maintain repositoriesClosed Repositories are used by the Internal Memory feature to store memorised data in BPA Platform's proprietary database format..

    Variable Administrator

    Variable Administrators create and maintain global variablesClosed Variables are created and used extensively throughout and can either have fixed values or values that are dynamically populated when a task is run. Global variables are available for all tasks in this BPA Platform installation. Once created, global variables can be used by any task..

    Task-level variables are only available if users are Task Administrators as well.

    Formula Administrator

    Formula Administrators create and maintain global formulas.

    Task-level formulas are only available if users are Task Administrators as well.

    Function Administrator

    Function Administrators create and maintain global functions.

    Task-level functions are only available if users are Task Administrators as well.

    Task Administrator

    When logged in, Task Administrators only have access to the top-level Tasks folder. From here, they can:

    ►Create and maintain tasks containing allowed tools
    ►Open tasks created by other users — note that if access to a tool has not been granted to the logged in Task Administrator, steps using those tools cannot be opened
    ►Run tasks created by themselves and other users
    ►Enable / disable tasks owned by themselves and other users
    ►Create and maintain task folders
    ►Maintain folders created by other users that they have been granted permission to view
    ►Create and maintain task-level variables, functions, and formulas
  6. If this user is a Task or Tool Administrator, go to the Tool Access tab. By default, all tools are available to all Task and Tool Administrators; clear the selection for those tools this user does not have access to. If only allowing access to a few, click Clear All then select the required tools.
    1. (Optional) If allowing access to the Database Query (ODBC)Closed You typically use the Database Query (ODBC) tool to extract specific records from a relational database, using a valid ODBC driver to make the connection. These are then made available to other task steps as a recordset., Database Query (OLEDB)Closed You typically use the Database Query (OLEDB) tool to extract specific records from a relational database, using a valid ODBC driver to make the connection. These are then made available to other task steps as a recordset., or Call Stored Procedure (OLEDB)Closed The Call Stored Procedure (OLEDB) tool executes database stored procedures and functions to provide read, write, and automated data processing. tools, you can also restrict access to particular database connections if required. Click Advanced and select those database connections this user is only allowed to see and use.
  7. If this user is a Task or Tool Administrator, go to the Memory Access tab. By default, all memory providers are available to all Task and Tool Administrators; clear the selection for those providers this user does not have access to. If only allowing access to a few, click Clear All then select the required memory providers.
    ►Memorise data using an OLEDB compliant data source
    ►Free-type and graphical generation of SQL Statements
    ►Transaction support
    ►Memorise based on rules created in VBScript
    ►The current Repository data for a task may be compared to a new recordset produced at task run-time to filter the data passed to the Output Step for processing
    ►Repository data can be exported as XML or CSV for backup purposes or use in other applications
    ►Previously exported XML files can be imported into BPA Platform
    ►Previously exported or new CSV files can be imported into BPA Platform
    ►A Repository may be selected for use in any task so that different columns may be populated from different data sources
    ►Repository data values can be edited, rows deleted, or the Repository "reset" by deleting all the data
    ►The Repository schema may be edited to change column details, insert columns or delete columns to match the data source
    ►Memorise data using an OLEDB compliant data source supporting stored procedures
    ►Map values to procedure parameters
    ►Transaction support
    ►Memorise based on rules created in VBScript
    ►Memorise data using an ODBC compliant data source
    ►Free-type and graphical generation of SQL Statements
    ►Transaction support
    ►Memorise based on rules created in VBScript
  8. If this user requires access to COM objects to create VBScripts with, go to the Script Objects tab and select the relevant objects.
  9. Click OK.

Editing a User Account

To open an existing account for editing, including changing the account's password, do the following:

  1. Expand the System resources tree and select Users.
  2. Double-click the required account.
  3. Adjust the properties as required.

Deleting a User Account

If required, you can temporarily disable a BPA Platform user account (edit the account and enable Disable Account in the General tab). However from time-to-time, you may need to delete the account entirely; do the following:

  1. Expand the System resources tree and select Users.
  2. Right-click on the required account and select Delete.
  3. Confirm the deletion.