Skip to main content
Solved

Workflow Call action in Nested entity

  • March 22, 2024
  • 1 reply
  • 365 views
InfFilipV
Hero (Partner)
Forum|alt.badge.img+12

Hi,
we want to use BPA to simulate process of printing Barcodes on Shop order. In Aurena there is Assistant which handle this.

Unfortunately we cannot get it work in BPA.

Calling of action in entity seems to be impossible, because there is no way to set EntitySet.
And then it throws error because such action does not exists.

But there is probably bug, because, when I setup EntitySet in “Action” where is available, it is stored and only not displayed in “Call” form. And then is called correct existing action.
But EntityParameters are used as parameters for action and not as parameters for Entity.

Do you know any workaround?

 




 

 

 



BR
Filip

Best answer by Buddhi Gunasekara

By looking at projection metadata, it seems the action you’re trying to call is a bound action. You can call a bound action like this..

By looking at projection odata metadata, we can see that it’s expecting a parameter of type IfsApp.CreateShopOrderReportsHandling.VrtShopOrderReportControl in your scenario.

By looking at the metadata again, we can see there’s an entity set we can use to read that entity

So we can use above information in a workflow.
 

API Read
API Call

You can try above to call the action you need. Given that you can provide a valid value to ${VrtObjkey}, workflow will make the action call, giving the entity read in first api task as  a parameter internally.

Filip | Developer | InfoConsulting.com

1 reply

B
Hero (Employee)
Forum|alt.badge.img+7
  • Buddhi Gunasekara
  • Hero (Employee)
  • 67 replies
  • Answer
  • March 25, 2024

By looking at projection metadata, it seems the action you’re trying to call is a bound action. You can call a bound action like this..

By looking at projection odata metadata, we can see that it’s expecting a parameter of type IfsApp.CreateShopOrderReportsHandling.VrtShopOrderReportControl in your scenario.

By looking at the metadata again, we can see there’s an entity set we can use to read that entity

So we can use above information in a workflow.
 

API Read
API Call

You can try above to call the action you need. Given that you can provide a valid value to ${VrtObjkey}, workflow will make the action call, giving the entity read in first api task as  a parameter internally.


Terms & ConditionsCookie settingsAccessibility statement