<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Dynamic routing to process model</title><link>https://community.appian.com/discussions/f/general/27681/dynamic-routing-to-process-model</link><description>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</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Dynamic routing to process model</title><link>https://community.appian.com/thread/107642?ContentTypeID=1</link><pubDate>Thu, 09 Feb 2023 09:22:07 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:597db5fa-0003-45e6-ae2f-ee95e135d9a7</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;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.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>