Human task preventing to press go button. (required field in payload)

Question

We have an one step BPEL human task implementation and assigned user must be filll some field of payload before sending task.
The problem is we are using standart worklist app and assinged user can send the task from worklist without opening it. So we can't control required field.
We need a Precondition like rule
is there any way to
Our SOA suite version is 10.1.3.3.
Thanks.

Answer 1

Know this is probably not the direction you wanted to go, but look at Vinay Kumar's blog post on using an initializer:  http://www.techartifact.com/blogs/2013/04/using-a-task-flow-initializer-to-initialize-a-task-flow.html#sthash.CG1CAgfz.1….  (pretty sure he got this from Nick Haralabidis's book: Oracle JDeveloper 11gR2 Cookbook: Nick Haralabidis: 9781849684767: Amazon.com: Books).
In this a prepare method is created in the Application Module impl java similar to your initialization code:
  public void prepare() {
    // get emps vo instance
    EmployeesVOImpl employees;
    employees = (EmployeesVOImpl)getEmployeesVO();
    // remove all rows from emp rowset
    employees.executeEmptyRowSet();
    // add a new emp row
    EmployeesVORowImpl employee = (EmployeesVORowImpl) employees.createRow();
    // add new emp to rowset
    employees.insertRow(employee);
Once you expose this as being a Client Interface in your application module, you have the method available to you to drag into your task flow and set the task flow's "URL Invoke" property to "url-invoke-allowed").  This would give you the empty row you're going to populate.
I don't go this route and instead drag a CreateInsert method onto the task flow as the initial default activity and then flow to the page.  To commit it, just create a binding for the Application Module's commit operation and invoke it from the backing bean when you intercept the submit action.
Hope this helps,
Dan