< class="prominent-subhead ">

Known Issue: Incorrect data returns when using a SmartObject list method as a reference in a workflow

This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.


After installing K2 Five (5.0) September 2018 Cumulative Update Fix Pack 6, multiple rows of data return instead of just one value. This occurs when your workflow is configured to return the destination user’s name that approved a task, by creating a reference in the workflow using the Activity Instance Destination SmartObject and passing the folio and activity display names to the reference.


This issue was introduced by a fix made in K2 Five (5.0) September 2018 Cumulative Update Fix Pack 6. More information on the fix can be found here.


Update your workflow by following the steps below:

    1. For the Activity Instance Destination use a SmartObject method instead of the Create Reference Step.


    2. Use the mappings as illustrated below. Ensure to add Workflow ID for the Process Instance ID. The Process Instance ID needs to be specified to filter out previous executed instances.


    3. Create a new data field and map it to the destination as illustrated in the image above. The data field will then be updated after every task.
    4. On the second SmartObject method, the data field can now be used in the workflow as an input property based on the correct return value.



Note the same issue may occur in other versions of K2 Five, you can apply the same workaround to these versions.