Independent Windchill Object

[Sha11]

Hello,

I have a requirement where users want to create an object in Windchill which will have its own set of attributes, life cycle, workflow and role based access. I was thinking that I can introduce a soft type for WTPart or WTDocument, but since there are already many reports and code which uses WTPart and WTDocument object instance in my system, I am hesitant to introduce the object as a subtype of WTPart or WTDoc.

Requesting you to provide any alternative type that I can make use of for this object.

Thanks,

Hari

[avillanueva]

What does the object represent? Does it store content?

[Sha11]

It represents a Process Change Request, but we do not have any process plans on our system. All the attributes will be manually populated by the users, and the object must go through some workflow tasks to be Approved or Canceled.

[HelesicPetr]

Hi @Sha11 

If the object should represents some change workflow, I would advice to use Change Request or Review Request object or Problem report type.

.

Create own subtype of object, set own attributes and set own new workflow as you need. 

You can also set rules that users can create just one specific subtype of change/review request if you do not use ootb change processes  

As I heard in the past from someone: Play with your Idea and Windchill

This way you separate the creation of WTDocument WTPart and your object.

PetrH

[Sha11]

Hello @HelesicPetr ,

Thank you for your response, I did not want to go with CR/CN objects since it provide association capabilities like affected items, resulting items. Since this object is going to be independent and no object is going to get attached, I was not leaning on CR/CN objects.