Getting Started#
Basic Concept#
When files from external users need to be processed in internal business systems, staff may need to review each uploaded file and move it to a different location based on the customer, project, or file type.
For example, if multiple external users upload contracts, images, reports, and data files to a shared upload area, staff must review the file name, upload information, and file type, then route each file to the appropriate business system or project folder.
As the number of uploaded files and external users grows, so does the work required to determine who each file belongs to, which project should process it, and which internal system should receive it.
With INNORIX Flow, files uploaded by external users can be received in one intake environment, classified by customer, project, or file type according to configured conditions, and automatically transferred to internal business systems.
External Users
│
│ Upload Files
▼
Upload Workspace
│
▼
Classification Flow
│
┌────┼──────────────┐
▼ ▼ ▼
Customer A Project B File Type C
│ │ │
▼ ▼ ▼
CRM / Folder Project System Processing SystemThis creates a file-processing flow from external file upload → file information review → classification rule application → internal system selection → file transfer → result verification.
Classification Criteria#
Files uploaded from external sources may not all belong to the same workflow.
For example, files for different customers may need to be processed in different business systems, while contracts, images, and data files within the same project may need to be sent to different work environments.
Classification can therefore use both the uploader and file characteristics or business rules.
Uploaded File
│
▼
┌─────────────────────┐
│ Classification Rules │
└──────────┬──────────┘
│
┌───────┼────────┐
▼ ▼ ▼
Customer Project File Type
│ │ │
└───────┼────────┘
▼
Target System| Classification Criteria | How It Is Used |
|---|---|
| Customer | Send to a customer-specific business system or storage location |
| Project | Route to a project-specific workspace |
| File Type | Process by type, such as documents, images, or data |
| File Name | Select a target based on configured naming rules |
| Upload Location | Determine the workflow based on the upload path |
For example, files can be classified by customer-specific upload folders, with .pdf files sent automatically to a document management system and .csv files sent to a data-processing environment.
Even when a single upload area is used, the actual internal processing environment can be separated according to file conditions.
Processing Structure#
Instead of sending every file to the same internal system, automatic classification connects rules to Targets so multiple processing paths can be configured within a single Flow.
Incoming Files
│
▼
Rule Evaluation
│
┌───────────────┼────────────────┐
│ │ │
▼ ▼ ▼
Customer Project File Type
│ │ │
▼ ▼ ▼
Customer System Project Folder Processing ServerThis replaces manual reclassification after file receipt by routing files to the required internal environment according to predefined criteria.
Business Teams#
File Intake#
Business teams can review files uploaded by external users in a single intake environment.
For example, when customers, partners, or other external contacts upload required files, internal staff can review submissions from a designated upload area instead of checking multiple emails or shared folders.
During file intake, the following information can be reviewed.
| Item | Details |
|---|---|
| Uploaded By | External user who uploaded the file |
| File Name | Identifies the uploaded file |
| File Type | Document, image, or data file |
| Upload Time | Time the file was received |
| Classification Status | Status before or during transfer to the internal system |
| Processing Result | Whether processing completed successfully or requires review |
Business teams can track how received files are being classified and continue follow-up work on specific files when needed.
Verify Processing#
After a file is classified automatically, you can verify that it was applied successfully to the internal system that handles the actual work.
For example, after files are transferred to customer-specific workspaces, staff can begin review, or continue the next task using files delivered to a project system.
File Uploaded
│
▼
Auto Classification
│
▼
Internal Workspace
│
├── Review
├── Approval
└── Next TaskAfter the file is applied to the internal system, it can continue into workflows like the following.
| Processing Result | Follow-up Work |
|---|---|
| Applied to Customer Workspace | Review customer-related work |
| Project Classification Complete | Project owner review |
| Document File Applied | Review or approval |
| Data File Applied | Analysis or processing |
| Additional Review Required | Review by the assigned staff, then reprocess |
This connects external file intake with the start of internal work in a single file flow.
IT Engineers#
Receive Environment#
To configure automatic classification, first prepare an intake environment where external users can upload files.
External users can share the same upload area, or separate upload locations can be configured by customer or business purpose.
External Upload
│
├── Customer A
│ └── /incoming/customer-a/
│
├── Customer B
│ └── /incoming/customer-b/
│
└── General Upload
└── /incoming/general/The receive environment can include the following settings.
| Configuration Item | Settings |
|---|---|
| Upload Location | Path where external files are received |
| Access Scope | Where external users are allowed to upload |
| File Conditions | File types to allow or classify |
| Identification Information | Criteria used to identify the customer or workflow |
| Source | File intake environment monitored by the Flow |
For example, external users can upload files only to designated locations, while an internal Flow starts the next operation when a new file appears in that location.
Classification Rules#
Before transferring received files to internal systems, define how they should be classified.
A classification flow can use a single rule or combine multiple conditions such as customer, project, and file type.
Incoming File
│
▼
┌───────────────────────┐
│ Customer = Customer A │
│ Project = Alpha │
│ Type = CSV │
└───────────┬───────────┘
▼
Data ProcessingFor example, you can configure classification rules like the following.
| Condition | Classification Target |
|---|---|
| Customer A | Customer A business system |
| Project Alpha | Alpha project workspace |
.pdf |
Document management system |
.jpg, .png |
Image-processing environment |
.csv, .json |
Data-processing server |
When multiple conditions are used, the flow can first identify the customer, then evaluate the project and file type for more specific routing.
This allows files from a single intake path to branch according to the actual internal processing structure.
Flow Setup#
Connecting classification conditions to Targets automatically routes uploaded files to the required internal systems.
Upload Source
│
▼
Incoming Files
│
▼
Classification Flow
│
┌─────────────┼─────────────┐
▼ ▼ ▼
Customer A Project B Data Files
│ │ │
▼ ▼ ▼
Internal A Workspace B Data ServerA Flow can be configured in the following ways depending on the business structure.
| Configuration Method | Use |
|---|---|
| Classify by Customer | Send each customer's files to a designated internal environment |
| Classify by Project | Send files to project-specific workspaces |
| Classify by Type | Select a Target by file extension and type |
| Multi-stage Classification | Identify the customer first, then classify further by project or type |
| Common Storage | Store all files in a central repository before routing them onward |
For example, all uploaded files can first be recorded in a central storage location, then transferred to the actual processing system according to classification rules.
Automatic Execution#
When an external user uploads a file, the classification Flow can run automatically based on a new-file event or other configured condition.
Files can be processed immediately after upload or classified in a batch at a scheduled time after multiple files are ready.
External Upload
│
▼
┌──────────────────┐
│ Execution Trigger │
└────────┬─────────┘
│
┌─────┼───────────┐
▼ ▼ ▼
New File Schedule Request
│ │ │
└─────┼───────────┘
▼
Classification Run| Execution Condition | Use |
|---|---|
| New File | Run automatically when a new file is uploaded |
| Date/Time | Process files in a batch at a specified time |
| After Transfer | Run after a previous transfer completes |
| URL Request | Run in response to a request from an external system |
| Manual Run | Run manually by an operator |
Defining execution conditions around file creation and business processing connects file intake through delivery to internal systems automatically.
Verify Results#
After classification runs, review the overall file-processing status and classification results in Runs.
Selecting a specific job shows which files were transferred to which Targets and which conditions were applied.
Each Run can display the following information.
| Item | Details |
|---|---|
| Source | Location where the external file was uploaded |
| Classification | Classification conditions that were applied |
| Target | Internal system that received the file |
| Total Files | Number of files to process |
| Total Size | Total file size |
| Progress | Current processing progress |
| Status | Completed, in progress, or requires review |
| Started | Job start time |
| Completed | Job completion time |
This makes it possible to review per-file processing results and actual transfer destinations even when files from multiple external users arrive at the same time.
Exception Handling#
If some files do not match the classification rules or are not transferred successfully to the specified internal system, review their processing status in the Run details.
For example, if a newly uploaded file has an extension that is not covered by an existing rule, or a Target has an access problem, review the affected file and the conditions that were applied.
Classification Run
│
▼
Result Review
│
┌──────┼─────────┐
▼ ▼ ▼
A ✓ B ! C ✓
│
▼
View Details
│
┌──────┼──────────────┐
▼ ▼ ▼
Rule File Info Target
│
└──────┬───────┘
▼
Adjust
│
▼
Retry
│
▼
Internal SystemWhen a problem occurs, review the following items together.
| Item | Details | Follow-up Action |
|---|---|---|
| File Information | Name, type, and upload location | Review classification conditions |
| Classification Rules | Applied customer, project, and file conditions | Adjust rules |
| Source | Status of the file intake environment | Review the upload path |
| Target | Connection state of the internal system | Review the target environment |
| Access Permissions | Whether files can be read and saved | Review permission settings |
| Execution History | Per-file processing results and Run information | Rerun the required operation |
After the issue is resolved, rerun only files that were not classified successfully or operations that did not reach a specific Target instead of reprocessing every external file.
This creates an automated classification flow from external file upload → receive-environment review → classification by customer, project, and file type → transfer to internal business systems → handoff to staff workflows → result verification → exception handling.
This lets you manage diverse incoming files in a single receive environment while automatically classifying them according to the actual internal business structure and routing them to the required systems and workspaces.