≡ Menu

How to create a Teamcenter Pseudo Folder

Pseudo-folder Icon (collapsed)
Share the knowledge

Recently someone asked me how to create a Pseudo Folder in Teamcenter. Well, that’s sort of what happened. Actually, I noticed in the logs that someone found this blog after Googling “create pseudo folder in tcua,” and I thought, hey! that’d make a good topic for a post! It fits in with the overall theme of, “things I didn’t understand when I started using Teamcenter.” And yes, this is what is known as, “playing to your audience.”

Anyways, the answer to the question, “how do I create a Pseudo-Folder in Teamcenter” is: “you don’t”. Next question?

Okay, okay, fine. I guess I’ll explain…

What is a Pseudo-Folder, anyway?

Pseudo-folder Icon (expanded)You see, the reason you can’t make pseudo-folders is because they’re not really folders at all; they’re fake folders. What they really are is just a convenient way to view a group of objects which all share a common relationship to some other object. So instead, what you really want to know is how to show pseudo-folders.

You’ll only see pseudo-folders underneath some other, parent, object, and the name of the pseudo-folder will be the name of some sort of relation. The contents of the pseudo-folder will be all of the objects that are the children of that relationship for the parent item. Finally, pseudo-folders are created and populated dynamically, at run-time. They themselves are not persistent in the database (the relationship they represent is persistent, however).

How to show a Pseudo-Folder under Items and Item Revisions

  1. Open the Rich Client (AKA, Portal)
  2. Edit → Options: General/Item (or Item Revision)
  3. On the General Tab: Select the item type in the box labeled Select Item type
  4. From the Available Relations column select the relation(s) you want to show as a psuedo-folder and move it to the Shown Relationscolumn if it isn’t already there.
    • If you stop here, then the related objects will simply appear underneath the parent item without being grouped in a pseudo-folder.
    • If you omit this step, then the next step will have no effect.
  5. Do the same thing on the Related Objectstab.
    • This is the step that shows the related objects in a pseudo-folder.

How to show a Pseudo-Folder under other types of objects

  1. Open the Rich Client (AKA, Portal)
  2. Open the User Preferences dialog.
    • Edit → Options: [Index] or [Search]
  3. Create or edit a preference named <type_name>_DefaultChildProperties.
    • Example: UGMASTER_DefaultChildProperties.
  4. Add to the values for this preference the relationship types you want to see underneath the parent item type.
    • This step corresponds to the the General tab settings in the steps for Items and Item Revisions. That user interface is basically giving you an automated way of doing this step.
    • Example:
      1. IMAN_UG_wave_geometry
      2. IMAN_UG_wave_part_link
      3. IMAN_UG_wave_position
      4. IMAN_UG_expression
      5. IMAN_UG_promotion
  5. Create or edit a preference named <type_name>_PseudoFolder
    • Example:UGMASTER_PseudoFolder
  6. Add to the values for this preference the same values you added to the _DefaultChildPropertiespreference.
    • This step corresponds to the settings on the Related Objects tab used for adding pseudo-folders to Items and Item Revisions.

If you followed along with the example what you should now see is five pseudo-folders underneath every UGMASTER dataset. These folders are populated with datasets with which the parent dataset has the indicated type of inter-part relation.

A few notes

  1. If you simply show the relationship without setting up pseudo-folders then nothing is shown beneath the parent item if there are no objects with that relationship. However, if you use pseudo-folders then the pseudo-folder is always shown, even if it is empty — you see this a lot with the standard view pseudo-folder under item revisions.
  2. As of TC 8 you can only show pseudo-folders for relationships which are configured as properties of the object type in the data model. This appears to be a new restriction which was not in Teamcenter Engineering. Reference: PR-02151780:

    The PseudoFolder is displayed only for relations that are set as properties for BusinessObjects. The customer needs to add IMAN_based_on Relation as property for Item and deploy the changes to the database and then set the preferences as required.

    Step 1) open Item in BMIDE

    Step 2) Add a new relation in properties tab

    Step 3) add IMAN_based_on relation

    Step 4) save the datamodel and Deploy the template to the database.

    Now you can see the IMAN_based_on pseudofolder

  3. In some circumstances you can create a relationship between two objects by pasting one object into another object’s pseudo-folder. For example, you can do this with the a Part Revision’s Represented By pseudo-folder.
  • https://twitter.com/Skinning_Door Prashant Shrivastava

    a very informative piece of info.. thanks a lot

  • Ramesh

    informative one

  • Future Teamcenter SME

    Your are rocking scott…continue posting useful info about TC UA….I from Teamcenter Enterprise background and now started my personal transition towards unified and your blog plays an pivotal role in my transition .

  • Siddharth

    Thank you Scott! Taking this topic further, is it possible to access related objects (secondary_object) through a compound property on a custom form? I’ve tried accessing all Identifiers associated through IMAN_aliasID and haven’t been successful yet. I am wondering if you could suggest possible correction in this syntax for compound property:

    — ItemRevision.IMAN_aliasid
    — IMAN_aliasid.secondary_object
    — Identifier.idfr_id


  • vdbriaan

    – Can one restrict access to the pseudo folder ?
    – Sometimes someone else (not the owner of the item that created it) needs to be able to add/modify contents to the pseudo folder.
    – Other group users must be able to see the folder or not OR they can see the folder but can not modify the contents. It that possible ?

    • Teamcenter Heretic

      Post action on the relation itself (a Pseudo folder is really only a relation)
      Also, maybe AM rule on the relation type?

      • suresh

        Hi, any one tried restricting access to pseudo folder?. can You please tell how to do this?.

    • Teamcenter Heretic

      Post action on the relation type. A pseudo-folder is just a representation of the relation.

    • suresh

      Hi, any one tried restricting access to pseudo folder?. can You please tell how to do this?.

      • Jeremie FEBURIE

        set GRM rules in Bmide …

  • Rahul Shendekar

    how to complete below :

    Psuedo Folder and Master Forms ?

  • Aaron Paluzzi

    Now here is the most important thing to me. How do you reverse the process? If I’m onsite at a customer and see a bunch of pseudofolders how do I find out what the name of the relationship backing them up is?

    Here are two use cases:

    1) You are designing a workflow. Part of the workflow is to take all objects in a particular pseudofolder attached to the workflow target and add them as additional targets of the workflow.

    2) You need to design a query that targets only objects that have objects in that pseudofolder.

    The problem in both cases is that you require the database name of the relation. Not just the display name. So “Specification” won’t work. You need “IMAN_specification”. The problem with pseudofolders is that you could very well have a folder named “Related Parts” that is representative of “IMAN_specification”. Most times no one ever thinks to keep this knowledge so asking the system admin results in a blank look, and there is no indication using “Right Click” / “View Properties” on a pseudofolder.

Optimization WordPress Plugins & Solutions by W3 EDGE