GET workflow configs API incorrectly returns nullable properties

In WorkflowTransitionRules, postFunctions, conditions, and validators should all be non-optional properties, however they can now potentially be returned nullable.

Hi @shorvathhunt,

I tested this and saw fields documented as required are missing in the response. For this reason, I’ve created ACJIRA-2323.

Do you know if the behaviour of the API has changed recently such that the fields are now omitted when previously they were all present, or do we just need to fix our API documentation?


Hey @dmorrow, this appears to be a recent regression; we have some codecs set up that check the runtime types of foreign data and they only started flagging this a week or so ago.