Initializing help system before first use

insightapi2~create_or_update_execution_worker_mapping

Purpose
Create a new mapping if one did not already exist for this worker and service combination, or update an existing mapping. The request body need not supply the worker and service, but if it does the IDs must match this URL.
Synopsis
function create_or_update_execution_worker_mapping(client:insightapi2~insightconfig, req:insightapi2~httprequest, resp:insightapi2~httpresponse):insightapi2~execution_service_worker_mapping
function create_or_update_execution_worker_mapping(client:insightapi2~insightconfig, service_id:text, worker_id:text, body:insightapi2~execution_service_worker_mapping, resp:insightapi2~httpresponse):insightapi2~execution_service_worker_mapping
function create_or_update_execution_worker_mapping(client:insightapi2~insightconfig, service_id:text, worker_id:text, body:insightapi2~execution_service_worker_mapping):insightapi2~execution_service_worker_mapping
Arguments
client 
An initialized insightapi2~insightconfig to call
req 
An initialized insightapi2~httprequest record. The body field may be populated with a value of type insightapi2~execution_service_worker_mapping. The params field may contain these indexes:
serviceId 
The service ID
workerId 
The worker ID
service_id 
The service ID
worker_id 
The worker ID
body 
A insightapi2~execution_service_worker_mapping value
resp 
A insightapi2~httpresponse record into which will be written a description of the response
Return value
The response body of the request, if it was of type insightapi2~execution_service_worker_mapping
Further information
1. Use the status field of the resp record to distinguish between different status codes returned by the operation, or the success attribute to check for 2xx status codes. If the resp record is not passed to this function, the model will abort with a runtime error if the response's status code does not indicate success. The expected responses from this operation are:
HTTP Status Code Response body type Description
200 insightapi2~execution_service_worker_mapping The created or updated mapping
403 The user did not have authorization to create or update this mapping
422 insightapi2~error_response The request was not well-formed. For example, if the request contained worker or service IDs and these did not match the URL.

2. If the response body could be read into a Mosel variable, it would be written to the body field of the resp record (and also returned from this function if it was a insightapi2~execution_service_worker_mapping), and the bodyfilename field of the resp record will be an empty string.
3. If the bodyfilename field of the resp record is set to a non-empty value on return, this will be a file containing the response body; the caller is responsible for deleting this file when it is no longer required.
Related topics
insightapi2~error_response
insightapi2~execution_service_worker_mapping
insightapi2~insightconfig
insightapi2~httprequest
insightapi2~httpresponse

Parent Topic ExecutionAdmin Operations

© 2001-2025 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.