API for Requirement

Get Requirement list along with Custom Fields

POST /rest/requirements/list/viewColumns

Description

Fetch data of Requirements along with custom fields. Returns data from latest version.

Request

Content-Type: application/json

Parameters

Table 28. Get Requirement list along with Custom Fields

Name

Located in

Required

Description

Default

Schema

viewId

body

yes

View ID of the user for that particular project and Requirement module. View ID can be fetched from latestViews section of Getinfo API.

-

integer

folderPath

body

yes

Path of folder whose Requirements are to be fetched

-

string

start

body

no

Start index of records

-

integer

limit

body

no

Number of records per page

-

integer

page

body

no

Page number to be displayed

-

integer



Response

Content-Type: application/json

Table 29. Response Code

Status Code

Description

Response Model

200

Successful

Response Entity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Get Details of a Requirement

POST /rest/requirements/list

Description

Get details of a requirement by providing ID of requirement, requirement version ID or requirement folder.

Request

Content-Type: application/json

Parameters

Table 30. Get Details of a Requirement

Name

Located in

Required

Description

Default

Schema

start

body

no

Start index of records

-

integer

limit

body

no

Number of records per page

-

integer

page

body

no

Page number to be displayed

-

integer

id

body

yes

Id of Requirement

-

integer

filter

body

no

Filter to be applied

-

string



Response

Content-Type:application/json

Table 31. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntityString

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



List Requirement version detail

POST /rest/requirements/getVersionDetail

Request

Content-Type: application/json

Parameters

Table 32. List Requirement version detail

Name

Located in

Required

Description

Default

Schema

reqID

body

yes

Id of Requirement

-

integer

start

body

no

Start index of records

-

integer

limit

body

no

Number of records per page

-

integer

page

body

no

Page number to be displayed

-

integer



Response

Content-Type: application/json

Table 33. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



List Requirements for Bulk  Operation

POST /rest/requirements/listForBulkOperation

Request

Content-Type: application/json

Parameters

Table 34. List Requirements for Bulk Operation

Name

Located in

Required

Description

Default

Schema

folderPath

body

yes

FolderPath of folder whose requirements are to be listed

-

string

start

body

no

Start index of records

-

integer

limit

body

no

Number of records per page

-

integer

page

body

no

Page number to be displayed

-

integer

filter

body

no

Filter to be applied

-

Array[Filter]



Response

Content-Type: application/json

Table 35. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Fetch Requirement List For Issue

POST /rest/requirements/list/forIS

Description

Get Requirement list based on particular id of issue.

Request

Content-Type: application/json

Parameters

Table 36. Fetch Requirement List for Issue

Name

Located in

Required

Description

Default

Schema

dfID

body

no

Id of issue

-

integer

start

body

no

Start index of records

-

integer

getLinked

body

no

True to get only those requirements that are linked with this Issue, false to get those requirements which are not linked with this Issue

-

boolean

limit

body

no

Number of records per page

-

integer

page

body

no

Page number to be displayed

-

integer

getColumns

body

no

Apply filter on user defined fields' values

-

boolean

udfFilter

body

no

Apply filter on user defined fields' values

-

Array[UdfFilter]

filter

body

no

System filters to be applied

-

Array[Filter]

viewId

body

yes

View ID of the user for that particular project and Requirement module. View ID can be fetched from latestViews section of Getinfo API.

-

integer



Response

Content-Type: application/json

Table 37. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Get List of Requirements while Linking to a Test suite

POST /rest/requirements/list/forTS

Description

Requirement list for Test Suite.

Request

Content-Type: application/json

Parameters

Table 38. Fetch Requirement List for Issue

Name

Located in

Required

Description

Default

Schema

start

body

no

Start index of records

-

integer

limit

body

no

Number of records per page

-

integer

page

body

no

Page number to be displayed

-

integer

scope

body

yes

Scope of the Requirement, possible values project, release, cycle, build

-

string

getColumns

body

no

True to get list of all available filters(System + UDF) in 'filterTemplate' field

-

boolean

viewId

