topic Default values for Activiti form properties in Alfresco Archive

Default values for Activiti form properties

thilo_ginkel — Fri, 09 Dec 2011 10:02:31 GMT

Hi there,we are using Activiti's FormService to attach custom form properties to tasks, e.g.: <userTask id="usertask1" name="Task 1"" activiti:candidateGroups="Group"> <extensionElements> <activiti:formProperty id="someProperty" name="Some Property" type="boolean" requi

Re: Default values for Activiti form properties

trademak — Fri, 09 Dec 2011 14:04:42 GMT

Hi,

Right, a default or an initial value (with an expression) is not implemented.
So if you would be willing to contribute a patch that would be great.
Maybe you can use an attribute name like default that could hold a static String or an expression?

Best regards,

Re: Default values for Activiti form properties

thilo_ginkel — Tue, 13 Dec 2011 08:04:05 GMT

Right, a default or an initial value (with an expression) is not implemented.
So if you would be willing to contribute a patch that would be great.
Maybe you can use an attribute name like default that could hold a static String or an expression?

Sounds good. I'll open a JIRA issue and attach a patch as soon as it is ready.

Regards,
Thilo

Re: Default values for Activiti form properties

thilo_ginkel — Wed, 14 Dec 2011 15:55:01 GMT

JIRA: http://jira.codehaus.org/browse/ACT-1028

My current patch candidate (attached to the JIRA issue above) makes a couple of assumptions:

Providing a required property on submitTaskFormData is no longer mandatory iff a default is maintained (in this case the default is saved)

If the default expression returns a java.lang.String, this is result is directly set as form property instead of routing it through the FormType for conversion

OTOH, when applying the form property default in submitFormProperty, routing it through convertFormValueToModelValue is strictly required

I tried to mimic the code style already used in FormPropertyHandler, but due to the fact that white space around operators was already used inconsistently, I had to go for one of them. 😉

I'd appreciate your feedback.

Thanks,
Thilo

Re: Default values for Activiti form properties

backslash — Mon, 30 Apr 2012 16:38:53 GMT

Hello guys,
sorry for reviving old topic. I was looking for exactly the same thing as thilo.ginkel and then I discovered that the patch(and also Activiti 5.9) is only working for UserTask forms and not for StartEvent forms. The reason is obvious from the source code. The whole default value assignment is under "execution != null" test, which evaluates to false because the process did not started yet.

I had make a simple modification to the logic and its working for me now. But I am new to Activiti development, so I dont really know if I should create new JIRA or update the aforementioned.

Re: Default values for Activiti form properties

trademak — Wed, 02 May 2012 07:52:35 GMT

Hi,

Please reopen the current JIRA and attach your patch to it.

Thanks,

Re: Default values for Activiti form properties

hheg8837 — Tue, 17 Jul 2012 16:31:59 GMT

We also desperately need working default value fields in Activiti Explorer …

It would be very nice if there was a bit feedback on this issue …

All the best,
Thomas

Re: Default values for Activiti form properties

frederikherema1 — Wed, 18 Jul 2012 06:24:28 GMT

I ran into this kind of thing before. Since the start-form is populated BEFORE the process starts, there is no execution. This may not sound like a big deal, but the form-property values are created using expressions. You can't evaluate an expression agains an execution if there is no execution yet.

The ExpressionManager expects a VariableScope to resolve variables agianst. We could add a dummy-scope which contains no variables, allowing the defaults to be initialized even without an expression. Although this is a bit fishy (implementation detail), this should get fixed. I'll look into it

http://jira.codehaus.org/browse/ACT-1028

Re: Default values for Activiti form properties

frederikherema1 — Wed, 18 Jul 2012 07:38:47 GMT

Added solution for this issue + included tests. Checked in on trunk, will be in 5.10 (https://fisheye.codehaus.org/changelog/activiti?cs=3555)

Re: Default values for Activiti form properties

hheg8837 — Wed, 18 Jul 2012 08:03:29 GMT

Thank you very much!

Re: Default values for Activiti form properties

micharg — Mon, 23 Jun 2014 16:40:15 GMT

I think activiti-bpmn-extensions-5.x.xsd needs also updating to support the attribute default.

Re: Default values for Activiti form properties

ddeligeo — Fri, 26 Feb 2016 17:31:35 GMT

Hey guys, is this feature broken again for StartEvent forms? I'm pretty new to Activiti, and have only used version 5.19, but I'm currently not able to retrieve the default value of a string form property associated with the StartEvent of a yet-to-be instantiated process definition. I also notice that, when I start the process directly through Explorer, the value is not defaulted in the form field. Seems to work fine for UserTasks, though. Of note, but probably not related, is that I'm only using the ReST API to interact with Activiti.

Thanks.

Re: Default values for Activiti form properties

jbarrez — Tue, 01 Mar 2016 20:46:02 GMT

A unit test or a combination of REST calls where you can see it going wrong would help here.
I don't know anything broken in this area … but you never know of course.