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.
User roles & permissions
Full-function and read-only licenses—
A full-function license permits the creation and modification of item records, approval of change forms, and the administration of collections in accordance with the role assigned to the user. A read-only license prevents the user from unlocking item windows, and therefore can't be used to create or edit items, add file attachments, or approve change forms. Viewing permissions are still regulated in accordance with the user's assigned role.
Creating a person record (that is, a new member of the Persons collection) allows someone's name to appear on a PDXpert item or to receive an email notice.
A person can interact with the PDXpert client application only after an administrator has created a user account that combines:
- An available full-function or read-only license; and
- A Persons collection record (say, Nik Tesla); and
- A named set of permissions as defined by a Roles collection member (like Analyst); and
- An account or "log-in" name (ntesla); and
- An optional account password (mypa$$w0rd).
A user account has two elements — an account (or "log-in") name and a password:
- Account names can be any string of characters, such as some combination of the user's first and/or last names or employee number. An account user name is not case-sensitive.
- Passwords are case-sensitive, and are managed by the account user. A temporary password is usually assigned when a log-in account is first created, and users are expected to change their passwords immediately. After the account is created, system administrators can never view a user's password; if a password is forgotten, a system administrator can only clear it or assign a new one.
For example, to add Nik Tesla as a change workflow observer, his Persons collection record must first be created. Although Nik may then receive observer emails, he would not be able to view the change unless he's also assigned a user account to open PDXpert.
PDXpert is installed with a standard set of security roles that permit users to access information appropriate for their responsibilities. Access can be further tailored on a per-role, and new user roles can be defined with their own set of permissions.
Administrators have the ability to create and delete user accounts, authorize group reviewers, manage collections, set system options and workflows, and make other changes to the system environment.
A role has administrator permissions when Collections/Rules: Manage is marked in the related member of the Roles collection.
An administrator can also modify selected item attributes if the role allows access to those items and the Administrator Override user preference is marked.
Analysts have overall responsibility for processing changes after they've been submitted. An analyst who's assigned to a change can edit fields, add and remove file attachments, modify any of the trustees' work, and route the change to the reviewing groups. Analysts who are not assigned to a change can process the workflow for any change form.
In addition to a system analyst, who can manage all item classes, there can be class-specific analysts:
- Document analyst: This role is limited to act as trustee only for documents.
- Part analyst: This role is limited to act as trustee only for parts.
Normal users have free access to create new items, as well as create and edit change forms that can then be submitted for approval. If a normal user is an item trustee or an authorized reviewer, more permissions may be available.
- Trustee: This is a self-assigned role; a trustee has certain rights to modify, release or delete items that the trustee has created.
- Reviewer: A group's representative (assigned by an administrator) for examining and approving change forms and their associated items.
Guests can view any item for which they have appropriate permission, but cannot make any database additions, changes, or deletions. Guests do not have permissions to view collection members.
A guest role is defined by clearing all Create new and Manage checkboxes on the Roles collection member window.
While roles define broad categories of access, the Product Families collection allows you to tailor access much more narrowly.
Users identified on a Product Families collection member's Product Team tab have permissions to modify specific item attributes even after an item has been released.
You can exclude a person, group, or organization from viewing items belonging to a particular product family, even if a role generally permits the user to view, create, or manage items. You can override this exclusion by explicitly adding the user to the Product Team. For instance, you can exclude the entire marketing team from viewing a new product design by listing that group on the Denied Access tab, but then allow the project's marketing manager to work on the project by adding that user to the Product Team tab.
Group reviewers represent their team's interest in the contents of a change form. One reviewer from each required group must approve a change form before it can be released; a single reviewer who disapproves the change prevents it from being released.
Obviously, to fully represent a group, a reviewer must have full access to the items affected by the change form. Therefore, reviewers typically will have broad permissions to view pending, released and canceled items, and must not be denied access by product family.
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 a document's 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 a part's 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