Creating and uploading a new document

• adminPath: Base URL for the admin path.

adminPath = "https://admin-main.playground.flowxai.dev/document/";

• processInstanceId: Extracts the process instance ID from the input. Assumes an input structure with a generatedDocuments property containing a generatedFiles property. Retrieves the keys, converts them to an array, and selects the first element.

processInstanceId = input.?generatedDocuments.?generatedFiles.keySet().toArray()[0];

• downloadPath: Retrieves the downloadPath property using the obtained processInstanceId.

downloadPath = input.?generatedDocuments.?generatedFiles.?get(processInstanceId).Company_Client_Document.downloadPath;`

• if condition: Checks if downloadPath is not null and constructs a new object in the output map.

if(downloadPath != null){
    output.put("generatedDocuments", {
        "filePath" : adminPath + downloadPath
    });
}

​

Action edit

• Action Type: Set to Upload File.
• Trigger Type: Choose Manual to allow user-triggered action.
• Required Type: Set it as Optional.
• Repeatable: Check this option if the action can be triggered multiple times.

​

Parameters

• Topics: Kafka topic where the file will be posted, in this example ai.flowx.in.document.persist.v1.

To identify your defined topics in your current environment, follow the next steps:

• From the FLOWX.AI main screen, navigate to the Platform Status menu at the bottom of the left sidebar.
• In the FLOWX Components list, scroll to the document-plugin-mngt line and press the eye icon on the right side.
• In the details screen, expand the KafkaTopicsHealthCheckIndicator line and then details → configuration → topic → document → persist. Here will find the in and out topics for persisting (uploading documents).

• Document Type: Metadata for the document plugin, in this example BULK.
• Folder: Configure a value by which the file will be identified, in this example it will be the${processInstanceId} (it will be replaced at runtime with a generated process instance id).
• Advanced configuration (Show headers): This represents a JSON value that will be sent on the headers of the Kafka message, in this example:

{"processInstanceId": ${processInstanceId}, "destinationId": "upload_document", "callbacksForAction": "uploadDocument"}`

​

Data to send

• Keys: Used when data is sent from the frontend via an action for data validation.

• Order: Set to 1 so it will be processed before the second child action.
• Action Type: Set to Upload File.
• Trigger Type: Choose Automatic, it does not need user intervention.
• Required Type: Set as Mandatory.
• Repeatable: Check this option if the action can be triggered multiple times.

• Language: In this example we will use MVEL.
• Body Message: Fill in the body of the message request by applying a logic similar to the one utilized in configuring the “preview_document” node. Establish a path that will be later employed to showcase the uploaded document within a preview UI component.

adminPath = "https://admin-main.playground.flowxai.dev/document/";
downloadPath = input.?uploadedDocument.?downloadPath;

if(downloadPath != null){
    output.put("uploadedDocument", {
        "filePath" : adminPath + downloadPath
    });
}

• Order: Set to 2 so it will be processed after the previously created Business Rule.
• Action Type: Set to Send data to user interface.
• Trigger Type: Choose Automatic, it does not need user intervention.
• Required Type: Set as Mandatory.
• Repeatable: Check this option if the action can be triggered multiple times.

• Message Type: Set to Default.
• Body Message: Populate the body of the message request; this object will be utilized to bind it to the document preview UI element.

{
    "uploadedDocument": {
        "filePath": "${uploadedDocument.filePath}"
    }
}

• Target Process: Used to specify to what running process instance should this message be sent - set to Active Process.