BPA Workflow to send a stream message so the user can access it in the bell
Hello,
So I want to create a workflow which does come verification and then sends a stream message so that the user can check the message here:
Does anybody know what is the IFS Rest API that i need to call or if i need to make some configurations to then call the method that will send the notification? And if i need to configure some URL so the message can be sent?
With best Regards,
Francisco Lopes
Page 1 / 1
@FLopes have you find a way to do that please?
@IFSRUNINNOVAL@FLopes
I haven’t tried myself yet. but looks like Projection StreamSubscriptions and EntitySet FndStreamMessages could be what you are looking for.
Cheers!
Damith
@dsj thank you.
i’ll try it
@dsj thank you
i have tried it in postman meanwhile
So : to authenticate using postman, i’m using an ROPC workflow with a token and ifsapp as username
When using the GET method (with no parameter) i’m getting only notification for IFSAPP
When POSTING a new message with ToUser any existing user but IFSAPP :
I’ll get the following error :
When ToUser is IFSAPP, the message is created correctly
That is a good starting point.
maybe i should rethink the way i authenticate with ifs. ?
maybe in a workflow this limitation doesnt exist?
This is getting interested As I think you should be able to send the notification to another user. Since you are getting a DB error, you could add ?odata-debug=json to the projection call tail and get the error stack and check how the no data error fires.
Cheers!
Damith
@dsj i’m not yet able to read correctly the odata-debug :
If i’m not mistaken , and based on the debug information, i should look at the stacktrace exception
for IFSAPP.STREAM_SUBSCRIPTIONS_SVC\", line 646 a CRUD CREATE method :
That call the following procedure
Have then added traces (cause why not?! )
The problem is, i think, we are querying FND_STREAM
When reading the view behind it :
we see that we have a WHERE that filter values based on the connected user
i don’t know for the moment if this is the intended behavior of the API or not