cancel
Showing results for 
Search instead for 
Did you mean: 

Required properties not enforced on custom transitions

rand
Champ in-the-making
Champ in-the-making
Hi everybody. I'm facing the following problem :

One of the steps of my workflow has two transitions leaving it. When the associated task is displayed in the task dialog, two buttons show up as expected.
Additionally, I've defined a required property in the task model.

The problem is, leaving this property blank disables the standard Save Changes button, but not the two custom ones, and the user can leave by any of these transitions without filling the required property.

Is this a bug, or have I missed something in the configuration ?
3 REPLIES 3

davidc
Star Contributor
Star Contributor
The Save Changes button will remain inactive until all mandatory properties are filled in.  A mandatory property must have the <mandatory> element defined against it in the content model definition.  This is also true for your custom properties.

However, you may have uncovered a bug with the transition buttons.  I think these remain active regardless of whether mandatory properties have been provided or not.

I'll raise a JIRA issue for the transition buttons.

In the mean-time, if you're still having problems with the Save Changes button could you post your content model definition and process definition files and I'll take a look.

rand
Champ in-the-making
Champ in-the-making
I'm sorry I wasn't clear in my first post (maybe 'cause I'm french  :? ) :

The behaviour of the Save Changes button was the one I expected, and my problem was indeed that the two "transition buttons" were not behaving the same !

Thanks for your reply anyway, you answered my question :]

Rand

davidc
Star Contributor
Star Contributor