I created a sample workflow that processes customer verification. It is intended to take the customer from one verification state to another.
Technically speaking, it should advance the value of one of the attributes of “Contact” table record each time the work flow executes until the attribute value is set to “Verification Complete”.
I observed that each time the workflow process is started, in the application, by the authorized role, a new record is created in the Contact table.The workflow does work for the newly created record.
I understand that the ID of the entity is passed by the BPM framework. It certainly seems to pass one for the record it creates but not the one already existing.
Please suggest a way to work with existing schema.
Please note: I am working with an existing schema. And there are tables that do not have primary keys. CUBA platform seems to update the existing DB by adding a primary key to each table that do not have one.