Hi all.
I would like to capture via API the error that has occurred within a process instance in Appian. I have tried to do it with several methods through the ProcessExecutionService, but I can't find a way to do it.
The error I want to capture is the one I can see within the process instance in the errors tab
Could you help me please?
Discussion posts and replies are publicly visible
Sorry, that is not supported as of now. If you want to centralize incident management, true to send process alerts to an email inbox and process these emails.
Thx Stefan. Finally after a quick research, I've seen that the operation can be done using PortalNotificationService (Appian API), but it' s actually deprecated, and the recommendation is to use the tempo interface....but I can't find any replacement class in the API .... Tempo interface is just an interface, and can only be used in that context....
It won't be possible in the future to access this information programatically? Do you know when will this class be removed from API?
"PortalNotificationService" is based on the old technology deprecated 8 years ago. This will not get you anywhere.
As I said, as of now, there is no way to do that. At least not in the way that you tried it. If you share more context, we can start to think about more creative ways.
I know that it's a depcrecated version, but still functional. From the api , there is no replacement class for PortalNotificationService, but have no idea about any other alternative....
In the API, it can be read this must be actually done using tempo interface, and I suposse that this interface uses another api class in order to read notifications. COuld be possible to get information about the way tempo interface works please?
Peter Lewis, can you help us with this?
Any update on this?
Peter Lewis ?
Sorry, I'm not aware of another alternative at the moment. Could you provide a bit more information about your use case? What are you trying to achieve?
HI Peter, we would like to be able to capture the detail of the error generated in a process instance and store it in the database.
We achieve this functionality via API, but using a deprecated class in Appian API. That's why we asked about any other way to get that information using different classes