Skip to main content

​@kamnlk ​@dsj 

I have a scenario where I want to trigger an async BPA WF based on new rows being inserted in INVOICE_TAB.

When using an intercompany invoice scenario - customer invoice in company A and supplier invoice in company B, the supplier invoice in company B is created by Connectivity Outbox background job.

It seems the event action / WF is not trigerred when record is being inserted by a Backgroung Job. 

Do you know if there’s any workaround for that?

I did turn on Watch on the WF, but the only observations being logged are the ones for the Customer Invoice in company A which is created online.

Any input on this is much appreciated.

​@Marcel.Ausan 

Are sure about the entities on which you want to trigger the event/workflow? 
As it seems to be more an event error then something to do with the workflow? 

If you setup just an email action or so does your event get triggered?

 

​@kvbe I just did a quick test to create an mail event action in the same event. I get both emails. One for Customer Invoice and another one for Supplier Invoice. So, it’s just the event action for WF that doesn’t get triggered

 

In the WF Observations I only see details for Invoice Id - 13589 - Customer Invoice that is created offline. No observations for supplier invoice that is created via background job.

​@Marcel.Ausan  ok perfect so all is triggering correctly then. 

Next step is that the workflow observations is not always working (depending on the version) 
you need to look into the BPA_ASYNC_SYS_TAB table. 

More info also here 


As a next step I would create a very simple workflow with start - action - stop 
and as an action you for example send an email or do a rest call to an external simple service (eg. https://learning.postman.com/docs/designing-and-developing-your-api/mocking-data/setting-up-mock)  or something like https://www.postb.in/ so you know for sure that your workflow was triggered

Thing is that if you can somehow test it without being it async that helps for debugging.
Let me know if that works 

 

Thanks ​@kvbe. 

So, I found the async record in BPA_ASYNC_RECORDS. Status is Done and I also have the attr with all the parameters the WF was called with.

So, it appears even if the environment is 24R2, the observations for async workflows are not saved when enabling the ‘watch’.

In the end, there was a logic issue in the WF and it didn’t update the record. When I saw no updates and no observations logged, I thought the WF is not executed. But that’s not the case.

Thanks a lot for your input. I also found below doc page very useful: https://docs.ifs.com/techdocs/25r1/040_tailoring/500_business_process_automation/060_workflow_architecture/020_async_workflows/?h=asy#asynchronous_workflows

Reply


Terms & ConditionsCookie settings