Skip to main content
Solved

Workflow - How can we use a IFS API call returning struct

  • March 23, 2026
  • 2 replies
  • 57 views

dsj
Ultimate Hero (Partner)
Forum|alt.badge.img+22
  • Ultimate Hero (Partner)

Hi All,

 

I tried to use an IFS API call which returns a struct but the return structure is not added to the debug values list. Is this not supported for workflows or is there any other way to call an IFS API call with a struct?

My example API call

WorkTaskHandling.GetPartSerialInfo(PartNo)
 

 

Debug value list.
Notice that previous steps which return string are added in the debug values but not the struct
 


GetPartSerialInfo struct response format
 

 

Best answer by pdollk

Hi ​@dsj 

I tried to call WorkTaskHandling.GetPartSerialInfo(PartNo) with a single API task and got some results in the ifsmasterbnddevcmb environment, but I could not find the proper value for PartNo. I searched for the page or table but was unable to find it.

 

As I know, workflows do not support calling functions whose output is a complex structure. A complex structure refers to a structure that contains another structure as an attribute. 

 

However, functions whose output is a structure, or a list of structures can be invoked through the workflow. 

 

2 replies

Forum|alt.badge.img+5
  • Do Gooder (Employee)
  • Answer
  • March 24, 2026

Hi ​@dsj 

I tried to call WorkTaskHandling.GetPartSerialInfo(PartNo) with a single API task and got some results in the ifsmasterbnddevcmb environment, but I could not find the proper value for PartNo. I searched for the page or table but was unable to find it.

 

As I know, workflows do not support calling functions whose output is a complex structure. A complex structure refers to a structure that contains another structure as an attribute. 

 

However, functions whose output is a structure, or a list of structures can be invoked through the workflow. 

 


dsj
Ultimate Hero (Partner)
Forum|alt.badge.img+22
  • Author
  • Ultimate Hero (Partner)
  • March 25, 2026

Hi ​@pdollk 

 

Thanks a lot for your exceptionally well reply :)

I understand what’s going on now. When the return structure is not a collection, then the values are added as workflow variables.

It was little confusing since the Call Return Value Name is not included in the variables list, but not a big issue since the values are there :)