hi all,
I found a minor issue with the notifications package relating to accept timeouts etc.
The "accept Interaction" activity has the following input parameters.
security.group connected to the vco configuration management group ldap path
timeout.date connected to the "timeout attribute"
This results in the following errors in the logs.
2014-01-09 11:02:21.983+1000 ERROR [STDERR] TimeHelper.dateFromString : ERROR
2014-01-09 11:02:21.983+1000 ERROR [STDERR] java.text.ParseException: Unparseable date: "null"
2014-01-09 11:02:21.983+1000 ERROR [STDERR] at java.text.DateFormat.parse(Unknown Source)
2014-01-09 11:02:21.983+1000 ERROR [STDERR] at ch.dunes.util.TimeHelper.dateFromString(TimeHelper.java:136)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at ch.dunes.model.type.DateConvertor.toObject(DateConvertor.java:24)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at ch.dunes.model.type.TypeConverter.toObject(TypeConverter.java:442)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at ch.dunes.model.type.TypeConverter.toObject(TypeConverter.java:425)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at ch.dunes.workflow.engine.mbean.AttributesConverterHelper.convertAttributeValueToObject(AttributesConverterHelper.java:54)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at ch.dunes.workflow.engine.mbean.runner.WorkflowItemInputRunner.findTimeoutDateName(WorkflowItemInputRunner.java:146)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at ch.dunes.workflow.engine.mbean.runner.WorkflowItemInputRunner.execute(WorkflowItemInputRunner.java:68)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at ch.dunes.workflow.engine.mbean.runner.WorkflowItemInputRunner.execute(WorkflowItemInputRunner.java:30)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.requestElementExecution(WorkflowHandler.java:875)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.handleWorkflowTokenNextStep(WorkflowHandler.java:619)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.executeToken(WorkflowHandler.java:500)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.handleTokenExecution(WorkflowHandler.java:416)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.access$200(WorkflowHandler.java:89)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler$1.execute(WorkflowHandler.java:330)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at ch.dunes.model.ar.AccessRightsTemplate.executeWithAccessRights(AccessRightsTemplate.java:16)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.doExecute(WorkflowHandler.java:326)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.run(WorkflowHandler.java:230)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at java.util.concurrent.FutureTask.run(Unknown Source)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
2014-01-09 11:02:21.999+1000 ERROR [STDERR] at java.lang.Thread.run(Unknown Source)
This is because the "timeout attribute" which is configured in the earlier "set task timeout" activity is set to.
timeout = newBlockingTaskTimeOutDate.getTime() - (lastNoticeHours * 3600000); // this returns an integer result
The accept interaction is expecting a date format. As such I think it may be better connected to "newBlockingTaskTimeOutDate attribute" which is the current date + the vCD default timeout time.