blackhawk - Monday, March 11, 2013 7:40 AM:
I am working on a team based permissions scheme where team members only can discover CAD Documents that belong to teams, where they are members.
I have added a field in the "new CAD Document" Form where the creator can assign a team. A new Permission has been created which now is default for the CAD ItemType. It includes Team Member, Manager and Guest. Can add is currently set to world.
When I log on as a testuser and create a new CAD Document this works fine. But I cant see CAD Documents created by other members of the same team. When I use the AML Studio to retrieve CAD Documents the permission id is still pointing to the old "New CAD" which was the standard permission instead of the one I set a default.
<permission_id keyed_name="New CAD" type="Permission">EA3ED7E7391542D7A17AF2F42B5274ED</permission_id>
Can anyone help on this issue?
Thanks
Eric Domke - Tuesday, April 2, 2013 9:10 PM:
Simply changing the default permission of an item type does not update existing records in the database. You will want to update all existing records in the database (perhaps with a SQL update statement or AML) to point to the new permission. This is something I always forget when changing permissions and run into similar issues.
blackhawk - Thursday, April 4, 2013 8:27 AM:
Thanks for your answer, but this does not seem to be the problem.
Once the ItemType has been changed, new Instances should behave according to the changes made to the ItemType. But somehow they don't.
Originally the ItemType CAD had the default permission "New CAD". I created a new Permission lets say "My new CAD" and set it as default. The original one was removed from the permissions tab. When I create new CAD Instances now, I expect them to have the "My new CAD" Permission. But according to the AML response they point to the original "New CAD".
zahar - Thursday, April 4, 2013 8:43 AM:
Marcel,
Check if you have Lifecycle Map for this ItemType. If so check that there is no specific permission on lifecycle stages
blackhawk - Thursday, April 4, 2013 8:57 AM:
Problem solved. Thank you!
