Skip to main content
C
ChiselnMallet11-Visitor
1-Visitor
May 20, 2020
Solved

Organization Level OIRs

  • May 20, 2020
  • 2 replies
  • 8263 views

I am trying to work backward from creating a new workflow for promotion requests... I want to make an additional lifecycle to select from.  I need to edit the OIR to allow a drop down for lifecycle selection. But... I just noticed that at the organization level.. I have both the site-OOTB and the slightly modified organization level OIR in the list.  My question is... how does windchill pick which OIR to use?

 

Thanks for any insight!

Best answer by MikeLockwood

Yes - very important.

The system first looks to OIR in the product/library. If not found, looks at Org level. If not found, looks at Site.

One can have complete OIRs at each level or only for example specify the lifecycle at a lower level.

 

Have to use the composite in order to combine them to verify in the OIR table.

2 replies

F
Florent_2743661-Visitor
1-Visitor
May 20, 2020

The system compiles all applicables OIRs from the Site to the context level and generates a "composite rule".

You should read the help center section: Understanding Object Initialization Rules (and sub-pages).

 

M
mmeadows-316-Pearl
16-Pearl
May 20, 2020

Best practice is to not touch the Site OIRs.  Site OIRs are a complete set defined by PTC.  Customers can override one or all of the Site level OIRs by defining customer specific OIRs at the Org (or lower levels as appropriate).

M
22-Sapphire I
MikeLockwood22-Sapphire I
22-Sapphire I
May 20, 2020

w/Matt - best practice.

Good to carefully document for any admin's involved to leave all at Site level alone and override at Org level.

 

An additional option is to create a Product or Library and have only the Manager Role in it, in order to test this sort of thing isolated from what users see (if you don't have a rehosted test environment).  In that test area, create Lifecycle, workflow template, Promotion mapping Preference, OIR, any needed ACL's in order to fully test.  Once proven, can export all, import at Org level.  Have to re-map preference which calls the workflow at Org level. Easy to get mixed up - helpful to have a block diagram.

M
22-Sapphire I
MikeLockwood22-Sapphire IAnswer
22-Sapphire I
May 20, 2020

Yes - very important.

The system first looks to OIR in the product/library. If not found, looks at Org level. If not found, looks at Site.

One can have complete OIRs at each level or only for example specify the lifecycle at a lower level.

 

Have to use the composite in order to combine them to verify in the OIR table.

C
ChiselnMallet11-VisitorAuthor
1-Visitor
May 20, 2020

Gotcha...  Making more sense now...  Also I don't see an ACL for promotion requests anywhere?  I had to make one for peer reviews... why is there no ACL?

M
mmeadows-316-Pearl
16-Pearl
May 20, 2020

Promotion Request ACLs are defined OOTB at the Product and Library level.  Companies regularly move all Product/Library ACLs to the Organization /Default/PDM domain to simplify and reduce their ACL caches and configuration burden, but it is extremely rare for a company to modify these ACLs.

 

What is the requirement for modifying the Promotion Request ACLs?

 

Terms & ConditionsAccessibility statement