Skip to main content
Version: 2.2.3

REQ_REFERENCE_INTERFACE

This method allows inserting a reference requirement using a REST web service. The recorded requirement will be available on the Requirement -> File -> Requirement screen.

POST /apigateway/se/generic/gn_webservice/gn_webservice_execute.php

Query parameters:

Query parametersTypeRequiredDescription
cdprodNumericYesProduct code
Constant value: 227
classnameStringYesClass name used in WADL
Constant value: req_reference_interface
classpathStringYesPath to the class used in WADL
Constant value: req_import

Example request:

Supported attributes:

Request body parameterTypeRequiredDescription
idrequirementStringYesRequirement ID #
nmrequirementStringYesRequirement name
idreqtypeStringYesRequirement type ID #
idrespuserStringYesResponsible user ID
idrespteamStringNoResponsible team ID #
iddocumentStringNoDocument ID #
dsurlStringNoUrl
iduserinitStringYes¹Starter user ID
dsdescriptionStringNoDescription
instanceStringNoThe value of this constant must be:
%WF_IDINSTANCE%
idactStringNoInstance activity ID #
actionStringNoThe action type that will be performed on the screen:
1 - Insert
info

Yes¹ - The iduserinit field will be required when the requirement revision is via workflow.

{
"idrequirement": "string",
"nmrequirement": "string",
"idreqtype": "string",
"idrespuser": "string",
"idrespteam": "string",
"dsurl": "string",
"iddocument": "string",
"iduserinit": "string",
"dsdescription": "string",
"instance": "string",
"idact": "string",
"action": 1
}

Example response:

200 OK

{
"success": true,
"total": 1,
"results": [
{
"Result": true,
"Code": 1
}
]
}