Skip to main content

Hi all,
We have built a custom API that changes a field (IFS Cloud).

I built the Custom event so that whenever this field is changed with “value,” the workflow is triggered. This works fine if I run the custom API from Postman or the value is changed using IFS Cloud. But for some reason, when it is sent via IFS Connect (Using Projection as Routing Rule), the workflow is not triggered.

Do you have any idea why this is a different behavior?

 

Thanks,

Im not sure about the connect. But i guess in this case table may be updating as a background job. If that is the case that may have caused the workflow to not to trigger on timing other than Asynchronous.

You can try changing the workflow timing to “Asynchronous” in the event action configuration and see if the workflow will be triggered in that mode

 

Also, you can enable observations on the workflow (workflow observations). If the workflow do trigger, we will be able to see observations from the workflow execution. 

 

 

Hi @kamnlk ,

I changed the timing to Asynchronous on the Custom event, but the Event is still not being triggered.

I also used the Projection action (using after and async as timing), but still, the Workflow is not triggered (Start Watch activate and empty).

Projection Action

 

Hi @Eleazar_AyaviriCarrillo 

In order to narrow down possible causes, can you confirm the value is updated properly in the table when the projection is called by IFS connect?

HI @kamnlk ,

yes, the value is updated always when using IFS Connect.

Hi @kamnlk ,

do you have any news?

Hi @Eleazar_AyaviriCarrillo ,

 

Sorry in delay in response, i was unable to create the exact situation, If possible can you please share the Routing Rule and the Address details in the IFS Connect?

Also, as a workaround you can try using IFS Connect REST Sender to call the projection action and see if the workflow triggers in that configuration. 

Hi @Eleazar_AyaviriCarrillo ,

 

Sorry in delay in response, i was unable to create the exact situation, If possible can you please share the Routing Rule and the Address details in the IFS Connect?

Also, as a workaround you can try using IFS Connect REST Sender to call the projection action and see if the workflow triggers in that configuration. 

Hi @kamnlk ,

no worries 🙂.

 

Do you know how to set the IFS Connect REST to call IFS APIs?

I tried but it gives me 400.

Please note, the issue is using Projection, because from PSO (which goes through IFS Connect and uses IFS Connect REST) is triggering the workflow.

Thanks

hi @Eleazar_AyaviriCarrillo ,

would it be possible to share the configurations you used when setting up the IFS Connect REST Sender?

 

also, as a somewhat of a guess, there is a somewhat related question on the IFS Connect REST Sender that might help you. Token request problem in Client Credentials flow | IFS Community 

Hi @kamnlk ,
this is the configuratin I used:
 

 

Reply


Terms & ConditionsCookie settings