Modification Timestamp for act_ru_jobs

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

damokles

The <em>act_ru_jobs</em> table is currently (Activiti 5.14) defined without a <strong>CREATED_</strong> column in contrast to <em>act_ru_task</em>, which has <strong>CREATE_TIME_</strong>. or <em>act_ru_event_subscr</em>, which has <strong>CREATED_</strong>.

For monitoring and analysis it would be really helpful to have information about the last modification of the job. So a column

`CREATED_` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP‍

would be really helpful. Are there any plans to add this, or can we just add this column ourselves?

CREATE TABLE `act_ru_job` (
   `ID_` VARCHAR(64) NOT NULL,
   `REV_` INT(11) NULL DEFAULT NULL,
   `TYPE_` VARCHAR(255) NOT NULL,
   `LOCK_EXP_TIME_` TIMESTAMP NULL DEFAULT NULL,
   `LOCK_OWNER_` VARCHAR(255) NULL DEFAULT NULL,
   `EXCLUSIVE_` TINYINT(1) NULL DEFAULT NULL,
   `EXECUTION_ID_` VARCHAR(64) NULL DEFAULT NULL,
   `PROCESS_INSTANCE_ID_` VARCHAR(64) NULL DEFAULT NULL,
   `PROC_DEF_ID_` VARCHAR(64) NULL DEFAULT NULL,
   `RETRIES_` INT(11) NULL DEFAULT NULL,
   `EXCEPTION_STACK_ID_` VARCHAR(64) NULL DEFAULT NULL,
   `EXCEPTION_MSG_` VARCHAR(4000) NULL DEFAULT NULL,
   `DUEDATE_` TIMESTAMP NULL DEFAULT NULL,
   `REPEAT_` VARCHAR(255) NULL DEFAULT NULL,
   `HANDLER_TYPE_` VARCHAR(255) NULL DEFAULT NULL,
   `HANDLER_CFG_` VARCHAR(4000) NULL DEFAULT NULL,
   PRIMARY KEY (`ID_`),
   INDEX `ACT_FK_JOB_EXCEPTION` (`EXCEPTION_STACK_ID_`),
   CONSTRAINT `ACT_FK_JOB_EXCEPTION` FOREIGN KEY (`EXCEPTION_STACK_ID_`) REFERENCES `act_ge_bytearray` (`ID_`) ON UPDATE NO ACTION ON DELETE NO ACTION
)
COLLATE='latin1_swedish_ci'
ENGINE=InnoDB;
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

BTW: are there any plans on harmonizing the column names between the tables?

trademak

Good point, can you raise a JIRA?