![]() ![]() ![]() Communicating with people requires forms to be rendered in some UI technology. Starting a process and completing user tasks is where people are involved into a process. Flowable supports complex Java objects to be stored as process variables like Serializable objects, JPA entities or whole XML documents as Strings. Form propertiesĪll information relevant to a business process is either included in the process variables themselves or referenced through the process variables. In a similar way, a user task can be completed with a form using the following API call: void pleteTaskWithForm(String taskId, String formDefinitionId,Īgain, for more information about form definitions have a look at the Form Engine user guide. The Flowable task application uses this method to start a process instance with a form as well.Īll form values need to be passed in the variables map and an optional form outcome string and process instance name can be provided. When a form definition is defined on (one of) the start event(s) of a process definition, this method can be used to start a process instance with the values filled-in in the start form. Map variables, String processInstanceName) To start a process instance with a start form definition you can use the following API call: ProcessInstance RuntimeService.startProcessInstanceWithForm(String processDefinitionId, String outcome, The FormModel object is a Java object representation of the form definition JSON. Or FormModel TaskService.getTaskFormModel(String taskId) ![]() FormModel RuntimeService.getStartFormModel(String processDefinitionId, String processInstanceId) You can also use the Flowable API to get the form definition JSON yourself. The Flowable task application is able to render an html form from the form definition JSON. Group of people: rendered as a select field where a group from the Identity group table can be selectedĮxpression: rendered as a label and allows you to use JUEL expressions to use variables and/or other dynamic values in the label text People: rendered as a select field where a person from the Identity user table can be selected ![]() Radio buttons: rendered as a radio field with the option values configured in the field definition Number: rendered as a text field, but only allows numeric valuesĭropdown: rendered as a select field with the option values configured in the field definition Multiline text: rendered as a text area field The following form field types are supported: The Form Engine user guide describes the structure of the form definition JSON in full length. Form definitionįull information about the form definitions and Flowable form engine can be found in the Form Engine user guide.įorm definitions can be created with the Flowable Form Designer that’s part of the Flowable Modeler web application, or created by hand with a JSON editor. We support two strategies to work with forms: Built-in form rendering with a form definition (created with the form designer) and external form rendering.įor the external form rendering strategy form properties can be used (that was supported in the Explorer web application in version 5), or a form key definition that points to an external form reference that can be resolved with custom coding. Flowable provides a convenient and flexible way to add forms for the manual steps of your business processes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |