<?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>Persistent tp!id after cancel.</title><link>https://community.appian.com/discussions/f/process/22586/persistent-tp-id-after-cancel</link><description>Hi. 
 
 I currently have a requirement to allow the canceling of a UI task while keeping tp!id the same. 
 Basically the equivalent to exiting out of the window and coming back to it later. 
 
 Is there a way to do this with a button labeled cancel within</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Persistent tp!id after cancel.</title><link>https://community.appian.com/thread/88282?ContentTypeID=1</link><pubDate>Tue, 23 Nov 2021 15:41:39 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:23e69065-e9d6-448d-9e45-e6dbf553658c</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;&lt;a href="/members/mikes0011"&gt;Mike Schmitt&lt;/a&gt; Is right. Think of a task in Appian as a business task, but not a technical one. A business task can not be cancelled. It must have some sort of outcome to continue the process.&lt;/p&gt;
&lt;p&gt;In Appian by default, you just navigate away to leave the task UI. If you want to make that more explicit to the user, create a link which points to the task list.&lt;/p&gt;
&lt;p&gt;I do not recommend that, because creating you own navigation metaphors will collide with the navigation concepts in Appian sooner or later.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Persistent tp!id after cancel.</title><link>https://community.appian.com/thread/88278?ContentTypeID=1</link><pubDate>Tue, 23 Nov 2021 15:33:39 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:9417eb7f-160e-4ff0-ba1c-8b53ccaa3663</guid><dc:creator>Mike Schmitt</dc:creator><description>&lt;p&gt;&lt;strong&gt;&lt;em&gt;tp!id&lt;/em&gt;&lt;/strong&gt; is auto-generated by the system and is unique to any given instance of a task (or any other node) - i&amp;#39;m not sure why there would be a &amp;quot;requirement&amp;quot; attempting to dictate how the back-end of the system behaves, particularly as such a thing is not possible.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>