McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 319

↗ View in doc context
page
319
source
finesse/v12.5/developer-guide/developer-guide.md
chunk_id
finesse::v12.5::developer-guide::developer-guide::303

SYSTEM variables are name references to the values returned by SystemVariable and do not require a node value. CUSTOM variables are self-defining and require a node and a unique name that does not conflict with any system variable. Data Type Value Variable Name String The extension this user is currently using. ${userExtension} String The login ID of the user. ${userLoginId} String The user's login name. ${userLoginName} String The name of the team the user belongs to. ${userTeamName} String The ID of the team the user belongs to. ${userTeamId} String The first name of the user. ${userFirstName} String The last name of the user. ${userLastName} Workflow API Errors Description Error Type Status The request body is invalid. Bad Request 400 API error such as the object is stale or does not exist. Finesse API Error 400 Unauthorized (for example, the user is not yet authenticated in the Web Session). The user is not authorized to use the API (the user is not an administrator). Authorization Failure 401 The user attempted to run the API against the secondary Finesse server. Configuration APIs cannot be run against the secondary Finesse server. Forbidden 403 The specified resource cannot be found. Not Found 404 Any runtime exception is caught and responded with this error. Internal Server Error 500 WorkflowAction The WorkflowAction object represents a workflow action that can be assigned to a workflow. Finesse supports a system-wide maximum of 100 workflow actions. The WorkflowAction object is structured as follows: Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 303 Cisco Finesse Configuration APIs Workflow API Errors