Process and Form DesignersPermanent link for this heading

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

ProcessesPermanent link for this heading

  • The signdialogtitle, signdialogheading and signdialogdescription process parameters can be used to customize the texts of the sign dialog. For multilingual strings, a LanguageStringList can be provided.
    For example: process.SetProcessParameter("signdialogtitle", "Sign");
  • For ad hoc process templates, the applicability can be defined in the same way as for BPMN processes (Applicable for, Object Class/Category of the File, Object Class/Category of the Teamroom).

FormsPermanent link for this heading

When you define a form, the following new options are available:


  • In the form metadata, on the “Advanced” tab, in the Available Processing States field, additional processing states can be selected to be available in the Processing State default property.
  • In the form metadata, on the “Advanced” tab, a prepare commit expression can be defined.
  • Template categories (component objects) can be used as base forms. When template categories of installed software components change, the forms based on them are marked as “Changed After Release”. These forms must be re-released to apply the changes.
  • An existing, not released category can be converted into a form. Thus, no migration is necessary if the category is to be extended with user-defined fields.

Fields of a Form

  • Fields of type “Password” can be defined.
  • The Multilingual Name property can be selected as a default property.
  • For fields, actions or app.ducx expressions for the following events can be defined on the “Advanced” tab:
    • Read Display String
    • Handle Copying of Field
    • Handle Construction of Field
    • Handle Destruction of Field
  • For fields, you can specify on the “Display” tab whether they should be displayed in a new row. Additionally, the width for fields displayed side by side can be defined.
  • Defined enumeration types (radio buttons or combo box) can be referenced in the Existing Enumeration Type field and thus reused.
  • In item lists of compound type, the COOSYSTEM@1.1:LanguageStringList default type can be selected.
  • If the form has already been released, the type of a field can be changed to compatible types (e.g. from string to hyperlink or password).