Dear experts,
For my risk event form, I want to create a custom save button when clicked it will erase the assigned_to field in the risk event form, where the submit button will proceed with the risk event form submission that will prompt to the defined user in the assigned_to field. Currently, the submit button will only appear in the first submission of the form, so if we submit for the first time even though there is no assigned_to defined, when we log back in to the risk event record, the submit button is gone and it will be replaced with the update button. To make sure the submit button is always present before the assigned_to is defined, how do we make it happen? So my requirement now is to have two buttons at the first creation of the risk event record, Save and Submit buttons. I have created an onLoad script, where when user creates a new risk event form, the system will autopopulate the assigned_to field. Both of this state of the risk event will still remain as "New". So after I save and I go back to the record, the risk event form should still has the two save and submit button still and their function still the same as mentioned above until it is submitted to the defined user in the assigned_to field. Currently, the submit and update buttons are using the global one that is in the screenshots below, if I create new ui actions will it bypass the Global Ui Action or should I add in my conditions in the global ui actions script or what can I do in this case? Please advise, thank you.
