39 Administering Design File Change Orders (DFCOs)

The Design File Change Order (DFCO) is a Change Order subclass with the Affected Files tab enabled. By enabling the Affected Files tab, the DFCO object can now be used to publish files with Agile PLM workflows, similar to the way ECOs are used to release item objects with Agile PLM workflows.

39.1 Basic Steps to Enable DFCOs

To enable the use of DFCOs, the following tasks must be performed:

1. In the Classes node, enable the DFCO subclass.

   See "Configuring Subclasses."

2. If needed, configure any additional DFCO-related tabs and attributes that you wish to use, for example:

   • Enable the Changes tab of the Designs object. Determine which Pending Changes table and Change History table attributes you want to use and ensure that those attributes are visible on the Changes tab. Ensure that the Read Designs privilege mask includes the appropriate Pending Changes and Change History attributes on the AppliedTo property Selected list. Refer to Table 39-1, "DFCO-related privilege masks" for more information.

   See "Configuring Tabs."

3. Determine which attributes will be visible in the Design object Version drop-down list and in the File Folder object Version drop-down list.

   
   

   Note: The Version drop-down lists of Design objects and File Folder objects are configured separately.

   
   

   The attributes that you can select for the Version drop-down list appear on the Title Block tab of Design class objects and on the Title Block tab of the File Folders class objects. See also "Defining Attribute Properties."

   To include the attribute in the Version drop-down list, set the attribute property Visible in Version Dropdown to Yes.

   • Version – The Version is always visible in the Version drop-down list, and is the first attribute displayed drop-down list. The remaining visible Version drop-down list attributes are displayed in the order that they appear on the Title Block.

   • Change Sequence

   • Published Change Order

   • Label

   • Revision

4. Confirm that the Release Change Order with Unincorporated Affected File Rows SmartRule is set as desired.

5. Enable the preconfigured DFCO roles and privileges, or create the privilege masks and roles that you require. You can use preconfigured roles and privileges as described in "DFCO Preconfigured Roles and Privileges."

   For detailed information about Agile PLM roles and privileges, see Chapter 16, "Roles" and Chapter 17, "Privileges and Privilege Masks."

6. Enable the preconfigured Default Design File Change Orders workflow. Or, create a custom DFCO workflow that meets your requirements.

   See Chapter 11, "Workflows."

7. Define any functional teams needed for DFCOs.

   See Chapter 41, "Administering Approval Matrix."

8. Assign DFCO-related roles to the appropriate users.

39.2 DFCO Preconfigured Roles and Privileges

When Agile PLM is installed or upgraded to release 9.3.5 or later, the following pre-defined roles relating to Design File Change Orders (DFCOs) are available.

• Design Change Analyst

• Design Engineer

Before assigning these roles to users, ensure that the roles and their privilege masks are properly enabled and configured by following these steps:

1. Ensure that all the privilege masks in the DFCO roles are enabled.

   1. Display the Design Change Analyst or Design Engineer role.

   2. Click the Privileges tab to display it.

   3. Click the Enabled column header to sort the privilege by Yes (enabled) and No (disabled).

   4. If any privilege masks are not enabled (No), double-click a privilege mask row to display the disabled privilege mask window.

   5. On the privilege mask General Info tab, select Yes in the Enabled drop-down list.

   6. Click Save and then close the privilege mask window.

   7. In the DFCO role window, click Refresh to update the Enabled fields on the Privileges table.

   8. Repeat step d through step g until all the privilege masks are enabled.