body

yes

View ID of the user for that particular project and Requirement module. View ID can be fetched from latestViews section of Getinfo API.

-

integer



Response

Content-Type: application/json

Table 39. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Fetch Requirement List For Test Case

POST /rest/requirements/list/forTC

Description

Get Requirement list based on particular id of test case.

Request

Content-Type: application/json

Parameters

Table 40. Fetch Requirement List for Test Case

Name

Located in

Required

Description

Default

Schema

tcID

body

no

Id of testcase

-

integer

start

body

no

Start index of records

-

integer

limit

body

no

Number of records per page

-

integer

page

body

no

Page number to be displayed

-

integer

scope

body

yes

Scope of the Requirement, possible values project, release, cycle, build

-

string

getColumns

body

no

True to get list of all available filters(System + UDF) in 'filterTemplate' field

-

boolean

viewId

body

yes

View ID of the user for that particular project and Requirement module. View ID can be fetched from latestViews section of Getinfo API.

-

integer



Response

Content-Type: application/json

Table 41. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



View Requirement Details

POST /rest/requirements/detail/data

Description

To view particular requirement's all fields

Request

Content-Type: application/json

Parameters

Table 42. View Requirement Details

Name

Located in

Required

Description

Default

Schema

version

body

yes

Version number of Requirement

-

integer

id

body

yes

Id of Requirement

-

integer



Response

Content-Type: application/json

Table 43. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



View Requirement's Version Information

POST /rest/requirements/versions/{id}

Request

Parameters

Table 44. View Requirement's Version Information

Name

Located in

Required

Description

Default

Schema

entityId

body

yes

Id of Requirement

-

integer

filter

body

no

filters to apply

-

Array[Filter]

id

body

yes

Id of Requirement

-

integer



Response

Content-Type: application/json

Table 45. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Create Requirement

POST /rest/requirements

Request

Content-Type:application/json

Parameters

Table 46. Create Requirement

Name

Located in

Required

Description

Default

Schema

rqFolderId

body

yes

FolderId of Requirement

-

string

name

body

yes

Summary of the Requirement

-

string

priority

body

no

Priority of Requirement

-

Array[integer]

component

body

no

Label of Requirement

-

Array[integer]

requirementState

body

no

Status of Requirement

-

Array[integer]

description

body

no

Description of Requirement

-

string

requirementOwner

body

no

Owner of Requirement

-

integer

scope

body

yes

Scope of the Requirement, possible values project,release,cycle,build

-

string



Response

Content-Type: application/json

Table 47. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

500

Returned when server connection times out

-



Update Requirement

PUT /rest/requirements

Request

Content-Type: application/json

Parameters

Table 48. Update Requirement

Name

Located in

Required

Description

Default

Schema

updateVersionFlag

body

no

Version number of Requirement(value = 3)

-

integer

updateWithVersion

body

no

Flag for the requirement update with version or not

-

boolean

description

body

no

Description of the Requirement

-

string

rqId

body

yes

Id of Requirement

-

integer

rqVersionId

body

yes

VersionId of Requirement

-

integer

requirementState

body

no

Status of Requirement

-

Array[integer]

priority

body

no

Priority of Requirement

-

Array[integer]

owner

body

no

Owner of Requirement

-

integer

name

body

no

Summary of Requirement

-

string

component

body

no

Label of Requirement

-

Array[integer]

versionComment

body

no

Comment about new version while creating it

-

string

bddData

body

no

Content which needs to save to QMetry.

-

string

fileName

body

no

Name of file from repository.

-

string

bddConfigrationID

body

no

BDD Configuration ID

-

integer

bddBranch

body

no

Branch name of repository.

-

string

bddFolderPath

body

no

Folder path of repository where file located.

-

string



Response

Content-Type: application/json

Table 49. Response Code

Status Code

Description

Response Model

200

Successful

RequirementRepository

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Archive Requirement

POST /rest/requirements/archiveEntity

Description

API To archive requirement based on specific version or all version

Request

Content-Type: application/json

Parameters

Table 50. Archive Requirement

