Metadata card required field

Question

Hi All,

We have objects with workflows and automatic state transitions that are in various stages of workflow.
When our metadata requirement for object changes - for example we add an additional property and make it mandatory the only way to make this work without causing existing objects to fail transition is by using metadata card configuration. If the property is set as required for that class, automatic transitions fails.
We need the required property to be made mandatory at the first stage of workflow only.
So the rule is set up to filter the state and make the property mandatory. This does not work.

Is there a bug or something i might have missed?

thanks

Joonas Linkola · Answer

It's a known limitation if the user makes the transition from the task pane instead of the metadata card. Any hard business rules should be enforced with server-side checks even if you have metadata card configurations for enhanced usability. From the configuration guide:

Joonas Linkola · Answer

Metadata card configurations are a client feature, only applied when the metadata card is displayed to the user, so they do not affect any server-side operations such as automatic state transitions. There is more information about this in the introduction of the metadata card configuration guide . One option you could try is to set a post-condition for the workflow state, e.g. " is not empty". I haven't tested how this affects automatic state transitions, though.

Metadata card required field

Top Replies