Best Practice Recommendations
Encouraged Actions
Number Length Customization for Windchill WTPart
1. Create a folder structure at <Windchill_Home>\wtCustom\wt\part\ and create a new text file named partModel.properties.
2. In this properties file, enter the property WTPartMaster.number.UpperLimit, such as WTPartMaster.number.UpperLimit=450.
3. Create an InfoReport by running the script infoReport wt.part.WTPartMaster in a Windchill Shell.
4. Compile the class file from Windchill shell from <Windchill_Home> \bin - ant -f tools.xml custom_column -Dgen.input=wt.part.
5. Log in to the database with Windchill server username and password.
6. Run the command SQL > desc WTPartMaster. Check the value for character limit for WTPart. Default is VARCHAR2(40).
7. Drop the Index - Run command SQL > @<Windchill_Home> \db\sql\wnc\Foundation\wt\part\drop_WTPartMaster_Index.sql
8. Alter Table- Run commandSQL > alter table WTPartMaster modify wtpartnumber VARCHAR2(450);
9. Create the Index - Run commandSQL> @<Windchill_Home> \db\sql\wnc\Foundation\wt\part\create_WTPartMaster_Index.sql
10. Commit the action.
11. Restart the Windchill Method Server
Other Encouraged Actions
• There should be a product created in Windchill with the same name as that of the FORAN project, in order to authenticate from the FPLMServer to Windchill.
• Gateway Administrators and Publishers should be granted sufficient authorization to the Windchill repository connected to the FPLMServer.
• Import from FORAN to Windchill will carry forward the instance-based attribute and its values to the next iteration, and will not delete any instance based attribute. If you want to delete a instance-based attribute, it should only be done from the Windchill side.
• A link from a Configuration Item to Design Solution relationship that has been mastered in FORAN should not be altered in Windchill from any of the UI actions.
• Cancelling a running job is recommended only:
◦ when the job has been idle for a long time, or
◦ if there are jobs in the Pending state for a long time, or if the Windchill Method server is not showing any transactions for the running Job.
|
|
After cancelling a job, and Unlocking Sub-Assembly IP node in FORAN, the FPLMServer console will display the warning: “Sub-Assembly identified with FORANID: XXX.XXX will not be unlocked yet, as it is included in a publishing process still running. You should try unlocking later.” If this occurs, lock the affected Sub-Assembly again and complete the publish operation.
|
Discouraged Actions
PTC discourages the following actions in Windchill Gateway for FORAN:
• Renaming/renumbering of business-object type parts, which have been authored in FORAN from the Windchill side, should only be done from the FORAN side.
• Modifying of FORAN-authored structures from the Windchill side, such as adding the same business object in an assembly structure with a quantity more than one for the same node of a FORAN-authored assembly, is not recommended. This should only be done from the FORAN side.
• Modifying of FORAN-authored structures from the Windchill side, such as adding an existing FORAN-authored Assembly from Windchill to the FORAN authored assembly, is not recommended. This should only be done from the FORAN side.
• If you have a PDM ProjectLink solution installed, objects from FORAN integration are not supported for ProjectLink activities.
