Rename folder
put
/documentManagement/v1/{documentManagementSystemId}/folders/{folderId}
This operation renames a folder in the underlying DMS/CMS.
Request
Path Parameters
-
documentManagementSystemId(required): string
Unique identifier for DMS/CMS as configured in the CXIF routing GKR criteria
-
folderId(required): string
GUID of the folder
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object
-
description: string
Folder descriptionExample:
Contracts Folder
-
name(required): string
Folder NameExample:
Contracts Folder
Response
Supported Media Types
- application/json
200 Response
Folder Updated successfully
Root Schema : FolderResponseBody
Type:
Show Source
object
-
createdBy: string
Name of the user who created the folderExample:
User_Name
-
createdWhen: string
(date-time)
Date of document creationExample:
2014-02-21T21:32:37Z
-
description: string
Folder DescriptionExample:
Contracts Folder
-
href: string
Path to the folder reachable via RMSExample:
/documentManagement/v1/ocm-1/folders/DB1C5AF480FFE61C588027A8T0000000000100000001
-
id: string
ID of the folderExample:
DB1C5AF480FFE61C588027A8T0000000000100000001
-
name: string
Name of the folderExample:
Contracts Folder
-
parentId: string
ID of the parent folderExample:
DB1C5AF480FFE61C588027A8T000000000010000331
-
updatedBy: string
Name of the user who updated the folderExample:
User_Name
-
updatedWhen: string
(date-time)
Date of folder updateExample:
2014-02-21T21:32:37Z
400 Response
Request validation failed
Root Schema : Error
Type:
object
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
401 Response
Authorization failure. The authorization header is invalid or missing
Root Schema : Error
Type:
object
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
403 Response
Operation is not permitted based on the supplied authorization.
Root Schema : Error
Type:
object
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
500 Response
Internal Server Error
Root Schema : Error
Type:
object
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
Examples
The following example shows how to rename folder by submitting a put request on the REST resource using cURL.
cURL Command
curl --<username:password> --request PUT
'{FABRIC_HOST}/documentManagement/v1/{documentManagementSystemId}/folders/{folderId}'
--header 'Authorization: Bearer <accessToken> --header 'Content-Type: application/json'
-D@renamefolder.JSON
Example of Request Body
The following shows an example of the request body in JSON format.
{ "name": "Contracts Folder", "description": "Contracts Folder" }
Example of Response Body
The following shows an example of the response body in JSON format.
{ "id": "DB1C5AF480FFE61C588027A8T0000000000100000001", "parentId": "DB1C5AF480FFE61C588027A8T000000000010000331", "name": "Contracts Folder", "description": "Contracts Folder", "createdBy": "User_Name", "createdWhen": "2014-02-21T21:32:37Z", "updatedBy": "User_Name", "updatedWhen": "2014-02-21T21:32:37Z", "href": "/documentManagement/v1/ocm-1/folders/DB1C5AF480FFE61C588027A8T0000000000100000001" }