Hello Allan, Thank you for your response. Actually I simply revoked the INSERT sigoption on the Assets application for the specific security group and created a custom button that runs an automation script that bypasses the access check. And this solution ...

Hi Oumayma, There are a few ways I can think of to accomplish this, and it's up to you how you'd like to move forward. I believe you'd be able to set up a signature option for the field if it isn't already configured for one. Then all you would have ...

This has been this way since it was implemented. I'll be honest, I haven't opened a support ticket to get a defect on it. IBM never documented this feature publicly. I only learned of it because I was at IBM and did this presentation ( MSUG - Automation ...

Looking at your screenshot it does appear that the constructor accepts the databean parameter but it then doesn't use it. This would need to be raised with IBM as a support case. They will need a log demonstrating the NullPointerException that is raised ...

Upon decompiling the class, it is observed that the dataBea n parameter passed into the DataBeanContext constructor has not been initialized. #Administration ------------------------------ Ethan Williams secrecy ------------------------------