Forms

There are some changes to forms in version 5.xTIBCO BPM Enterprise, for example, there are some changes to get and set methods. Unless stated otherwise, when importing a pre-version 5.x project into version 5.x TIBCO Business Studio - BPM Edition that use scripts that contain any of the following features, problem markers are generated that you must fix.

There are also changes to business object model data types and scripting that impact forms, for example changes to business object model data types. See Business Object Model Data Types and Scripting.

Scripting API changes

  • Script actions, computation actions and validation scripts are all migrated automatically. External JavaScript files must be migrated manually.
  • There are some changes to get and set methods. Previously, properties used to be read or written using a get or set method respectively. Now, such get/set method pairs have been replaced by direct properties, which can be used as lvalues (to write them) or rvalues (to read them). Read-only properties never had a set method, and such properties cannot be used as lvalues. For a full list of the new properties and remaining methods, see "API for Scripting" in the TIBCO Business Studio™ - BPM Edition Forms User's Guide. <obj-expr>.getXxx() and <obj-expr>.setXxx(<value-expr>) calls are automatically migrated to use property access syntax <obj-expr>.xxx and <obj-expr>.xxx = <value-expr> respectively.
  • Multi-valued structured-type properties are now JavaScript Array objects, not List objects. Most List method calls are automatically migrated to use the corresponding Array API. See List.iterator() below for exceptions to this.
  • Multi-valued simple-type values can no longer be assigned.
  • In pre-version 5.x, field values could be accessed using f.controlName. In version 5.x, f.xxx and f[<expr>] are replaced by control.xxx.value and control[<expr>].value, respectively.
  • In pre-version 5.x parameter values could be accessed using p.paramName. In version 5.x, p.xxx and p[<expr>] are replaced by data.[expr] and data[xxx], respectively.

CSS Best Practice

Version 5.x TIBCO BPM Enterprise now enforces CSS best practice, by removing all the deprecated configuration properties that used to control rendering of form components by non-CSS means. Following import of a pre-version 5.x project, any such properties (for example, font size, weight, color, and so on,) must be re-applied using pure CSS techniques. As part of this, Font and Layout property tabs and their associated property sections have been removed.

Resource/Model Name Length

You can no longer use long names for your resource/models. If you have used long names, when importing to version 5.x, you will receive problem markers that you will need to fix.

Duration Forms Component Type No Longer Supported

In pre-version 5.x TIBCO BPM Enterprise, the duration control allowed the users to specify a duration using a configurable set of temporal units. The duration control is no longer supported in version 5.x.

Custom Controls API changes

The API for custom controls has changed to use direct property access instead of get/set method calls. Custom controls supply a JavaScript wrapper script which (in common with all external JavaScript resources) is not migrated. You must migrate the JavaScript wrapper script manually. See "Custom Controls" in the TIBCO Business Studio™ - BPM Edition Forms User's Guide.

List.iterator()

For List.iterator() and all calls on the resulting Iterator object such as hasNext(), next(), add(), remove() and so on, are not automatically migrated. You must manually refactor any code that uses List.iterator().