Name

Located in

Required

Description

Default

Schema

entityIds

body

yes

An array of requirementId or requirementVersionId

-

Array[integer]

isArchived

body

yes

True for archive, false for unarchive

-

boolean

isEntityVersion

body

no

True for archive specific version of Requirement otherwise false

-

boolean



Response

Content-Type: application/json

Table 51. Response Code

Status Code

Description

Response Model

200

Successful

Response Entity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Delete Requirement

POST /rest/requirements/deleteEntity

Description

API To Delete Requirement

Request

Content-Type: application/json

Parameters

Table 52. Delete Requirement

Name

Located in

Required

Description

Default

Schema

entityIds

body

yes

An array of requirementId

-

Array[integer]



Response

Content-Type: application/json

Table 53. Response Code

Status Code

Description

Response Model

200

Successful

Response Entity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Delete Requirement Version

POST /rest/requirements/deleteEntityVersion

Description

API To Delete Requirement Version

Request

Content-Type: application/json

Parameters

Table 54. Delete Requirement Version

Name

Located in

Required

Description

Default

Schema

entityId

body

yes

Id of Requirement

-

integer

entityVersions

body

yes

An array of version number of the Requirement

-

Array[integer]



Response

Content-Type: application/json

Table 55. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



List Requirement Folders for selected folder

POST /rest/requirements/tree

Request

Content-Type: application/json

Parameters

Table 56. List Requirement Folders for selected folder

Name

Located in

Required

Description

Default

Schema

rqFolderID

body

yes

Folder ID of Selected Requirement Folder

-

integer

hideFolders

body

no

Flag to Hide empty Folders

-

boolean

sort

body

no

Sort Folders by date or name. E.g.

sort: "[{"property":"name","direction":"ASC"}]"

sort: "[{"property":"createdDate","direction":"DESC"}]"

-

string



Response

Content-Type: application/json

Table 57. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Create Requirement Folder

POST /rest/requirements/folders

Request

Content-Type: application/json

Parameters

Table 58. Create Requirement folder

Name

Located in

Required

Description

Default

Schema

parentId

body

yes

Id of parent folder

-

integer

name

body

yes

Folder Name

-

string



Response

Content-Type: application/json

Table 59. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Archive Requirement Folder

POST /rest/requirements/folder/archive

Request

Content-Type: application/json

Parameters

Table 60. Archive Requirement Folder

Name

Located in

Required

Description

Default

Schema

Archive Folder Request

body

yes

Archive Folder Inputs

-

RqFolderArchiveRequestDetail



Response

Content-Type: application/json

Table 61. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Unarchive Requirement Folder

POST /rest/requirements/folder/unarchive

Request

Content-Type: application/json

Parameters

Table 62. Unarchive Requirement Folder

Name

Located in

Required

Description

Default

Schema

Archive Folder Request

body

yes

Archive Folder Inputs

-

RqFolderArchiveRequestDetail



Response

Content-Type: application/json

Table 63. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Update Requirement Folder

PUT /rest/requirements/folders

Request

Content-Type: application/json

Parameters

Table 64. Update Requirement folder

Name

Located in

Required

Description

Default

Schema

folderId

body

yes

Unique identifier of Requirement Folder to update

-

integer

name

body

yes

Updated Folder Name

-

string



Response

Content-Type: application/json

Table 65. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Delete Requirement Folder

POST /rest/requirements/folders/delete

Request

Content-Type: application/json

Parameters

Table 66. Update Requirement folder

Name

Located in

Required

Description

Default

Schema

folderId

body

yes

Unique identifier of Requirement Folder

-

integer



Response

Content-Type: application/json

Table 67. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

500

Returned when server connection times out

-



Get List of Testcase in Requirement

POST /rest/requirements/testcase/list

Request

Content-Type: application/json

Parameters

Table 68. Get List of Testcase in Requirement

Name

Located in

Required

Description

Default

Schema

rqId

body

yes

Id of Requirement

-

integer

start

body

no

Start index of records

-

integer

limit

body

no

