Getting Started
Basic Concept
Transfer Files Directly to a Designated Workspace Without a Shared Drive
Business files are created and used in various locations, such as personal PCs, servers, and project environments.
When files are used by another person or in a subsequent task, they may need to be saved in a shared location and then prepared in the required work environment.
Workspace file transfer is a function that directly connects the environment containing the files to the workspace where the actual work takes place, allowing required files to be transferred directly.
By specifying the files to transfer and the target workspace, files can be transferred directly from where they were created to the workspace where they will be used.
This creates a file flow that continues from file creation through reflection in the target workspace and into the next task.
transfer flow
Continue from File Selection to Reflection in the Target Workspace
Workspace file transfer involves checking the files to transfer, selecting the target workspace where the files will be used, and transferring the files to the specified location.
After the transfer is complete, you can check the file reflection status in the target workspace and continue the required work.
① Select Files to Transfer
↓
② Select Target Workspace
↓
③ Check Transfer Conditions
↓
④ Transfer Files
↓
⑤ Reflect Files in Workspace
↓
⑥ Check Results
This flow directly connects the environment containing the files to the required workspace.
Select files from their current location and transfer them to the workspace where the actual work takes place, connecting file preparation and business use in a single flow.
Business Changes
Reduce Repetitive Download and Upload Work
When files created in one work environment are used in another, using a shared location can add file storage and preparation steps.
For example, one person may create a result file on a PC and save it to a shared location, after which another person repeatedly prepares the file in their own workspace.
Workspace file transfer reduces these file management steps by transferring files directly from their current location to the workspace where they will actually be used.
Before and After Transfer
| Category | Traditional File Sharing | Workspace File Transfer |
|---|---|---|
| File Preparation | Save files to a shared location | Select files to transfer directly |
| Target Selection | Check files in the shared location | Select the target workspace directly |
| File Movement | Perform file storage and preparation steps | Transfer directly to the target location |
| Start Work | Start work after preparing files | Start work with the reflected files |
In this way, workspace file transfer connects the workspace where files will actually be used as the transfer target.
You can quickly select the required files and transfer them to the designated workspace, naturally continuing from file preparation to the next task.
Business Team
Workspace Selection
Select the Workspace Where Files Will Be Used and Transfer Them
When transferring files, first select the workspace where the files will actually be used.
For example, you can send a completed report to the review team's workspace or directly reflect processing results in a workspace for each project.
After checking the files to transfer, select the required workspace and the location where the files will be stored.
The transfer target is the workspace where files will be checked and used in the next task.
Before transferring, you can check the following items.
| Item to Check | Details |
|---|---|
| Business Purpose | Confirm the task that will use the files |
| Workspace | Select the target where files will be used |
| File Location | Check the location where files will be used within the workspace |
| Files to Transfer | Select files required for the current task |
After selecting the target workspace and files and starting the transfer, the required files can be sent directly to that work environment.
transfer check
Check Whether Files Were Successfully Reflected in the Target Workspace
After starting the file transfer, check the current job progress and the file reflection result in the target workspace.
For an in-progress job, check the transfer status; after the transfer is complete, the files can be used in the target workspace.
The flow from transfer to the next task is as follows.
Start File Transfer
↓
Check Transfer Progress
↓
Reflect in Target Workspace
↓
Check Files
↓
Continue to Next Task
The transfer result provides the following information.
Job Status
Transfer Progress
Transferred File Count
Total File Size
Transfer Start and Completion Times
Target Workspace
After the transfer is complete, check the file reflection status in the target workspace and continue review, modification, or follow-up work based on the files.
IT Engineer
environment configuration
Connect the Source Device and Workspace and Set Access Scope
To configure workspace file transfer, first connect the device containing the files to the target workspace.
On the Source device, configure access to check and read the files to transfer; in the target workspace, configure access so transferred files can be reflected at the specified location.
Prepare the following access scopes for the transfer environment.
| Category | Required Access Scope |
|---|---|
| Source Device | Check and read files to transfer |
| Target Workspace | Store and reflect files |
| User | Check and run transfer jobs |
| Operator | Manage the connected environment and transfer settings |
After connecting the device and target workspace, set the file path and target location to use for the actual transfer.
This clearly defines which files from which location will be transferred to which workspace.
transfer setup
Define the Files to Send, Target Location, and Execution Conditions
After configuring the environment, set the files to transfer, target location, and conditions that start the job.
In the transfer settings, specify the Source and Target and configure file paths, filters, and execution conditions according to the business workflow.
First, specify the path containing the files to transfer on the Source.
For example, files created under /data/report/daily can be configured as transfer targets.
If necessary, select files to transfer based on file name, extension, or path conditions.
In the Target, specify the workspace and actual location where the files will be reflected.
File transfer jobs can start under various conditions depending on the business workflow.
Date/Time: Transfer at the specified date and time
After Transfer: Transfer after the previous job is complete
Sync: Transfer based on file changes
URL Request: Transfer through an external request
By setting the files, target location, and execution conditions, you can configure a single transfer job covering the process from file readiness through reflection in the target workspace.
Flow Configuration
Connect Directly from the Device Containing the Files to the Target Workspace
After completing the transfer settings, connect the Source and Target in Flow to configure the full file transfer path.
The Source provides the files to transfer, Flow processes them according to the configured conditions, and the Target reflects the files at the specified location in the target workspace.
The basic transfer structure is as follows.
Source Device
│
│ Files
▼
Transfer Flow
│
▼
Workspace
│
▼
Target Path
After confirming the required files on the Source, transfer them to the target workspace through the configured Flow and reflect them at the specified location.
Depending on the work environment, you can transfer files from multiple devices to one workspace or branch files from one Source to multiple workspaces.
Automation Connection
Connect Follow-up Tasks and External Services After Transfer Completion
By connecting required tasks after file transfer is complete, you can automatically continue work after files are reflected in the target workspace.
For example, when a result file is reflected in the workspace, you can start the next processing task or configure a completion notification to be sent to the responsible person.
The basic automation flow is as follows.
file transfer
↓
Reflect in Workspace
↓
Confirm Transfer Completion
↓
Run Follow-up Task
↓
Check Result
If necessary, the file transfer result can also be connected to external services.
| Integration Area | Usage |
|---|---|
| Business & Collaboration | Connect transfer completion notifications and follow-up tasks |
| Monitoring | Check transfer status and execution results |
| Security | Check the file transfer environment and related events |
For example, you can notify users of transfer completion through a collaboration tool and configure the business management system to start the next task.
You can also connect to a monitoring environment to check transfer status and, when necessary, integrate with a security system to manage the file usage environment.
This configuration creates an automation flow centered on file transfer that connects file preparation → workspace reflection → notification → follow-up work → operational verification.
Check Result
Check Transfer Status and File-Level Processing Results
When a transfer job runs, you can check its current progress and overall processing result in Runs.
In the run list, you can compare the status of multiple transfer jobs and, by selecting a specific job, check the Source and Target, transfer volume, progress, and file-level processing results.
Each Run provides the following information.
| Check Item | Details |
|---|---|
| Source | Device and path from which files were transferred |
| Target | Workspace and location where files are reflected |
| Total Size | Total transfer size |
| Total Files | Number of files to process |
| Progress | Current transfer progress |
| Status | Job completion and progress status |
| Started | Job start time |
| Completed | Job completion time |
The transfer result lets you check the file reflection status in the target workspace.
For an in-progress job, check its current processing status; if specific files require additional review, check those items through the detailed results.
Incident Response
Check the Transfer Environment and Rerun Required Jobs
When a situation requiring additional review occurs during file transfer, use the Run details to check the job's processing status and where the issue occurred.
Then check the Source and Target connection status, file paths, and access permissions, complete the necessary actions, and rerun the job.
Incident response can proceed as follows.
Check Run
↓
View Details
↓
Source check
↓
Target check
↓
Check Path and Permissions
↓
Adjust Environment
↓
Retry
↓
Create New Run
↓
Confirm Reflection in Target Workspace
↓
Completed
When checking the transfer environment, review the following items together.
| Check Item | Details | Follow-up Task |
|---|---|---|
| Device Connection | Source system connection status | Check connection status |
| Target Connection | Workspace access status | Check target environment |
| File Path | Source and Target paths | Adjust paths and rerun |
| Access Permissions | File read and save permissions | Check permission settings |
| File Status | Transfer target file information | Check file status |
| Execution Record | Run details and activity history | Adjust execution environment |
For example, you can check file information on the Source or adjust the Target storage location and then rerun the job.
After rerunning, use the new Run to verify that the files were successfully reflected in the target workspace.
This process enables step-by-step management of the transfer environment and file processing status and stable operation of the file transfer flow from the Source to the target workspace.