eworkGetField and eworkSetField Fail Without Form Segment Name Prefix

Metastorm

The information in this article applies to:

Product: Metastorm BPM
Version: 9.0

Issue

• When used with a form segment, eworkGetField and eworkSetField fail in a client-side script, even though the syntax specified in the Designer User Guide is used.

Resolution

• This is a known issue.

• The workaround is to prefix the field name with the form segment name. For example, a form segment named FormSegment1 contains a text field named Text1. The form segment is dragged from the Toolbox onto a form. On the form, the name of the form segment is FormSegmentReference1.

  If eworkGetField and eworkSetField are called from the form, e.g. by clicking a button, the following behavior is seen:

  FAIL:
  eworkGetField( "TextField1", "" );
  eworkSetField( "TextField1", "", "test" );

  WORK:
  eworkGetField( "FormSegmentReference1TextField1", "" );
  eworkSetField( "FormSegmentReference1TextField1", "", "test" );