2. Ensure that the DFCO-related AppliedTo properties are selected as appropriate for each of these preconfigured DFCO-related privilege masks. Refer to the table below.

   Table 39-1 DFCO-related privilege masks

   Privilege mask	Selected DFCO-related Applied To properties
   Add to Table All Design File Changes	Select the appropriate Applied To properties: Changes.Affected Files.Affected Files Changes.Affected Files.Redline Markup
   Cancel Checkout All Design File Changes	Select the appropriate Applied To properties: Changes.Attachments Changes.Affected Files
   Checkin All Design File Changes	Changes.Attachments Changes.Affected Files
   Checkout All Design File Changes	Select the appropriate Applied To properties: Changes.Attachments Changes.Affected Files
   Checkout Designs by Folder Owner Only	Select the appropriate Applied To properties: Changes.Attachments Changes.Affected Files.Affected Files
   Delete From Table All Design File Changes	Select the appropriate Applied To properties: Changes.Affected Files.Affected Files Changes.Affected Files.Redline Markup
   GetFile All Design File Change	Select the appropriate Applied To properties: Changes.Affected Files.Affected Files Changes.Affected Files.Redline Markup
   ViewFile All Design File Changes	Select the appropriate Applied To properties: Changes.Affected Files.Affected Files Changes.Affected Files.Redline Markup
   Modify Design File Changes	Select the appropriate Applied To properties: Change Orders.Redline Markup.File Name Change Orders.Redline Markup.Markup Description Change Orders.Redline Markup.Markup Name Change Orders.Redline Markup.Markup Number
   Modify Designs	If necessary, select the attribute: Designs.Change History.Folder Version
   Read Designs	When you enable the Design object Changes tab, then add the appropriate Changes tab table attributes to the Read Designs privilege mask: Designs.Pending Changes.<attribute> Designs.Change History.<attribute>
   Read Designs I have Created	When you enable the Design object Changes tab, then add the appropriate Changes tab table attributes to the Read Designs I have Created privilege mask: Designs.Pending Changes.<attribute> Designs.Change History.<attribute>
   Read Design File Changes	If necessary, select the appropriate Affected Files table attributes and Redline Markup table attributes: Change Orders.Affected Files.<attribute> Change Orders.Redline Markup.<attribute>

   
   

   See "Modifying the AppliedTo Property."

   See also "Notes about Privilege Mask AppliedTo Properties Specific to Change Order Criteria."

3. Ensure that the roles are enabled.

   1. Display the Design Change Analyst role or the Design Engineer role.

   2. Select Yes in the Enabled drop-down list.

   3. Click Save.

39.2.1 Notes about Privilege Mask AppliedTo Properties Specific to Change Order Criteria

The following table lists privileges that display AppliedTo properties when the selected criteria for the privilege mask specifies the Change Order class or any Change Order subclasses, for example, ECO or DFCO.

For example, the preconfigured ViewFile Items privilege mask has no AppliedTo properties. The preconfigured ViewFile All Design File Changes privilege mask has three AppliedTo properties, as shown in the following table.

Table 39-2 DFCO-related privilege mask AppliedTo properties

Privileges	AppliedTo properties available when a Change Order criteria is specified in the privilege mask
Add to Table	DFCO-specific AppliedTo properties: Changes.Affected Files.Affected Files Changes Affected Files.Redline Markup are in addition to the existing Add to Table AppliedTo properties: Changes.Attachments and Changes.Releationships.
Cancel Checkout	Changes.Attachments Changes.Affected Files.Affected Files
Checkin	Changes.Attachments Changes.Affected Files.Affected Files
Checkout	Changes.Attachments Changes.Affected Files.Affected Files
Delete From Table	DFCO-specific AppliedTo properties: Changes.Affected Files.Affected Files Changes Affected Files.Redline Markup are added to the existing Delete from Table AppliedTo properties: Changes.Attachments and Changes.Releationships.
Getfile	Changes.Attachments Changes.Affected Files.Affected Files Changes.Affected Files.Redline Markup
ViewFile	Changes.Attachments Changes.Affected Files.Affected Files Changes.Affected Files.Redline Markup

39.2.2 Notes about Affected Files Attributes Modify Capabilities

The modification of all Affected Files attributes are controlled by Modify privilege masks applied to Affected Files attributes (Change Orders.Affected Files.attribute). For an example, see preconfigured DFCO privilege mask Modify Design File Changes.

