Form Field Usage at Action Does Not Match Field's Default Action Usage

Metastorm

The information in this article applies to:

Product: Metastorm BPM
Version: 7.x

Issue

• Unless it is changed, the default action usage for a calculated form field is read-only and for a field associated with a variable it is optional.

  The issue is that if a field is added to a form and the default action usage is changed, this usage will be reflected at the action only if the form is selected for the action after the field was added. Here's an example:

  1. A new form, Form2, is added to a procedure. Calculated field Text2 is added to Form2, and the default action usage is changed to hidden. Form2 is then selected for use with Action2. At Action2, the usage for Text2 is hidden, as expected.

  2. Next, calculated field Text3 is added to Form2. The default action usage is again changed to hidden. At Action2, the usage for Text2 is read-only, which is incorrect. If Form2 were now associated with Action3, Text2 and Text3 would have the correct usage of hidden at Action3.

  3. Using a field associated with a variable exhibits the same behavior as the example above.

Resolution

• This is a known issue. The workaround is to manually change the field usage at actions for new fields added to forms already in use at those actions if the usage has been changed from the default.