<?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>topic Modification Timestamp for act_ru_jobs in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/modification-timestamp-for-act-ru-jobs/m-p/157301#M111495</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The &amp;lt;em&amp;gt;act_ru_jobs&amp;lt;/em&amp;gt; table is currently (Activiti 5.14) defined without a &amp;lt;strong&amp;gt;CREATED_&amp;lt;/strong&amp;gt; column in contrast to &amp;lt;em&amp;gt;act_ru_task&amp;lt;/em&amp;gt;, which has &amp;lt;strong&amp;gt;CREATE_TIME_&amp;lt;/strong&amp;gt;. or &amp;lt;em&amp;gt;act_ru_event_subscr&amp;lt;/em&amp;gt;, which has &amp;lt;strong&amp;gt;CREATED_&amp;lt;/strong&amp;gt;.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For monitoring and analysis it would be really helpful to have information about the last modification of the job. So a column &lt;/SPAN&gt;&lt;PRE class="language-none line-numbers"&gt;&lt;CODE&gt;`CREATED_` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;SPAN&gt; would be really helpful. Are there any plans to add this, or can we just add this column ourselves?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;PRE class="language-none line-numbers"&gt;&lt;CODE&gt;&lt;BR /&gt;CREATE TABLE `act_ru_job` (&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;`ID_` VARCHAR(64) NOT NULL,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;`REV_` INT(11) NULL DEFAULT NULL,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;`TYPE_` VARCHAR(255) NOT NULL,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;`LOCK_EXP_TIME_` TIMESTAMP NULL DEFAULT NULL,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;`LOCK_OWNER_` VARCHAR(255) NULL DEFAULT NULL,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;`EXCLUSIVE_` TINYINT(1) NULL DEFAULT NULL,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;`EXECUTION_ID_` VARCHAR(64) NULL DEFAULT NULL,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;`PROCESS_INSTANCE_ID_` VARCHAR(64) NULL DEFAULT NULL,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;`PROC_DEF_ID_` VARCHAR(64) NULL DEFAULT NULL,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;`RETRIES_` INT(11) NULL DEFAULT NULL,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;`EXCEPTION_STACK_ID_` VARCHAR(64) NULL DEFAULT NULL,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;`EXCEPTION_MSG_` VARCHAR(4000) NULL DEFAULT NULL,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;`DUEDATE_` TIMESTAMP NULL DEFAULT NULL,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;`REPEAT_` VARCHAR(255) NULL DEFAULT NULL,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;`HANDLER_TYPE_` VARCHAR(255) NULL DEFAULT NULL,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;`HANDLER_CFG_` VARCHAR(4000) NULL DEFAULT NULL,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;PRIMARY KEY (`ID_`),&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;INDEX `ACT_FK_JOB_EXCEPTION` (`EXCEPTION_STACK_ID_`),&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;CONSTRAINT `ACT_FK_JOB_EXCEPTION` FOREIGN KEY (`EXCEPTION_STACK_ID_`) REFERENCES `act_ge_bytearray` (`ID_`) ON UPDATE NO ACTION ON DELETE NO ACTION&lt;BR /&gt;)&lt;BR /&gt;COLLATE='latin1_swedish_ci'&lt;BR /&gt;ENGINE=InnoDB;&lt;BR /&gt;&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;BTW: are there any plans on harmonizing the column names between the tables?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 18 Mar 2014 17:04:10 GMT</pubDate>
    <dc:creator>damokles</dc:creator>
    <dc:date>2014-03-18T17:04:10Z</dc:date>
    <item>
      <title>Modification Timestamp for act_ru_jobs</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/modification-timestamp-for-act-ru-jobs/m-p/157301#M111495</link>
      <description>The &amp;lt;em&amp;gt;act_ru_jobs&amp;lt;/em&amp;gt; table is currently (Activiti 5.14) defined without a &amp;lt;strong&amp;gt;CREATED_&amp;lt;/strong&amp;gt; column in contrast to &amp;lt;em&amp;gt;act_ru_task&amp;lt;/em&amp;gt;, which has &amp;lt;strong&amp;gt;CREATE_TIME_&amp;lt;/strong&amp;gt;. or &amp;lt;em&amp;gt;act_ru_event_subscr&amp;lt;/em&amp;gt;, which has &amp;lt;stro</description>
      <pubDate>Tue, 18 Mar 2014 17:04:10 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/modification-timestamp-for-act-ru-jobs/m-p/157301#M111495</guid>
      <dc:creator>damokles</dc:creator>
      <dc:date>2014-03-18T17:04:10Z</dc:date>
    </item>
    <item>
      <title>Re: Modification Timestamp for act_ru_jobs</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/modification-timestamp-for-act-ru-jobs/m-p/157302#M111496</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Good point, can you raise a JIRA?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Mar 2014 16:20:06 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/modification-timestamp-for-act-ru-jobs/m-p/157302#M111496</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2014-03-21T16:20:06Z</dc:date>
    </item>
  </channel>
</rss>

