| Agile Product Lifecycle Management CAD for Cloud Integration Guide Release 9.3.6.18 E99983-07 |
|
 Previous |
 Next |
| Agile Product Lifecycle Management CAD for Cloud Integration Guide Release 9.3.6.18 E99983-07 |
|
Previous |
Next |
CAD for Cloud functionality allows functional users in the CAD development process to coordinate and relate designs in Agile PLM to items in Product Development. This chapter must be read by the PLM administrator; and, it is addressed to users such as Engineering Coordinators and CAD Engineers.
In Agile PLM, the CAD for Cloud integration is supported primarily by the Publish Workspace tab that is available on a Design File Change Order (DFCO). As a CAD Design user, you can do the following from the Publish Workspace tab:
Relate and unrelate a design in Agile PLM to a PD Cloud Engineering item (PD item, or item).
Navigate from a design on Publish Workspace to its related PD item.
Relate and unrelate an Agile PLM DFCO to a PD Cloud ECO.
Navigate from a DFCO on Publish Workspace to its related PD Cloud ECO.
Validate and publish a design (or design structure) to Product Development.
These tasks are covered in more detail in the following sections.
Once the CAD for Cloud administration steps from the previous chapter are completed, the CAD for Cloud development process can be used to allow for an integration between Agile PLM and Product Development.
The following are some basic information about the Publish Workspace functionality:
Designs that are designated as HelperPart are not visible on the Publish Workspace. They cannot be directly related to a PD item and cannot be published using the Publish Workspace.
You can add generic and instance designs which are on the DFCO's affected files table to the Publish workspace. Once published to PD, Generic and Instance design components appear in the item's structure.
The buttons of search functionalities on the Publish Workspace tab are disabled for any DFCO that is already Implemented, Released, or Canceled.
If you select designs and click the Publish button, Publish Workspace displays the details of the Job ID and the Published By columns. When the ECO is related to the DFCO, clicking the Unrelate ECO button removes the data in the Job ID and Published By columns. Likewise, if the item is related to the design and you click the Unrelate Items button, the data in these columns are removed.
When you hover over the Job ID a Quick View widget appears, which upon clicking displays the publish job details. The details available in the widget are:
Job ID: The ID of the job you published.
Published By: Name of the person who published the job.
No. of design(s) being published: The number of designs you publish.
Submitted On; The Date and time you submitted the publish job.
Started On: The date and time you started the publish.
Updated On: The date and time you updated the publish.
Finished On: The date and time you finished the publish.
Job Status: The status of the publish job: Submitted, In Process, Completed, FailedCurrent Process Step: The status the publish is in: Completed, Not Started, Auto-relating Item, Validating, Adding PD ECO Relationship, Adding PD ECO Affected Items, Adding PD Item Attachments, Redlining PD Item Structure, Adding PD Item Relationship.
When you select and publish a row from Agile PLM to PD Cloud or relate a PD item to a design in the 'In Process' status, until the publish of the selected row is completed you cannot perform other functions such as unrelate item, unrelate ECO or validate, on it. An error message "Cannot relate item for the design(s) that is being published to PD Cloud. Please try again when publish is completed." appears in the information area of Publish Workspace tab.
You cannot perform Publish in the Publish Workspace if a PD ECO is not related to a DFCO. An error message, "Cannot publish without a related PD ECO. Please relate a PD ECO first and then try again." appears in the information area of the Publish Workspace tab.
When the design(s) you select is in the process of being published from Agile PLM to PD Cloud, and you click the Un-incorporate button in the Affected Files tab, an error messaage, "The selected design(s) cannot be un-incorporated because it is being published to PD Cloud. Selected design(s) that is not being published will be un-incorporated." appears in the information area of the Publish Workspace tab.
For each design row on the Publish Workspace, the following information is available:
Has been checked out - A check mark is shown if the design is currently checked out
Incorporated - A lock symbol is shown if the design is currently incorporated
Folder Number - The number of the design.
Folder Description - The description of the design.
Folder Version - The version number of the design.
Item Number - When the design is related to an item in PD, this field is filled with the Item Number that links to the item in PD.
Item Description - The item's description.
Item Lifecycle Phase - The lifecycle state of the item.
Item Revision - The current revision of the item.
ECO Number - When the DFCO is related to an ECO in PD, the ECO Number that links to the ECO in PD appears in this field.
Job ID - Displays the ID- the same Job ID for designs that have same publish job.
Published By - Displays the name of the person who adds designs to Publish job
Status - This field displays status information, including the current publish status of the design or auto-relate status.
Details - Provides error messaging during validation and publishing.
You can relate and publish a design in the CAD for Cloud system (that is, Agile PLM) to an engineering item in PD Cloud from a DFCO's Publish Workspace (PW). There are two ways to do this:
Manual relate by Search
Auto-relate by Publish (this function is an in-built subtask of Publish process)
Listed below are the rules for relating an Agile PLM design with a PD Cloud item:
A Design (Model/Drawing) can relate to only one PD item, across all pending DFCOs.
An item can relate to only one Model and to its corresponding Drawing, across all pending DFCOs.
A Drawing and its associated Model can relate to a single item.
If configured (auto-relate enabled), a Drawing auto-relates to the item that its Model is related to (a Model's Item Number is automatically applied to its Drawing when the Drawings exclusive Item Number is not available).
For the CAD for Cloud integration to work seamlessly, a Design must have a CAD-specific relationship with a PD Item and similarly a DFCO must have a CAD specific relationship with a PD ECO on Cloud. The CAD specific relationship implies:
Creating a Reference Object for a remote Cloud PD business object that it is relating to
Adding the above created Reference Object to the local object's Relationship table
Updating the text attribute of the above Relationship row with value 'CAD' which is configured by the property CadToCloud.LinkType.
|
Note: Default setting ’CadToCloud.LinkType=Text01' entry in CloudIntegration.properties can be customized with available text attribute on the Relationship tab only during the initial CAD for Cloud installation/integration. Once the system is in production, updating this property will break the functioning of the system. |
This image shows a Design (P00015.SLDPRT) Relationship tab before relate function:
This image shows the Design (P00015.SLDPRT) after the relate function - CAD specific Relationship.
A design engineer would create new designs and/or modify existing ones by incrementing versions as necessary, to meet the day to day design requirements of engineering modeling. Designs that are newly created require establishing a relationship with a PD item, while the pre-existing designs may already be related.
As part of their business process, design engineers would add newly created and/or modified designs onto a DFCO's Affected File table. On the DFCO's PW table, all those designs that are previously related appear with already related PD item in the corresponding design's Item Number column, while the newly created ones are left with blank columns.
Below is an image showing the PW tab on DFCO (DFCO00026) showing one design (P00015.SLDPRT) previously related to item (P00015) and another design (P00013.SLDPRT) not related.
You can either keep the existing relationship and continue with the publish process or change with different items, as required. In such a case, you have to unrelate the existing relationship first, then relate to a different item.
Support NX CAD File Types
As stated early, CAD to Cloud integration only allows one model (part or assembly) to be related to a PD Item. A PD Item can have a Drawing and a model related but not two models. This rule is dependent on being able to properly identify models and Drawings for each supported CAD system.
RUP16 provides the ability to switch the method used to identify Models and Drawings from the file extension to Design.p2.2010 (SubType).
Configuration changed in CloudIntegration.properties:# System Level configuration parameter - to use Design Subtype for Drawing# If this property is not set (or missing), it defaults to 'FALSE'. Its value can be one of TRUE/YES, FALSE/NO# Design will be considered to a Drawing if this is enabled and Design P2.TEXT04 has value of "Drawing"USE_DESIGN_SUBTYPE_FOR_DRAWING =
Open the DFCO that contains the design.
Go to the Publish Workspace tab.
Select the design part row to which you will relate a PD Item and then click Relate Item.
OR
Double-click in the empty cell of the Item Number column. The Search window appears.
|
Note: If the Design is already related to a PD Item, select the row, and click the Unrelate button. Once the Number cell is cleared, click again to bring up the Search window. |
Enter the Search criteria in the search field and press Enter. Only Engineering Items are returned in the result set. Only the current released revision for each Item is listed in the search results.
|
Note: The Search of an item is controlled by Opt In "Leverage consistent item search across Product Management" with Manage Administrator Profile Values [Code: ORA_EGP_ITEM_SEARCH_CHAR_LIMIT]The default search criteria is 3 characters when enabled. |
Double-click to select the PD Item. Once a selection is made, a link to the related Item appears on the Publish Workspace.
The Item Search window remains open even after selection. You can continue to add more Item-Design relationships, but you must select the Item Number cell on Publish Workspace first or Item selection will not work. Click the X, or press Esc, to close the Item Search window.
|
Note: The DFCO.PW.ItemRevision is blank until publish returns Completed Status. It is a new pending revision after adding/updating PD Item into PD ECO as Affected Item. |
To open the related Item in PD, click the link in the Item Number column on the Publish Workspace. The Item opens in PD to the current revision.
Once a Design object is successfully related to a PD Item, the relationship between the two objects is included on the Relationships tab of the Design object.
|
Note: The design object is added to the PD Item's relationships table only after publish is complete. |
As long as the user has the appropriate privileges, on the Design object's Relationships tab, the related PD Item's Item number, Description, and Current Status (Lifecycle Phase) fields are visible. The Link Type is updated to be CAD. Click the link in the Name column on the Publish Workspace to open the PD Item to the latest released revision. If the publish result is completed, the PD Item opens to the pending revision. If you open the PD Item from the Relationships tab it always opens the latest released revision of the related Item.
Once the DFCO is released, any relationships that were made between a Design and a PD Item remain in tact and are carried over into any subsequent DFCOs in which the Designs may be included.
Auto-relate by Publish
The CAD for Cloud system can perform Auto-relate for designs that need to be related to PD Items automatically, during the Publish process, as a sub-task.
To turn this feature on, you (here, the system administrator) must identify a suitable Design class' Page Two Text Attribute and use its 'API Name' to set the property 'DESIGN_ATTRIBUTE_FOR_PD_ITEM_NUMBER' in the CloudIntegration.properties file to store the PD Item number.
The DESIGN_ATTRIBUTE_FOR_PD_ITEM_NUMBER is set to TEXT01~TEXT25.
In general, customers upgrading from Agile PLM may already have configured a Page2 Text Attribute of Design class to store the 'Part Number'. You need to check if such an attribute is configured in the Java Client. If the configuration exists, use the API Name of that attribute. Otherwise, enable another text attribute on P2 and use its API Name.
The following is an example (you are free to choose other text attributes from TEXT01~TEXT25):
DESIGN_ATTRIBUTE_FOR_PD_ITEM_NUMBER = TEXT12
|
Note: This property can be configured/altered any time during production but requires a system re-start to make it effective. |
During the publish process, if the Auto-relate feature is enabled, the Designs selected for publish goes through the auto relate process in batches. The size of the batches depends on the value of the configurable property 'CLOUD_PD_BATCH_SIZE_FOR_BULK_API' in CloudIntegration.properties. By default, this value is set to 25. As an administrator, you can change or tune its value based on the performance of the system.
During the auto-relate process, the following steps are executed for each Design in a batch:
Checks whether the design is related to the item or not. If it is already related it excludes the Design from the process. If not, it considers the design for the auto-relate process;
Reads the value for item number from the configured P2 Text Attribute on Design;
If the Item Number is available on P2.Text attribute, the Design auto-relate process continues;
If the Item Number is not available on P2.Text attribute and the Design is a Model, the process reports error 'Needs Related Item' and excludes the Design from the auto-relate process;
If the Item Number is not available on P2.Text attribute and the Design is a Drawing, the auto-relate process further pursues for the Item Number through its associated Model - the Model's Item Number is automatically applied to its Drawing when its exclusive Item Number is not provided. When unable to determine the Item Number, reports error 'Needs Related Item' and excludes the Design from the auto-relate process;
Validates the Item Number for the following business rules. Reports corresponding error and excludes it from auto-relate if they are not met:
If the Design is a Model, the same Item Number is not related to any other Models except to its associated Drawing, across pending DFCO's;
If the Design is a Drawing, the same Item Number is not related to any other Drawings except to its associated Model, across pending DFCO's.
Once all conditions are met, the auto-relate process ascertains the Item Number for Design and checks if that number exists in PD Cloud through web services;
If the Item is not found, reports error 'Mapped PD Item for Design does not exist in Cloud system' and excludes the Design from the auto-relate process;
If the Item is found, the auto-related process creates the corresponding reference object to PD Item, relates it to the corresponding Design and updates LinkType with the value 'CAD'.
If the Design fails during any of the above auto-relate process steps, the system reports corresponding error in the 'Details' column and sets 'Status' column to 'Failed'. The failed Design is completely excluded from further processing of Publish sub-tasks.
During the publish process, if the Design is a Drawing that has not yet been related to PD Item, but it's associated Model is already related to an Item or set to auto-related, the system determines the Model's related Item Number as Drawing's Item Number to be related.
That is, the Model's Item Number automatically applies to its Drawing, if it is not provided with exclusive Item Number.
When unavailable or unable to determine, the system reports error 'Needs Related Item' and excludes such Drawings from the auto-relate process.
The CAD for Cloud system can automatically create PD Items that need to be related when they do not exist on Cloud during the Publish process as a subtask. The Auto-Create feature is designed as an internal function and is turned off, by default.
|
Note: The PD Cloud administrator must set the PD item UOM to "Each" to be able to auto-create PD item during publish from PLM to PD. Currently, this is the only supported UOM in CAD for Cloud's auto-create item function. |
The prerequisite configurations or setup to turn on the auto-create feature are:
Enable the Auto-relate feature so that the Item Number to be created and related is ascertained:
Configure 'DESIGN_ATTRIBUTE_FOR_PD_ITEM_NUMBER' property to source Item Number;
Enable system level Auto-Create feature by setting ’CLOUD_CREATE_PD_ITEM_SUPPORTED' property value to ’TRUE'. Out-of-the-box, its default value is set to ’FALSE'.
Configure PD Item class so that the created Item belongs to it:
Create a list of Engineering PD Item's sub class names;
Associate the above list to a suitable Page2 List attribute on Design class;
Configure API name of above attribute to the 'DESIGN_ATTRIBUTE_FOR_PD_ITEM_CLASS' property in 'CloudIntegration.properties' file. The Auto-Create feature is not enabled if this property is blank or set to an invalid attribute;
Configure 'Create' Yes/No selection switch so that you can opt in/out of creating an Item at each Design object level:
Create a list with entries 'Yes' and 'No', if such a list does not already exist;
Associate above list to a suitable List Attribute on Page2 tab of Design class;
Configure API name of the above attribute to the 'DESIGN_ATTRIBUTE_FOR_CREATE_PD_ITEM_FLAG' property in 'CloudIntegration.properties' file. The Auto-Create feature is not enabled if this property is blank or set to an invalid attribute.
Listed below are a few examples:
DESIGN_ATTRIBUTE_FOR_PD_ITEM_NUMBER =
DESIGN_ATTRIBUTE_FOR_PD_ITEM_CLASS =
DESIGN_ATTRIBUTE_FOR_CREATE_PD_ITEM_FLAG =
DESIGN_ATTRIBUTE_FOR_PD_ITEM_UOM =
|
Note: The above property settings can be altered any time during production, but require a system re-start to make it effective. |
During the publish process, if the Auto-Create feature is enabled, the Designs selected for publish goes through the auto create process in batches. The size of the batches depends on the value of the configurable property 'CLOUD_PD_BATCH_SIZE_FOR_BULK_API' in CloudIntegration.properties. By default, its value is set to 25 but you (as an administrator) can change/tune its value based on the performance of the system.
The Auto Create process does the following additional tasks within Auto-relate for each Design in batch:
If the Item search process does not find the Item Number and the create Item option is set to blank or 'No' on the corresponding Design, the auto-create process reports error 'Mapped PD Item for Design does not exist in Cloud system' and excludes the Design from the auto-create/relate process;
If the Item search process does not find the Item Number and the create Item option is set to ’Yes' on the corresponding Design, the auto-create process includes the Item Number for bulk creation though PD Item web services.
All the Items meant for creation will be processed in batches using the Item Service bulk API.
The auto-relate process will continue for the Designs corresponding to successfully created Items. The failed items will report error 'Failed to create PD Item Object on Cloud PD' and be excluded from the auto-relate and publish process.
|
Note: Auto-Create reports error ’Create PD Item failed due to Invalid PD Item Class Name' if the PD Item Class is set to ’Root Item Class' or is left blank. |
During Item class creation, the System administrator has to choose/configure a suitable Item Number generation method from the available methods, based on business requirement needs. Item Classes in Oracle Product Development Cloud allows you to configure the following types of Item Number generation methods:
Rule-Generated
Sequence-Generated
User-Defined
Product Management Rules are similar to pre-event tasks and they process attributes data and/or execute built-in or external functions including web services. When rules are configured and associated to an item class, they get executed during item object creation of such class. If a PD item class is configured to Rule-Generated, it takes Item Number from the associated Rule, which makes the system block direct input of Item Number through UI, Import, and Web Services. When Items of that class are created, value for the Item Number is read-only from Rule.
C4C Auto-Create feature supports only User-Defined and Rule Generated Item Number generation methods. So, Item classes meant for the purpose of auto-create from Designs should be configured to use only these two methods. Items created directly on PD system do not apply this restriction and they work well for Auto-relate or Search and Relate features.
You need an additional configuration or setup for a C4C integration instance, that allows you to create PD items from classes configured to use both User-Defined and Rule-Generated, or just Rule-Generated, Item Number generation method.
A C4C integration instance allows to create PD Items only from classes configured to use User-Defined Item Number generation method, no additional setup is required even though the remaining Item classes uses different Item Number generation methods.
A released DFCO in Agile PLM has a relationship with an ECO in PD Cloud, but the new DFCO does not carry the relationship with the ECO forward.
Design engineers can set, modify, correct, and propagate to PD Cloud the proper Unit of Measure (UOM) in their designs. This lets the CAD for Cloud publish process pull the selected value during item creation in PD Cloud.
The Agile administrator works with a new list called UOM Names, and a new property in CloudIntegration.properties called DESIGN_ATTRIBUTE_FOR_PD_ITEM_UOM. The administrator adds the value to the Page Two list being used for UOM in a design's attributes.
When setting DESIGN_ATTRIBUTE_FOR_PD_ITEM_UOM in CloudIntegration.properties, the administrator sets it to the API name of the list attribute as it appears in Java Client, for example, DESIGN_ATTRIBUTE_FOR_PD_ITEM_UOM=list20. The list values are added to the associated list for the list20 attribute.
A default value may be set in Java Client for commonly used UOMs. Design engineers can choose from the UOM list and set the value accordingly in each design.
The administrator wants to specify a Design Revision in Agile PLM to push to an Item Revision in PD Cloud. Herein, the word revision (or rev) is understood to be the revision of the item in PD Cloud; if that revision number was pushed to PD from a design in PLM, still, on the design side, it is always called design revision (or design rev).
So, more specifically, the administrator wants to specify the PD item's revision to be the same as the PLM design that is going to be published in PD using CAD for Cloud. To achieve this, a new property, PUSH_DESIGN_REVISION, is in the CloudIntegration.properties file.
If PUSH_DESIGN_REVISION is set to False, the existing behavior of the item - in this case, its revision - is copied to Design.Revision during Publish, whether or not the design's revision has been assigned a value.
If PUSH_DESIGN_REVISION is set to True, follow the table's first two rows below for proper configuration of pushing design revision to the item revision.
Table 3-1 Push Design Revision to Item Revision
| Push Design Revision | Design.Rev before publish | PD.Item new Rev after publish | Design.Rev after publish |
|---|---|---|---|
|
TRUE |
No value |
Keep item revision. |
Update from the PD item's revision on the change (new rev). |
|
TRUE |
Has a value |
Push design revision to Item revision. |
Keep design revision. |
|
FALSE |
No value |
Keep item revision. |
Update from the PD item's revision on the change (new rev). |
|
FALSE |
Has a value |
Keep item revision. |
Update from the PD item's revision on the change (new rev). |
Steps to configure Push design rev capability:
Open the configuration file CloudIntegration.properties to set PUSH_DESIGN_REVISION value to TRUE and save it back as below:
# Keep the existing Item.Revision behavior if the property is set to FALSE. Design.Revision reflects the Item.Revision after a successful publish.
# Push the value set in the Design Revision to the Item Revision if the attribute value is not blank, otherwise, the behavior is the same as setting this property to FALSE.
Restart the Agile Application Server.
Populate the values of the Revision attribute of those designs that are to be published.
Publish designs as usual in the DFCO PublishWorkspace.
If the publish operation fails, an error message appears in Publish Workspace Details column from PD Cloud.
|
Note: The design files are either uploaded to UCM or created as smart URL in the PD Item based on the properties values (PUBLISH_UPLOAD_FILETYPES and UBLISH_UPLOAD_MAX_FILESIZE) set by the administrator in the CloudIntegration.properties. The uploaded files are added to the PD Item's attachment table based on revision. This allows for fine grain control on the file types and file size for uploading to UCM. |
You can remove the relation between a Design that was previously related to an Item.
To unrelate a PLM Design from a PD item:
Open the DFCO that contains the Design.
Go to the Publish Workspace tab.
Select the row(s) of the Design(s) that you want to unrelate from a PD item(s).
Click the unrelate Item button.
If the selected row had a related PD Item, the relationship is removed and all Item-related and Status information is cleared from the Publish Workspace. If, however, the relationship between the Design and the Item exists for a released revision, the relationship will not be removed.
You can also unrelate an Item from a design that has been published to PD. When the relationship is removed, the PD Item's information is cleared from the Publish Workspace and the relationship is no longer listed on the Relationships tab of the Design. After the unrelate action, the Design is deleted from the PD Item's Relationships tab. This however, will not remove previously published Item attachments or Item structures.
You can relate a DFCO in Agile PLM to an ECO in PD Cloud from the Publish Workspace tab on a DFCO's Affected Files tab.
To relate a DFCO in Agile PLM to an ECO in PD Cloud:
Open the DFCO.
Go to the Publish Workspace tab.
Click the Relate ECO button. The Relate ECO Search window appears. The Relate ECO button is grayed out, if there is no row in the Publish Workspace tab.
In the Search window, enter the search criteria and click Enter.
Double-click to select a pending ECO. The Search window closes. The ECO and the DFCO are now related. The relationship is applied to the entire DFCO and its related Items. The ECO Number is automatically filled in for every Design row on the Publish Workspace window.
To open the related ECO in PD, click the link in the ECO Number column on the Publish Workspace. The ECO is opened in PD. After the ECO is related, and before publish, only the ECO is added onto the DFCO's Relationships tab. After publish, the DFCO is added into PD on the ECO's relationships table.
When the DFCO is Released or put on Hold, the relationships between the DFCO and ECO are maintained.
You can unrelate a DFCO in Agile to an ECO in PD from the Publish Workspace tab of a DFCO, only if the DFCO is related previously.
To unrelate a DFCO in Agile to an ECO in PD:
Open the DFCO.
Go to the Publish Workspace tab.
If the ECO is not related yet, click the Relate ECO button to relate it.
The Relate ECO button name changes to Unrelate ECO.
Click this button to unrelate the ECO.
You see that before Publish, when you relate a DFCO to an ECO in the Publish Workspace, the DFCO creates a relationship to the PD ECO. Click the Unrelate button to delete the existing Agile DFCO relationship.
After you relate a DFCO to a PD ECO and perform a Publish, both the Agile DFCO to PD ECO and the PD ECO to Agile DFCO relationships are created. BOM and Attachment redlines are also created. Clicking the Unrelate button deletes both the relationships. The unrelate function deletes only the relationships and not the BOM and Attachment redlines from the ECO.
If the DFCOs are in the Open, Draft, or Canceled status and you click the Unrelate ECO button, it will unrelate the ECO. If the ECO is released in PD, the error message: "ECO has been released and cannot be unrelated." appears in the information area of the Publish Workspace tab.
A design user can validate or check whether a design is ready to be published. To qualify for "Publish Ready" Status, a design must first have a related PD Item, a related pending ECO, and must be incorporated. If you fill in the Design P2 Text 12 attribute in PLM Web Client, you don't have to go to the publish workspace to search and relate the design to a PD item.
To validate a Design's publish readiness:
Open the DFCO.
Go to the Publish Workspace tab.
Select the row of the unpublished Design that you want to validate and click the Validate button.
Check the Details column for any corresponding error messages describing which criteria has not been met yet. If the design validates successfully, the Details column will contain the Publish Ready message.
|
Note: Configure the maximum number of change lines that are allowed in a change order is controlled by optin feature "Improve Change Order Data Loading with a Maximum Limit Setting for Affected Objects" with Manage Administrator Profile Values [Code:EGO_MAX_LINES_PER_CO] |
You can publish native files, 2D, and 3D files to an Engineering Item in PD from the Publish Workspace. A publish results in the following:
Design files are published to the PD Item's Attachments tab as a smart URL under the related pending PD ECO revision.
The Design structure is published to the PD Item's BOM tab under the related pending PD ECO's revision
The Design is added into the PD Item's Relationships tab under the related pending PD ECO's revision
The PD Item is added into the PD Change's Affected Item's tab, if it is not already an Affected Item.
Redlined BOM/Attachment tabs are updated.
The DFCO is added into the PD Change's Relationships tab.
|
Note: Restarting the application moves pending publish jobs to the Completed status. |
|
Note: The design engineer should not checkout or checkin the designs that are being published to Cloud PD. |
The current publish status of a design is available in the Status and Details columns for the affected design.
If a design has not been manually related to a PD Item using the Publish Workspace, but a valid PD Item number has been assigned through the Page Two attribute, the Design is auto-related during the publish process.
If a design drawing has not been manually related to a PD Item using the Publish Workspace or the Page Two attribute, auto relation is attempted. See "Auto-relating a Design Drawing during Publish" for more information.
When publishing a design to PD, if the related PD Item is already on the related ECO's Affected Items table, once the publish process successfully completes, the Item Revision is updated on the Publish Workspace. Otherwise, if the related PD Item is not already on the related ECO's Affected Items table, the PD Item is added to the ECO's Affected Items as part of the publishing process. The Item Revision is then updated on the Publish Workspace.
To publish a Design to PD:
Open the DFCO.
Go to the Publish Workspace tab.
You can publish one or multiple rows to PD. Select the row(s) of the unpublished Design(s) that you want to publish to PD and click the Publish button.
The Status column reflects the status of the attempt to Publish. The following are the possible publish status options in the Status column:
Blank - design has not been published yet
In-Process - design is in the process of being published
Failed - design failed to publish to PD
Completed - design has been successfully published to PD
If the design was successfully published to PD, the Status column for the row states Completed. If the Status column contains a Failed message, the Details column has a corresponding error message describing why the failure occurred. You can also see status on the Title Block tab of the Design object itself.
Once a design is successfully published to PD, to open the pending revision of the Item in PD, click the link in the Item Number column on the Publish Workspace tab.
If you check out a design after it is published or failed a publish attempt, the Status is reset and returns to being blank. The Status changes are reflected in the Affected Files table, as well as the Publish Workspace.
The Design Engineer can publish all the related affected designs in the Publish Workspace, or a subset of the related Affected Designs, to PD Cloud. For those designs that are In Process, selecting them and clicking on the Un-Relate Item, Validate, or Publish buttons will result in an Error message that the action cannot be completed while the design is being published. For selecting design that is not being published, Un-Relate Item, Validate or Publish could be performed correctly.
Clicking on the Un-Relate ECO button while any publish is in progress will result in an Error message, and the ECO will not be unrelated.
CAD structures can be successfully published, as well. During the publish process, if a selected Design row has a child component, and if the child has a related PD Item, the child is added as a structure member to the parent PD Item, which is related to the parent Design.
The PD Item structure attribute Source System is set as CAD to identify that this is a row controlled by CAD. The PD Item's structure attribute Quantity is also updated with the Quantity from the related child Designs.
For a structure that was originally created in PD, during a publish operation with a Quantity update, the Source field is set as CAD and CAD takes ownership of the published structure components.
This property, when configured with an eligible Design Page Two list, lets the Design Engineer decide whether the PD item BOM structure is updated when publishing the design. If the value is set to Yes, then the PD item BOM structure is updated with the information from the design. If the value is set to No, then only the design's attributes and attachments are updated in the PD item, and the BOM structure will not be modified.
The Engineering Coordinator needs to establish the guideline on when the PD Item BOM structure should be updated based on the company's business requirements and communicate the guideline to the CAD Engineers.
This lists all possible configuration behaviors of the selective publish function:
1. Publish BOMs for all designs (and design structures) when this property does not exist in CloudIntegration.properties file.2. Publish BOMs for all designs (and design structures) when this property exists in CloudIntegration.properties file but is left "blank" (List attribute no value). 3. Publish BOMs for all designs (and design structures) when this property is set to an invalid list or disabled list attribute.4. Publish BOMs for all designs (and design structures) when this property is set to a valid list attribute, but no entries in list (empty list entries)5. Publish BOMs for all designs (and design structures) when this property is set to a valid list attribute, with Yes and No as the value, but no default value set.6. Don't Publish BOM when this property is set to a valid List attribute having valid entries, but the administrator choose No or it is default to No.
7. Publish BOM when this property is set to a valid List attribute having valid entries, and the administrator choose Yes or it is default to Yes.
With PUBLISH_FILETYPES added to CloudIntegration.properties, the administrator defines the specific file types of design files - or None or All - that can be added to PD Items as "smart URLs" in the Publish action.
If the design's extension matches the file types listed in PUBLISH_FILETYPES, then a "smart URL" of the design is published to the PD item's Attachments tab.
If the Agile administrator has left the PUBLISH_FILETYPES property Blank, no files will be uploaded as "smart URLs" to PD Items.
If there is no PUBLISH_FILETYPES property in CloudIntegration.properties (either your version of CAD for Cloud precedes ver. 9.3.6.9, or your administrator has removed this property from the properties file), all types of design files are uploaded as "smart URLs" to PD Items.
User with Admin Privilege Can Cancel a C4C Publish Job
Prior to 9.3.6.14, if a C4C Publish Job became stuck "in process," the user had no way to clear the status and republish. 9.3.6.14 provides two ways to clear stuck C4C publish jobs.
Manual Cancel Publish Job
New Administrator applied to privilege added "Cancel Publish Job."
If a user has this new privilege, they will have access to new Cancel Job button in the Job Status pop-up window.
CLOUD_CAD_PUBLISH_THREAD_TIMEOUT
A new configuration parameter - CLOUD_CAD_PUBLISH_THREAD_TIMEOUT is introduced in CloudIntegration.properties file as following:
# Timeout (minutes) for CAD Publish thread since last updated, default 120 minutesCLOUD_CAD_PUBLISH_THREAD_TIMEOUT = 120
This timeout setting is not for the whole job but is for each publish step. For example, last updated time is recorded at the beginning of files uploaded to UCM and will be updated again when the upload is finished. A publish thread is considered to be stuck if there is no update for configured timeout. The Publish will be aborted and the Publish status will be to "Failed" in Publish Workspace with detailed message "C4C Publish is terminated due to being idle longer than the pre-configured time since last update (publish thread may be stuck)."
In the CAD for Cloud integration, you can use the DFCO's Actions > Save As menu option on a Released or Canceled DFCO to create a new DFCO. When using Save As on a Released or Canceled DFCO, its Designs, and their relationships to Items in PD are carried over to the new DFCO. Since a Released DFCO has Designs that are also related to ECOs, note that the relationships between the Designs and ECOs are not carried over to the new DFCO. The Save As option does not work on Pending DFCOs.
