| Agile Product Lifecycle Management Administrator Guide Release 9.3.3 E39286-04 |
|
 Previous |
 Next |
| Agile Product Lifecycle Management Administrator Guide Release 9.3.3 E39286-04 |
|
Previous |
Next |
The Agile PLM SmartRules are documented in SmartRules.
To modify a SmartRules setting:
Under System Settings, double-click SmartRules. The SmartRules window appears.
At the rule you want to change, select a setting from the drop-down list. The list of possible settings can include the following values:
Allow – The system permits the process to occur.
Disallow – The system prevents the process from occurring.
Warning – The system warns the user that the process is occurring.
Remove – Removes all approvals/rejections on the Workflow tab when the routable object returns to the status where first rejected.
Retain – Keeps all approvals/rejections on the Workflow tab when the routable object returns to the status where first rejected.
Display – Displays the object in the table.
Display with Just Description – Displays the object with its subclass and description. The part number and other values read from the object are not displayed.
Display with Just Part Num and Rev – Displays the object with its subclass, part number, and revision. The description and other values read from the object are not displayed.
No Display – Does not display the object in the table. No warning is given.
No Display with Warning – Does not display the object in the table. Issues the following on the tab: "There are x objects not displayed due to insufficient user privilege."
When you have finished, click Save.
To revert to the original settings or start over, click Close. You will be prompted whether you want to close the window without saving; click Yes if you do or No if you do not.
This section explains the SmartRule settings you can configure.
Settings: Yes, No (default)
When set to Yes, upon removing an attached file from a business object Attachments tab, if the file folder is not in use by any other business object (that is, no versions of the file folder are referenced by a business object), the file folder is automatically soft-deleted.
A user with the appropriate search capabilities can run the File Folder Recycle Bin Search and hard-delete (or undelete) the soft-deleted file folder.
Settings: Allow (default), Disallow, Warning
Allows or disallows automatic installation of Microsoft Project (2002 and 2003) DLLs into a user's system registry. Installation of these DLLs enables seamless publishing using an Agile menu within Microsoft Project. It should be set to Disallow if your company does not want any applications to be automatically installed, or if you prefer to set up an Agile-MS Project connection systemwide.
Settings: Allow (default), Disallow, Warning
Allows or disallows RFQ or response-line data to be published to objects in the Quote History subclass.
Settings: Allow (default for non-Oracle DB systems, and for upgrading customers), Disallow (default for Oracle DB systems)
For systems based on Oracle DB, this SmartRule validates whether a BOM recursion can occur, that is, when a subassembly includes one of its parent items from an upper level of the BOM tree structure on its own BOM. (A recursive BOM structure, if carried to its logical conclusion, would repeat indefinitely).
The validation happens when a change order (ECO, SCO, and MCO) advances to Released, or when Release Audit is performed, or when the change tries to advance when current status needs to Pass Release Audit (assuming SR setting is Disallow).
|
Note: Because non-Oracle DB systems do not allow or check for recursion, this SmartRule has no effect; these systems should see the default setting is Allow. |
|
Important: The PG&C and PCM solutions do not support BOM recursion. For companies using either of these solutions, set this SR to Disallow. |
Settings: Allow, Disallow, Warning (default)
Determines whether to allow movement of the routable object to the next status or warn the user that an approver has rejected the change. It affects all Review or Released status types.
If you require the ability to determine if a routable object should be allowed to proceed when it does not meet the SmartRule, set it to Disallow. A user with Override privilege can advance the routable object in the workflow. See the Caution about this property in Override.
|
Note: To ensure that a routable object is not autopromoted through the workflow after a user has rejected it, set this SmartRule to "Disallow." Setting it to "Warning" will, in some cases, allow the routable object to be autopromoted through the workflow even when that is not the intended behavior. |
Settings: Allow, Disallow, Warning (default)
Determines whether to allow movement of the routable object to the next status when an acknowledger has not responded with either an acknowledgment. It affects all Review or Released status types and applies only to changes that are being manually moved to the next level. Autopromotion requires that each acknowledger acknowledge the routable object.
Settings: Allow, Disallow, Warning (default)
Determines whether to allow movement of the routable object to the next status when an approver has not responded with either an approval or a rejection. It affects all Review or Released status types and applies only to changes that are being manually moved to the next level. Autopromotion requires that each approver either approve or reject the routable object.
Settings: Allow, Disallow, Warning (default)
Determines whether to allow movement of the routable object to the next status or warn the user that an observer has rejected it. It affects all Review or Released status types.
If you require the ability to determine if a routable object should be allowed to proceed when it does not meet the SmartRule, set it to Disallow. A user with Override privilege can promote the routable object. See the Caution about this property in "Override."
Settings: Allow, Disallow (default), Warning
Determines whether an attachment file that is being checked in can have a different file extension than the file that was checked out.
|
Note: This rule is overridden when an item's attachment is Latest-x and the file extension in the attached file folder is changed and is therefore different than the extension of the item's checked-out file. |
Settings: Disallow, Reference (default), Reference with Warning
Controls automatic copying of files to a new revision. The system checks this SmartRule only when a pending change is created and not when attachments are added. The settings work as follows:
Disallow – The new item pending revision is created with no design attachments.
Reference – Agile uses the existing file folder and creates a new reference to it on the item's new pending revision Attachments tab.
Reference with Warning – The same as the Reference setting, with the option of choosing no design attachments for the new pending revision.
Settings: Copy, Copy with Warning, Disallow, Reference (default), Reference with Warning
Controls automatic copying of files to a new revision. The system checks this SmartRule only when a pending change is created and not when attachments are added. The settings work as follows:
Copy – For the item's new pending revision, Agile creates a new file folder and creates a new copy of the attachment file, which is placed in the new file folder.
Reference – Agile uses the existing file folder and creates a new reference to it on the item's new pending revision Attachments tab.
Disallow – The new item pending revision is created with no attachments.
Copy with Warning – The same as the Copy setting, with the option of choosing no attachments for the new pending revision.
When you add items to the pending ECO, you are presented with a warning dialog that includes a row for each item you are adding.
To add the item and to copy the attachments, check both the Add check box and the Attachments check box.
To add the item with no attachments, check only the Add check box.
Reference with Warning – The same as the Reference setting, with the option of choosing no attachments for the new pending revision.
When you add items to the pending ECO, you are presented with a warning dialog that includes a row for each item you are adding.
To add the item and to reference the existing attachments, check both the Add check box and the Attachments check box.
To add the item with no attachments, check only the Add check box.
|
Note: If you set this rule to Disallow, files that were added to the Introductory revision after the object was associated with a change (that will result in released Rev A) will not be copied to subsequent revisions. Also, when a new Change is created, all the files that were added to the Introductory revision won't be added to the newly created revision. |
Settings: Copy, Do Not Copy (Default)
If set to Copy, then all relationship rows will be carried over to the new revision of revision-controlled objects.
If set to Do Not Copy, the relationships are not copied to the new revision of the revision-controlled objects.
Settings: Allow, Disallow, Warning (default)
Should prevent accidental deletion of Instances, which already have a BOM, from the Instance tab. Deleting the Instance would lead to the loss of the Model relationship, including the Configuration Draft.
Settings: Retain (default), Remove
Defines whether ad hoc (not the default) approvers acknowledgers, and observers will be removed from the list when the routable object is rejected and returned (that is, demoted) to a previous status. It affects all Review and Released status types in all workflows.
Retain – When a workflow is returned to a previous status (including Pending), the ad hoc reviewers are retained and they will see the change when it advances through the workflow again.
Remove: – When a workflow is returned to a previous status (including Pending), the ad hoc reviewers are removed; they will not see the change again unless the originator or change analyst adds them back.
Settings: Retain (default), Remove
Defines whether approvals/rejections already recorded will be removed from the routable object's Workflow tab when it is rejected and returned (that is, demoted) to a previous status. It affects all Review and Released status types in all workflows.
Retain – When a workflow is returned to a previous status (including Pending), the signoffs that are already recorded are retained.
Remove – When a workflow is returned to a previous status (including Pending), the signoffs are removed and approvers will have to sign off again when the change advances through the workflow.
Settings: Disallow (default), Allow
Controls the display of the Timesheet tab in Product Portfolio Management.
Disallow – The Timesheet tab and all associated actions are disabled.
Allow – The Timesheet tab is displayed next to the My Assignments tab for users to enter Actual Hours against a task or activity. When the Timesheet is enabled, data entry for Actual Hours on the Team tab is disabled.
Settings: Warning (default), No Display
Controls the display of information about an object on the Change History, Where Used, Affected Items, Manufacturers, BOM, or Pending Changes tables when the user doesn't have the Discovery privilege for the object. Possible settings are Warning (the default) and No Display.
If the Discovery Privilege property in the Database node is disabled, then so is this SmartRule.
|
Note: When this setting is changed, users must exit the Agile Java Client and log in again before the change takes effect. |
Settings: Warning (default), No Display
Controls the display of information about the Results table when the user does not have the Discovery privilege for an object in the table.
If the Discovery Privilege property in the Database node is disabled, so is this SmartRule.
|
Note: When this setting is changed, users must exit the Agile Java Client and log in again before the change takes effect. |
Settings: No Display with Warning (default), Display, Display with Just Description, Display with Just Part Num and Rev, No Display
Controls the display of information about an item in the BOM table when the user does not have the Discovery privilege for the item.
|
Note: When this setting is changed, users must exit the Agile Java Client and log in again before the change takes effect. |
Settings: Display (default), No Display
Controls the display of model structures that are created by objects of the Designs class.
Settings: Allow, Disallow, Warning (default)
Controls the use of duplicate find numbers when users add items to a BOM.
This SmartRule has been expanded to dictate whether or not the same find number can be used in a site-specific portion of a BOM as is used in the global portion of a BOM. It also dictates whether or not the same find number can be used within a site-specific portion of the BOM.
For example: If the Duplicate Find Numbers SmartRule is set to Disallow, then:
Find Number 1 cannot be used for Part 123 on the Milpitas BOM if Find Number 1 is used for Part 234 on the Global BOM.
Find Number 1 cannot be used for Part 123 on the Milpitas BOM if Find Number 1 is also used for Part 234 on the Milpitas BOM.
The same find number can be used in more than one site-specific portion of the BOM regardless of the Duplicate Find Numbers SmartRule setting.
For example: Find Number 1 could be used for Part 123 on the Singapore section of the BOM and Find Number 1 could be used for Part 234 on the Milpitas section of the BOM. The setting of the Duplicate Find Numbers SmartRule does not affect this behavior.
If the Duplicate Find Numbers SmartRule is set to Allow, any item can have the same find number as another item regardless of what site section of the BOM they are on.
Settings: Allow, Disallow, Warning (default)
Controls the use of duplicate item numbers when a user adds items to a BOM.
Settings: Allow, Disallow, Warning (default)
Controls whether duplicate reference designators can be used on a BOM. This SmartRule has been expanded to dictate whether or not the same reference designator can be used in a site-specific portion of a BOM as is used in the global portion of a BOM. It also dictates whether or not the same reference designator can be used within a site-specific portion of the BOM.
For example: If the Duplicate Ref Des SmartRule is set to Disallow, then:
Reference Designator 1 cannot be used for Part 123 on the Milpitas BOM if Reference Designator 1 is used for Part 234 on the Global BOM.
Reference Designator 1 cannot be used for Part 123 on the Milpitas BOM if Reference Designator 1 is also used for Part 234 on the Milpitas BOM.
The same reference designator can be used in more than one site-specific portion of the BOM regardless of the Duplicate Ref Des SmartRule setting.
For example: Reference Designator 1 could be used for Part 123 on the Singapore section of the BOM and Reference Designator 1 could be used for Part 234 on the Milpitas section of the BOM. The setting of the Duplicate Ref Des SmartRule does not affect this behavior.
If the Duplicate Ref Des SmartRule is set to Allow, any item can have the same reference designator as another item regardless of what site section of the BOM they are on.
Settings: Allow, Disallow, Warning (default)
Controls whether a new rev can be released with an effective date that is earlier than one or more old revisions. This SmartRule also applies to the effectivity dates for site-specific items on the Affected Items table.
Settings: Allow, Disallow, Warning (default)
Controls gaps between the obsolete date of an existing part and the effective date of its replacement part on affected items. This SmartRule also applies to the effectivity dates for site-specific items on the Affected Items table.
Settings: Allow, Disallow, Warning (default)
Controls overlaps in the effective dates of an existing part and the obsolete date of its replacement parts on an affected item. This SmartRule also applies to the effectivity dates for site-specific items on the Affected Items table.
Settings: Allow, Disallow (default)
Controls ability to add new data from PPM Activities or Gates to completed (Released) Activities.
Settings: Disallow (default), Allow
Controls whether comments can be recorded while performing Delete, Archive, or Delegate actions in Product Portfolio Management.
Settings: Yes (default), No
This rule applies only to customers that have both the PCM and PG&C solutions. Otherwise, you can ignore it.
The rule controls whether legacy Part Family objects (in PG&C solution) and new Commodity objects (in PCM solution) are to be treated by the system as Commodity objects that are shared by both solutions. The default is Yes.
To treat Part Families and Commodities differently, set the rule to No. However, you must also configure the Commodities class to make the rule effective. For more information, see "Part Groups: Configuring Part Families" in Appendix A of Product Governance & Compliance User Guide.
Settings: Allow, Disallow, Warning (default)
Controls whether an item can be released when the item's BOM contains unreleased items. This SmartRule is pertinent to multiple sites: when a "parent" item is released, the rule checks the BOM components for site association and whether the BOM components are also released for that particular site.
Settings: Allow, Disallow (default), Warning
Allows or limits the association of items (parts or documents) with PSRs (problem reports or NCRs).
Settings: Allow, Disallow (default), Warning
Allows or limits the association of QCRs (CAPAs or audits) with PSRs (problem reports or NCRs).
Settings: Allow, Disallow, Warning (default)
Controls whether a manufacturer part can have multiple item parents.
If set to Disallow or Warning (the default), the system checks items as the change order's Workflow performs a Release Audit. This function has been enhanced; for more information, see "Release Audit, or Audit Current Status for Conditions to Release."
Settings: Allow, Disallow (default), Warning
Controls the entering of "negative prices" in the Material Price Adder attribute.
Settings: Allow, Disallow (default), Warning
Controls the entering of "negative prices" in the Material Price fields.
Settings: Allow, Disallow (default), Warning
Controls the entering of "negative prices" in Non-Material Price fields.
Settings: Allow (default), Disallow
Controls the sending of notifications to resource pool owners for programs in Proposed state.
Settings: Allow (Default), Disallow, Warning
Object Edit Conflicts SmartRule controls what happens when more than one person is editing an object at the same time. When the first user saves his edits, the object is updated. This smartrule answers the question: What happens when the second user attempts to save his updates?
Editing fields on the Title Block (Page 1, Page Two, or Page Three), and to editing cells in tables:
Allow: The second object save overwrites and previous conflicting changes without any error message.
History for the object records the changes made by the second user as well the changes made by the first user.
Preliminary items without a revision do not record Title Block modifications in the history records.
Routable objects that are Pending or Unassigned do not record Cover Page modifications in history. Routable objects in Submitted, Review, or Released statuses record Cover Page modifications in history.
Disallow: The second user's Save button is disabled and an error message within the page tells the user what he must do to recover his edits: "This object has been modified by another user. Copy and save your edits so you can reapply them. Select 'Cancel' to cancel your changes and refresh the object."
For the second user, the Save button is disabled and the page is no longer in edit mode.
Agile PLM displays an error message to the second user stating that the object has been modified by another user. The second user is instructed to save his edits so he can reapply.
On the object, the second user has only a Cancel button active. Clicking Cancel refreshes the page and the second user must reapply his edits.
Warning: Allows the second user to save his changes, but warns him that he will overwrite the previous changes made by another user: "This object has been modified by another user. Saving your changes will overwrite previous changes. Select 'OK' to save your changes or select 'Cancel' to cancel your changes."
Agile PLM displays a warning that saving edits may overwrite edits made by another user. The user is prompted to respond:
OK – The second user's edits overwrite any previous changes. History records both the first user's edits and the second user's edits.
Cancel – The focus returns to the object page. Clicking Cancel on the object page refreshes the page and the second user must reapply his edits.
For tables, this SmartRule applies to editing attributes within a table, but does not apply when adding or removing table rows.
The Object Edit Conflicts SmartRule does not apply to Agile PPM.
Settings: Allow, Disallow (default), Warning
Controls overlapping effectivity periods of price lines on price objects and PCOs.
Settings: Allow, Disallow (default), Warning
Controls whether a PSR can be associated with both affected items and related PSRs (Allow), or only affected items or related PSRs (Disallow).
|
Note: There is no business logic between items on the Affected Items tab and items on the Related PSR tab (that is, an item listed on Related PSR will not be copied to the Affected Items of the parent PSR).There is business logic between PSRs and QCRs, so if a PSR is associated with a QCR, items from both the PSR's Affected Items tab and its Related PSR tab will automatically populate the QCR's Affected Items tab. |
Settings: Allow, Disallow (default)
Controls the display in Web Client of Redline Title Block tab for Change Orders and Manufacturer Orders.
Settings: Allow (default), Disallow
Controls whether users are allowed to redline the Manufacturers tab from an ECO. If the setting is Disallow, all buttons in the Redline Manufacturer table are disabled. Possible settings are Allow (the default) or Disallow.
Settings: No Display (default), Warning
Controls whether a QCR can be released either manually or through auto-promotion even though all items on the Affected Items tab have not been associated with a Change.
If you set it to No Display, the SmartRule permits a QCR to be released even though all its affected items do not have an associated Change. Such a QCR will also pass a release audit without a warning.
If you set it to Warning, the SmartRule warns users that a QCR is being released even though all its affected items do not have an associated Change.
Settings: Allow, Disallow, Warning (default)
Controls whether a routable object can be unreleased if has an affected item that is on the BOM of a released assembly.
Settings: Allow, Disallow, Warning (default)
Controls whether change orders can be unreleased.
Settings: Allow, Disallow, Warning (default)
Controls whether change requests can be unreleased.
Settings: Allow, Disallow, Warning (default)
Controls whether deviations can be unreleased.
Settings: Allow, Disallow, Warning (default)
Controls whether manufacturer orders can be unreleased.
Settings: Allow, Disallow, Warning (default)
Controls whether QCRs can be unreleased.
Settings: Allow, Disallow, Warning (default)
Controls whether stop ships can be unreleased.
Settings: Allow, Disallow (default), Warning
|
Note: None of the choices result in the workflow being altered. |
A user may modify an attribute by giving it a value that does not match the workflow's matching criteria. This SmartRule governs whether the system accepts the changed attribute.
When modifying an Item, the server validates the workflow entry matching criteria of those Changes, PSRs or QCRs that have a workflow associated with them, and the workflow is not in the Completed or the Canceled status type.
If this SmartRule is set to Warning or Disallow, any attempt to modify attributes of the routable object that are specified in the workflow's matching criteria results in an immediate warning or prevention of the modification. However, if the workflow's matching criteria includes a reusable criteria that specifies an item's attribute, the user will be allowed to modify the value of that item attribute to a value that does not match the reusable criteria. No warning will be given. If, after that item attribute has been modified, the user then modifies the routable object in any way, the user is warned that the routable object no longer matches the workflow's matching criteria. This workflow entry check is bypassed for changes which have reached their Canceled or Completed status types.
Settings: Allow, Disallow, Warning (default)
Controls the use of "0" as a value for the Material Price field.