39.2.3 Notes about Add File Folder to Affected Files Tab Capabilities

The capability to add file folders to the Affected Files table is controlled by the Add to Table privilege. See "DFCO Preconfigured Roles and Privileges," and "Add to Table and Delete from Table Privileges."

A user can also add file folders to the Affected Files table if he has Modify privileges applied to filename: Change Orders.Affected Files.Filename.

The following table describes the privileges that will allow a user to add or remove from the DFCO Affected Files table.

Table 39-3 Summary of privilege masks for Add and Remove from Affected Files table

Affected Files table actions (Add button and Remove button)	Action can be performed with Modify privilege	Action can be performed with Add To Table privilege	Action can be performed with Delete From Table privilege
Add > To Change Order	Yes	Yes	N/A
Add > To Selected File Folder	Yes	No	N/A
Remove > From Change Order	Yes	N/A	Yes
Remove > From Selected File Folder	Yes	N/A	No

39.2.4 Notes about DFCO Incorporate and Unincorporate Affected Files Capabilities

• Incorporate – The ability to incorporate affected files is determined by Modify privilege applied to:

  • File Folders.Title Block.Incoporated flag

    For an example, see preconfigurd DFCO privilege mask Modify File Folder

  • Changes Orders.Affected Files.Incorporated flag

    For an example, see preconfigured DFCO privilege mask Modify Design File Changes

  The ability to incorporate is not based on the folder owner.

  If two users try to incorporate at the same time, the first user to incorporate will do so successfully. The second user will see an error message that the file is already incorporated. The Object Edit Conflicts SmartRule does not apply to affected file incorporation.

• Unincorporate – The ability to unincoporate is determined by Modify privilege applied to:

  • File Folders.Title Block.Incoporated flag

    For an example, see preconfigurd DFCO privilege mask Modify File Folder

  • Changes Orders.Affected Files.Incorporated flag

    For an example, see preconfigured DFCO privilege mask Modify Design File Changes

  The ability to unincoporate is not based on the folder owner.

39.3 Workflow Special Rules for DFCOs

Because the Design objects that are published with DFCOs may originate in Agile Engineering Collaboration (EC), the following rules apply to the workflow process for DFCOs.

• A released (published) DFCO cannot be un-published.

  If a released change order has affected files, then an error message is displayed if the end user attempts to select a workflow status that precedes the released-type status in the workflow status list.

  Once a DFCO enters the released-type status (the Published status in the preconfigured DFCO workflow) or the complete-type status, it cannot be moved backwards in the workflow to a pre-release status.

• The DFCO cannot be cancelled after it is released (published) or implemented.

• When a DFCO is cancelled, the following rules apply:

  • If there are affected files on the cancelled change order, then the DFCO cannot be moved to another status, even if the workflow Manual Next Valid Status properties are set to allow it.

  • The Change Sequence number read-through field on the affected files table Design object Title Block tab is cleared.

  • The Design object versions that were created through the DFCO remain valid on the Design object, but any reldine/markup files that were created through the DFCO exist only on the cancelled DFCO.

  • The cancelled change order number and the associated Change Sequence number are not shown on the Design object Version drop-down list.

  • Files can be checked in and checked out from the Files tab of the File Folder or Design object after the DFCO is cancelled.

• The SmartRule Publish Change Order with Unincorporated Files determines whether the DFCO can be published with unincorporated files. See "Publish Change Order with Unincorporated Affected File Rows."

39.3.1 DFCO and Release Audit

See "Release Audit, or Audit Current Status for Conditions to Release."

Specific release audit checks for DFCOs are:

• Release audit checks for unreleased Design structure children.

• Release audit checks for unincorporated file folders according to the setting of the SmartRule Publish Change Order with Unincorporated Affected File Rows. See also "Publish Change Order with Unincorporated Affected File Rows."

• Release audit checks that affected file Design structure recursive components are included on the Affected Files table of the same DFCO.