Move Contents
Operation name
Move Contents
Function overview
Moves the contents (files or folders) in Box specified in input data.
For details on API specifications used by this component, refer to the Box API reference at the following URLs:
-
https://developer.box.com/reference/put-files-id/
-
https://developer.box.com/reference/put-folders-id/
Data model
The data model of this component is table model type.
Properties
For details on use of variables, refer to Variables.
Basic settings
Item name |
Required/Optional |
Use of variables |
Description |
Remarks |
---|---|---|---|---|
Name |
Required |
Not available |
Enter a name that is used on the script canvas. |
|
Input data |
Required |
Not available |
Select a component on the script canvas. |
|
Required settings
Item name |
Required/Optional |
Use of variables |
Description |
Remarks |
---|---|---|---|---|
Destination |
Required |
Not available |
Select a connection resource.
|
|
Advanced settings
Item name |
Required/Optional |
Use of variables |
Description |
Remarks |
---|---|---|---|---|
Retrieval method for user information |
Required |
Not available |
Specify a method to retrieve information for a user specified for login in the input schema.
|
|
Specification method for Box content |
Required |
Not available |
Select a method to specify Box content.
|
|
Output successfully processed items to results data |
Optional |
Not available |
Select whether to output successfully processed items to results data in addition to failed items.
|
|
Comment
Item name |
Required/Optional |
Use of variables |
Description |
Remarks |
---|---|---|---|---|
Comment |
Optional |
Not available |
You can write a short description of this connector. |
|
Schemas
Input schema
The number of columns and the contents differ depending on the settings for Specification method for Box content.
<?xml version="1.0" encoding="UTF-8" ?> <table> <row> <column>login</column> <column>from_box_content_path</column> <column>to_box_folder_path</column> <column>from_box_content_id</column> <column>from_box_content_type</column> <column>to_box_folder_id</column> <column>new_name</column> </row> <row> : </row> </table>
Element name |
Label |
Description |
Required/Optional |
Remarks |
---|---|---|---|---|
row |
|
Repeats for the amount of content to move. |
|
|
column |
login |
Enter the email address that the user uses to log in. |
Required |
|
from_box_content_path |
Enter the path of the move source contents. |
Required |
Note
|
|
to_box_folder_path |
Enter the path of the move destination folder. |
Required |
Note
|
|
from_box_content_id |
Enter the ID of the move source content. |
Required |
Note
This item is available only when Specification method for Box content is ID.
|
|
from_box_content_type |
Enter the type of the move source content (file or folder).
|
Required |
Note
This item is available only when Specification method for Box content is ID. |
|
to_box_folder_id |
Enter the ID of the move destination folder. |
Required |
Note
This item is available only when Specification method for Box content is ID. |
|
new_name |
Enter the name of the move destination contents. |
Optional |
Note
|
Output schema
The number of columns and the contents differ depending on the settings for Specification method for Box content.
<?xml version="1.0" encoding="UTF-8" ?> <table> <row> <column>result</column> <column>login</column> <column>from_box_content_path</column> <column>to_box_folder_path</column> <column>from_box_content_id</column> <column>from_box_content_type</column> <column>to_box_folder_id</column> <column>new_name</column> <column>status_code</column> <column>error_code</column> <column>message</column> <column>request_id</column> </row> <row> : </row> </table>
Element name |
Label |
Description |
Remarks |
---|---|---|---|
row |
|
Repeats for the number of processed input items. |
Note
When Output successfully processed items to results data isn't selected, rows are repeated only for the number of input items that failed in the processing. |
column |
result |
When request execution succeeds, "succeeded" is output. When input is invalid, "skipped" is output. When request execution results in an error, "failed" is output. |
|
login |
login of the processed input item is output. |
|
|
from_box_content_path |
from_box_content_path of the processed input item is output. |
Note
This item is available only when Specification method for Box content is Path. |
|
to_box_folder_path |
to_box_folder_path of the processed input item is output. |
Note
This item is available only when Specification method for Box content is Path. |
|
from_box_content_id |
from_box_content_id of the processed input item is output. |
Note
This item is available only when Specification method for Box content is ID. |
|
from_box_content_type |
from_box_content_type of the processed input item is output. |
Note
This item is available only when Specification method for Box content is ID. |
|
to_box_folder_id |
to_box_folder_id of the processed input item is output. |
Note
This item is available only when Specification method for Box content is ID. |
|
new_name |
new_name of the processed input item is output. |
|
|
status_code |
If the result is "failed", an HTTP status code is output from Box. |
|
|
error_code |
If the result is "failed", an error code that identifies the error contents is output. |
|
|
message |
If the result is "skipped" or "failed", an error message is output. |
|
|
request_id |
If the result is "failed", the ID that uniquely distinguishes the request relative to Box is output. |
|
Loading schema in Mapper
The schema is loaded automatically.
For details, refer to Edit Schema.
Mass data processing
Mass data processing isn't supported.
Transaction
Transaction isn't supported.
Parallel Stream Processing
PSP isn't supported.
Available component variables
Component variable name |
Description |
Remarks |
---|---|---|
succeeded_count |
The number of input items that were processed successfully is stored. |
|
failed_count |
The number of input items that failed in the processing is stored. |
|
skipped_count |
The number of input items that were skipped in the processing is stored. |
|
message_category |
When an error occurs, the category of the message code corresponding to the error is stored. |
|
message_code |
When an error occurs, the code of the message code corresponding to the error is stored. |
|
message_level |
When an error occurs, the severity of the message code corresponding to the error is stored. |
|
error_type |
When an error occurs, the error type is stored. |
|
error_message |
When an error occurs, the error message is stored. |
|
error_trace |
When an error occurs, the trace information for the error is stored. |
|
Message codes, exception messages, and limitations
Connector |
Message code |
Exception message |
Limitations |
---|---|---|---|
Messages and limitations of the Box connector |