We are using custom workflow rules to lock sub-objects on a main object, when the main object locks. However, even though the users cannot edit the sub-object fields, they are able to create new ones, or delete existing ones.
The goal would be to have it so that if the instance is locked, none of the sub-objects related to that instance should be editable AT ALL. We have a custom script that sets the "Locked?" fields to Yes when we lock the main object, and then a business rule to Disable Editing Record if "Locked?" = Yes. This sadly still allows users to create new fields and delete existing ones even when locked (as evidenced by screenshots 2 & 3). If possible, it would be great to be able to execute business rules on a subobject based on conditions in a main object as well (if main is locked, don't allow any actions on subobject).
------------------------------
DH
Computer Programmer
------------------------------