Not all contexts are displayed in Set Location during Move operation

[Pieter_Du_Toit]

Hi,

I would like to move WTParts to a different context and/or folder but when I try to select a different context location in the Move operation, only two of the several contexts display in the Set Location drop down.

With Policy Administration I have added Full Control for wcadmin on the Root domain for All Contexts but does not work. Still only the two contexts get displayed.

Where in the configuration am I missing something?

Please assist.

Thank you 

[JHall]

@Pieter_Du_Toit 

I think wcadmin might need to be added to Org Admins.  Also it may not be a member of those Context teams.  Just a couple easy things to check.

James

[Pieter_Du_Toit]

Hi,

Will do the checks and see what happens.

Regards

[Pieter_Du_Toit]

When I go to my Products list I see only two. They are the only products available for selection during Set Location for the Move Operation.

There is however a whole list of products that needs to show up during Set Location.

If I check correctly I should have have Full Control for the Concept JS product. What am I missing? Is there a reason for it not showing in my Products list and thus it is not available during Set Location?

Appreciate your assistance.

[DmitryC · Accepted solution]

Hi Pieter,

I think I know the reason for this behavior.

Having rights to a context and seeing it on the list are two different things.

Here is an example:

We do not use the wcadmin account directly, instead, we are using a bunch of named accounts for people who have site admin access, therefore wcadmin didn't open any contexts, except for the initial one. Currently, we have 4 products and 1 library, but they are not on the list:

If I will do an advanced search for the products - I will find them all, and I will have full access to them, and as soon as I will open them at least once - they will appear in the recent list, but not in the products list.

To add products to the list you will have to explicitly add users into the product team. Almost any role in a product will do the job, and we have dedicated groups/role just for ensuring visibility:

Give it a try and see if it helps.

Kind regards,

Dmitry.

[Pieter_Du_Toit]

Thank you for your assistance.

Added wcadmin as a member of the products and they are now available for selection.

[mmeadows-3]

An alternative solutions for those with lots of contexts...

Site Administrator accounts like wcadmin have full permissions to everything (WTObject).  However, they must search for anything below the Organization context level.

Create a saved search (e.g. 'Contexts') that includes Product/Library/Project/Program contexts.  The criteria needs to include all possible contexts (e.g. Organization = <org name> for single organization or Name != '*$*' or some other character that is never found in a context name).

Then search to access any new context.  Once accessed, it will appear in the recent contexts pane of the Navigator.

In this way, the Site Administrator does not need to be added to the context team of new contexts.

[Pieter_Du_Toit]

Thanks for the tip!

[DmitryC]

Hi Pieter,

Just remember that you have to have enough access in both the source and the destination contexts to move an object. This may fall apart quickly if any of the contexts are created as 'private', or if you have 'deny' permissions anywhere.

What I would do in your place:

1. Create parts in both contexts in the same state

2. Go into 'Edit Access Control' and hit the 'i' icon to see the full list of all policies that govern the access control to a given object.

3. Check that you are granted with appropriate access and nothing restricts it explicitly. 

Kind regards, 

Dmitry.

[Pieter_Du_Toit]

Thank you.

I will take the various steps and see if I am successful.

Regards