Getting Started#
Core Concept#
Keep Files in the Same State Across Multiple Work Environments
Work files are used across various environments, including individual team members' PCs, department shared folders, and servers. Work folder synchronization connects files so that the state of files used in one folder can be kept the same across other work environments. Even when the same work files are used in multiple locations, the required files can be managed and used in the same state.
┌─────────────────────┐ ┌─────────────────────┐
│ Work PC │ │ Shared Folder │
│ │◀──────────────▶│ │
│ Files │ Keep in Sync │ Files │
└──────────┬──────────┘ └──────────┬──────────┘
│ │
└──────────────────┬────────────────────┘
│
▼
┌──────────────────────────┐
│ Work Folder │
│ Synchronization │
└────────────┬─────────────┘
│
▼
┌──────────────────────────┐
│ Servers · Systems │
└──────────────────────────┘Synchronization Flow#
Automatically Connect the Process from File Changes to Reflection
Work folder synchronization checks the state of files in connected folders and reflects changes between them according to the configured conditions. When a file is created or modified in one folder, the synchronization conditions and processing targets are checked. The changed file is reflected in the connected folder, and changes made in the other folder can be checked and synchronized in the same way.
① File Change
↓
② Check Changes
↓
③ Check Synchronization Conditions
↓
④ Reflect Changes in the Connected Folder
↓
⑤ Check Results
Through this flow, whenever a file changes in any work environment, required changes can be reflected based on the state of the connected folders, and the results can be managed as part of a single workflow.
Workflow Changes#
Reduce File Management and Repetitive Work
When work files are used in multiple locations, each task involves checking the latest files and organizing them in the required locations. Work folder synchronization connects the process after a file changes into a configured workflow.
Before and After Synchronization
| Category | Manual Management | Work Folder Synchronization |
|---|---|---|
| File Check | Check files in multiple locations | Use the latest files from connected locations |
| File Reflection | Manually manage files in the required locations | Automatically reflect changes according to configured conditions |
| Workflow Connection | Prepare files for the next task | Connect to the next task after reflecting changes |
| Repetitive Work | Repeat the same management process | Process automatically according to a defined workflow |
Work folder synchronization connects each work environment where files are used. Users can build workflows that lead from finding and organizing files to actual work, and regularly generated reports and result files can be managed in the same way.
Teams#
Check the Latest Files#
Open the Latest Files Immediately When Starting Work
When the same files are used across multiple work environments, it is important to immediately check the latest files that serve as the basis for the current work when starting a task. With two-way synchronization, changes made in Work Folder A and B are reflected in each other, allowing each user to continue working from the latest file state in their respective folder.
For example, if a proposal is modified in Work Environment A in the morning and work resumes in Work Environment B in the afternoon, the changes are reflected in the synchronized folder. The user can open the latest version of the proposal from the work folder currently in use and continue working immediately.
Check Before Starting Work
| Check Item | Files Needed for Work |
|---|---|
| Previous Work | The file last worked on |
| Changes by Other Users | The latest reflected file |
| Current Work Reference | The file to use now |
Because changes made in Work Folders A and B are reflected in each other, work can continue immediately with the latest file regardless of which folder is used to start the task.
Connect the Workflows#
Carry the File from the Previous Task Directly into the Next Task
Work often continues beyond one person's task, with created files moving on to review, modification, approval, and other subsequent tasks. With two-way synchronization, files modified in each work environment are reflected in each other so the same files can continue to be used.
For example, after the author modifies a report, a reviewer can check the file in another work environment and modify its contents, with the changes then reflected back in the connected folder.
A Workflow That Continues with One File
Write ↕ Report Modification ↕ Review · Modification ↕ Approval ↓
Follow-up Work
By reflecting changes made at each stage of the work, the next task can naturally continue based on the file from the previous task.
Shorten Repetitive Work#
Reduce the Time Spent on Daily File Management
Reports generated daily or materials updated regularly are sometimes used across multiple work environments. With two-way synchronization, files changed in each work environment are reflected in the others, reducing repetitive file management work.
Example of Repetitive Work
┌──────────────────────────┐ ┌──────────────────────────┐
│ Work Environment A │ │ Work Environment B │
└────────────┬─────────────┘ └────────────┬─────────────┘
│ │
▼ ▼
┌──────────────────────────┐ ┌──────────────────────────┐
│ Create Report │ │ Check / Edit Files │
└────────────┬─────────────┘ └────────────┬─────────────┘
│ │
▼ ▼
┌──────────────────────────┐ ◀──────▶ ┌──────────────────────────┐
│ Work Folder A │ Bidirectional │ Work Folder B │
└────────────┬─────────────┘ Synchronization └────────────┬──────────┘
│ │
└──────────────────┬──────────────────────┘
│
▼
┌──────────────────────────────┐
│ Reflect Changes to Each Other│
└──────────────┬───────────────┘
│
▼
┌────────────────────────┐
│ Use in Next Task │
└────────────────────────┘For example, when a daily work report is created in one folder and its contents are checked or modified in another work environment, the changes are also reflected in the connected folder. Users can immediately use the files needed for each task and reduce repetitive file management.
| Work Use Case | Synchronization Flow |
|---|---|
| Daily Report | Create · Modify ↔ Reflect in Work Folder |
| Regular Result Files | File Change ↔ Reflect in Connected Environment |
| Repetitive Data Sharing | Reflect Changes Across Work Environments |
IT Engineer#
Environment Setup#
Connect the Folders to Synchronize
To configure two-way file synchronization, first add the two systems to be connected to the flow and configure the folder to synchronize on each system.
Each system checks for file changes, and when a file is created or modified on one side, the changes are reflected in the folder on the other side according to the configured conditions.
Connect the Two Systems
In Flow Canvas, select the systems to synchronize and place them in the flow. In the screen, the RHEL and Windows systems are connected, and the settings in the center can be used to configure the file synchronization direction and processing conditions between the two systems.
Connecting the two systems enables a two-way file flow that checks and reflects changes between both systems, rather than a simple transfer path that processes files from one side to the other.
Use a screen showing the RHEL and Windows systems placed in Flow Canvas with a Two-way connection configured between them.
Configure the Synchronization Folder on Each System
After connecting the systems, specify the folder to synchronize in each environment.
For example, D:\git\Datasets\install can be configured as the synchronization target on Windows#1, and /data/distribution/install can be configured on CentOS.
Each folder serves both as the location where files are checked and as the location where changes from the other system are reflected.
┌──────────────────────────────┐ ┌──────────────────────────────┐
│ Sync Folder A │ │ Sync Folder B │
└──────────────────────────────┘ └──────────────────────────────┘
│ │
▼ ▼
Windows #1 CentOS
│ │
▼ ▼
D:\git\Datasets\install /data/distribution/install
│ │
│ Check for Changes │
│ │
└───────────────┐ ┌─────────────────┘
▼ ▼
┌─────────────────┐
│ Two-way Sync │
└───────▲───▲─────┘
│ │
┌──────────────────┘ └──────────────────┐
│ │
│ Reflect Changes │
│ │
└──────────────────┐ ┌──────────────────┘
│ │
▼ ▼
Changes Reflected
on Both FoldersWhen a file is added or modified in one folder, the changes are reflected in the other folder according to the configured synchronization criteria. Conversely, changes made on the other system can be reflected in the connected folder in the same way.
Check the Connection Status
After configuring each system and folder, check the connection status. Verify that the system can be accessed normally and that the specified folder can be used, then save the synchronization flow.
Once the two environments are connected, the following structure is ready.
| Category | System | Synchronization Folder |
|---|---|---|
| Sync Environment A | Windows#1 | D:\git\Datasets\install |
| Sync Environment B | CentOS | /data/distribution/install |
| Synchronization Method | Two-way | Reflect changes on both sides |
The two systems and folders are now connected as a single two-way synchronization flow.
Execution Conditions#
Decide When and Which Files to Synchronize
Once the environment is configured, set when to start the synchronization task, which changes to check, and which files to target between the two systems.
Use the Start When, Sync on, Direction, and Filter options in the settings panel on the right to configure the synchronization execution criteria.
Select the Synchronization Start Condition
In Start When, select how to start the file synchronization task.
- Date/Time: Run synchronization at the specified date and time
- After Transfer: Run after another file processing task is completed
- Sync: Synchronize based on file changes
- URL Request: Run synchronization through an external request
Select Sync to automatically synchronize based on changes in the work folder.
Use a screen showing the Start When, Sync on, Direction, Filter, and Endpoints settings.
Specify Which Changes to Check
In Sync on, select which file changes to use as the synchronization criteria.
- New Items: Check for changes when a new file is created
- Modified Items: Check for changes when an existing file is modified
For example, select both options to synchronize newly created reports as well as subsequent modifications.
Check file creation or modification in one folder and reflect the changes in the connected folder according to the configured synchronization direction.
Configure One-way / Two-way Synchronization
In Direction, select the direction in which file changes are processed.
- One-way: Reflect changes from one folder in the other folder
- Two-way: Reflect changes made in both folders in each other
For this two-way synchronization, select Two-way. This allows changes made when a file is created or modified on either side to be reflected in the other folder according to the configured criteria.
Choose Which Files to Synchronize
If necessary, use Filter to select the files to synchronize.
By configuring filters based on file names, extensions, or work-specific conditions, you can process only the required files instead of synchronizing every file.
For example, report workflows can target document files such as PDF, DOCX, XLSX, and PPTX.
Check the Folders to Connect
In Endpoints, check the two systems and folders connected for two-way synchronization.
The screen shows the following two environments configured as synchronization targets.
| Category | System | Folder |
|---|---|---|
| Endpoint A | RHEL | daily-report |
| Endpoint B | Ubuntu | report-summary |
By configuring the execution conditions, changes, synchronization direction, and file filters, you can configure two-way synchronization between the two folders based on the required file changes.
Duplicate Policy#
Decide How to Handle Files with the Same Name
In two-way synchronization, you need to consider situations where a file is changed on one side while files with the same name exist in both folders. In File Conflict Handling, select which file should be used as the basis for reflecting changes.
Select a Handling Method
Use a settings screen showing Overwrite, Skip, Numbering, and the Example for each method.
The screen provides the following three methods.
| Handling Method | Existing File | Changed File | Processing Result |
|---|---|---|---|
| Overwrite | Replace with the changed file | Reflect | Keep the latest state based on the changed file |
| Skip | Keep as is | Do not reflect | Keep the existing file |
| Numbering | Keep as is | Save with an added number | Keep both files |
When files with the same name exist in both folders
For example, if both Work Folder A and B contain report.pdf and the file is changed on one side, the changes are managed according to the configured handling method.
┌──────────────────────────┐ ┌──────────────────────────┐
│ Work Folder A │ │ Work Folder B │
└────────────┬─────────────┘ └────────────┬─────────────┘
│ │
▼ ▼
Changed report.pdf Existing report.pdf
│ │
└────────────────┐ ┌────────────────────┘
▼ ▼
Two-way Synchronization
│
▼
File Conflict Handling
│
┌───────────────┼───────────────┐
│ │ │
▼ ▼ ▼
┌───────────────┐ ┌───────────────┐ ┌───────────────┐
│ Overwrite │ │ Skip │ │ Numbering │
└───────┬───────┘ └───────┬───────┘ └───────┬───────┘
│ │ │
▼ ▼ ▼
┌───────────────┐ ┌───────────────┐ ┌───────────────┐
│ Replace with │ │ Keep existing │ │ report (1).pdf│
│ changed file │ │ file │ │ │
└───────────────┘ └───────────────┘ └───────────────┘Choose the Method That Fits the Work
Overwrite is suitable when you want to reflect a changed file in the other folder as well and align the file states in both folders with the latest version.
Skip can be used when the existing file in each folder should be retained.
Numbering is suitable when files used in both folders need to be kept together. Files with the same name can be distinguished when saved, allowing both the changed and existing files to be managed.
Selection Criteria at a Glance
| File Management Method | Selection |
|---|---|
| Reflect the latest state based on the changed file | Overwrite |
| Keep the existing file | Skip |
| Keep both existing and changed files | Numbering |
By configuring file conflict handling criteria, you can consistently manage changes even when files with the same name are found in Work Folders A and B.
Check Results#
Review Executed Task Results at a Glance
When a two-way synchronization task runs, the Dataset screen lets you check the synchronization status of connected folders and recent execution results together.
At the top of the screen, you can check the current Dataset version, total file count, size, and last update time. In Sources below, check the synchronization status for each connected system and folder, and in Runs, review the progress of tasks currently being executed.
Check Synchronization Status by Folder
In Sources, you can view the Device and Path connected to synchronization in a list.
Each item provides the following information.
| Check Item | Details |
|---|---|
| Device | Connected system or device |
| Path | Synchronization folder path |
| Last Sync | Last synchronization time |
| Files | Number of files managed in the folder |
| Size | Total file size |
| Status | Current synchronization status |
For example, the screen shows Windows#1 connected to multiple folders, and each folder's status can be viewed as Sync, Syncing, Sync Failed, and so on.
This makes it easy to quickly determine which folders have synchronized successfully, whether a task is currently in progress, and which items require additional review.
Check Running Synchronization Tasks
In Runs at the bottom of the screen, you can view recently executed synchronization tasks.
Each task provides the following information.
Flow
│
├── From / To
│
├── Trigger
│
├── Progress
│
└── StatusUse From/To to check the file flow between connected systems, and Trigger to check the condition that caused the task to run.
Use Progress to check the current processing progress, and Status to determine whether the task is proceeding normally.
For example, a task in Running status means synchronization is currently in progress, and the progress indicates how much of the overall task has been processed.
Check Synchronization Results Together
For two-way synchronization, it is important to check the status and execution results of each connected folder together rather than checking only one folder.
┌──────────────────────────────┐ ┌──────────────────────────────┐
│ Folder A │ │ Folder B │
└──────────────┬───────────────┘ └──────────────┬───────────────┘
│ │
│ Check for Changes │ Check for Changes
│ │
└─────────────────┐ ┌───────────────┘
▼ ▼
┌──────────────────┐
│ Two-way Sync │
└────────┬─────────┘
│
▼
┌──────────────────┐
│ Dataset Status │
└────────┬─────────┘
│
┌─────────────┴─────────────┐
│ │
▼ ▼
┌────────────────────────┐ ┌────────────────────────┐
│ Sources │ │ Runs │
├────────────────────────┤ ├────────────────────────┤
│ Status by Folder │ │ Check Execution Results│
└────────────────────────┘ └────────────────────────┘On the Dataset screen, you can check the synchronization status by folder → currently running tasks → overall file status on a single screen.
Therefore, operators can check whether changes are being reflected normally in a specific folder, review progress when a task is running, and perform additional checks based on the affected item when Sync Failed occurs.
Incident Response#
Check and Reprocess When a Problem Occurs
If processing of some files is not completed during a two-way synchronization task, check the execution results, then identify which synchronization direction encountered the problem and reprocess the necessary work.
Incident response follows the flow of check task status → check synchronization direction → identify the cause → retry → confirm completion.
Check for Problems in the Processing Status
Check executed tasks in Runs with the statuses Completed, Failed, and In Progress.
When you select a task with Failed status, review the execution information and file processing results, and identify which environment between Work Folders A and B requires attention while processing the changes that occurred there.
Synchronization Run
│
▼
Check Task Status
│
├── Completed ──→ Check Results
│
└── Failed
│
▼
Check Synchronization Direction
│
▼
Check Details
│
▼
Identify Cause and Take Action
│
▼
Retry
│
▼
Check Completion ResultReprocess After Identifying the Cause
In two-way synchronization, check the connection status of both systems, folder paths, access permissions, and file status together. Use task details and the Audit Log to identify which folder's changes require attention during processing.
Once the check is complete, rerun the task or the file being processed. After retrying, use the new Run to verify that changes in both folders have been reflected normally.
| Check Item | Details to Check | Follow-up Action |
|---|---|---|
| System Connection | Connection status between the two work environments | Check the connection, then retry |
| Folder Path | Paths of both synchronization folders | Check the paths, then rerun |
| Access Permissions | File read/write permissions for both folders | Check permissions, then reprocess |
| File Status | Status of files targeted for synchronization | Check the files, then retry |
| Execution History | Audit Log and synchronization results | Identify the cause, then run the task |
Set the Retry Criteria
When a task can continue normally after being rerun, such as after a temporary connection issue or a change in the file processing environment, retry the synchronization task.
When the same item repeatedly requires attention, review the execution conditions, connection status of both folders, access scope, and file conflict handling policy together and incorporate the findings into operational criteria.
Recovery Flow at a Glance
Failed Run
↓
View Details
↓
Check Synchronization Direction
↓
Identify Cause
↓
Adjust Environment or File Status
↓
Retry
↓
Create a New Run
↓
Check Reflection Results in Both Folders
↓
CompletedIn this way, by identifying and reprocessing issues based on execution results and detailed records, you can manage tasks that occurred during two-way synchronization until the file states in both work environments are reflected normally again.