Process and Form Designers

As a process or form designer you can expect the following new feature.

• In user-defined forms, specified field widths are always considered. This can result in gaps if several fields are defined in a line and one or more of them are hidden by visible expressions.
• For user-defined forms, a Filter Expression for Values Within Search can be defined for properties of type “Object”, which is evaluated in the context of a search.
• For an input field or an item list of type “Object” (type of content: forms), a backward linking with another input field or item list of type “Object” can be defined. In the case of backward linking, the other object is automatically referenced in the object entered in the field.
• The help text for user-defined fields can now only be entered as normal text and no longer formatted. If you edit existing user-defined forms, you may need to remove the HTML tags from the help texts.
• The “Import Form” and “Export Form” actions have been replaced by the standard “Upload” and “Download” actions.
• BPMN process usability
  Previously, if a restriction was defined, the process could only be executed on objects that were assigned to one of the listed categories or one of the listed object classes or one of the listed object aspects.
  Now, the usability will be evaluated in the same way as the usability of templates. If a restriction is defined, the process can only be executed on objects that have been assigned one of the listed categories and one of the listed object classes and one of the listed object aspects.
  Note: The same logic is also used for activity definitions, process definitions, escalation definitions and templates for ad hoc processes.