Number of records per page

-

integer

page

body

no

Page number to be displayed

-

integer



Response

Content-Type: application/json

Table 69. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



View Release & Cycle of Requirement

POST /rest/requirements/scope/list

Description

To view list of scope(Release/Cycle) for requirement

Request

Content-Type: application/json

Parameters

Table 78. View Release & Cycle of Requirement

Name

Located in

Required

Description

Default

Schema

entityId

body

yes

Id of Requirement

-

integer

start

body

no

Start index of records

-

integer

limit

body

no

Number of records per page

-

integer

page

body

no

Page number to be displayed

-

integer



Response

Content-Type: application/json

Table 79. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Add Release & Cycle Requirement

POST /rest/requirements/scope/add

Description

To view list of scope(Release/Cycle) for requirement

Request

Content-Type: application/json

Parameters

Table 80. Add Release & Cycle Requirement

Name

Located in

Required

Description

Default

Schema

entityId

body

yes

Id of Requirement

-

integer

sourceBuildId

body

yes

BuildId of the Cycle associated with Release

-

integer

sourceProjectId

body

yes

ProjectId of the Requirement

-

integer

sourceReleaseId

body

yes

ReleaseId of the Project

-

integer

sourceScope

body

yes

Scope of the requirement like project, release, build, cycle.

-

string

entityType

body

yes

Entity type for the requirement, the default value is RQ

-

string

releaseCycleMapping

body

yes

An array of release, cycle & version mapping

-

Array[ReleaseCycleMapping]

opType

body

yes

Operation types possible value likes otherscope or current

-

string

withVersion

body

no

Scope added with the version or not

-

boolean

updateFlag

body

no

This flag for the scope update or not

-

boolean

destinationProjectId

body

yes

ProjectId based on operation type, possible value likes current project or another project of the id

-

integer

entityData

body

yes

An array of entityId & version for the Requirement

-

Array[EntityData]



Response

Content-Type: application/json

Table 81. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Remove Release & Cycle from Requirement

POST /rest/requirements/scope/add

Description

To view list of scope(Release/Cycle) for requirement

Request

Content-Type: application/json

Parameters

Table 82. Add Release & Cycle Requirement

Name

Located in

Required

Description

Default

Schema

entityId

body

yes

Id of Requirement

-

integer

sourceBuildId

body

yes

BuildId of the Cycle associated with Release

-

integer

sourceProjectId

body

yes

ProjectId of the Requirement

-

integer

sourceReleaseId

body

yes

ReleaseId of the Project

-

integer

sourceScope

body

yes

Scope of the requirement like project, release, build, cycle.

-

string

entityType

body

yes

Entity type for the requirement, the default value is RQ

-

string

releaseCycleMapping

body

yes

An array of release, cycle and version mapping

-

Array[ReleaseCycleMapping]

opType

body

yes

Operation types possible value likes otherscope or current

-

string

withVersion

body

no

Scope added with the version or not

-

boolean

updateFlag

body

no

This flag for the scope update or not

-

boolean

destinationProjectId

body

yes

ProjectId based on operation type, possible value likes current project or another project of the id

-

integer

entityData

body

yes

An array of entityId & version for the Requirement

-

Array[EntityData]



Response

Content-Type: application/json

Table 83. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Get List of Users for Project

POST /rest/requirements/list/projectUsers

Request

Content-Type: application/json

Parameters

Table 84. Get List of Users for Project

Name

Located in

Required

Description

Default

Schema

projectId

body

yes

ProjectId

-

integer

rqID

body

yes

Entity Key of Requirement

-

integer



Response

Content-Type: application/json

Table 85. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

500

Returned when server connection times out

-



Get BDD Branch List

POST /rest/requirements/getBranchList

Description

Get the branch of repository.

Request

Content-Type: application/json

Parameters

Table 86. Get BDD Branch List

Name

Located in

Required

Description

Default

Schema

bddConfigID

body

yes

ID of BDD repository for particular project from DB.

-

integer



Response

Content-Type: application/json

Table 87. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Pull File from Repository

