Hide Sub-types from document selection list in one context

[LG_10096154]

There is something wrong with this Post a Question, it just loops around and around. So this is not a "question"

We have many sub-types of wtDocument. They are all available in all contexts.

What I would like to do is only display the sub-types of documents that each context should use.

So, can't make them non-Instantiable as that is at the Org level.

I can add in a deny on the ACL at the context but that's a crude method. 

I have been able to use a "disable" in the OIR that removes an option but it only works at the Org level and not at the context (unless I'm doing something wrong).

<AttrValue id="lifeCycle.id" algorithm="com.ptc.core.foundation.lifecycle.server.impl.LifeCycleTemplateAttributeAlgorithm">
<Arg>Disabled</Arg

[joe_morton]

There are different ways to achieve this, and different Windchill admins will probably disagree with me, or have other methods I don't know of.

My preferred way to manage this is by context Roles. Document type X can be created by Role 1. The only way users would see that option is if they are in Role 1. Any context that doesn't need Document type X doesn't have any users in Role 1. 

Another way to manage this that I've seen, but don't really like, is by life cycle template. If your OIR for document Y is at Org level and requires life cycle template 2, you can store that life cycle template 2 in just the contexts where you want document Y to appear. The document won't appear anywhere else because other contexts don't have access to the required life cycle template. This works OK if you have a document that is specific to just 1 context. If the document is needed in multiple contexts, it would become confusing and difficult to maintain because you're essentially copying the life cycle template to each additional context.

Another method I've seen is adding a "bad OIR" in the contexts where you want block creation. You can put any invalid info here. Call a life cycle template that doesn't exist, for example. That will effectively block the creation of the document type in that particular context. In this scenario, you're copying that "bad OIR" to every context where you want to block creation.

[LG_10096154 · Accepted solution]

Using an ACL does not remove the option, it just gives a warning message to context the systems admin.

I did use a local "bad" OIR that has a named lifecycle that does not exists. That removed it from the selection for that context.

<!-- set the lifecycle -->

<AttrValue id="lifeCycle.id" algorithm="com.ptc.core.foundation.lifecycle.server.impl.LifeCycleTemplateAttributeAlgorithm">

<Arg>nope</Arg>

</AttrValue>

</AttributeValues>

[Catalina]

Hi @LG_10096154 ,

I wanted to see if you got the help you needed.

If so, please mark the appropriate reply as the Accepted Solution or please feel free to detail in a reply what has helped you and mark it as the Accepted Solution. It will help other members who may have the same question.

Of course, if you have more to share on your issue, please pursue the conversation.

Thanks,

[pwilliams-3]

The way I have architected the solution at Steelcase is purely by ACLs.  The OIR and Life Cycle are defined at the Org level and the ACLs that allow creation exist at the Product or Context level for specific roles.