HI ,
I have a jira integration requirement and need to call jira from appian to create epic,story and read few data from jira.
To handle integration errors and maintaining each jira int call before and after maintaining the logging in DB.
Instead of having the error handling and logging in each of every process model , thinking to have a common routing process based on dynamic parameter
it should that process and since error handling and logging db and email notifications are in common process no need to have in sub process alone.
with this redundant code is reduced and can be used for any other workflow later since it is a common component.
what is the best approach for this
Thanks
Soujanya
Discussion posts and replies are publicly visible
Creating common objects has two sides. It can encapsulate complexity, but this complexity can become very complicated. For me, this feels like a multi level approach might fit. Some low level models implement the technical part and some mid level models implement the routing and organizational aspects.