POST /rest/requirements/pullFile

Request

Content-Type: application/json

Parameters

Table 88. Pull File from Repository

Name

Located in

Required

Description

Default

Schema

bddConfigrationID

body

yes

ID of BDD repository for particular project from DB.

-

integer

fileName

body

yes

Name of the file which needs to get data from the repository.

-

string

bddFolderPath

body

yes

Folder path of the repository where the file is located. If it is on root level, then there will be empty data.

-

string

rqVersionID

body

yes

ID of rqversion from DB.

-

integer

bddBranch

body

yes

Branch name of the repository from where the data will be pulled.

-

string



Response

Content-Type: application/json

Table 89. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Push File to Repository

POST /rest/requirements/pushFile

Request

Content-Type: application/json

Parameters

Table 90. Push File to Repository

Name

Located in

Required

Description

Default

Schema

bddData

body

yes

Content that needs to be pushed to the repository.

-

string

bddConfigrationID

body

yes

ID of BDD repository for particular project from DB.

-

integer

fileName

body

yes

Name of the file which needs to get data from the repository.

-

string

bddFolderPath

body

yes

Folder path of the repository where the file is located. If it is on root level, then there will be empty data.

-

string

comments

body

yes

Push comments for file.

-

string

rqVersionID

body

yes

ID of rqversion from DB.

-

integer

bddBranch

body

yes

Branch name of the repository from where the data will be pulled.

-

string

notifyUser

body

no

Whether to notify user (in "userList" parameter) or not.

-

boolean

userList

body

no

*(needed if notifyUser is set "true")

List of QMetry users to whom the mail intimating the file push needs to be sent.

-

string



Response

Content-Type: application/json

Table 91. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Update Requirements with BDD data

PUT /rest/requirements

Request

Content-Type: application/json

Parameters

Table 92. Update Requirements with BDD data

Name

Located in

Required

Description

Default

Schema

updateVersionFlag

body

no

Version number of Requirement(value = 3)

-

integer

updateWithVersion

body

no

Flag for the requirement update with version or not

-

boolean

description

body

no

Description of the Requirement

-

string

rqId

body

yes

ID of the Requirement

-

integer

rqVersionId

body

yes

VersionId of the Requirement

-

integer

requirementState

body

no

Status of the Requirement

-

Array[integer]

priority

body

no

Priority of the Requirement

-

Array[integer]

owner

body

no

Owner of Requirement

-

string

name

body

no

Summary of Requirement

-

string

component

body

no

Label of Requirement

-

Array[integer]

versionComment

body

no

Comment about new version while creating it

-

string

bddData

body

yes

Content that needs to be pushed to the repository.

-

string

bddConfigrationID

body

yes

BDD Configuration ID

-

integer

fileName

body

yes

Name of the file which needs to get data from the repository.

-

string

bddFolderPath

body

yes

Folder path of the repository where the file is located. If it is on root level, then there will be empty data.

-

string

bddBranch

body

yes

Branch name of the repository from where the data will be pulled.

-

string



Response

Content-Type: application/json

Table 93. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Get BDD Folder Tree

POST /rest/requirements/getBDDFolderTree

Description

Get list of associated folders

Request

Content-Type: application/json

Parameters

Table 94. Push File to Repository

Name

Located in

Required

Description

Default

Schema

bddConfigrationID

body

yes

ID of BDD repository for particular project from DB.

-

integer

bddBranch

body

yes

Branch name of repository.

-

string

folderPath

body

no

Path of the folder for which user wants to get the child folders in case of BitBucket repository.

-

string



Note

In case of Bitbucket repository, the API request returns first level of directory structure. To drill down to child folders, call the API again with the "folderPath" parameter that contains "fullPath" from the previous API response.

Response

Content-Type: application/json

Table 95. Response Code

Status Code

Description

Response Model

200

Successful

ResponseEntity

400

Invalid json object or mandatory fields missing

-

401

Unauthorised or session expired

-

500

Returned when server connection times out

-



Definitions

EntityManager

Table 96. EntityManager

