Skip to main content
1-Visitor
December 28, 2011
Question

Defining Target Folder Check in

  • December 28, 2011
  • 3 replies
  • 7138 views

Has anyone successfully change the default target folder check in of objects on a user basis? Currently, all of the users are checking in objects into a main root folder set up in Windchill because that is the default check in location. The only way to avoid checking in object into the root folder, that I know of, is to have the user change the target folder location when they create a new workspace. I would like to set up the system so that when a user checks in objects it goes into their personalize folder within the system. I don't want the user to have to set the target location every time they create a new workspace.

3 replies

22-Sapphire I
December 29, 2011

By object type, you can specify what folder all new objects go into, using the SubFolders element of the OIR.

Store at root level (all are this way OTB):

<AttrValue id="folder.id"
algorithm="com.ptc.core.foundation.folder.server.impl.FolderPathAttributeAlgorithm">
<Arg>/Default</Arg>
</AttrValue>

Store one level down (need to create this folder):

<AttrValue id="folder.id"
algorithm="com.ptc.core.foundation.folder.server.impl.FolderPathAttributeAlgorithm">
<Arg>/Default/Other Folder</Arg>
</AttrValue>

If you create this at Site or Org level, then need to create the folder in every Product / Library where they need to be created.

13-Aquamarine
December 29, 2011

Hi Mike...

I've read your response and I see what you're proposing... but how would you set the folder by user? I think this technique successfully sets the default checkin folder to a subfolder under the default but without the ability to vary that "Other Folder" by the current users' ID, I think the same problem still exists. Then again, perhaps I'm missing something?

Thanks!

-Brian

1-Visitor
December 29, 2011

idk if this will work, but maybe you could extend FolderPathAttributeAlgorithm and override the calculate method?

if(args != null && args.length == 1 && args[0].equals("(somethingunique)")) {

return FolderHelper.service.getFolder(xxxxxxx, wtcontainerref);

} else {

return super.calculate(args,wtcontainerref);

}

B.Champ1-VisitorAuthor
1-Visitor
January 3, 2012

Sorry for the confusion but by personalized folder I meant project folder. Brian, you are on the right track. Currently our system is set up so that there is only one Product and under product there are project (context) folders setup. I know you can change the checkin location for the group as a whole but I want to vary the checkin for each user. I would like us to be able to manage our data better by project not by the user who created/modified it.

1-Visitor
January 4, 2012

Hi Bon

In our organisation(and in common practice)

We make individual product for each project

Define team and role for each product to give access to persons

Can you give a screenshot of your folder structure

Regards

K.Mahanta

13-Aquamarine
January 4, 2012

I think he's just got one monolithic structure with subfolders taking the traditional place of products. Hmm... a screenshot might help!

B.Champ1-VisitorAuthor
1-Visitor
January 4, 2012

Here is a screen shot.

untitled1.JPG

13-Aquamarine
January 4, 2012

Hi Bon...

Is it true that Nuvasive is your only product?

Thanks...

-Brian

B.Champ1-VisitorAuthor
1-Visitor
January 4, 2012

That is correct.