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.
Set up and manage system emails
In the PDXpert client, selectmenu | to manage the email account. The email account setup and queue can be managed by anyone with administrator permissions.
The PDXpert Application Server — not the PDXpert client — uses the email account on this window to send email notices.
Setting up the email account—
If user activities create notices before your email account is entered here, the queue may already contain emails waiting to be sent. Before configuring the email account, review the Queue tab's email list and delete any obsolete notices.
Create a new email account, such as PDXpert.NoReply@MyCompany.com or possibly use a third-party email service like PDXpert.MyCompany@gmail.com.
Ensure that the email account can forward all outbound notices. SMTP servers may place restrictions on the source or destination of the emails, or the total number that can be forwarded within a given time.
Ensure that emails sent from the account do not fill up the account storage and prevent new emails being forwarded.
If your SMTP server accepts connections only from known senders, confirm that the PDXpert server computer is whitelisted.
To help recipients manage their email notices, use a dedicated email account rather than a personal email account. However, for testing purposes, you can click thebutton: your Windows default email account is copied, and enter your account password.
PDXpert does not handle any inbound email traffic, and won't respond to replies by email recipients. Consider adding an auto-responder notice to the account.
Although a "forwarding only" account can be used, you won't receive test confirmations at the end of this setup process.
On the Settings tab, enter the email address into the Email address for sending notices textbox.
Click thebutton. You'll be prompted to provide the account password, after which the PDXpert Application Server tries several typical settings for sending email notices. If useful settings are discovered, a test email is sent from PDXpert to your email account, using your email server and account credentials.
If the email account settings cannot be discovered automatically, manually enter the email account values. You should first specify the Outgoing mail server (SMTP) of your outbound email (SMTP) server. An SMTP server is an internet domain, often with a sub-domain prefix, such as mail.mycompany.com or smtp.office365.com, or an IP address like 188.8.131.52.
To get the SMTP settings for a commercial email service, search the web for outgoing smtp settings for service, such as outgoing smtp settings for Office 365 or outgoing smtp settings for gmail.
You can obtain the SMTP server name from your IT administrator, or look in your email client (such as Microsoft Outlook) for the server your own email account uses.
If the PDXpert Application Server is installed on a computer that has a local Windows SMTP server enabled, you can use the value of localhost.
- You can enter the IP address of your Microsoft Exchange server. If you don't know the Exchange server's IP address, but you do know its machine name, you can determine its IP address by "pinging" it from the Windows command line: ping servername where you substitute your Exchange server's computer name for servername (for example, ping msexchange or ping mailserver). The screen shows the IP address for that server in the first line, between the square brackets. In the following example, the IP address of myserver is 192.168.23.105: , and then type
Pinging myserver [192.168.23.105] with 32 bytes of data:
Reply from 192.168.23.105: bytes=32 time<1ms TTL=128
If your SMTP server does not use the default TCP port 25, enter the server's preferred Port number (for example, 587).
Your PDXpert server computer's firewall and other software (antivirus/antispam) must allow a TCP connection through this port.
If your SMTP server requires an encrypted connection, mark Use SSL for encrypted connection. For example, mark this checkbox when using smtp.gmail.com with port 587.
There are two types of SSL authentication for SMTP, explicit and implicit.
The Microsoft .NET mail client used by PDXpert supports explicit SSL in accordance with internet standard RFC 2228. Explicit SSL connects to a normal SMTP port (typically 25 or 587) in plaintext. The .NET mail client then issues a STARTTLS to start encryption.
Implicit SSL is an unofficial protocol that begins immediate encryption using an agreed port (often 465). By design, the Microsoft .NET mail client used by PDXpert does not support implicit SSL.
Specify the account Name for the email account that is used to send notices to PDXpert users.
Enter the account Password for the email account name provided in the Name textbox, and re-type it in the Confirm password textbox.
Click on thebutton, then click the button. An email notice is sent from the email account that you've specified back to that same account. A new email appears in the account's in-box to confirm that the account settings are correct.
Test emails are relayed from the SMTP server to the same email account. To verify that the test notices are being correctly received, you must be able to view the inbox of the email account. If the receiving POP account is unable to store and display the test emails (for example, it's a forwarding-only account and there's no inbox), then you won't be able to directly verify the entire process.
Common email issues—
- To receive a workflow notice, each recipient must have a valid email address entered into the Persons member record. Ensure the email address has the correct spelling.
- Since any person who processes a workflow action already knows about it, the system normally won't send the workflow notice to that person. This simply reduces email inbox clutter. If you prefer to receive these emails, open the Copy me on email notices that I trigger. and mark
- The change form's workflow must be configured to send notices to identified users during the expected workflow event. For example, if observers should be sent email notices when a change form moves from Accepted to Released, then the Observers checkbox on template workflow path must be marked and all observing persons must be displayed in the change form's Observers tab.
- Some email servers are configured to distinguish between email addresses
inside and outside the company.
- If PDXpert is using an outside email account (like PDXpert.MyCompany@gmail.com), confirm that the account is allowed.
- If emails sent to addresses within your company (User1@MyCompany.com) are successful and emails sent outside your company (User2@gmail.com) are not — or vice versa —, then check the email server's domain forwarding rules.
- PDXpert may be configured to send many notices to many recipients, so appropriately configure any limits on the email account (such as the maximum SMTP relays).
- If you have an enterprise anti-spam list, whitelist PDXpert's assigned email address in the spam filter definition file. Users with individual anti-spam filters must also whitelist this email address.
- New email notices are added to a queue that's processed every ten minutes. Notices may have a delay of up to 10 minutes (in addition to any email server processing).
Sometimes email notices cannot be sent because, for instance, the email SMTP server is unavailable due to system maintenance, network interruption or other issue. The PDXpert Application Server holds the email notices in a queue and tries to re-send them every 10 minutes for up to 24 hours.
The list displays the status of each unsent email:
Email ready: The email notice is in the queue and is sent during the next connection to the SMTP server. If the email remains unsent for more than 10 minutes, then the email settings specified in the Settings tab should be reviewed for correctness.
Email blocked: The email notice has not been sent, typically because the SMTP server is unavailable. The system continues to attempt to send blocked notices for up to 24 hours.
Email failed: When all attempts have failed, the system will stop trying to send the email notice. A failure often occurs because the user's email address is blank or invalid in the Persons collection member.
If the email server has been unavailable for a while, unsent emails may no longer be useful to their intended recipients. In this case, delete selected (or all) notices from the email queue before re-enabling the email server.
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