<?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>Tempo Approvals</title><link>https://community.appian.com/discussions/f/process/13136/tempo-approvals</link><description>I have a process in which management uses Tempo to approve a task. Once approved, the flow moves on to the next task but the value is never stored in the process variable I use on the old legacy form. The value is only captured when the approval is done</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Tempo Approvals</title><link>https://community.appian.com/thread/59458?ContentTypeID=1</link><pubDate>Thu, 23 Aug 2018 04:54:29 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:93aa7910-47c2-49e2-b578-0eb85d23bb1c</guid><dc:creator>ankitab0001</dc:creator><description>Hi tonyc, &lt;br /&gt;
Make sure you provide AC parameters into the form in the UI task and not a PV. Also, while defining the ac parameters in the input tab, make sure you have saved it into a PV.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Tempo Approvals</title><link>https://community.appian.com/thread/59456?ContentTypeID=1</link><pubDate>Thu, 23 Aug 2018 04:22:57 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:f1a94457-971a-4b13-adff-4b0d3cf6237e</guid><dc:creator>ravalik</dc:creator><description>Hi tonyc,&lt;br /&gt;
&lt;br /&gt;
As far as I know it is possible to configure a form with approve or reject buttons which stores a value  when the user submits the form.&lt;br /&gt;
Using the Submit and Button components, you can store a value when the user submits your form, such as true for Approve or false for reject.In this way you can accomplish your requirement.&lt;br /&gt;
&lt;br /&gt;
Thanks,&lt;br /&gt;
ravalik&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Tempo Approvals</title><link>https://community.appian.com/thread/59453?ContentTypeID=1</link><pubDate>Thu, 23 Aug 2018 04:10:44 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:0a68f455-912f-49d5-abdd-bbfeb989de69</guid><dc:creator>sandeepd</dc:creator><description>Hi &lt;a href="/members/tonyc"&gt;tonyc&lt;/a&gt; ,&lt;br /&gt;
&lt;br /&gt;
It is a very common use case. Rather than saving value into ri! or local! variable in your tempo interface it would be good if you can save these form value on button click. May be Save on Approval button. And pass that ri! value  from interface form to pv! in Process model.&lt;br /&gt;
&lt;br /&gt;
Thanks,&lt;br /&gt;
Sandeep&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Tempo Approvals</title><link>https://community.appian.com/thread/59442?ContentTypeID=1</link><pubDate>Wed, 22 Aug 2018 20:37:59 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:51a13cbd-26a3-4374-b8d7-2bd217c95f8d</guid><dc:creator>Colton Beck</dc:creator><description>&lt;p&gt;You should be able to store the user&amp;#39;s button selection into a process variable and use it downstream in the process. You don&amp;#39;t need to use script tasks or gateways to capture a user&amp;#39;s selection. More information available &lt;a href="https://docs.appian.com/suite/help/18.2/Configuring_the_User_Input_Task.html"&gt;here&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>