rif6894 - Tuesday, May 8, 2012 12:25 AM:
I have testing the creation of a new revision and wish to confirm whether the following is the correct behaviour.
1. Create a new Document, promote to Released. The permissions are automatically set to 'Released Document'
2. Lock the object and make a change or use the 'Create New Revision' icon in the Document form. A new revision is created.
3. By using the AML of <Item action='get' id='....' type='Document'>, the output shows that the <permission_id keyed_name = "Released Document' type="Permission">7432....</permission_id>
My assumption was that if a new revision was created, the New Document permissions would be used as the object is created at the initial state as defined within the Lifecycle and the Item's Type definition of the default state. Why is the 'Released Document' permision being carried forward to the new revision?
4. The work-around is to manually set the access ot the 'New Document' permission. Is this the correct approach?
thanks in advance
Brian - Tuesday, May 8, 2012 7:13 AM:
Hi rif,
The behaviour you are describing is not what I would expect to see.
I created a new document. Promoted it to Released using Manual Release. Created a new revision using Create New Revision and then retrieved all of the Document records in the system. This is what I get:
<Result>
<Item type="Document" typeId="B88C14B99EF449828C5D926E39EE8B89" id="F3C02881F28B434CBEC16769EFCD9C3D">
<generation>1</generation>
<id keyed_name="100004" type="Document">F3C02881F28B434CBEC16769EFCD9C3D</id>
<name>Testing permissions</name>
<permission_id keyed_name="New Document" type="Permission">F0E3A6D242FC4889A9A119EEBC8EC79E</permission_id>
<itemtype>B88C14B99EF449828C5D926E39EE8B89</itemtype>
</Item>
<Item type="Document" typeId="B88C14B99EF449828C5D926E39EE8B89" id="0042B5E92138499A963AF4F1D8CB5DDC">
<generation>2</generation>
<id keyed_name="100004" type="Document">0042B5E92138499A963AF4F1D8CB5DDC</id>
<name>Testing permissions</name>
<permission_id keyed_name="Released Document" type="Permission">74C205C37E7C4D56BBBE99B52B28431E</permission_id>
<itemtype>B88C14B99EF449828C5D926E39EE8B89</itemtype>
</Item>
<Item type="Document" typeId="B88C14B99EF449828C5D926E39EE8B89" id="DB4DBB403C3A4B9293131002ED600AA6">
<generation>3</generation>
<id keyed_name="100004" type="Document">DB4DBB403C3A4B9293131002ED600AA6</id>
<name>Testing permissions</name>
<permission_id keyed_name="New Document" type="Permission">F0E3A6D242FC4889A9A119EEBC8EC79E</permission_id>
<itemtype>B88C14B99EF449828C5D926E39EE8B89</itemtype>
</Item>
</Result>
As you can see the permissions are changing for each generation of the Document which is exactly what you should expect to see.
Not sure if you are still looking at a particular revision/generation of the Document. Rather than just looking at the "current" Document. Maybe your AML is looking for a particular ID?
Hope this helps,
Brian.
Brian - Tuesday, May 8, 2012 10:40 PM:
Richard,
Can you post the exact AML that you are using to retrieve the Document data that lead to the first post?
Cheers,
Brian.
rif6894 - Wednesday, May 9, 2012 5:05 AM:
Creating a Document object, Manual Release, and then using the 'Create New Revision' option gives the correct permissions.
<Item type="Document" typeId="B88C14B99EF449828C5D926E39EE8B89"
id="E77F7EC6B88742D580E34D6F7B79A739">
<description>New Revision created using 'Create New Revision'
</description>
<generation>1</generation>
<id keyed_name="RiF Test 001" type="Document">E77F7EC6B88742D580E34D6F7B79A739
</id>
<name>RiF Test 001</name>
<permission_id keyed_name="New Document" type="Permission">F0E3A6D242FC4889A9A119EEBC8EC79E
</permission_id>
<state>Preliminary</state>
<itemtype>B88C14B99EF449828C5D926E39EE8B89</itemtype>
</Item>
<Item type="Document" typeId="B88C14B99EF449828C5D926E39EE8B89"
id="CBA31D5A9F9048F9934D2E00A35F60E3">
<description>New Revision created using 'Create New Revision'
</description>
<generation>2</generation>
<id keyed_name="RiF Test 001" type="Document">CBA31D5A9F9048F9934D2E00A35F60E3
</id>
<name>RiF Test 001</name>
<permission_id keyed_name="Released Document" type="Permission">74C205C37E7C4D56BBBE99B52B28431E
</permission_id>
<state>Released</state>
<itemtype>B88C14B99EF449828C5D926E39EE8B89</itemtype>
</Item>
<Item type="Document" typeId="B88C14B99EF449828C5D926E39EE8B89"
id="80F4C71D57DC47D183B9E55A8C2A8433">
<description>New Revision created using 'Create New Revision'
</description>
<generation>3</generation>
<id keyed_name="RiF Test 001" type="Document">80F4C71D57DC47D183B9E55A8C2A8433
</id>
<name>RiF Test 001</name>
<permission_id keyed_name="New Document" type="Permission">F0E3A6D242FC4889A9A119EEBC8EC79E
</permission_id>
<state>Preliminary</state>
<itemtype>B88C14B99EF449828C5D926E39EE8B89</itemtype>
</Item>
However, if a 'Document' object is created, manually released, then updated using 'Edit', add some comments, then 'Save, Unlock and Close', the permissions are set incorrectly to 'Release Document'
<Item type="Document" typeId="B88C14B99EF449828C5D926E39EE8B89"
id="494BFEFA424B493AB8C75E50B221817C">
<description>Create a new revision using 'Lock', edit description,
and then 'Save, Unlock and Close'</description>
<generation>1</generation>
<id keyed_name="RiF Test 002" type="Document">494BFEFA424B493AB8C75E50B221817C
</id>
<name>RiF Test 002</name>
<permission_id keyed_name="New Document" type="Permission">F0E3A6D242FC4889A9A119EEBC8EC79E
</permission_id>
<state>Preliminary</state>
<itemtype>B88C14B99EF449828C5D926E39EE8B89</itemtype>
</Item>
<Item type="Document" typeId="B88C14B99EF449828C5D926E39EE8B89"
id="2F837BE925774285876197AA6CC809A0">
<description>Create a new revision using 'Lock', edit description,
and then 'Save, Unlock and Close'</description>
<generation>2</generation>
<id keyed_name="RiF Test 002" type="Document">2F837BE925774285876197AA6CC809A0
</id>
<name>RiF Test 002</name>
<permission_id keyed_name="Released Document" type="Permission">74C205C37E7C4D56BBBE99B52B28431E
</permission_id>
<state>Released</state>
<itemtype>B88C14B99EF449828C5D926E39EE8B89</itemtype>
</Item>
<Item type="Document" typeId="B88C14B99EF449828C5D926E39EE8B89"
id="EE68AA7600944C18BBFCD7F79B9A2879">
<description>Create a new revision using 'Lock', edit description,
and then 'Save, Unlock and Close'
Update comment</description>
<generation>3</generation>
<id keyed_name="RiF Test 002" type="Document">EE68AA7600944C18BBFCD7F79B9A2879
</id>
<name>RiF Test 002</name>
<permission_id keyed_name="Released Document" type="Permission">74C205C37E7C4D56BBBE99B52B28431E
</permission_id>
<state>Preliminary</state>
<itemtype>B88C14B99EF449828C5D926E39EE8B89</itemtype>
</Item>
As you can see, one method sets the correct permissions; the other method of editting doesn't.
Your thoughts on this would be appreciated
This output was obtained using
<AML>
<Item action='get' type='Document' order_by='name, generation' select='permission_id, name, description, generation, major_revision, state'>
<name condition='like'>RiF Test %</name>
<generation condition='gt'>0</generation>
</Item>
</AML>
Brian - Wednesday, May 9, 2012 8:43 AM:
rif,
I think we might be getting somewhere.
How are you editing the Document when it is in Released state? The standard lifecycle will only Allow Aras PLM to edit in this state. This suggests that you are using a method and have granted it Aras PLM execution rights. Or you have edited the document lifecycle or Released Document permissions.
Can you post the code that does the lock, edit, unlock? It looks like you might have set it to not version on this edit. Otherwise the generation would not be "1" on both of these outputs which are clearly different data based on the edited description.
Cheers,
Brian.
rif6894 - Wednesday, May 9, 2012 7:42 PM:
Brian
Problem resolved - due to a combination of permissions being elevated too far for the purposes of importing data, and modification of the permissions to assist with data import.
This morning, I went back to a OOTB installation of 9.3, and worked through the permissions of a non-privledged user, with incremental Identity membership changes, to ensure that sufficient permissions were grantted to perform day-to-day activities; not to enable data importing as that task has been evaluated. I have taken a paper copy of all permissions for Document and Part lifecycles for the OOTB installation.
