Function prototype	action_list_user (session, id , action{, path = NULL} {, action_context = NULL})
API Version	2.7.8 and higher

Returns the possible actions available for the active user In the TASKS and EVENTS page. This function returns a list of possible choices related with a TASK or EVENT insertion (currently only EVENT actions are available).
Input parameters:	*session: a valid session reference obtained by a call to session_init () id: reference to the USER for whom the list of actions is requested action: type of actions requested. If null, then the list of available actions will be returned. Possible values: "MESSAGE": Returns actions for posting a new EVENT path: The goal of this parameter is to organize the actions hierarchically (as in a file tree where path represents the subdirectory). When calling action_list_user(), some of the actions returned may be of type PATH, in which case the value of the path returned can be used to make a subsequent call to action_list_user() to get the actions nested in that path. action_context*: JSON structure that the function will use as context information to generate the list of actions. See ACTION CONTEXT (JSON) for more information
Output parameters:	result: XML with the list of possible actions: *description: Description of the actions returned. It can be considered as a 'title' that explains what the action list contains. actions: List of actions. Each action in the XML contains ref: action reference that can be used to invoke action_exec (). If the action is of class PATH, then this it can be used to call again the function passing the value in the path* parameter to obtain a new list of actions name: short name in the active session’s language description: description in the active session’s language class: One of the following values: "ACTION": The item returned is an action that can be executed by invoking action_exec () "PATH": The item returned is not an an action. It is just a way to navigate through a tree of actions organized hierarchically. When an ACTION has class="PATH", it means that to continue the navigation, we should use the value returned in *ref* to invoke again this function (passing the value in the *path* parameter) "INPUT": The item returned is not an an action. It is just a way of requesting information that it is necessary to generate an action. When an ACTION has class="PATH", it means that the API needs user interaction to continue the navigation. See below parameter *input, which describes the type of information requested type: action type input: This value only has meaning when class="INPUT", and describes the type of data requested as input. Possible values are: "TEXT": We need call again this function passing a text value entered by the user in the action_context* parameter. ErrorMsg: If any error occurs, then this value contains a description of the error translated to the current language ErrorCode: If any error occurs, then this value contains any of the standard ERROR CODES
Request sample:	action_list_user ( “LCAAAAAAAAAAAA”, 13232, “EVENT”, "", "{program: 323}" );
Response sample:	<result> <?xml version="1.0" encoding="utf-8"?> <actions> <description>Select the type of message</description> <action> <ref>ACTION=MESSAGE&issuer=POSTER&event_multi=1&event_type=2</ref> <name>CARE ISSUE</name> <description/> <class>ACTION</class> <type>MESSAGE</type> </action> <action> <ref>ACTION=MESSAGE&issuer=POSTER&event_multi=1&event_type=1</ref> <name>SOCIAL ISSUE</name> <description/> <class>ACTION</class> <type>MESSAGE</type> </action> </actions> </result> <ErrorMsg></ErrorMsg> <ErrorCode></ErrorCode>
Notes:

Return Error codes

ERROR CODE
INVALID_TOKEN	The session token provided is not valid
INSUFFICIENT_PRIVILEGES	The session user does not have the necessary privileges to create request the 'action' indicated
INVALID_JSON	The JSON string provided in parameter *action_context* has an invalid format
USER.NOT_FOUND	The USER reference provided in parameter id does not correspond to an existing USER
CASE.NOT_FOUND	The CASE reference provided in parameter action_context does not correspond to an existing CASE
TEAM.NOT_FOUND	The TEAM reference provided in parameter action_context does not correspond to a valid TEAM
PROGRAM.NOT_FOUND	The PROGRAM reference provided in parameter action_context does not correspond to a valid PROGRAM
INVALID_DATE	The date value provided in parameter action_context does not have a valid format

Browser not supported