Skip to main content


 

Symptoms


A SmartForms Client event was not progressing to the next activity after the form was submitted. Also there were questions about how to transfer data from the form into the workflow in order to use this data in a line rule.
 

Diagnoses


We noticed that we could action the worklist item when it was at that smartforms client event by using workspace to manually select the proper action. Only then would it move onto the next activity. If we used the form buttons to try and action the workflow it still remained on the Smartforms Client event activity. Most likely there needed to be some rules added to integrate the form to the workflow. Currently the workflow was only integrated properly with the form.
 

Resolution

The solution to this issue also tied into explaining the questions about passing data from the form to the workflow. First off we needed to ensure that the proper rules existed to action the workflow when either the cancel or complete buttons were pressed on the form. After checking the form we saw that no workflow action rules existed on those buttons. Currently we only had a transfer data rule to pass a value of the outcome (either complete or cancel) to a form parameter of "Outcome". We first added in an "open the worklist item" rule to when the form is initialized. Next on both complete and cancel buttons we added in an "action the worklist item". In the action the worklist item we have the option to also populate a datafield contained in the workflow. So, we then created a Datafield for "FormOutcome" in the workflow itself, added the datafield into the line rule for the activities following this one, set it to go down the cancel path if FormOutcome = Cancel and go down the complete path if FormOutcome = Complete. Then we deployed the workflow to update it in the form. Now we went back to the form and the action a worklist configuration. In here we dragged the "Outcome" form parameter into the "FormOutcome" datafield, ensured that the serial number was passed, and added in the proper action name. Form was checked in, workflow was redeployed to solve a "datafield not found" error, and then the form actioned the item as intended.




 
Be the first to reply!

Reply