Stje_Cro - Tuesday, April 19, 2011 7:33 AM:
I have some parts that couldn't be modified by user, but some fields on Part form should be editable, fields like description or Remarks.
When i lock the Part I would block some button, for a specific group of Part,
on Form Tabs (for example "new relationship" on Tab Part BOM) or keep the Tab in Unlocked state (not editable).
This don't depends on part classification, but on value of an column in Part DB Table.
Someone have an suggestion or advice on how i can do this?
Someone can help me please?
Brian - Tuesday, April 19, 2011 9:37 AM:
Well you could do this but it would require some work.
To start you have to realise that ANY edit of a part in released state will create a new revision which probably isn't what you want. So first you have to define a lifecycle state that allows you to edit the part without rolling the revision if you are only editing the "allowed" bits.
You may have to have a look at the ECN workflows and the server events triggered by the various promotions of the ECN lifecycle to ensure that things still change the way you want them too.
Then you will have to edit the part form and decide how you are going to block some of the fields and allow others to be edited. You may want to put two fields on the form for each Item type field. One in the "disabled" state and one not. You display one if you want to be able to edit and the other if you only want people to be able to read it. For the other fields you can toggle the "disabled" flag on the field itself.
To stop people from adding/changing relationships you will have to respond to the grid events in the Relationship Type. When you want to stop someone from adding a new item return false from the onInsertRow event.
Realistically you need to decide if this is the right way of doing things. Are you allowing these changes because of problems in your processes or is there really a legitimate reason for them? I have found that most often this sort of processing is a reflection of poor process. Going back and fixing the reasons why people feel they need to make these changes is a better solution. Create Item types that link to the Part rather than the Part linking to them. So you could create a Remarks Item type with a Part Item type Property. You could create these at any time and expose them on a tab on the Part form using a configurable grid or a custom HTML grid.
Hope this helps,
Brian.
Stje_Cro - Wednesday, April 20, 2011 2:55 AM:
Hi Brian,
thank you for post.
We would use ARAS as a support tool for R&D departement.
We have a server where are all definitive Parts, but only some peaple have access to it.
Now, we would import all data from existing server to Aras and use it for develop new items. This items shouldn't be modified by R&D User.
ARAS give us the possibility to add additional information about an item (Part.)
But for the imported parts only the "new ARAS field" should be editable and the others should be read only.
If it's a part created in ARAS then the user have access to all fields on form.
This thing is already done. The fields on form are editable or not depends on part type (imported or created in aras)
But i would keep the tabs in not editable state for the imported Parts even if the part is locked and editable.
I hope i gave you a good explanation.
Stjepan
