<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Expose QEM API with task specific information currently contained in attrep_Status table in Suggest an Idea</title>
    <link>https://community.qlik.com/t5/Suggest-an-Idea/Expose-QEM-API-with-task-specific-information-currently/idi-p/2032438</link>
    <description>&lt;P&gt;Currently we use attrep_status for task specific information like&amp;nbsp;&lt;SPAN&gt;task timestamp information. Since the table is common within all our tasks, there is contention on table when multiple updates are happening for all tasks.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The current strategy / mitigation is to have separate tables for each task or group by similar tasks as well as reducing the update frequency to 5 mins. This causes lot of admin work and consolidation on data and latency in task status.&lt;BR /&gt;&lt;BR /&gt;Requesting to expose this information via QEM&amp;nbsp;GetTaskDetails API. This would reduce lot of admin work and contention at the target ( attrep_status table updated)&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 31 Jan 2023 19:37:44 GMT</pubDate>
    <dc:creator>birendodia</dc:creator>
    <dc:date>2023-01-31T19:37:44Z</dc:date>
    <item>
      <title>From now on, please track this idea from the Ideation por...</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Expose-QEM-API-with-task-specific-information-currently/idc-p/2100338#M13601</link>
      <description>&lt;P&gt;From now on, please track this idea from the Ideation portal.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;A title="Link to new idea" href="https://ideation.qlik.com/app/#/case/281283" target="_blank" rel="noopener"&gt;Link to new idea&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Meghann&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;EM&gt;NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you &lt;STRONG&gt;only&lt;/STRONG&gt; see 1 tab with the login page, please try clicking this link first: &lt;STRONG&gt;&lt;A title="Authenticate me!" href="#" target="_blank" rel="noopener"&gt;Authenticate me!&lt;/A&gt;&lt;/STRONG&gt;&amp;nbsp;t&lt;/EM&gt;&lt;EM&gt;hen try the link above again. Ensure pop-up blocker is off.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Aug 2023 15:28:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Expose-QEM-API-with-task-specific-information-currently/idc-p/2100338#M13601</guid>
      <dc:creator>Meghann_MacDonald</dc:creator>
      <dc:date>2023-08-02T15:28:58Z</dc:date>
    </item>
    <item>
      <title>Re: Expose QEM API with task specific information currently contained in attrep_Status table - Status changed to: Closed - Archived</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Expose-QEM-API-with-task-specific-information-currently/idc-p/2100339#M13602</link>
      <description />
      <pubDate>Wed, 02 Aug 2023 15:29:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Expose-QEM-API-with-task-specific-information-currently/idc-p/2100339#M13602</guid>
      <dc:creator>Ideation</dc:creator>
      <dc:date>2023-08-02T15:29:00Z</dc:date>
    </item>
  </channel>
</rss>

