Process and Form DesignersPermanent link for this heading

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

  • When initially defining a condition in BPMN process diagrams, you can decide whether you want to define the condition using the condition editor (graphical user interface with predefined properties) or the code editor (app.ducx expression). Subsequent changes will open the corresponding editor directly.
    Note: You can switch from the condition editor to the code editor using the “Open Code Editor” button. In doing so, the condition is taken over, but must be manually converted into a valid app.ducx expression.
  • If an activity such as "Approve", "Release" or "Review" is denied, activities are not executed in BPMN processes, even if they belong to the same multi-instance task.
  • The new activity “Forward for Editing” is available in BPMN process diagrams.
  • The “Release for Usage” activity (only available in BPMN processes) allows a template, form, etc. to be released for usage. In addition, a corresponding signature is applied.
  • Using the “Show Overview of app.ducx Expressions” context menu command, you get an overview of all app.ducx expressions defined in a BPMN process and, if applicable, in the subprocesses. This facilitates troubleshooting in particular.
  • In order to be able to define users stored in a Teamroom property as workflow participants, the following abstract participants are available:
    • Property of the Teamroom of the Object
    • Role by Property of the Teamroom of the Object
  • If a list property is used to define the workflow participants, it is possible to specify whether the activity should be inserted multiple times. Thus, it is possible to create a separate activity instance for each resolved participant or only one activity instance for all participants.
  • Fabasoft app.ducx Expressions stored in expression properties can be displayed in the detail view of lists.
  • For component objects and software components, the full reference is displayed in the Full Reference field to simplify the writing of app.ducx expressions.
  • In BPMN processes, the join type (AND or OR join) can be defined for a converging parallel gateway.
  • When downloading BPMN process diagrams, the following options are available:
    • Download Diagram With Preview
      Downloads the XML representation and preview images of one or more BPMN process diagrams including any sub-processes that may be contained.
    • Download
      Downloads the XML representation of one or more BPMN process diagrams including any sub-processes that may be contained.
    • Upload
      The downloaded BPMN process diagrams can be uploaded again (also in another installation if applicable). Either a single XML file or an entire ZIP file can be uploaded. If a ZIP file is uploaded, existing diagrams can be updated.
  • If you specify a symbol for a form, it will be displayed instead of the object class symbol for objects that have the form assigned.
  • In order to easily translate the multilingual strings of your processes, forms and other customizing objects, they can be exported collectively as a CSV file and imported again. For this purpose, the action "Translations" > "Export" or "Import" is available in app rooms and Teamrooms under “Templates and Presettings” or directly in app configurations.
  • A corresponding status symbol is displayed for changed customizing objects. In the case of compound customizing objects, a status symbol is only displayed if the root object has changed.