<?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>Best practice to get targeted processId</title><link>https://community.appian.com/discussions/f/best-practices/38948/best-practice-to-get-targeted-processid</link><description>We&amp;#39;re in the design phase of creating cross-channel communication for business processes. We use CRM, Mobile, Kiosk, and other channels to send and receive messages to and from Appian. Our goal is to develop a web API that enables message exchange between</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Best practice to get targeted processId</title><link>https://community.appian.com/thread/147336?ContentTypeID=1</link><pubDate>Fri, 18 Apr 2025 15:21:36 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:a040e7b7-a9cd-4229-b1d5-9aaef402746e</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;Then, I suggest to calculate the expected load and do some performance testing.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Best practice to get targeted processId</title><link>https://community.appian.com/thread/147329?ContentTypeID=1</link><pubDate>Fri, 18 Apr 2025 08:55:36 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:ecdbad1f-5dbe-42ba-9d24-639e2d3c73e3</guid><dc:creator>ahmadb3492</dc:creator><description>&lt;p&gt;Also, there&amp;rsquo;s a cron job that could start a process for each customer to perform various business validations and actions.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Best practice to get targeted processId</title><link>https://community.appian.com/thread/147328?ContentTypeID=1</link><pubDate>Fri, 18 Apr 2025 08:51:44 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:c5c2a6d3-fd2a-4508-adc6-b64828c73b37</guid><dc:creator>ahmadb3492</dc:creator><description>&lt;div class="css-186bnk2 css-lb9cx4-stack css-3sj1cp css-1bjhv8d css-1vznryd css-1soja3n"&gt;
&lt;div&gt;
&lt;p class="css-nrxxf9 css-pelz90 css-0 css-s9mxsb css-bmcd97-textWhiteSpace css-0 css-542wex"&gt;Certainly more than one per second, as our mobile app has high-demand requests&amp;nbsp;that could be sent to the BPM.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Best practice to get targeted processId</title><link>https://community.appian.com/thread/147327?ContentTypeID=1</link><pubDate>Fri, 18 Apr 2025 08:31:46 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:914cf77d-2351-4d3a-811e-dd9722f2db29</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;Any performance question depends on the expected load. If you do this once a second, I would go with a process report.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Best practice to get targeted processId</title><link>https://community.appian.com/thread/147325?ContentTypeID=1</link><pubDate>Fri, 18 Apr 2025 07:44:17 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:e69c234a-10e1-45ca-9e2b-c4a5ba1974fe</guid><dc:creator>ahmadb3492</dc:creator><description>&lt;div class="css-186bnk2 css-lb9cx4-stack css-3sj1cp css-1bjhv8d css-1vznryd css-1soja3n"&gt;
&lt;div&gt;
&lt;p class="css-nrxxf9 css-pelz90 css-0 css-s9mxsb css-bmcd97-textWhiteSpace css-0 css-542wex"&gt;I&amp;#39;m responding from my personal account since I&amp;#39;m currently on vacation. From a performance standpoint, which approach is considered more efficient: the database or the report?&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Best practice to get targeted processId</title><link>https://community.appian.com/thread/147315?ContentTypeID=1</link><pubDate>Thu, 17 Apr 2025 13:40:17 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:3a62ec17-eb74-4b40-93cb-8809461c97c6</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;There is no need to create a report for each model. Assuming that the variable name is consistent, you can use the report &amp;quot;Details for Process Model&amp;quot;, and then pass a list of relevant models as the context.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Best practice to get targeted processId</title><link>https://community.appian.com/thread/147313?ContentTypeID=1</link><pubDate>Thu, 17 Apr 2025 13:13:48 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:161fbee9-9f81-4211-b994-e1966a07bc80</guid><dc:creator>ahmadb803565</dc:creator><description>&lt;p&gt;&lt;span&gt;For the first point, I&amp;#39;m referring to the report for each process model (car loan, KYC, etc.). As you know, we stored the correlation ID in the process variable. Based on our current knowledge&amp;mdash;please correct me if I&amp;#39;m wrong&amp;mdash;if we want to search for the process variable, we should create a report for each individual process model.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Best practice to get targeted processId</title><link>https://community.appian.com/thread/147312?ContentTypeID=1</link><pubDate>Thu, 17 Apr 2025 12:17:40 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:e6b3c38b-c0d5-44ad-947e-f44872ea0814</guid><dc:creator>Stefan Helzle</dc:creator><description>[quote userid="294628" url="~/discussions/f/best-practices/38948/best-practice-to-get-targeted-processid"]However, this would require creating separate process reports for each case.[/quote]
&lt;p&gt;Why this?&lt;/p&gt;
&lt;p&gt;But, storing process ID and correlation ID in a DB is a good approach.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>