Thanks a lot for your help.
BR.
White
Thanks a lot for your help.
BR.
White
Pushkar
Regarding this preference
"Workspace> Add to Workspace and Check Out> Check Out Collector>Include related Drawings"
When you select the model for checkout, the drawing is collected in the checkout table but is not by default marked for checkout. I personally don't know of way to change that, but would be happy to learn otherwise. When you right click an item in workspace and perform a checkout the check collector seems not to be invoked.
I would say the default collectors for add to workspace, checkout and checkin "help" to ensure latest drawing is stored with latest model but it does not enforce it. If I overlooked something please let me know.
We experience this issue a lot. It is an easy mistake to make, and can lead to drawing errors especially when you have different people working on model and drawing. Users are often confused why the drawing they retrieved in workspace using latest looks different to drawing published using as-stored. We have just implement a custom validator in the new promotion wizard to check for this. When promoting the drawing it checks if the latest drawing linked model version matches the as-stored drawing linked model version.
Regards
Darren
Dear Team,
I am trying to retrieve Resources from PlanActivity in Project link can any one please tell me the API name through which I can fetch it
Hi Jones,
I am using Windchill 10.2 M020, CreoView Adapters 3.0 M020 and Creo Parametric 3.0 M040. It's the main viewable.
Thanks,
Bhagirath
Hi Jim,
I am actually looking for both.
I wish to see if all the nodes were populated accordingly or not and then corresponding to that node in the tree do we have those layouts, attributes and its related constraints.
So this is what i want to do. As the tree might have lot many number of nodes, what can I be doing it ? How to automate the process ? Should I be developing a utility ? Can you please suggest me the same.
Thanks and Regards,
Aditya Achanta
I am able to burst a document and its images into ACM, creating the correct folder structure based on the xml. But when i check out a piece of that content and add an image, then check it back in, i am unable to get the root node of that content. The Root node contains the values i need to the folder structure, thus the image is being saved in a default place - 'No MetaData'. Here is the image path code form the burst config.
<locnhook sourcetype="graphic" type="acl"><![CDATA[function ln_burst::generate_graphic_path(oid)
{
local tagname = oid_name(oid);
local folder_name;
local arr[1];
local doc = oid_doc(oid);
# All elements get stored in the Library
folder_name = '/Libraries/Commentaries Work-Academic';
# get the publication title
# EX: Fundamentals of Financial Planning
if(defined($main::BURSTINFO[$doc.'.pub_folder'])) { folder_name = $main::BURSTINFO[$doc.'.pub_folder']; }
else
{
# the publication title is needed for folder name
local publication_name;
local publication_subject;
if(defined($main::BURSTINFO[$doc.'.publication_name'])) {
publication_name = $main::BURSTINFO[$doc.'.publication_name'];
publication_subject = $main::BURSTINFO[$doc.'.publication_subject'];
}
else {
if(oid_root()){
if(oid_attr(oid, "dc.title")){
publication_name = oid_attr(oid, "dc.title");
publication_subject = oid_attr(oid, "dc.subject");
}
}
else{
publication_name = 'No MetaData';
}
# store in global array
if(!defined($main::BURSTINFO[$doc.'.publication_name'])) {
$main::BURSTINFO[$doc.'.publication_name'] = $publication_name;
$main::BURSTINFO[$doc.'.publication_subject'] = $publication_subject;
}
}
folder_name .= '/' . $publication_subject;
# use first letter of name for alpha index folder
if($publication_name = "No MetaData"){
folder_name .= '/NM';
}
else{
folder_name .= '/' .substr($publication_name, 1, 1);
}
# append the publication title
folder_name .= '/' . $publication_name . '/';
}
# level, index and toc folders are done, else...
# assign folder for element
# Images
folder_name .= 'Images';
#local fid=open('D:\Source\XML\BurstDevLog.txt', "a+");
#put( fid, "folder name: $folder_name" );
#put( fid, "\n " . time_date() . "\n" );
#close(fid);
if(index(folder_name, '&')) {
gsub('\“', '"', $folder_name);
gsub('\”', '"', $folder_name);
gsub('\’', "'", $folder_name);
gsub('\‘', "'", $folder_name);
gsub('\&', "and", $folder_name);
}
# store in global array
if(!defined($main::BURSTINFO[$doc.'.pub_folder'])) {$main::BURSTINFO[$doc.'.pub_folder'] = folder_name;}
return folder_name;
}
dms::set_burst_hook_value(ln_burst::generate_graphic_path(dms::burst_hook_first_oid()));
]]></locnhook>
Hi Darren
You are right, when we select the model/assembly for checkout the drawing is collected but not marked for checkout, I was just testing with the parts/assemblies already in the workspace modified with the drawing before starting checkout
If drawing is already not modified in the workspace this setting does not work
Regrads,
Pushkar
Got it. I see installed fonts in Control Panel -> Appearance -> Fonts.
Do I need to make sure the font I am using in CAD Documents is installed on sever?
I guess this whole PART_NAME is legacy issue - maybe from Pro/Intralink days before my time? I will try the solution in which our standard title block will have &PTC_COMMON_NAME in the "Part Name" box instead of that designated &PART_NAME model parameter.
Still, I think one problem will remain:
Once the part is saved and uploaded to the server, its parameter PTC_COMMON_NAME is no longer editable (double-clicking a table cell that contains &PTC_COMMON_NAME results in the familiar prompt to "Enter value for PTC_COMMON_NAME", but entering a different value brings a rather unhelpful error message in the status bar "ERROR: Relation has an error. Please re-enter:") I am guessing that is actually because the PTC_COMMON_NAME parameter became locked by Windchill.
Anyway, I was not looking to back-drive the WC filename or WC Number - those need to be unique. But I don't see why, in principle, WC Name can't be changed from the Creo side.
In my opinion, what should happen is that PTC_COMMON_NAME remains editable; if it's changed, then upon check-in, Windchill renames the WC Name of the CAD object.
This is the good news just arrived from TS:
Some good news to provide at the moment. After some analysis and discussion, the R&D agreed to backport the fix to 10.2 M030.
For the moment the target is 10.2 M030 CPS20.
I will keep you informed in case there are any changes in the plan.
You can use Java Method in Query Builder to retrieve the values of Workflow Variables, You can implement a Java file as follows:https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS114482&art_lang=en&posno=3&q=java%20in%20query%20builder&sour…
Also, You can create a method to have two arguments and pass them as parameter in query builder which will retrieve the values and display that in the Report.
Let me know if you need more details i can send some snippets.
It would be great if we can get Report on Alias Attributes through Report Manager, We would reduce the use of Joins and further complexities in Reporting.
E.g If I have an Alias attribute to show all the Change Orders on a Change Request, I dont need to join multiple tables in Query Builder to do that, I should be able to add the Alias attribute from Query Builder and Get the result.
When upgrading to 10.0 from 10.2 M030, I have 2 questions.
.
Are there are negatives to upgrading on the same production server?
.
I have always seen where most upgrade to a separate server, for fear of conflicts with db, wc folders, vaults, etc.
.
What is the 1st accept MOR to upgrade to
.
I have always read where anything before M020 has too many bugs to upgrade to. If not M030.
.
Thanks
Larry Jett
Definitely safer to upgrade to a different server, leaving the source alone. But, many people have one good production server and much lower hardware for non-production and don't have the choice.
When using the same server, need to very strictly and carefully document paths, etc., and shut down HTTP Server and Windchill DS from one when addressing the other.
Advisable and relatively easy to practice this by installing on a test server, adding a small amount of data to it, and then proceeding. Completely safe this way to develop and document the procedure.
Abhishek,
in the community there is a group about Reporting I think you should join and where you can ask or wrote on query builder.
I wrote a document Resource for reporting with lots of report ready to use, collected from many sources and Mike it's one of the biggest contributors.
Abhishek,
I think that this is not a question/discussion but it seems more a request you have to do opening a new idea.
Thanks Mike.
.
What MOR would you wait till, before doing an upgrade. Would you upgrade to 11.0 M010, wait till M020, or all way till M030.
.
Larry
As Ben mentioned only Admin user can see files that are uploaded to Windchill but not yet checked in. Ask your Windchill System Admin to search for the object you are trying to upload.
What version of Windchill? If this is Windchill 11.0 M010, there is a High severity SPR open regarding this. See CS245684 and SPR 6131564 for details. There is a workaround in the CS document.
Are you checking in a new family table instance? If so, it's possible that you have a Number conflict.
Why: The Number of a newly created instance matches the Number of an instance already existing on the server.
Solution: When renaming or creating instances it is important to rename the "Name, File Name and Number".