A comprehensive guide to integrating document creation from templates, managing uploads, and configuring workflows for document processing.
Document generation
..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.Preview document
Explanation of MVEL code
Upload document
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: