Start an ad-hoc process of a user

This endpoint starts the ad-hoc process, i.e. triggers a new instance of a technical workflow at the module specified by the ad hoc process starter id. This module is usually a Task Generator or followed by a Task Generator.

Request

URL: /task/adhoc/{user}/{id}

Method: POST

Authorization: required

POST /ibis/rest/task/adhoc/testuser/74933f6c-72c6-44c5-9e90-91070f98c7dd HTTP/1.1
Accept: application/xml
Host: localhost:8080

The request body is empty.

Request Path Parameters

Name Description Required Allowed values

Name	Description	Required	Allowed values
`user`	Username	yes	Any existing username
`id`	ad hoc process starter id	yes	Identifying an ad hoc process starter the user has access to

user

Username

yes

Any existing username

id

ad hoc process starter id

yes

Identifying an ad hoc process starter the user has access to

Request Query Parameters

Name Description Required Allowed values

Name	Description	Required	Allowed values
`lang`	language	no (default: `de`)	`de` or `en`
`client`	tenant name	no	Ex: Virtimo_AG

lang

language

no (default: de)

de or en

client

tenant name

Ex: Virtimo_AG

Response

HTTP/1.1 201 SUCCESS_CREATED
Content-Type: application/plain

10f66801-77e7-4dfa-8f40-0f5039d4552a

SUCCESS_CREATED (201): New task receives the attributes popup=true and user=<username> in the context of which the ad hoc task was generated.
SUCCESS_NO_CONTENT (204): No follow-on task

Errors

Authorization Failed (401): Authorization with the given username and password failed. Please revisit both values and provide valid credentials.

<html>

    <head>
        <title>Status page</title>
    </head>

    <body style="font-family: sans-serif;">
        <p style="font-size: 1.2em;font-weight: bold;margin: 1em 0px;">Unauthorized</p>
        <p>The request requires user authentication</p>
        <p>You can get technical details <a
                href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.2">here</a>.<br>
            Please continue your visit at our <a href="/">home page</a>.
        </p>
    </body>
</html>

Server Error (500): Execution on the INUBIT server failed. Have a look into the response message, otherwise access to the INUBIT log is required to retrieve further information.
Service Unavailable (503): In maintenance mode the INUBIT server endpoint will not respond to incoming requests but return this error response. Once the maintenance mode is switched off the endpoint will respond normally.