insightapi2~move_to_app_root
Purpose
Move the given folder or scenario to the root (top level) of this app. The folder or scenario must already belong to this app.
Synopsis
function move_to_app_root(client:insightapi2~insightconfig, req:insightapi2~httprequest, resp:insightapi2~httpresponse):insightapi2~folder_or_scenario
function move_to_app_root(client:insightapi2~insightconfig, id:text, body:insightapi2~reference_folder_or_reference_scenario, resp:insightapi2~httpresponse):insightapi2~folder_or_scenario
function move_to_app_root(client:insightapi2~insightconfig, id:text, body:insightapi2~reference_folder_or_reference_scenario):insightapi2~folder_or_scenario
Arguments
|
client
|
An initialized
insightapi2~insightconfig to call
|
||
|
req
|
An initialized
insightapi2~httprequest record. The
body field may be populated with a value of type
insightapi2~reference_folder_or_reference_scenario. The
params field may contain these indexes:
|
||
|
id
|
The app ID
|
||
|
body
|
The folder or scenario to move, with its ID and object type
|
||
|
resp
|
A
insightapi2~httpresponse record into which will be written a description of the response
|
Return value
The response body of the request, if it was of type
insightapi2~folder_or_scenario
Further information
1. Use the
status field of the
resp record to distinguish between different status codes returned by the operation, or the
success attribute to check for 2xx status codes. If the
resp record is not passed to this function, the model will abort with a runtime error if the response's status code does not indicate success. The expected responses from this operation are:
| HTTP Status Code | Response body type | Description |
|---|---|---|
| 200 | insightapi2~folder_or_scenario | The moved folder or scenario |
| 403 | The user did not have authority to move the folder or scenario | |
| 404 | insightapi2~error_response | The app did not exist, or the user was not a member of it |
| 422 | insightapi2~error_response | The user is trying to move some other type of object (not a folder or scenario), or the scenario is unavailable to the current user |
2. If the response body could be read into a Mosel variable, it would be written to the
body field of the
resp record (and also returned from this function if it was a
insightapi2~folder_or_scenario), and the
bodyfilename field of the
resp record will be an empty string.
3. If the
bodyfilename field of the
resp record is set to a non-empty value on return, this will be a file containing the response body; the caller is responsible for deleting this file when it is no longer required.
Related topics
insightapi2~error_response
insightapi2~folder_or_scenario
insightapi2~reference_folder_or_reference_scenario
insightapi2~insightconfig
insightapi2~httprequest
insightapi2~httpresponse
insightapi2~folder_or_scenario
insightapi2~reference_folder_or_reference_scenario
insightapi2~insightconfig
insightapi2~httprequest
insightapi2~httpresponse
© 2001-2024 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation ("FICO"). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.