Relative Folder Path OIR

[pwilliams-3]

Hi Everyone,
I'm trying to devise the product container folder structure to begin to manage various soft types of WTDocument. At this time I have first level folders with domains to control ACLs. These first level folders align to different functional areas in the company. Each functional area will be creating different or the same types of documents but each functional area should not have access to the other's documents.

Currently my thought is to have a Documents folder for each functional area.

Root
|-Functional Area 1
|-Documents
|-Functional Area 2
|-Documents
|-Functional Area 3
|-Documents

So on to my question... Is it possible in an OIR to give a relative path to force the destination? For example if I wanted the "Specification" document soft type to be able to be created in /Root/Functional Area 1/Documents and in /Root/Functional Area 2/Documents.

What are other companies doing to structure their Product containers to store and organize documents?

Patrick Williams | Engineering Systems | c: 616.947.2110
[cid:image002.jpg@01CE0F44.6DA55E70]

[Rajesh_A]

I also got similar requirement. Is there anyway the folder info can be managed in OIR.

I tried with putting Folder Path in Folder.id arg, but not worked.

[ddemay]

You can do this with custom java code algorithm but need to know how to use
FolderHelper API and /or QuerySpec. This code is called BEFORE the user
interface is rendered however. A listener, queue, workflow, or other
monitoring capability via Ajax would have to change the folder if decision
criteria input is made after UI is rendered.



Hope that is clear.

[bwilcox]

In Reply to Patrick Williams:

Hi Everyone,
I'm trying to devise the product container folder structure to begin to manage various soft types of WTDocument. At this time I have first level folders with domains to control ACLs. These first level folders align to different functional areas in the company. Each functional area will be creating different or the same types of documents but each functional area should not have access to the other's documents.

Currently my thought is to have a Documents folder for each functional area.

Root
|-Functional Area 1
|-Documents
|-Functional Area 2
|-Documents
|-Functional Area 3
|-Documents

So on to my question... Is it possible in an OIR to give a relative path to force the destination? For example if I wanted the "Specification" document soft type to be able to be created in /Root/Functional Area 1/Documents and in /Root/Functional Area 2/Documents.

What are other companies doing to structure their Product containers to store and organize documents?

Patrick Williams | Engineering Systems | c:
[cid:image002.jpg@01CE0F44.6DA55E70]

You can specify default context folders using an OIR for the object. Below is an example that I used:

<attributevalues objtype="wt.doc.WTDocument|&lt;strong">cc.grantprideco.DNG_PR">

<attrvalue final="false" force="false" ignore="false" algorithm="com.ptc.core.foundation.folder.server.impl.FolderPathAttributeAlgorithm" id="folder.id">
<arg>/Default/FOLDERNAME</arg>
</attrvalue>
<attrconstraint final="false" force="false" ignore="false" algorithm="com.ptc.core.rule.server.impl.GatherAttributeConstraints" id="folder.id">
<value algorithm="com.ptc.core.rule.server.impl.GetServerPreGeneratedValue"> </value>
<value algorithm="com.ptc.core.rule.server.impl.GetImmutableConstraint"> </value>
</attrconstraint>

</attributevalues>

In the above code, just replace the cc.grantprideco.DNG_PR with your document soft type name and replacethe FOLDERNAME wording with the appropriate folder name that you want to use for the document type.

Benjamin Wilcox – IntelliServ^™

PPM & PDM Administrator

IntelliServ provides broadband networking and along-string
evaluation services for high-definition downhole and sub-surface operations > Get the Facts.

[AL_ANDERSON]

I don't understand your language when you say, "product container folder
structure" and "These first level folders align to different functional
areas in the company." It would help if you reword things using
Windchill's terminology.

I think you are saying that you have one Organization context in your
Windchill installation, and you are asking about "Project, Product, and
Library" contexts for each of your various business units and document
within your organization. These are the three types of basic contexts
available under the Organization level. Each of those constexts, in turn,
can have its own subfolder (a.k.a. "Folder") structure that can either
inherit the domain rules of its parent context, or have its own
folder-mapped domain or subdomain to differentiate access in one subfolder
from others. In most cases, for simplicity, you probably want to avoid
subfolder-specific domains and subdomains, although they certainly come in
handy when you need them.

Projects each get their own project context, so your real question seems
to be about Product and Library contexts. Your first question will be
"what's a Product and what's a Library?" In Windchill 10.1, the difference
seems to be largely semantic, but you will want to make some
company-policy to guide your own context creation. At our company, we
decided that "Product" contexts are for high-level product "standard"
structure objects and all of those high-level supporting CAD models. Most
of our ordinary parts and documents, however, are in "libraries."

Using access control you can limit who can create what light-types in what
context by Role within each context team. It is easy to limit one type of
document to only one library or product context. Within a particular
library or product context, where a user has "create" permission, an OIR
can set the subfolder within that library you want that object to get
created.

I hope that helps a little at least getting started so you can follow up
with more specific questions using the Windchill terminology.

Al








[solutions] - RE: Relative Folder Path OIR

Ben Wilcox
to:
solutions
07/11/2013 08:36 AM

Please respond to Ben Wilcox



Caterpillar: Confidential Green Retain Until: 08/10/2013





In Reply to Patrick Williams:
Hi Everyone,
I'm trying to devise the product container folder structure to begin to
manage various soft types of WTDocument. At this time I have first level
folders with domains to control ACLs. These first level folders align to
different functional areas in the company. Each functional area will be
creating different or the same types of documents but each functional area
should not have access to the other's documents.

Currently my thought is to have a Documents folder for each functional
area.

Root
|-Functional Area 1
|-Documents
|-Functional Area 2
|-Documents
|-Functional Area 3
|-Documents

So on to my question... Is it possible in an OIR to give a relative path
to force the destination? For example if I wanted the "Specification"
document soft type to be able to be created in /Root/Functional Area
1/Documents and in /Root/Functional Area 2/Documents.

What are other companies doing to structure their Product containers to
store and organize documents?

Patrick Williams | Engineering Systems | c: 616.947.2110
[cid:image002.jpg@01CE0F44.6DA55E70]


You can specify default context folders using an OIR for the object. Below
is an example that I used:

<attributevalues objtype="wt.doc.WTDocument|cc.grantprideco.DNG_PR">

<attrvalue final="false" force="false" ignore="false" <br="/>algorithm="com.ptc.core.foundation.folder.server.impl.FolderPathAttributeAlgorithm"
id="folder.id">
<arg>/Default/FOLDERNAME</arg>
</attrvalue>
<attrconstraint final="false" force="false" ignore="false" <br="/>algorithm="com.ptc.core.rule.server.impl.GatherAttributeConstraints"
id="folder.id">
<value <br="/>algorithm="com.ptc.core.rule.server.impl.GetServerPreGeneratedValue">
</value>
<value algorithm="com.ptc.core.rule.server.impl.GetImmutableConstraint">
</value>
</attrconstraint>
</attributevalues>

In the above code, just replace the cc.grantprideco.DNG_PR with your
document soft type name and replace the FOLDERNAME wording with the
appropriate folder name that you want to use for the document type.

Benjamin Wilcox ? IntelliServ?
PPM & PDM Administrator
IntelliServ provides broadband networking and along-string
evaluation services for high-definition downhole and sub-surface
operations > Get the Facts.

Site Links: View post online View mailing list online Send new post
via email Unsubscribe from this mailing list Manage your subscription

Use of this email content is governed by the terms of service at: