The structure of the “applicant” object is described below
{
"applicant": [
{
"value": "",
"reference": "",
"id": 0
}
]
}
In the reference image in ASMS, you can see the Requester field.
| Properties | Description |
|---|---|
| value | Requester ID in DevOps, will be related to an additional list-type field since this concept does not exist in DevOps |
| Reference | Unique identifier to create a relationship between the concepts project > category, itemType, typeRegister, applicant, responsibleGroup, responsible, company, client see |
| Id | Applicant ID in ASMS |
EXAMPLE: Applicant Relationship in Aranda/DevOps ASMS
To create the list of applicants, follow the instructions below:
- Get the IDs of Aranda ASMS applicants.
- Get the IDs/names of DevOps applicants.
- Assign the following applicant equivalence:
| DevOps Applicant | Applicant in Aranda | Applicant Id Aranda | |
|---|---|---|---|
| applicant 1 | Applicant 1 | 1 | |
| applicant 2 | Applicant 2 | 13 |
- Type the Applicant Id Aranda On Property “id” and the DevOps Applicant of its equivalent taken from DevOps Applicant On Property value
{
"applicant": [
{
"id": 1,
"value": "applicant 1"
},
{
"id": 13,
"value": "applicant 2"
}
]
}