PDXpert PLM Software
On-line Help Guide
This help topic describes the current PDXpert PLM release. Earlier releases may be different. To view your release's version of this topic, open PDXpert and press the F1 key or select the Help menu.
Manage user accounts
PDXpert software is licensed for a specified number of named user accounts.
A named user account is a unique log-in username that is assigned exclusively to one person, and which no other person may use.
A workgroup may share a named user account to look up product data on a kiosk computer. The kiosk uses a read-only user account on a single computer at a specified physical location. If you follow the rules (see below), then for licensing purposes you may count the kiosk computer as one person, regardless of how many actual people use the kiosk computer.
A PDXpert software license may not be used with more than one server computer. The PDXpert client may not be used to provide concurrent, shared, floating, enterprise, site or other non-exclusive user access.
A full-function named user account permits users to create new part, document and change records; add file attachments to the system library; review, comment on, and approve change forms; and configure the system through the administrator role. You can easily select (and edit) which permissions are applied to each user account by assigning the user an appropriate role from the Roles collection.
A read-only named user account allows a user to view - but not add or change - data records and attached files.
Whenever you wish, you can reassign a full-function license to a read-only user, and vice versa. You can also delete one person's log-in account and reassign that license to a different person.
Open the User Management window ( ) to:
- Create a new user account using an available full-function or read-only license
- Assign or modify a user's role
- Assign or reset a user account password
- Assign, change or remove a user's selected out of office agent
- Delete a user account and free up the related license to assign to another user
If desired, you can assign a read-only role to a user with a full-function license, and that license will act identically to a read-only license.
If the number of log-in accounts exceeds the maximum permitted by your license, then only the super administrator account is permitted to log into PDXpert. Use the Super Admin account to remove any excess log-in accounts.
To manage user accounts, you must be assigned an administrator role. An administrator role is one that has its Rules/Collections: Manage checkbox marked. See the Roles collection reference for details. The system's super administrator always has permissions to create and remove user accounts.
Any change that you make to a user's account may not take effect until after that user closes the PDXpert client.
Creating a new user account—
A user account is licensed for the exclusive use of one person. The new user account has a role, a username and an optional password, and the default set of user preferences.
A new user account row is displayed when (1) unused licenses are available, and (2) a Persons collection member doesn't yet have a user account.
In the Access column, select whether you are assigning a Full-function or Read-only user account.
The total number of licensed user accounts is specified by your PDXpert software license. To open the Software License Key dialog, select the command from the menu.
In the Person column, select the person whom you want to have a user account.
If you don't see the person in the list, (1) close this User Management window, (2) create a new person record in the Persons collection, in the Collection Explorer (Places/Organization/Persons > Persons), and (3) re-open the User Management window. Include the person's email address — when the user account is created, an email is sent to the person with the account name and PDXpert client download link.
In the Role column, select the set of permissions that a user will have within PDXpert.
Roles are created and modified in the Roles collection. If you don't see the desired role in the list, (1) close this User Management window, (2) create a new role record in the Roles collection, in the Collection Explorer (Places/Organization/Persons > Roles), and (3) re-open the User Management window.
Enter the Account name that the person should use for the log-in dialog. The log-in name is not case-sensitive: LEE and lee refer to the same user.
If you want the user authenticated by your organization's LDAP (Lightweight Directory Access Protocol) service, enter both the domain name and user name as <domain>\<username>. User names are validated within a domain; for example, company\lee and engineering\lee are different accounts. You can specify an LDAP server name or IP address, and include an optional port number (usually 389 or 636), such as 10.1.2.3:389\lee
The PDXpert server (not client) computer sends the user's credentials for LDAP authentication, and must join the LDAP domain. PDXpert uses the default Windows .NET protocol: username and password are encrypted using Kerberos ("sealing"), and data integrity is verified ("signing").
This username is used only for account log-in. Within the PDXpert application, the user is identified by the Persons member record.
Assign an account name that's clearly related to the person's name. It's difficult to manage software license compliance using a generic account name like quality.
If you wish, enter the Password that the person should use for the log-in dialog. Although a user's password is case-sensitive, this temporary password does not need to meet the requirements you specify in the Password policy system rule. For example, you can provide the user with a blank temporary password even though you specify a minimum password length.
If you're using LDAP to authenticate the user, this password is not used and can be left blank.
The password value is hidden after you create the account.
In the Action column, click the button to save the new user account.
Your user may now log into PDXpert using the account name and password you've assigned.
Creating a new kiosk account—
A kiosk account provides read-only access to any number of people in a workgroup on one physical computer. The new kiosk account must have read-only access and an account username that begins with kiosk… characters.
Create a new member in the Persons collection using the kiosk computer's network name, such as SERVICE02. If necessary, close the User Management window, create the member, and then re-open the User Management window.
In the Access column, select the Read-only user account.
If you don't see a Read-only user account, you can select a Full-function user account. The role that you select in Step 4 (below) must have the Restrict access to read-only checkbox marked.
In the Person column, select the kiosk computer's name that you created in Step 1.
In the Role column, select the set of viewing permissions that kiosk users will have within PDXpert.
Enter the Account name that kiosk users should enter for the log-in dialog. The username must begin with kiosk, such as kiosk2 or kiosk-service.
If you wish, enter the Password that the person should use for the log-in dialog. The password should meet the requirements you specify in the Password policy system rule.
In the Action column, click the button to save the new user account.
Setting a person as the super administrator—
The system's super administrator handles unusual situations: the PDXpert Server can reset this user's password, and this user can reduce user accounts to comply with the license. See the Collections reference > Places/Organizations/Persons > Persons: Default member of collection help topic.
Set the super administrator as the default member of the Persons collection:
In the Collection Explorer, go to the Persons collection (within the Places/Organizations/Persons group).
Select the person who will be assigned the super administrator permissions.
This person must have a user account with full-function access.
Right-click the person's name in the list, and selecton the context menu.
Modifying an existing user account—
You can assign a user a different role, reset a log-in password, and modify an out of office agent.
To assign a current user a new role, select the role from the dropdown list box in the Role column. The value is saved immediately.
To reset (clear) a forgotten password from the user account, click on thebutton at the password textbox. You can leave the password blank, or enter a new password and then click the button to save it.
The password value is hidden before you clear it, and immediately after you save a new password.
To add or modify a user's out of office agent, select the agent from the dropdown list box in the Agent column. Only persons with a full-function user account are listed. To remove a user's assigned agent, select the blank value from the dropdown list. Your selection is saved immediately.
Converting a user account between full-function and read-only access—
The system identifies a user account by its account access and assigned account name. To change a user's access, the system must build a new user account using the new Access value.
- To remove the existing access and free the log-in name, delete the existing user account.
- Create the new user account.
Changing a user account name—
The system identifies a user account by its account access and assigned account name. To change a user account log-in name, the system must build a new user account using the new Account name.
- To remove the existing user account log-in name, delete the existing user account.
- Create the new user account.
Deleting an existing user account—
Deleting a user account eliminates the person's ability to log into PDXpert and frees one license, making it available for reassignment to another person.
To remove a person's log-in credentials and release the license, click thebutton on the appropriate row.
Deleting a user account deletes that person's user preferences. If you create a new account for that person, then preferences (such as Enable local views and Out of office agent) are assigned their default values, and must be reviewed.
If the person is currently assigned as the super administrator, a different person must be set as the super administrator before the account can be deleted. In the Persons collection, select the name of the new super administrator, right-click to open the context menu, and select the command.
When an employee leaves your PDXpert system, you'll typically delete the user account but retain the person's record for historical accuracy. See Setting a person's status to inactive in the help topic Collections reference > Places/Organizations/Persons > Persons.
If the former user has selected an out of office agent, deleting the user account also removes the agent's permissions to the user's items and tasks. If you wish, you can temporarily specify an agent to take control of the previous user's in-process items. During this period, it's possible to assign a read-only license to the former user, then set the agent; the agent needs a full-function license.
Help Guide Contents [PDF]
- 0001. Welcome!
- 0002. Help conventions
- 0100. PDXpert Application Server
- 0101. Server overview
- 0200. How to...
- 0300. Console reference
- 0400. How to start the PDXpert client
- 0500. Program concepts
- 0600. How to set up PDXpert
- 0700. How to use the Item Explorer
- 0800. How to use the Collection Explorer
- 0900. How to work with documents
- 0901. Manage documents
- 1000. How to start a document
- 1003. Fill in the new document
- 1004. Add or remove references
- 1005. Save your document
- 1006. Remove your document
- 1007. Release your document
- 1008. Manage a released document
- 1009. Revise a released document
- 1010. Cancel a released document
- 1100. How to work with parts
- 1101. Manage parts
- 1200. How to start a part
- 1203. Fill in the new part
- 1204. Add, modify or remove BOM parts
- 1205. Import a CAD BOM
- 1206. Add or remove approved sources
- 1207. Add or remove references
- 1208. Save your part
- 1209. Remove your part
- 1210. Release your part
- 1211. Revise a released part
- 1212. Manage a released part
- 1213. Cancel a released part
- 1300. How to revise multiple markups
- 1400. How to work with change forms
- 1401. Processing a change
- 1402. Originate a new change form
- 1403. Analyze a submitted change
- 1404. Fix change processing errors
- 1405. Remove your change form
- 1406. Review a routed change
- 1407. Resolve an on-hold change
- 1408. Analyze an accepted change
- 1409. Use a released change
- 1410. View a completed change
- 1411. Analyze a stopped change
- 1412. View a rejected change
- 1413. Remove a canceled change
- 1414. Return a submitted change
- 1500. How to work with file attachments
- 1600. How to report, import & export
- 1601. Create a report
- 1602. Export a PDX package
- 1603. Use the Report/Export Wizard
- 1700. Import & update items
- 1701. Initialize your PLM database
- 1702. Use the External Data Importer
- 1703. Item Master import
- 1704. Iteration-level relational imports
- 1705. Bill of materials import
- 1706. References import
- 1707. Revision files import
- 1708. Sources import
- 1709. Item-level relational imports
- 1710. Item files & links import
- 1711. Materials import
- 1712. Groups collection import
- 1713. Materials collection import
- 1714. Organizations collection import
- 1715. Persons collection import
- 1716. Custom collection import
- 1800. View & export via ODBC
- 1801. View database objects
- 1802. Create an ODBC connection
- 1803. ItemViews reference
- 1804. ReferencePairViews reference
- 1805. SourcePairViews reference
- 1806. SourceItemMasterView reference
- 1807. StructurePairViews reference
- 1808. ChangeViews reference
- 1809. ChangePairViews reference
- 1810. FilePairMasterView reference
- 1900. How to perform other tasks
- 2000. Menu reference
- 2100. Item Explorer reference
- 2200. Document window reference
- 2300. Part window reference
- 2400. Change Form window reference
- 2500. System Rules reference
- 2501. System Rules window
- 2502. General: Copy files to snapshot
- 2503. General: Item uniqueness definition
- 2504. General: Reviewer's comment required
- 2505. Default File Access
- 2506. Password Policy
- 2507. References Tabs
- 2508. BOM: Allow duplicate parts
- 2509. BOM: Lock part default unit of measure
- 2510. BOM: Allow partner parts
- 2600. Collections reference
- 2601. Managing collections
- 2602. Custom attributes
- 2700. Places/Organizations/Persons
- 2800. General
- 2900. Documents
- 3000. Parts
- 3100. Changes
- 3108. Custom collections
- 3200. Other reference topics
- 3300. Software licenses & legal notices