Initializing help system before first use

insightapi2~create_job

Purpose
Create a job for a scenario.
Synopsis
function create_job(client:insightapi2~insightconfig, req:insightapi2~httprequest, resp:insightapi2~httpresponse):insightapi2~job
function create_job(client:insightapi2~insightconfig, body:insightapi2~job_creation_request, resp:insightapi2~httpresponse):insightapi2~job
function create_job(client:insightapi2~insightconfig, body:insightapi2~job_creation_request):insightapi2~job
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~job_creation_request. The params field should be empty.
body 
The job to create
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~job
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
201 insightapi2~job The job was successfully created
403 The user did not have authority to create the job, or did not have authority to execute the compute job on the execution service
404 insightapi2~error_response The scenario did not exist or was unavailable to the current user
422 insightapi2~error_response The job's execution mode did not exist in its app, or the request was not well-formed. This may be because: * The request contains an incorrect object type * The app cannot be executed * The execution mode did not exist for this scenario's app * The attachment tag rules are not met
423 insightapi2~error_response The scenario is already in the job queue
429 insightapi2~error_response There are currently more jobs than the configured maximum

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~job), 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~job
insightapi2~job_creation_request
insightapi2~insightconfig
insightapi2~httprequest
insightapi2~httpresponse

Parent Topic Jobs 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.