POST Assign Txn

The transaction assign operation reassigns a submission task to the user specified in the query.

To assign a task, the following requirements must be met.

• The form status is not "completed" or "abandoned".
• The transaction is a task, and the taskKey is not empty.
• The task is accessible by the user calling the API.
• The task is not currently associated with a user. (To reassign a task, unassign it first.)

caution

If any of these conditions are not met, a 400 Bad Request HTTP status code is returned.

Request

HTTP request

POST https://<JM_SERVER>/workspaces/secure/api/v1/txn/assign

Request body

The POST request must contain a JSON structure describing the task assignment. To support multiple parameters, this API uses HTTP Content Type: application/json.

The available query attributes are listed below. All attributes are optional except where otherwise indicated.

caution

If you specify an invalid request attribute, a 400 Bad Request HTTP status code is returned.

Attribute	Description
params	Map Required. A map containing the assign attributes.

Supported assign attributes

The supported assign attributes are listed below.

caution

If you specify an invalid assign attribute, a 400 Bad Request HTTP status code is returned.

Attribute	Description
submitKey	String Required. The submit key property of the task to assign.
userKey	String Required. The user key property of the user account to assign the task to.

Response

If successful (that is, the task is assigned to the user and no errors occurred during the execution of this API), this operation returns a response with a HTTP 200 OK status code.

Error messages

Error key	Error	HTTP status code
accessDenied	The user does not have access to transaction specified by the submitKey	400 Bad Request
internalError	Please see Error Log ID {number}	500 Internal Server Error
submitKeyNotSpecified	submitKey not specified	400 Bad Request
txnAlreadyAssigned	The task is currently assigned to a user. To reassign it, unassign it first, then assign it to the new user.	400 Bad Request
txnAlreadyFinished	The transaction specified by the submitKey has already been finished (Completed or Abandoned)	400 Bad Request
txnNotFound	The transaction specified by the submitKey was not found	400 Bad Request
txnNotTask	The transaction specified by the submitKey is not a task	400 Bad Request
userKeyNotSpecified	userKey not specified	400 Bad Request
userNotFound	The user account specified by the userKey was not found	400 Bad Request

Error responses

HTTP status code	Description
400 Bad Request	Bad request or request parameter. Check error message for details.
404 Not Found	Ensure the URL endpoint is entered correctly.
500 Internal Server Error	Exception occurred in txn assign. Contact administrator.

Example

Ensure you specify Content-Type: application/json.

Example request

POST /workspaces/secure/api/v1/txn/assign HTTP/1.1
Host: https://transact.workspaces.com
Content-Type: application/json
{
    "params": {
        "submitKey": "15d071280b92c867f86975b9cd2e8765",
        "userKey": "378595572a1bd63ff9b5972b7a1c91dd"
    }
}