BooleanFormPropertyRenderer renders to Button

[bernd_ruecker]

A boolean Form Property renders to a button in the current explorer.

This is completly unintuitive and actually I have no idea how to control the boolean flag now on the gui 😉 Can you help me out? I did find the BooleanFormPropertyRenderer and see how it is rendered, but not how the value is written back quickly.

And can we change this to a checkbox which is what I would expect here?

Cheers
Bernd

[frederikherema1]

Hi Bernd,

Should be a checkbox indeed, I'll fix this… The value of the button is actually always false (unless it's a toggle button, which can have it's state changed). No error was thrown since the Button Field value type is Boolean.

[bernd_ruecker]

Thanks!

[meditel]

Hi,

Is that available on Trunk / Branch ? is it possible to build a version with this correction ?

Best Regards,
Meditel

[bernd_ruecker]

Hi Meditel.

It is committed in trunk and will be released with Activiti 5.8. You can build a release from the trunk head yourself, sure 🙂

Cheers
Bernd

[meditel]

Hi,

I have build explorer2 from Trunk and successfully deployed.
I have added a checkBox to a form like this :

<activiti:formProperty id="test" name="test" type="boolean" variable="false" required="true" readable="true" writable="true"></activiti:formProperty>

The boolean type is perfectly rendered as a checkBox, but i have this exception :
Cause: java.lang.IllegalArgumentException: CheckBox only accepts Boolean values
What is going wrong ?

Best Regards,
Meditel

[meditel]

I tried also without the variable="false" and got the same exception

[frederikherema1]

The variable is not the VALUE, but the name of the variable to use for that property. So you should have a variable with name "test" of type boolean, don't specify the "variable" attribute.

[meditel]

Hi,

'variable' attribute is automatically filled by the Eclipse plugin, so this might be a plugin bug.
Eclipse plugin should put 'value' instead of 'variable'.

Best Regards,
Meditel

[trademak]

Hi,

Right this is something that needs to be improved in the Eclipse Designer.
It's however not so straightforward to solve this, but I'll have a look at it.

Best regards,