Skip to main content
Solved

Output attributes of a workspacerunner

  • Jul 14, 2016 9:57 AM UTC
  • 2 replies
  • 308 views
Forum|alt.badge.img

Dear all,

I have a (parent) workflow that uses an Excel file as input. The file contains string values which are used to query an API on the internet. Every record contains a different querystring. The actual calls are made by a workspace which is used as a workspacerunner (see the first image).

In that workspace I have exposed returned fields as attributes (see the second image). The problem I am having is that I expext a number of attributes coming out of the workspacerunner, but I only get two, which are the input attributes of the workspacerunner. How do I make the workspacerunner spit out the right attributes?

Best answer by david_r

The WorspaceRunner does not transmit the attributes (or features) that where created in the child workspace, it only transmits whatever went into it (initiating features).

If your parent workspace needs to access the features created inside a child workspace, you will have to store them to some intermediate file format (FFS could be a good choice) and then pick them up after the WorkspaceRunner, e.g. with a FeatureReader.

View original
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

david_r
Celebrity
  • david_rCelebrity
  • Best Answer
  • Jul 14, 2016 10:23 AM UTC

The WorspaceRunner does not transmit the attributes (or features) that where created in the child workspace, it only transmits whatever went into it (initiating features).

If your parent workspace needs to access the features created inside a child workspace, you will have to store them to some intermediate file format (FFS could be a good choice) and then pick them up after the WorkspaceRunner, e.g. with a FeatureReader.

Forum|alt.badge.img
  • pimverver
  • Author
  • Jul 14, 2016 11:27 AM UTC

That did the trick, especially the Featurereader! Thank you.

Kind regards,

Pim

Community Stats

32,990
Posts
125,025
Replies
41,911
Members
Terms & ConditionsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.