Mapping the outputs of the Activity
Create a map between the Dropbox output parameters and the orchestration variables. The expected response is generated on a successful mapping.
Name |
Data type | Required | Description |
has_more | boolean | No | If true, then there are more entries available |
cursor | integer | yes | A string that encodes the latest information that has been returned. |
Enteries ->thumb_exists | boolean | yes | True if the file is an image that can be converted to a thumbnail via the /thumbnails call. |
Enteries ->rev | string | yes | A unique identifier for the current revision of a file. This field is the same rev as elsewhere in the API and can be used to detect changes and avoid conflicts. |
Enteries ->modified | string | yes | The last time the file was modified on Dropbox, in the standard date format (not included for the root folder). |
Enteries ->modifier | string | yes | For files within a shared folder, this field specifies which user last modified this file. |
Enteries ->path | string | yes | Returns the canonical path to the file or folder. |
Enteries ->is_dir | boolean | yes | Whether the given entry is a folder or not. |
Enteries → size | string | yes | A human-readable description of the file size (translated by locale). |
Enteries → root | string | yes | The root or top-level folder depending on your access level. All paths returned are relative to this root level. Permitted values are either dropbox or app_folder. |
Enteries → read_only | boolean | yes | For shared folders, this field specifies whether the user has read-only access to the folder. For files within a shared folder, this specifies the read-only status of the parent shared folder. |
Enteries → icon | string | yes | The name of the icon used to illustrate the file type in Dropbox's icon library. |
Enteries → bytes | integer | yes | A deprecated field that semi-uniquely identifies a file. Use rev instead. |
Entries-> revision | integer | yes | The file size in bytes. |
reset | string | yes | If true, clear your local state before processing the delta entries. reset is always true on the initial call to /delta (i.e. when no cursor is passed in). Otherwise, it is true in rare situations, such as after server or account maintenance, or if a user deletes their app folder. |