This guide provides a detailed walkthrough for seamlessly integrating document uploads into a process definition by incorporating a user task node with an Upload action. This feature empowers users to actively engage with the process and select the desired file for upload.
..in
topic to initiate a request in the Process Engine. It includes information for generating an βAccountCreationβ document with a custom ID β119237β in English. Data specifies client details extracted dynamically from user input (first name, last name, age, country) and company information (name, registration date).
..out
Kafka topic, where the Process Engine expects a reply. It contains details about the generated PDF file corresponding to the custom ID β119237β and the βAccountCreationβ template. The response provides file-related information such as file ID, document type, document label, storage path, download path, number of pages, and any potential errors (null if none). The paths provided in the response facilitate access and download of the generated PDF file.
Explanation of MVEL code
ai.flowx.updates.document.html.persist.v1
and its key: uploadedDocument
.persist
topics.
Configuring the File Upload action
ai.flowx.in.document.persist.v1
.KafkaTopicsHealthCheckIndicator
line and then details β configuration β topic β document β persist. Here will find the in and out topics for persisting (uploading documents).BULK
.${processInstanceId}
(it will be replaced at runtime with a generated process instance id).callbacksForAction
- the value of this key is a string that specifies a callback action associated with the βupload_documentβ destination ID (node). This is part of an event-driven system (Kafka send action) where this callback will be called once the βupload_documentβ action is completed.Configuring the Business Rule action
Configuring the Send Data to User Interface action
..in
topic:
..out
topic with details about the processed document: