Skip to main content
Solved

WorkspaceRunner - return values?

  • August 25, 2026
  • 3 replies
  • 48 views

datablue
Supporter
Forum|alt.badge.img+11

I have a workspace that creates a CSV file from an ArcGIS feature service. I have five attributes that contain 0 to 5 comma-separated 5-digit integers. I sort the integer list then look up text values in an Excel file. I’d like to put this task in a separate workspace and call it from a WorkspaceRunner. For example, I convert “12345, 12346, 12347” to “Desc1,Desc2,Desc3”

I have a programming background and was thinking of a WorkspaceRunner as a function or sub-routine with a return value. I understand how to pass a parameter to a workspace, but how do I get a return value (e.g. “Desc1,Desc2,Desc3”) back to the parent workspace? I have a feeling that I’m misunderstanding what a WorkspaceRunner can do. Thanks.

Best answer by veronikaatsafe

Hi ​@datablue,

You are on the right track with your answer, as the WorkspaceRunner only outputs process metadata (_proc_count and _processes{}) and does not expose any features or attributes generated inside the child workspace. Using a custom transformer would be similar to using a function call, so it should be the right tool for your purposes. 

You may find these resources helpful: 
Creating a Custom Transformer — FME Documentation
Exporting a Custom Transformer — FME Documentation
Output attributes of a WorkspaceRunner — Community Post

If you have any other questions, please let me know!

3 replies

datablue
Supporter
Forum|alt.badge.img+11
  • Author
  • Supporter
  • August 25, 2026

I will answer my own question here.

I believe that I need to use a Custom Transformer and not a separate workspace. This will allow me to return a value. I do need to figure out how to export a custom transformer so that I can use it in other workspaces.


veronikaatsafe
Safer
Forum|alt.badge.img+9
  • Safer
  • Best Answer
  • August 26, 2026

Hi ​@datablue,

You are on the right track with your answer, as the WorkspaceRunner only outputs process metadata (_proc_count and _processes{}) and does not expose any features or attributes generated inside the child workspace. Using a custom transformer would be similar to using a function call, so it should be the right tool for your purposes. 

You may find these resources helpful: 
Creating a Custom Transformer — FME Documentation
Exporting a Custom Transformer — FME Documentation
Output attributes of a WorkspaceRunner — Community Post

If you have any other questions, please let me know!


datablue
Supporter
Forum|alt.badge.img+11
  • Author
  • Supporter
  • August 26, 2026

Hi ​@demyanovaver

Just yesterday I got my first custom transformer working. It’s a powerful feature. I plan to export it and use it from multiple workspaces. Thanks for your message and links.