RE: Generic upload documents component

Megha Ramnani — Fri, 23 May 2025 10:22:04 GMT

Hi Tomislav Fuček

This is a common scenario, and it's definitely feasible to design a generic, scalable document upload component. Here's a recommended approach:

1. Use Configuration Tables:
Store rules like allowed document types, file extensions, upload limits, and task/organization mappings in a database. This makes your logic data-driven and easy to update.

2. Decision Rules:
Use decision tables or expression rules to fetch validation logic dynamically based on task and organization.

3. Reusable Component:
Build a reusable upload interface that takes task name and organization as inputs, fetches config, and enforces rules (e.g., extension checks, single vs. multiple upload).

4. Centralized Validation:
Create one expression rule to handle all upload validations using the config data.

This approach improves maintainability and makes it easy to adapt for new organizations or countries.

RE: Generic upload documents component

Stefan Helzle — Fri, 23 May 2025 08:54:51 GMT

Feels like this is more about generic validations, than a generic file upload component. A simple approach could be to create a main validation expression, which takes all the relevant parameters as input, and then branches out to separate and more specific validation expressions.