Getting Started
Core Concepts
Automatically run recurring file tasks according to schedules and conditions
Business operations continuously involve tasks that are processed in the same way, such as daily reports, regularly collected data, and files that are repeatedly deployed.
Recurring task automation configures the files to process, destination locations, and execution conditions so file tasks run automatically according to a defined flow.
For example, you can transfer files at a specified time every day, or automatically run the next file-processing task when a new file becomes available in a specific folder.
By configuring an automation flow, recurring file tasks can continue to run according to the criteria defined for the business operation.
Automation Flow
Automatically connect everything from execution conditions to file processing and result confirmation
Recurring task automation determines when to start a task, checks for files that meet the conditions, and runs tasks in the configured order.
① Check Execution Conditions
↓
② Check Target Files
↓
③ Run File Task
↓
④ Run Next Task
↓
⑤ Check Results
For example, a task scheduled to run every morning starts at the specified time and processes the configured files. Tasks triggered by file creation or changes automatically continue from the point when the target file becomes ready through the next task.
Connecting execution conditions and task order this way lets you manage recurring file work as a single automation flow.
Business Impact
Reduce repetitive file management and focus on results
Recurring file work repeatedly involves checking the same files, transferring them to defined locations, and running the next task.
With automation, file processing proceeds according to predefined conditions and task order. Instead of handling repetitive execution steps, operators can review processed results and use them for the next task.
| Category | Manual Processing | Recurring Task Automation |
|---|---|---|
| Task Start | Operator starts the task when needed | Starts automatically according to schedules and conditions |
| File Processing | Check files and targets for each task | Process automatically according to configured criteria |
| Task Order | Run required tasks manually in sequence | Run each stage according to the configured flow |
| Result Usage | Prepare for the next task after processing | Use completed files immediately for the next task |
| Work Management | Review execution details for each task | Review work status based on execution results |
Automation organizes recurring file-processing steps into a business workflow and lets operators focus on the results needed for the next task.
Business Teams
Review recurring task results and use completed files in business operations
Automation Usage
Prepare business files and use automatically processed results
Business teams prepare files for automation tasks at the designated work location.
For example, saving a daily report or a regularly generated result file in a designated folder triggers the automation according to the configured schedule or file state.
File transfer and follow-up processing proceed according to the configured flow, allowing business teams to review processed files and use them for the next task.
| Work | Automation Usage |
|---|---|
| Daily Report | Automatically transfer after the report is saved |
| Recurring Data | Automatically collect at the specified time |
| Result File | Automatically apply to the work location after processing is complete |
Business teams can manage frequently used files at defined locations and take advantage of automated file flows.
Job Status
Check currently running automation tasks and processing status
Business teams can check the current status of automatically executed file tasks.
Review running tasks and recently completed tasks, and when needed, check the processed files together with the current progress.
The screen provides the following information.
| Review Item | Use |
|---|---|
| Task Name | Check which business task is currently being processed |
| Progress Status | Check task progress |
| Progress | Check the current processing scope |
| Processed Files | Review files processed automatically |
| Execution Time | Check when the task was executed |
Business teams can prepare for the next task by checking the processing status of the tasks and files currently required for their work.
Completed Files
Use automatically prepared files immediately for the next task
When an automation task completes, the processed files are applied to the designated work location.
Business teams can review completed files and use them for the next tasks, such as review, approval, sharing, or analysis.
For example, when a daily business report is automatically applied to a designated workspace, the responsible user can review the file and continue the review process.
Automated File Processing
↓
Confirm Completion Result
↓
Review File
↓
Review · Share · Approve
↓
Next Task
Automated file processing prepares the files needed for the next task at a defined location, connecting the workflow naturally.
Work Management
Manage recurring task results at a glance
As automation tasks run repeatedly, business teams can review work status based on accumulated execution results.
For example, reviewing the results of a daily report-processing task shows when files became available and which result files can currently be used.
| Review Details | Business Use |
|---|---|
| Recent Execution Results | Review the latest business results |
| Completed Files | Identify files currently available for use |
| Execution Time | Review when the work was processed |
| Accumulated Execution History | Manage the status of recurring work |
Instead of changing automation settings, business teams can review and use recurring work based on execution results and completed files.
IT Engineers
Configure and operate execution conditions and processing flows for recurring tasks
Environment Connection
Configure the systems and file locations used for recurring tasks
IT engineers connect the servers, PCs, storage systems, and file paths used by automation tasks.
Specify the Source where files become ready and the Target where processing results are applied. When needed, multiple systems can be connected in a single Flow.
| Role | Configuration |
|---|---|
| Source | System and path from which files are collected |
| Processing | File-processing task |
| Target | System and path where processing results are applied |
This environment provides the foundation for configuring file flow and processing order in automation tasks.
Execution Conditions
Configure how tasks start based on schedules and file status
After the automation environment is ready, IT engineers configure the conditions that start each task.
Use execution criteria suited to the business environment, such as a specified date and time, file creation or changes, completion of a previous task, or an external service request.
| Execution Criteria | Purpose |
|---|---|
| Date/Time | Run the task on the specified schedule |
| File Change | Run based on changes in file state |
| After Transfer | Run the next stage after the previous task completes |
| URL Request | Run in response to an external system request |
Configure target files using conditions such as file path, name, or extension to define the processing scope of the automation task.
Flow Configuration
Connect file transfer and follow-up tasks in execution order
After configuring execution conditions, connect tasks such as file transfer, processing, and result storage in the Flow Canvas.
Each task can be connected to the next based on the execution result of the previous stage, allowing file-processing processes across multiple systems to be configured as a single flow.
Trigger
↓
File Transfer
↓
Processing
↓
Result Storage
↓
Next Flow
IT engineers can connect task stages according to the required processing order for each business operation and configure the complete file flow for recurring execution.
Result Analysis
Analyze the status and processing results of recurring tasks
Automatically executed tasks provide execution history and detailed processing results in Runs.
Each Run shows the conditions that started the task, Source, Target, number of processed files, total processed volume, execution time, and status.
| Review Item | Details |
|---|---|
| Trigger | Task start condition |
| Source | Location where files are prepared |
| Target | Location where results are applied |
| Files | Number of processed files |
| Size | Total processing volume |
| Time | Execution time |
| Status | Task status |
Reviewing accumulated execution history lets you analyze and manage recurring task patterns and file-processing results according to the business environment.
Exception Handling
Review task status from execution records and process tasks again when needed
When a task requires additional review, IT engineers use Runs and Audit Log to check the execution process and processing status.
You can inspect the current task environment based on execution conditions, system connections, file paths, access scope, target files, and task order.
Review Execution Record
↓
Check Task Status
↓
Check Execution Conditions
↓
Check System · Path · File Status
↓
Adjust Settings or Environment
↓
Rerun Task
↓
Check Processing Result
| Inspection Item | Details |
|---|---|
| Execution Conditions | Schedule and Trigger settings |
| System Connection | Source and Target connection status |
| File Path | Processing target location |
| Access Scope | File-processing permissions |
| Execution Record | Run and Audit Log |
This separates the roles clearly: business teams focus on using automated results and files in their work, while IT engineers focus on designing the automation environment and managing execution conditions and flows.