Adding Users
You can add users individually, or you can import multiple users simultaneously from a comma-separated values (CSV) file or LDAP server connection.
Users who are associated with an LDAP server connection are authenticated against LDAP each time they start aPriori.
Adding a Single New User
1 Click Add User on the Users tab to display the Add User window.
By default, the Standard tab is displayed.
2 Enter user information into the fields on the Standard tab.
Column | Description |
|---|---|
Login ID | Identifier required to log in to aPriori. |
Full name | Enter the full name of the user for the associated Login ID. |
Last name | Last name of the user for the associated Login ID. |
First name | First name of the user for the associated Login ID. |
Middle name | Middle name of the user for the associated Login ID. |
E-mail | The user’s email address. |
System Admin | Check this box to provide access to the System Admin Toolset. Uncheck the box to restrict access. |
VPE Admin | Check this box to provide access to the VPE Toolset. Uncheck the box to restrict access. |
Provenance | LDAP connection name. If your site uses one or more LDAP servers and you have defined LDAP connections for doing so, use this field to select the LDAP server connection against which the user will be authenticated. If you select an LDAP server connection, you will not assign the user a password. Select the blank option if you do not want to use LDAP authentication. NOTE: See LDAP Connection Behavior as of Release 2017 R1 for additional behavior introduced in Release 2017 R1. |
Password | Enter the user’s password. If this field is disabled, LDAP authentication is selected. |
Confirm Password | Re-enter the user’s password. Once confirmed, the password is stored in encrypted format. |
Location | The user’s physical location. |
Department | The user’s department. |
Manager | The name of the user’s manager. |
Function | Some companies specify a role or other job description for employees. Use this field to contain this kind information. |
User License | Select the license ID (as provided by aPriori) that this user should be using. |
Preferred Currency | Select the default currency in which component costs are displayed by default for the user. |
Schema Privileges | Select the component database to which the user is connected by default when aPriori starts. (For information about deployments and schemas, see Editing User Settings in the Managing deployments). |
Default Schema | If your company has multiple schemas to restrict access to specific cost objects, select the schema the user will be connected to by default. |
Roles | Reserved for Cost Insight Design. |
Default Role | Reserved for Cost Insight Design. |
Reset Password | When set, the new user can log in one time with the password you have specified but must immediately change to a new password of their choice. |
3 (Optional) Click the Extras tab if you want to define up to ten Extra user fields.
These extra fields enable you to use additional information about each user to affect aPriori behavior. You can use these fields in whatever way makes sense for your company. For example, you could use these in conjunction with Access Control rules (as properties to the "currentUser" subject), or to implement new custom workflow capabilities delivered by aPriori’s Professional Services team.
4 Click OK.
The new user’s Login ID is displayed in green at the bottom of the user list.
5 Select File > Publish Changes from the System Administrator menu bar or click 
in the toolbar to display the Publish Changes window, then click Yes to publish your changes.
in the toolbar to display the Publish Changes window, then click Yes to publish your changes.Importing Multiple Users from a CSV File
You can import users from a spreadsheet in the form of a CSV (comma-separated values) file.
In addition to the details listed in the procedure steps below, the following rules determine how entries are handled:
• Users are added or deleted as follows:
• If a login id exists in the spreadsheet but not in aPriori, the user is added.
• If a login id does not exist in the spreadsheet but does in aPriori, the user is deleted.
• The last super user cannot be deleted
• A currently logged-in user cannot be deleted.
• The provenance value from the spreadsheet overwrites any existing provenance value for an existing user. If a user’s provenance changes from LDAP to either blank or Manual, their password is reset to the default value provided during spreadsheet import. On their next login, they will be prompted with a Reset Password dialog (the same as a new user added via spreadsheet).
• User attribute values overwrite any existing attribute values for a matching user (i.e., the spreadsheet cell value replaces the aPriori user attribute value based on column name).
Use the following procedure to import users from a CSV file:
1 Ensure that your CSV file contains the column headers you need from the list below so that aPriori can map data in those columns to specific fields in the aPriori users list. Only the loginID column is required. The other columns are optional.
• loginID
• fullName
• firstName
• lastName
• middleName
• email
• isAdmin – Use values of yes or no; true or false
• isVPEAdmin – Use values of yes or no; true or false
• location
• department
• manager
• function
• schemaPrivileges
IMPORTANT: schemaPrivileges values must be entered in the format
<deploymentName>:<schemaName>
Also, If the SchemaPrivileges column has multiple values separated by commas, then these should be enclosed in quotes so that the values are not imported into incorrect columns:
"Default:Default Scenarios,Default:Development Scenarios"
<deploymentName>:<schemaName>
Also, If the SchemaPrivileges column has multiple values separated by commas, then these should be enclosed in quotes so that the values are not imported into incorrect columns:
"Default:Default Scenarios,Default:Development Scenarios"
• defaultSchema
IMPORTANT: defaultSchema values must be entered in the format
<deploymentName>:<schemaName>
<deploymentName>:<schemaName>
• userLicenseName
• preferredCurrency – Three-letter currency code. Possible values are:
- USD – U.S. Dollars
- BRL – Brazilian Real
- CAD – Canadian Dollar
- CNY – Chinese Renminbi Yuan
- EUR – Euro
- GBP – British Pound Sterling
- HKD – Hong Kong Dollar
- INR – Indian Rupee
- JPY – Japanese Yen
- KRW – South Korean Won
- MXN – Mexican Peso
- TWD – Taiwanese NT Dollar
• roles
• default role
• provenance
• extra1 through extra10 – See the previous section ("To add a new single user")
The currency code in your CSV file must also be active in the Deployment Data tool of the VPE Toolset to successfully set the user’s preference. For more information, see the aPriori VPE Administration Guide.
Note: If existing users are not present in an imported spreadsheet, those users are removed, regardless of provenance setting.
A sample CSV file (aPriori_Import_Users.csv) is provided in the install-support/templates folder in your aPriori installation folder.
2 Click Import from Spreadsheet to display the Select spreadsheet file window.
3 Navigate to the CSV file, select it, and click Open to compare the users in the CSV file to the users already in the aPriori user database and display the Synchronize with LDAP window that summarizes pending changes from this comparison.
The Import from Spreadsheet window displays the:
• Added users – Number of pending new users; that is, users found in the CSV file that were not in the aPriori user database
• Deleted users – Number of pending deleted users; that is, users in the aPriori user database that were not in the CSV file
4 Click OK to display the following changes on the Users tab:
• New users’ login IDs are displayed in green.
• Users to be removed are displayed in gray, with a strikethrough.
• Modified users’ login IDs are displayed in blue.
5 Review your changes.
We recommend using the Show Pending Changes checkboxes at the top of the Users tab to quickly review your changes. Check the Added, Removed, or Modified boxes to show only those users.
Uncheck the boxes to show all users.
NOTE: Ensure that mandatory fields Schema Privileges and Default Schema are populated for each user. If not, ensure that the values in the .csv spreadsheet ar defined correctly (i.e., in the format <deploymentName> : <schemaName> . Proceeding to publish your changes without these fields correctly defined can result in the following error message when these users attempt to login: “Not authorized to connect to any schemas. Please contact your administrator.”
6 Revert any pending changes by right-clicking one or more rows in the table and selecting one of the following options from the context menu:
• Remove – Remove the selected users from the user list
• Undo Remove – Restore the selected users marked for removal
• Undo Edits – Remove any changes made to a user via import or manual edits
Ctrl+click or Shift+click to select multiple rows.
7 Select File > Publish Changes from the System Administrator menu bar or click in the toolbar to display the Publish Changes window, then click Yes to publish your changes.
in the toolbar to display the Publish Changes window, then click Yes to publish your changes.Change indicators are removed.
If you delete users, any aPriori licenses allocated to these users are released and available for assignment to other users.
Importing a User CSV File from the Command Line
As of 2018 R3 SP1, you can import a CSV user spreadsheet from the command line as well as from the UI (as described in the previous section). This command line approach is similar to aPriori BOM Loader and Bulk Costing functionality, as well as the Access Control group functionality also introduced in 2018 R3 SP1.
The command to run this functionality is:
<apriori_install>\bin\loadUsers.cmd
loadUsers.cmd syntax
loadUsers.cmd <importFilePath> <defaultPassword>
{<userName>} {<userPassword>}
{<userName>} {<userPassword>}
where:
<importFilePath> is the full path to the import user spreadsheet file.
<defaultPassword> is the password for newly created users.
<userName> is the aPriori user account under which the changes will be made.
<userPassword> is the password for the aPriori user.
<userName> and <userPassword> are optional if Single Sign On is enabled. The loader will try to log in using the current Windows user login if they are omitted. Note that the user should be a member of the Super Users group.
IMPORTANT: Although importing the user spreadsheet from the command line has the same basic behavior as importing through the UI, you will not have the opportunity to review the results before publishing the changes. This means that if an active user is not included in the spreadsheet that user will be removed upon import. So, for example, if you imported a small spreadsheet with just a few users for whom you wanted to make some changes, all the other users would be immediately removed upon import. The spreadsheet should include all active users and the way they should exist in the database after the import, even if they are not being changed. Here is a summary of all import behavior:
1 Users who are in the spreadsheet but not in the user database will be added and activated so long as all their details are valid.
2. Active users who are in the spreadsheet will either be:
a. Modified if any of their fields have changed.
b. Skipped if their fields have not changed. (“Skipped” means they are neither updated nor removed.)
3. Active users who are not in the spreadsheet will be removed.
4. Removed users who are in the spreadsheet will be activated if a valid license is specified for them. Other valid changes within the same row will be accepted. If you have an activate row and one or more rows that change other fields for that user, only the activate row will be accepted and the other rows will be skipped as duplicates. You cannot modify a removed user (except by activating them). Removed users who should remain removed do not need to be included in the spreadsheet.
Import Multiple Users by Synchronizing with an LDAP Server Connection
1 Configure one or more LDAP connections.
For more information, see Managing LDAP Server Connections on page 1.
2 Click Synchronize with LDAP to display the Synchronize with LDAP window.
3 Select one or more LDAP connections and click OK to compare the users from the LDAP connection’s User Search Path (with filter criteria) to the users already in the aPriori user database and display a summary of pending changes from this comparison.
You can check the Select/Deselect All box to select all the LDAP connections. Uncheck the box to deselect all the LDAP connections.
The summary displays the:
• Added users – Number of pending new users; that is, users found in LDAP that were not in the aPriori user list
• Deleted users – Number of pending deleted users; that is, users in the aPriori user list with the Provenance set to the selected LDAP connection, that were no longer in the LDAP connection
4 Click OK to display the following changes on the Users tab:
• New users’ login IDs are displayed in green.
• Users to be removed are displayed in gray, with a strikethrough.
• Modified users’ login IDs are displayed in blue.
Once the Users pane refreshes, these change indicators are removed.
5 Review your changes.
We recommend using the Show Pending Changes checkboxes at the top of the Users tab to quickly review your changes. Check the Added, Removed, or Modified boxes to show only those users. Uncheck the boxes to show all users.
6 Revert any pending changes by right-clicking one or more rows in the table and selecting one of the following from the context menu:
• Remove – Remove the selected users from the user list
• Undo Remove – Restore the selected users marked for removal
• Undo Edits – Remove any changes made to a user via import or manual edits
Ctrl+click or Shift+click to select multiple rows.
7 Select File > Publish Changes from the System Administrator menu bar or click in the toolbar to display the Publish Changes window, then click Yes to publish your changes. Change indicators are removed.
in the toolbar to display the Publish Changes window, then click Yes to publish your changes. Change indicators are removed. If you deleted users, any aPriori licenses allocated to these users are released and available for assignment to other users.