<?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>Tracking task versus process execution</title><link>https://community.appian.com/discussions/f/process/14539/tracking-task-versus-process-execution</link><description>It seems that the Process Report allows tracking Tasks (defined within the process) against their completion being late only on the level of the entire Process (i.e., rather than deadlines assigned individual individual tasks). 
 
 What is the best practice</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Tracking task versus process execution</title><link>https://community.appian.com/thread/65261?ContentTypeID=1</link><pubDate>Wed, 20 Mar 2019 06:15:18 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:809bed61-d53c-4aad-84fa-abfb33ddb073</guid><dc:creator>jerzym0001</dc:creator><description>Thank you, fully agree.  At the time of my posting I was still not aware that Escalations, Exceptions and Deadlines can be configuired at the Task level.  Obviously, my purpose to establish OLAs and SLAs is to enable tracking the completion progress of tasks to enable pro-active escaltion/recovery.  Again, thank you for your timely response.  I gor my learning from here: &lt;a href="https://docs.appian.com/suite/help/19.1/Process_Node_and_Smart_Service_Properties.html"&gt;docs.appian.com/.../Process_Node_and_Smart_Service_Properties.html&lt;/a&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Tracking task versus process execution</title><link>https://community.appian.com/thread/65256?ContentTypeID=1</link><pubDate>Tue, 19 Mar 2019 15:57:31 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:4bfc4af9-1102-4717-ba73-cafb37011906</guid><dc:creator>Stewart Burchell</dc:creator><description>I would encourage you to think about the problem differently. What are you going to do with this information, assuming it&amp;#39;s going to be recorded post-facto? If the purpose is to ensure that overall SLAs (or individual OLAs) are met, then build this as pre-emptive actions in the process. Design your Tasks to have a relevant combination of Escalations and Exceptions to try to ensure that the SLAs and OLAs are met. That, after all, is the purpose of Management Information - situational awareness that leads to action. If this is at all deterministic then automate it.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>