Update/Modify BP Records Permission

PUT /ws/rest/service/v1/bp/record/permission/{project_number}

Purpose:

Update non-workflow records permission (in user mode) of a specific BP in a shell based on shell number or from Company level if project/shell number is not provided.

The input JSON shall provide various options to be considered for fetching the data

Input:

All parameters should be URL encoded.

Path Parameter

project_number: Specify the Project number in which the records exists, if not provided then records are considered to be fetched from Company Level.

POST body is a JSON

Note: POST call has input & output both as JSON in the body.

{

"options":{

"bpname" : "simple1"

},

"data": {

"record_no": ["uxss1-0007", "uxss1-0006", "uxss1-0005"]

"permissions": [

{

"login_name": "coadmin",

"type": "U",

"full_name": "Company Administrator",

"permission": {

"edit_data": "1",

"modify_permission": "0",

"view": "1"

}

}

{

"full_name": "Building Managers",

"group_name": "Building Managers",

"permission": {

"edit_data": "1",

"view": "1",

"modify_permission": "0"

},

"type": "PG"

}

]

}

}

Here "bpname" & "record_no" are mandatory in options.

In the request body record_no can be provided in below two formats

1. "record_no": ["uxss1-0007", "uxss1-0006", "uxss1-0005"] For one or more records.

2. "record_no": "uxss1-0007" For only one record.

If record_no not provided, then error response will be provided to user to provide record_number.

Output:

JSON object containing 'status', 'data', 'message'

Message will be present if status is not 200 otherwise it will be "success".

In This Section

Update/Modify BP Records Permission Sample Response



Legal Notices | Your Privacy Rights
Copyright © 1998, 2022

Last Published Tuesday, February 8, 2022