name

type

required

description

example

properties

object

optional

-

-

open

boolean

optional

-

-

delegate

object

optional

-

-

entityManagerFactory

EntityManagerFactory

optional

-

-

joinedToTransaction

boolean

optional

-

-

criteriaBuilder

CriteriaBuilder

optional

-

-

transaction

EntityTransaction

optional

-

-

flushMode

string

optional

-

-

metamodel

Metamodel

optional

-

-



EntityManagerFactory

Table 97. EntityManagerFactory

name

type

required

description

example

properties

object

optional

-

-

cache

-

optional

-

-

open

boolean

optional

-

-

criteriaBuilder

CriteriaBuilder

optional

-

-

persistenceUnitUtil

persistenceUnitUtil

optional

-

-

metamodel

Metamodel

optional

-

-



EntityTransition

Table 98. EntityTransition

name

type

required

description

example

active

boolean

optional

-

-

rollbackOnly

boolean

optional

-

-



Metamodel

Table 99. Metamodel

name

type

required

description

example

entities

array[EntityTypeObject]

optional

-

-

managedTypes

array[ManagedTypeObject]

optional

-

-

embeddables

array[EmbeddableTypeObject]

optional

-

-



ResponseEntity

Table 100. Response Entity

name

type

required

description

example

headers

object

optional

-

-

body

object

optional

-

-

statusCode

string

optional

-

-



RequirementRepository

Table 101. RequirementRepository

name

type

required

description

example

manager

EntityManager

optional

-

-

fieldMapForViewColumns

object

optional

-

-

joinExistsListForTS

array[string]

optional

-

-



ReleaseCycleMapping

Table 102. ReleaseCycleMapping

name

type

required

description

example

release

integer

required

ID of release

-

cycle

array[integer]

required

An array of cycle's Id

-

version

integer

required

Number of the version

-



EntityTypeObject

Table 103. EntityTypeObject

name

type

required

description

example

name

string

optional

-

-

supertype

IdentifiableTypeObject

optional

-

-

idClassAttributes

array[SingularAttributeObjectObject]

optional

-

-

idType

TypeObject

optional

-

-

attributes

array[AttributeObjectObject]

optional

-

-

declaredAttributes

array[AttributeObjectObject]

optional

-

-

pluralAttributes

array[PluralAttributeObjectObjectObject]

optional

-

-

SingularAttributes

array[SingularAttributeObjectObject]

optional

-

-

declaredPluralAttributes

array[PluralAttributeObjectObjectObject]

optional

-

-

declaredSingularAttributes

array[SingularAttributeObjectObject]

optional

-

-

persistenceType

string

optional

-

-

bindableType

string

optional

-

-



EmbeddableTypeObject

Table 104. EmbeddableTypeObject

name

type

required

description

example

attributes

array[AttributeObjectObject]

optional

-

-

declaredAttributes

array[AttributeObjectObject]

optional

-

-

pluralAttributes

array[PluralAttributeObjectObjectObject]

optional

-

-

SingularAttributes

array[SingularAttributeObjectObject]

optional

-

-

declaredPluralAttributes

array[PluralAttributeObjectObjectObject]

optional

-

-

declaredSingularAttributes

array[SingularAttributeObjectObject]

optional

-

-

persistenceType

string

optional

-

-



ManagedTypeObject

Table 105. ManagedTypeObject

name

type

required

description

example

attributes

array[AttributeObjectObject]

optional

-

-

declaredAttributes

array[AttributeObjectObject]

optional

-

-

pluralAttributes

array[PluralAttributeObjectObjectObject]

optional

-

-

SingularAttributes

array[SingularAttributeObjectObject]

optional

-

-

declaredPluralAttributes

array[PluralAttributeObjectObjectObject]

optional

-

-

declaredSingularAttributes

array[SingularAttributeObjectObject]

optional

-

-

persistenceType

string

optional

-

-



IdentifiableTypeObject

Table 106. ManagedTypeObjectIdentifiableTypeObject

name

type

required

description

example

supertype

IdentifiableTypeObject

