The CASL syntax for the action is: `session.addNodeStatus ;`
In Python, you can call the action using the following syntax: `results=s.session.addNodeStatus()`
The R syntax for the `addNodeStatus` action is: `results
The Lua syntax for this action is: `results, info = s:session_addNodeStatus{}`
By setting the 'promote' parameter to TRUE, the table is added with a global scope, making it accessible to other sessions, provided they have the necessary permissions. The target caslib must also have a global scope.
The `batchresults` action requires the `uuid` parameter, which is a string that specifies the UUID of the session.
To use the `batchresults` action in CASL, you would call `session.batchresults` and provide the session's UUID. For example: `session.batchresults / uuid="your-session-uuid";`.
Yes, the example provided in the documentation, 'Switch an Action Running in Another Session to Batch Mode,' indicates that you can use the `batchresults` action to change the mode of an action in another session by specifying its UUID.
The checkOutObject action reserves an object and all of its children for update exclusively by the current client session. It can also prevent an object and its parents from being checked out exclusively by another session when using the 'Shared' checkOutType.
The 'checkOutType' parameter accepts two values: "EXCLUSIVE" and "SHARED". "EXCLUSIVE" is the default and ensures only the current session can update the object. "SHARED" prevents other sessions from getting an exclusive lock on the object and its parents, without locking the object itself.