Creates a new metadata cascade policy that applies a given metadata template to a given folder and automatically cascades it down to any files within that folder.
In order for the policy to be applied a metadata instance must first be applied to the folder the policy is to be applied to.
The access token received from the authorization server in the OAuth 2.0 flow.
The ID of the folder to apply the policy to. This folder will need to already have an instance of the targeted metadata template applied to it.
"1234567"
The scope of the targeted metadata template. This template will need to already have an instance applied to the targeted folder.
global, enterprise "enterprise"
The key of the targeted metadata template. This template will need to already have an instance applied to the targeted folder.
In many cases the template key is automatically derived
of its display name, for example Contract Template would
become contractTemplate. In some cases the creator of the
template will have provided its own template key.
Please list the templates for an enterprise, or get all instances on a file or folder to inspect a template's key.
"productInfo"
Returns a new of metadata cascade policy.
A metadata cascade policy automatically applies a metadata template instance to all the files and folders within the targeted folder.
The ID of the metadata cascade policy object.
"6fd4ff89-8fc1-42cf-8b29-1890dedd26d7"
The value will always be metadata_cascade_policy.
metadata_cascade_policy "metadata_cascade_policy"
The enterprise that owns this policy.
Represent the folder the policy is applied to.
The scope of the metadata cascade policy can either be global or
enterprise_*. The global scope is used for policies that are
available to any Box enterprise. The enterprise_* scope represents
policies that have been created within a specific enterprise, where *
will be the ID of that enterprise.
"enterprise_123456"
The key of the template that is cascaded down to the folder's children.
In many cases the template key is automatically derived
of its display name, for example Contract Template would
become contractTemplate. In some cases the creator of the
template will have provided its own template key.
Please list the templates for an enterprise, or get all instances on a file or folder to inspect a template's key.
"productInfo"