optional

-

-

idClassAttributes

array[SingularAttributeObjectObject]

optional

-

-

idType

TypeObject

optional

-

-

attributes

array[AttributeObjectObject]

optional

-

-

declaredAttributes

array[AttributeObjectObject]

optional

-

-

pluralAttributes

array[PluralAttributeObjectObjectObject]

optional

-

-

SingularAttributes

array[SingularAttributeObjectObject]

optional

-

-

declaredPluralAttributes

array[PluralAttributeObjectObjectObject]

optional

-

-

declaredSingularAttributes

array[SingularAttributeObjectObject]

optional

-

-

persistenceType

string

optional

-

-



AttributeObjectObject

Table 107. AttributeObjectObject

name

type

required

description

example

name

string

optional

-

-

declaringType

ManagedTypeObject

optional

-

-

collection

boolean

optional

-

-

persistentAttributeType

string

optional

-

-

javaMember

Member

optional

-

-

association

boolean

optional

-

-



SingularAttributeObjectObject

Table 108. AttributeObjectObject

name

type

required

description

example

type

TypeObject

optional

-

-

version

boolean

optional

-

-

optional

boolean

optional

-

-

id

boolean

optional

-

-

name

string

opional

-

-

declaringType

ManagedTypeObject

optional

-

-

collection

boolean

optional

-

-

persistentAttributeType

string

optional

-

-

javaMember

Member

optional

-

-

association

boolean

optional

-

-

bindableType

string

optional

-

-



PluralAttributeObjectObjectObject

Table 109. PluralAttributeObjectObjectObject

name

type

required

description

example

elementType

TypeObject

optional

-

-

collectionType

string

optional

-

-

name

string

opional

-

-

declaringType

ManagedTypeObject

optional

-

-

collection

boolean

optional

-

-

persistentAttributeType

string

optional

-

-

javaMember

Member

optional

-

-

association

boolean

optional

-

-

bindableType

string

optional

-

-



Member

Table 110. Member

name

type

required

description

example

modifiers

integer

optional

-

-

name

string

opional

-

-

synthetic

boolean

optional

-

-



TypeObject

Table 111. TypeObject

name

type

required

description

example

persistenceType

-

-

-

-



Filter

Table 112. Filter

name

type

required

description

example

value

object

required

Value to search based on type of filter

-

comparison

string

required

The comparison operator 'lt' or 'gt' for Date type filter

-

type

string

required

Type of Filter

-

field

string

required

Field name on which filter is to be applied



EntityData

Table 113. EntityData

name

type

required

description

example

entityId

integer

required

Id of EntityId of Entity

-

version

integer

required

VersionId of Entity

-



RqFolderArchiveRequestDetail

Table 114. RqFolderArchiveRequestDetail

name

type

required

description

example

rqFolderIDs

array[integer]

required

Array of Requirement Folder Ids

-

isBulkOperation

boolean

optional

Is from BulkOperation flag

-

isSingleOperation

boolean

optional

Is single operation

-

includeRootFolderEntities

boolean

optional

Required to include Root Folder Entities

-



RqFolderUnarchiveRequestDetail

Table 115. RqFolderUnarchiveRequestDetail

name

type

required

description

example

rqFolderIDs

array[integer]

required

Array of Requirement Folder Ids

-

isBulkOperation

boolean

optional

Is from BulkOperation flag

-

isSingleOperation

boolean

optional

Is single operation

-

includeRootFolderEntities

boolean

optional

Required to include Root Folder Entities

-



UdfFilter

Table 116. UdfFilter

name

type

required

description

example

type

string

required

Array of Requirement Folder Ids

-

value

boolean

optional

Is from BulkOperation flag

-

udfmID

boolean

optional

Is single operation

-

field

boolean

optional

Required to include Root Folder Entities

-



RequirementRepository

Table 117. RequirementRepository

name

type

required

description

example

manager

EntityManager

optional

-

-

fieldMapForViewColumns

object

optional

-

-

joinExistsListForTS

array[string]

optional

-

-



Publication date: