Clarity

We have processes in place to lock and unlock fields based on the user activitiy.Is there a way to lock/unlock these fields using a query? I am trying to see if we run in to any issues and need to manually reset the fields.  What would be our options?    Thank you.  

Hi,             You can lock ot unlock the attributes based on query. we have implemented this in our organization for requisition object by process level using GEL Script. Gel  Script is below which we have implemented in our organization    Gel Script:    Unlocked Attributes
===================    
 DELETE FROM ODF_LOCKED_ATTRIBUTES WHERE OBJECT_CODE = 'requisition' AND ODF_PK='${gel_objectInstanceId}'  locked attributes:
   
   

      SELECT CREATED_BY CRE_BY1 FROM RSM_REQ_REQUISITIONS WHERE ID=${gel_objectInstanceId}              
              ${CREBY1.rows[0].CRE_BY1} 
      INSERT INTO ODF_LOCKED_ATTRIBUTES VALUES(ODF_LOCKED_ATTRIBUTES_S1.nextval,'requisition',${gel_objectInstanceId},
      'intmat_pref',SYSDATE,${CRE_BY1},SYSDATE,${CRE_BY1})
      INSERT INTO ODF_LOCKED_ATTRIBUTES VALUES(ODF_LOCKED_ATTRIBUTES_S1.nextval,'requisition',${gel_objectInstanceId},
      'rmg_internalmatch',SYSDATE,${CRE_BY1},SYSDATE,${CRE_BY1})
      INSERT INTO ODF_LOCKED_ATTRIBUTES VALUES(ODF_LOCKED_ATTRIBUTES_S1.nextval,'requisition',${gel_objectInstanceId},
      'local_grade',SYSDATE,${CRE_BY1},SYSDATE,${CRE_BY1})      INSERT INTO ODF_LOCKED_ATTRIBUTES VALUES(ODF_LOCKED_ATTRIBUTES_S1.nextval,'requisition',${gel_objectInstanceId},
      'office_address',SYSDATE,${CRE_BY1},SYSDATE,${CRE_BY1})  
      INSERT INTO ODF_LOCKED_ATTRIBUTES VALUES(ODF_LOCKED_ATTRIBUTES_S1.nextval,'requisition',${gel_objectInstanceId},
      'approved_resource',SYSDATE,${CRE_BY1},SYSDATE,${CRE_BY1})
      INSERT INTO ODF_LOCKED_ATTRIBUTES VALUES(ODF_LOCKED_ATTRIBUTES_S1.nextval,'requisition',${gel_objectInstanceId},
      'attach_file',SYSDATE,${CRE_BY1},SYSDATE,${CRE_BY1})
 -------------------------------------------------------------------------------------------------------   Lock Attributes:   INSERT INTO ODF_LOCKED_ATTRIBUTES VALUES(ODF_LOCKED_ATTRIBUTES_S1.nextval,'requisition',${gel_objectInstanceId},
      'intmat_pref',SYSDATE,${CRE_BY1},SYSDATE,${CRE_BY1})   Unlock Attributes:   DELETE FROM ODF_LOCKED_ATTRIBUTES WHERE OBJECT_CODE = 'requisition' AND ODF_PK='${gel_objectInstanceId}'   and attribute_code='local_grade'    ThanksSenthil    

Thank you Senthil. This helps.

Hello,

We have implemented a trigger (few years ago) for locking a custom attribute on the resource object and it has been working fine. We are in V13 (13.0.1.0102 02 0023) and noticied that the lock is not working anymore. The trigger is inserting row in to odf_locked_attributes, still attribute is not getting locked. I am wondering if there are any changes in the current version to prevent the locking behavior. (Resource object does not have process option)

Thank you,

Rajani.