Facade API Test Cases

Test Case ID Type Description
Verify in Aconex that a document is correctly upserted

on the basis of entity when single or multiple attributes
are passed using INPUT Parameters to POST under
BATCH Action based on defined Request body in XML
INPUT Parameters:
X-EIP-ClientApplication=xxxxxxx
contextName=xxxxxxxx
EIP_224_01 MANUAL
are passed using INPUT Parameters to POST under
BATCH Action based on defined Request body in JSON
INPUT Parameters:
MANUAL
are passed along with documentNumber using INPUT
Parameters to POST under BATCH Action based on
defined Request body in XML
INPUT Parameters:
MANUAL
are passed along with documentNumber using INPUT
Parameters to POST under BATCH Action based on
defined Request body in JSON
INPUT Parameters:
MANUAL
Verify in Aconex that multiple document is correctly
upserted on the basis of entity when single or multiple
attributes are passed using INPUT Parameters to POST
under BATCH Action based on defined Request body in
XML
INPUT Parameters:
MANUAL
attributes are passed using INPUT Parameters to POST
under BATCH Action based on defined Request body in
JSON
INPUT Parameters:
MANUAL
attributes are passed along with documentNumber
using INPUT Parameters to POST under BATCH Action
based on defined Request body in XML
INPUT Parameters:
MANUAL
attributes are passed along with documentNumber
using INPUT Parameters to POST under BATCH Action
based on defined Request body in JSON
INPUT Parameters:
MANUAL
Verify in Aconex that single or multiple document is
correctly upserted on the basis of entity when INPUT
Parameters are blank under BATCH Action using POST
method based on defined Request body in XML
INPUT Parameters:
X-EIP-ClientApplication=
contextName=
MANUAL
Parameters are blank under BATCH Action using POST
method based on defined Request body in JSON
INPUT Parameters:
contextName=
MANUAL
Parameters contain invalid value under BATCH Action
using POST method based on defined Request body in
XML
INPUT Parameters:
contextName=
MANUAL
Parameters contain invalid value under BATCH Action
using POST method based on defined Request body in
JSON
INPUT Parameters:
contextName=
MANUAL
correctly upserted on the basis of entity using INPUT
Parameters to POST under BATCH Action when all
attibutes contain blank value based on defined Request
body in XML
INPUT Parameters:
contextName=
MANUAL
attibutes contain blank value based on defined Request
body in JSON
INPUT Parameters:
contextName=
MANUAL
Parameters to POST under BATCH Action when single or
multiple attibutes contain blank value based on defined
Request body in XML
INPUT Parameters:
contextName=
MANUAL
multiple attibutes contain blank value based on defined
Request body in JSON
INPUT Parameters:
contextName=
MANUAL
attibutes contain invalid value based on defined
Request body in XML
INPUT Parameters:
contextName=
MANUAL
attibutes contain invalid value based on defined
Request body in JSON
INPUT Parameters:
contextName=
MANUAL
multiple attibutes contain invalid value based on
defined Request body in XML
INPUT Parameters:
contextName=
MANUAL
INPUT Parameters:
contextName=
MANUAL
INPUT Parameters:
contextName=
MANUAL
Verify in Acones that single or multiple document is
param in POST request under BATCH Action when
single or multiple attributes is passed along with
mandatory attribute documentId in request body in
XML
MANUAL
JSON
MANUAL
mandatory attribute documentNumber in request body
in XML
MANUAL
in JSON
MANUAL
mandatory attribute Title in request body in XML
MANUAL
mandatory attribute Title in request body in JSON
MANUAL
mandatory attribute documentType in request body in
XML
MANUAL
JSON
MANUAL
mandatory attribute discipline in request body in XML
MANUAL
mandatory attribute discipline in request body in JSON
MANUAL
mandatory attribute documentStatus in request body in
XML
MANUAL
JSON
MANUAL
mandatory attribute dateIssued in request body in XML
MANUAL
mandatory attribute dateIssued in request body in JSON
MANUAL
mandatory attribute originatingCompany in request
body in XML
MANUAL
body in JSON
MANUAL
mandatory attribute revision in request body in XML
MANUAL
mandatory attribute revision in request body in JSON
MANUAL
Verify in Acones that single or multiple document
should not upserted on the basis of entity using INPUT
single or multiple attributes is passed without
XML
MANUAL
JSON
MANUAL
in XML
MANUAL
in JSON
MANUAL
mandatory attribute title in request body in XML
MANUAL
mandatory attribute title in request body in JSON
MANUAL
XML
MANUAL
JSON
MANUAL
mandatory attribute discipline in request body in XML
MANUAL
mandatory attribute discipline in request body in JSON
MANUAL
XML
MANUAL
JSON
MANUAL
mandatory attribute dateIssued in request body in XML
MANUAL
mandatory attribute dateIssued in request body in JSON
MANUAL
body in XML
MANUAL
body in JSON
MANUAL
mandatory attribute revision in request body in XML
MANUAL
mandatory attribute revision in request body in JSON
MANUAL
Validate in Aconex date format of dateOnDocument
attribute using INPUT param is passed in POST under
BATCH Action based on defined Request body in XML
INPUT Parameters:
contextName=
MANUAL
Validate in Aconex date format of dateOnDocument
attribute using INPUT param is passed in POST under
BATCH Action based on defined Request body in JSON
INPUT Parameters:
contextName=
MANUAL
Validate datatype String, Date, Integer, boolean of all
document attribute in entity using INPUT param to
POST under BATCH Action based on defined Request
body in XML
MANUAL
Validate datatype String, Date, Integer, boolean of all
document attribute in entity using INPUT param to
POST under BATCH Action based on defined Request
body in JSON
MANUAL
Validate datatype length of all document attribute in
entity using INPUT param to POST under BATCH Action
MANUAL
Validate datatype length of all document attribute in
entity using INPUT param to POST under BATCH Action
MANUAL
Verify in Aconex that single or multiple document
should not be upserted on the basis of entity when
INPUT Param is passed in POST request under BATCH
Action and Request Body is Blank
MANUAL
Verify in Aconex that single or multiple document
should not be upserted on the basis of entity using
when incorrect WADL is passed
MANUAL
Extract list of Aconex projects that are configured in
MCDB using GET method based on defined WADL
containing contexts and validate data response with
MCDB
MANUAL
Verify that when unsecure protocol http is passed in
WADL then an error should return using GET method
upon trying to extract list of Aconex project that are
configured in MCDB
MANUAL
Verify that when MCDB is not connected with Aconex

then an error should return using GET method upon
trying to extract list of Aconex project that are
MANUAL configured in MCDB
A list of Aconex projects should not return that are
configured in MCDB using GET method when incorrect
WADL is passed in that case an error should return
MANUAL
Validate the XML/JSON response which is getting from
Aconex side it should be correct and human readable
MANUAL
Extract specific details of Aconex project that are
configured in MCDB using GET Method based on
defined WADL containing {context Name} param and
validate data response with MCDB
MANUAL
Verify when null value is passed in contextName param
using GET method based on defined WADL in that case
an error should display
MANUAL
Verify when special character value is passed in
contextName param using GET method based on
defined WADL in that case an error should display
MANUAL
Verify when String,float,int,char value is passed in
contextName param using GET method based on
defined WADL in that case an error should display
MANUAL
Verify when space value is passed in contextName
param using GET method based on defined WADL in
that case an error should display
MANUAL
Verify that when unsecure protocol http is passed in
WADL then an error should return using GET method
upon trying to extract specific details of Aconex project
that are configured in MCDB
MANUAL
Verify that when MCDB is not connected with Aconex
then an error should return using GET method upon
trying to extract specific details of Aconex project that
MANUAL are configured in MCDB
A specific details of Aconex projects should not return
that are configured in MCDB using GET method when
incorrect WADL is passed in that case an error should
return
MANUAL
Validate the XML/JSON response which is getting from
TEAMWorks side it should be correct and human
readable
MANUAL
Extract document from Aconex by perfoming filter
operation using GET method based on defined
mandatory parameters with single or multiple attribute
contextName=
documentId=
dateIssued=
documentNumber=
title=
Refer Coloumn D under Aconex Facade GET API Matrix

Workbook

operation using GET method based on defined
mandatory parameters with single or multiple attribute
contextName=
documentId=
dateIssued=
documentNumber=
title=
showDocumentHistory=
q=
Extract document should not return from Aconex by
perfoming filter operation using GET method when
invalid value is passed in filter and mandatory param
contextName=
documentId=
dateIssued=
documentNumber=
title=

invalid value is passed in mandatory param
contextName=
documentId=
dateIssued=
documentNumber=
title=

invalid value is passed in filter param
contextName=
documentId=
dateIssued=
documentNumber=
title=

blank value is passed in all parameter
contextName=
documentId=
dateIssued=
documentNumber=
title=
blank value is passed in all filter param except
mandatory parameter
contextName=
documentId=
dateIssued=
documentNumber=
title=

perfoming filter operation using GET method when only
mandatory parameter contains blank value
X-EIP-ClientApplication=xxxxxx
contextName=xxxxxxx
documentId=
dateIssued=
documentNumber=
title=

X-EIP-ClientApplication contains blank value
contextName=xxxxxxx
documentId=
dateIssued=
documentNumber=
title=

X-EIP-ClientApplication contains blank value
contextName=xxxxxxx
documentId=
dateIssued=
documentNumber=
title=
invalid value is passed in showDocumentHistory and q
parameter
contextName=
documentId=
dateIssued=
documentNumber=
title=
q=

operation using GET method when blank value is passed
in showDocumentHistory and q parameter
contextName=
documentId=
dateIssued=
documentNumber=
title=
q=
Validate datatype of all attribute by replacing

Integer,Boolen, String with string ,char,float in filter
operation using Get method
Validate datatype length of all attribute in filter

operation using GET method
Extract document from Aconex using GET method with
single or multiple filter attribute based on provided
param as per below
X-EIP-ClientApplication : DSC
contextName :26089_xxx
documentId : 1353331688066671054
pageSize=25
pageIndex=1
sort= originatingCompany.ASC
showDocumentHistory=true
q=true
Extract document from Aconex using GET method

based on provided param without attribute in that case
full document result should display
pageSize=25
pageIndex=1
q=false

based on provided param without attribute in that case
full document result should display
pageSize=25
pageIndex=1
q=false
when shortDocumentHistory and q param is blank
pageSize=25
pageIndex=1
shortDocumentHistory=
q=
Extract documentin ASC or DESC from Aconex using GET

method based on provided sort param
pageSize=25
pageIndex=1

based on provided paging param
pageSize=25
pageIndex=1
Extract document from Aconex using GET method when

all param is blank except mandatory parameters
pageSize=
pageIndex=
sort=
q=
Mandatory Parameters:
Extract document should not return from Aconex using
GET method when mandatory parameters contains
blank value
pageSize=
pageIndex=
sort=
q=
X-EIP-ClientApplication :
contextName :
Extract document should not return from Aconex using

GET method when mandatory parameters is missing
pageSize=
pageIndex=
sort=
q=
contextName :

only pageSize value is passed in parameter
pageSize=
contextName :
only pageIndex param is passed remaining is blank
pageIndex=
contextName :

only sort param is passed remaining is blank
pageIndex=
contextName :
Verify that document should not return from Aconex

using GET method when string,float,char is passed in
pageSize and pageIndex
contextName=xxxxxx
commodityName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
Commodity name can be Valve,Spool,Bulkpipe
Extract project specific commodity records from

TEAMWorks using GET method when pageSize param
cross default pageSize value (like 150 size)
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx

Verify that project specific commodity records should
not return from TEAMWorks using GET method when
pageIndex param contains either negative or zero value
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
This test case is to verify when we are passing

parameter values {search_type=FULL} to get a list of
document from a specific aconex project in pages
EIP_224_03 MANUAL
parameter values
{
search_type=FULL
documentNumber=0987654321
} to get a matching document metadata from a specific
aconex project in pages
EIP_224_04 MANUAL
parameter values
{
search_type=FULL
documentNumber=0987654321
sortField=
sortDirection=
}
to get latest revision of each matching document
metadata from a specific aconex project in pages
EIP_224_05 MANUAL
parameter values
{
search_type=FULL
documentNumber=
sortField=
sortDirection=
showDocumentHistory=true} to get all latest revision of
matching document from specific aconex project in
pages
EIP_224_06 MANUAL
This test case is to verify when we are passing valid
multiple parameter values
{
ClientApplication=DSC
search_type=FULL
documentNumber=
trackingid=
documentType
discipline=
title=
author=
sortField=
sortDirection=
} to get matching document metadata from a specific
EIP_224_07 MANUAL
This test case is to verify when we are passing invalid
parameter values
{
search_type=FULL
documentNumber=
trackingid=
documentType
discipline=
title=
author=
sortField=
sortDirection=
} to get matching document metadata from a specific
EIP_224_08 MANUAL
parameter values
{
search_type=FULL1312#$#%
}
EIP_224_09 MANUAL
This test case is to verify when "search_type"
parameter is set to blank.
EIP_27_10 MANUAL
This test case is to verify when "search_type"
parameter is set with invalid values (eg. Sfsf,13212,!@!
13212,000)
EIP_27_11 MANUAL
This test case is to verify when "search _type"
parameter is set to null value
EIP_27_12 MANUAL

parameter values
{
search_type=NUMBER_LIMITED
search_Result_Size = 75
}
to get metadata from specific aconex project in pages
EIP_224_13 MANUAL
parameter values
{
search_type=NUMBER_LIMITED34343443
search_result_ size = 23
}
EIP_224_14 MANUAL
parameter values
{
search_type=123526735
search_result_ size = 2343@$
}
EIP_224_15 MANUAL
parameter values
{
search type=134231@$$@
search_result_ size = $#%
}
EIP_224_16 MANUAL
parameter values
{
search_result_ size = 000000
}
EIP_224_17 MANUAL
parameter values
{
search_result_ size = null
}
EIP_224_18 MANUAL
parameter values
{
search_type= NUMBER_LIMITED
search_result_ size =
}
EIP_224_19 MANUAL
This test case is to verify when we are passing valid
multiple parameter values
{
documentNumber=
trackingid=
documentType
discipline=
title=
author=
}
EIP_224_20 MANUAL
parameter values
{
documentNumber=fgfg32432
trackingid=fdgfdg454
documentType=000ghhfgh32432@$
discipline=fdgfd#@$224
title=fgfgd@$@!$223214
author=gfdghfth@$@@$24324
}
EIP_224_21 MANUAL
parameter values
{
search_type=PAGED
page_size= 75
page_number=8
}
to get document metadata from specific aconex project
in pages
EIP_224_22 MANUAL
parameter values {search_type=PAGED
page_size= 77
page_number=8
}
in pages
EIP_224_23 MANUAL
parameter values
{
search_type=PAGED
page_size= 77
page_number=8
}
in pages
EIP_224_24 MANUAL
parameter values
{
search_type=PAGED
page_size= 77
page_number=8
}
to get document metadata from a specific aconex
project in pages
EIP_224_25 MANUAL
parameter values
{
search_type=PAGEDfdgtfdg
page_size= fsdfdsf
page_number=dgfdggfd
}
project in pages
EIP_224_26 MANUAL
parameter values
{
search_type=PAGED
page_size=
page_number=
show_document_history=343435
}
project in pages
EIP_224_27 MANUAL
parameter values
{
search_type=null
page_size= null
page_number=null
show_document_history=true
}
project in pages
EIP_224_28 MANUAL
This test case is to verify when we are passing multiple
parameter values
{
search_type=PAGED
documentNumber=
trackingid=
documentType
discipline=
title=
author=
}
project in pages
EIP_224_29 MANUAL
invalid parameter values
{
documentNumber=
trackingid=
documentType
discipline=
title=
author=
sortField=docno
sortDirection=ASC
showDocumentHistory=true}
EIP_224_30 MANUAL
parameter values
{
search_type= COUNT_ONLY
}
EIP_224_31 MANUAL
parameter values
{
documentNumber=
}
to get count of matching document from a specific
Aconex project
EIP_224_32 MANUAL
parameter values
{
discipline=
}
Aconex project
EIP_224_33 MANUAL
parameter values
{
author=
}
Aconex project
EIP_224_34 MANUAL
parameter values
{
search_type= COUNT_ONLY35646
pagesize=75
}
Aconex project
EIP_224_35 MANUAL
parameter values
{
search_type=COUNT_ONLY
documentNumber=
trackingid=
documentType=
discipline=
title=
author=
}
Aconex project
EIP_224_36 MANUAL
parameter values
{
search_type=COUNT_ONLY
documentNumber=
trackingid=
documentType=
discipline=
title=
author=
}
EIP_224_37 MANUAL
This test case is to verify whether document is
searchable and sortable when attribute name is
"approved"
EIP_225_38 MANUAL
"asBuiltRequired"
EIP_225_39 MANUAL
searchable and sortable when passing multiple
parameter value(for eg. title,author so on.)
EIP_225_40 MANUAL
"attribute1"
EIP_225_41 MANUAL
"attribute2"
EIP_225_42 MANUAL
"attribute3"
EIP_225_43 MANUAL
"attribute4"
EIP_225_44 MANUAL
"author"
EIP_225_45 MANUAL
"authorisedBy"
EIP_225_46 MANUAL
"category"
EIP_225_47 MANUAL
"check1"
EIP_225_48 MANUAL
"check2"
EIP_225_49 MANUAL
"comments"
EIP_225_50 MANUAL
"comments2"
EIP_225_51 MANUAL
"confidential"
EIP_225_52 MANUAL
"contractDeliverable"
EIP_225_53 MANUAL
"contractnumber"
EIP_225_54 MANUAL
"contractorrev"
EIP_225_55 MANUAL
"current"
EIP_225_56 MANUAL
searchable and sortable when attribute name is "date1"
EIP_225_57 MANUAL
"date2"
EIP_225_58 MANUAL
"discipline"
EIP_225_59 MANUAL
"docno"
EIP_225_60 MANUAL
"doctype"
EIP_225_61 MANUAL
"filename"
EIP_225_62 MANUAL
"fileSize"
EIP_225_63 MANUAL
"fileType"
EIP_225_64 MANUAL
"forreview"
EIP_225_65 MANUAL
"markupdate"
EIP_225_66 MANUAL
"markupLastModifiedDate"
EIP_225_67 MANUAL
"milestonedate"
EIP_225_68 MANUAL
"numberOfMarkups"
EIP_225_69 MANUAL
"packagenumber"
EIP_225_70 MANUAL
"percentComplete"
EIP_225_71 MANUAL
"plannedsubmissiondate"
EIP_225_72 MANUAL
"printSize"
EIP_225_73 MANUAL
"projectField1"
EIP_225_74 MANUAL
"projectField2"
EIP_225_75 MANUAL
"projectField3"
EIP_225_76 MANUAL
"received"
EIP_225_77 MANUAL
"reference"
EIP_225_78 MANUAL
"registered"
EIP_225_79 MANUAL
"reviewed"
EIP_225_80 MANUAL
"reviewSource"
EIP_225_81 MANUAL
searchable and sortable when passing parameters value
with attribute field.
For eg.
{ sortField=docno
sortdirection=DESC
documentNumber=
}
EIP_225_82 MANUAL
searchable and sortable when passing multiple
parameters value with attribute field.
For eg.
{ sortField=docno
sortdirection=DESC
documentNumber=
discipline=
title=
author=
}
EIP_225_83 MANUAL
values in "sort_field" parameter.
EIP_225_84 MANUAL
values in "sort_direction" parameter.
EIP_225_85 MANUAL
values in "dataApproved" parameter.
EIP_225_86 MANUAL
values in "content_search" parameter.
EIP_225_87 MANUAL
values in "discipline" parameter.
EIP_225_88 MANUAL
values in "pagesize" parameter.
EIP_225_89 MANUAL
values in "showDocumentHistory" parameter.
EIP_225_90 MANUAL
values in "searchResultSize" parameter.
EIP_225_91 MANUAL
values in "pageNumber" parameter.
EIP_225_92 MANUAL
values in "clientApplication" parameter.
EIP_225_93 MANUAL
This test is to verify to get metadata from specific
Aconex project using filter condition
"documentNumber"=1353331688064575123
EIP_27-94 MANUAL
Aconex project using filter condition "documentStatus"
EIP_27-95 MANUAL
This test is to verify to filter metadata from specific
Aconex project using multiple parameter value
"clientApplication"
EIP_27-96 MANUAL
Aconex project using filter condition "documentType"
EIP_27-97 MANUAL
Aconex project using filter condition "discipline"
EIP_27-98 MANUAL
Aconex project using filter condition "dateIssued"
EIP_27-99 MANUAL
Aconex project using filter condition "discipline"
EIP_27-100 MANUAL
value in filter condition for eg.{
documentNumber=6253gijhdjshf^%
documentStatus=sdhsjahbfd
discipline= jfidjf&86 etc.}
EIP_27-101 MANUAL
Extract document details from Aconex using GET
method, based on defined parameters and validate
data response with Aconex
Defined parameters:
documentId : 1353331688066671054
EIP_247_102 MANUAL
Extract document details from Aconex using GET
method, when only documentId param is blank in
Defined Parameters and validate data response with
Aconex
Defined parameters:
documentId :
MANUAL
Document details should not return from Aconex using
GET method, when documentId and contextName
param is passed in Defined Parameters
Defined parameters:
documentId : xxxxxx
MANUAL
GET method, when X-EIP-ClientApplication and
documentId param is passed in Defined Parameters
Defined parameters:
X-EIP-ClientApplication :xxxxxxxx
documentId : xxxxx
MANUAL
GET method, when only contextName param is passed
in Defined Param and remaining is blank
Defined parameters:
MANUAL
GET method, when only documentId param is passed
in Defined Param and remaining is blank
Defined parameters:
documentId : xxxxxxxxxx
MANUAL
GET method, when only X-EIP-ClientApplication param
is passed in Defined Param and remaining is blank
Defined parameters:
MANUAL
GET method, when invalid value is passed in Defined
Param
Defined parameters:
documentId : 1353331688066671054
EIP_247_105 MANUAL

GET method, when blank value is passed in all Defined
Param
contextName :
EIP_247_106 MANUAL documentId :
Extract document metadata from Aconex using GET

method, based on defined parameters
Defined parameters:
MANUAL documentId : 1353331688066671054
Document metadata should not return from Aconex
using GET method, when documentId param is blank in
Defined Parameters
Defined parameters:
documentId :
MANUAL
using GET method, when only contextName param is
blank in Defined Parameters
Defined parameters:
contextName :
documentId : xxxxxx
MANUAL
using GET method, when only X-EIP-ClientApplication
param is blank in Defined Parameters
Defined parameters:
documentId : xxxxxx
MANUAL

using GET method, when documentId and
contextName param is passed in Defined Parameters
Defined parameters:
contextName :xxxxx
MANUAL documentId : xxxxxx

using GET method, when X-EIP-ClientApplication and
documentId param is passed in Defined Parameters
Defined parameters:
MANUAL documentId : xxxxx

using GET method, when X-EIP-ClientApplication and
contextName param is passed in Defined Parameters
Defined parameters:
MANUAL documentId : xxxxx
using GET method, when all defined param is blank
Defined parameters:
contextName :
MANUAL documentId :

using GET method, when invalid value is passed in
defined parameters
Defined parameters:
contextName :
MANUAL documentId :

using GET method, when incorrect WADL is passed
MANUAL
Verify that new document id gets created using POST
request, in case where document id does not exist in a
document Number based on defined input payload
{
sourceSystem
documentSystem
clientApplication
projectNumber
dateIssued
documentNumber
revision
title
documentType
GSCode
tagNumber
locatorCod
projectField1
projectField2
projectField3
comments
responsiblePerson
responsibleOffice
accessList
confidential
filename
data
}
EIP_247_111 MANUAL

{
documentNumber:
projectNumber:
documentType:
EIP_247_112 MANUAL }

{
documentType:
{
sourceSystem
documentSystem
clientApplication
projectNumber
dateIssued

{
documentNumber
revision
title
documentType
GSCode
tagNumber
Verify that existing document id gets updated using

POST request , in case where document id exist in
{
documentNumber:
projectNumber:
documentType:
Verify that existing document number is updated using

POST request based on defined input payload
{
documentType:
}
EIP_247_117 MANUAL
{
documentNumber:
}
EIP_247_118 MANUAL

{
documentType:
documentSubType:
}
EIP_247_119 MANUAL
{
documentType:
discipline:
}
EIP_247_120 MANUAL
{
GSCode:
tagNumber:
}
EIP_247_121 MANUAL
{
GSCode:
tagNumber:
locatorCode:
projectField1:
}
EIP_247_122 MANUAL
{
GSCode: ADGG - 24673643&^*"
tagNumber: "PSV-&%^&*(12ff,
locatorCode: null
projectField1": 223
}
EIP_247_123 MANUAL

POST request when we are passing blank input payload
{
documentType:
discipline:
}
EIP_247_124 MANUAL

{
documentType: 00000
discipline: 00000000
}
EIP_247_125 MANUAL

{
documentType: null
discipline: null
}
EIP_247_126 MANUAL

{
documentType: 2323.493849
discipline: 384.98
{
documentType: +++++
discipline: -----%%///
Request Body Method Operation
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET BATCH
GET GET Contexts
GET GET Contexts
GET GET Contexts
GET GET Contexts
GET GET Contexts
GET GET Context
GET GET Context
GET GET Context
GET GET Context
GET GET Context
GET GET Context

GET GET Context
GET GET Context
GET GET Context

GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
POST
POST
POST
POST
POST
POST
POST
POST
POST
POST
POST
POST
POST
POST
POST
POST
POST
POST
Aconex API Facade Call References/Query Expected Status Code
http://ashst95070.becpsn.com:8011/DocumentService/Aconex/projects/{projectNumber}/documents/{documentid}/docume
200
200
200
http://ashst95070.becpsn.com:8011/Docume
ntService/Aconex/projects/
{projectNumber}/documents/
{documentid}/document???
clientApplication={clientApplication}&showDo
cumentHistory={showDocumentHistory}&sear
chType=Full&documentNumber={documentN
umber}&sortField={sortField}
200
200
200
400
400
400
400
400
{documentid}/document?
clientApplication={clientApplication}&searchTy
pe=NumberLimited&searchResultSize={search
ResultSize} 200
pe=NumberLimited&searchResultSize={search
ResultSize} 400
pe={searchType}&searchResultSize={searchRe
sultSize} 400
400
400
200
200
http://ashst95070.becpsn.com:8011/DocumentService/Aconex/projects/26089/documents/{documentid}/document?clientA
200
clientApplication={clientApplication}&pageNu
mber={pageNumber}&searchType=Paged&pag
esize={pagesize} 200
clientApplication={clientApplication}&show_d
ocument_history={showDocumentHistory}&pa
geNumber={pageNumber}&searchType=Paged
&pagesize={pagesize} 200
200
200
200
pe=Count_Only 200
200
200
200
200
200
200
clientApplication={clientApplication}&docume
ntNumber={documentNumber}&sortField={so
rtField} 200
rtField} 200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
200
rtField}&sortDirection={sortDirection} 200
ntNumber={documentNumber}&discipline={di
scipline}&title={title}&author={author}&sortFi
eld={sortField}&sortDirection={sortDirection} 200
200
200
200
clientApplication={clientApplication}&content
Search={contentSearch} 200
200
clientApplication={clientApplication}&pagesize
={pagesize} 200
clientApplication={clientApplication}&showDo
cumentHistory={showDocumentHistory} 200
clientApplication={clientApplication}&searchR
esultsize={searchResultsize} 200
mber={pageNumber} 200
clientApplication={clientApplication} 200
200
200
clientApplication={clientApplication}
200
200
200
dateIssued={dateIssued} 200
200
200
http://ashst95070.becpsn.com:8011/DocumentService/Aconex/projects/{projectNumber}/documents/{documentid}?ClientAp
200
ntService/Aconex/projects/26089/documents/
1353331688066671054?ClientApp=DSC
200
http://ashst95070.becpsn.com:8011/DocumentService/Aconex/projects/{projectNumber}/documents/{documentid}?ClientAp
200
Expected Result Actual Result User Story Link
Document metadata should be

displayed from specific Aconex
project in response. EIP-253
Data response should be match
with Aconex MCDB database
An error message should be

displayed

return

return
XML/JSON Response should be

valid
Data response should be match

with Aconex MCDB database
applicationInstance is null should

be displayed

be displayed

be displayed

be displayed

displayed
return

return
XML/JSON Response should be

valid
All Document metadata should be
displayed from specfic Aconex
project in pages
EIP-218
displayed from specfic Aconex
project in pages as per matching.
EIP-219
Latest revision of document
metadata should be displayed
from a specific aconex project in
pages
All document metadata of latest
revision should be displayed.
Matching document metadata

should be displayed from a
specific aconex project in pages
Invalid_Parameter_Value message
should be displayed with status
code
code
Every document in the project
should be returned in response
code
code
Fixed number of results should be
displayed in pages
code
code
code
code
code
code
Fixed number of results should be

displayed with each matching
parameter.
code
Document results should be

displayed as per pagination filter
code
code
code
code
code
code
Document should be displayed in
pages as per matching fields .
code
Only Count of matching items

should be return in response
A count of matching document

should be displayed.

code

code
Document should be searchable

and sortable when attribute name
is "approved"

is "asBuiltRequired"

with multiple parameter value.
Document should be sortable

when attribute name is "attribute"

when attribute name is
"attribute2"
is "attribute3"

is "attribute4"

is "author"

"authorisedBy"

is "category"

when attribute name is "check1"

when attribute name is "check2"
Document should not be sortable
or searchable when attribute
name is "comments" .

name is "comments2" .

"confidential"

"contractDeliverable"

is "contractnumber"

is "contractorrev"

name is "current" .
is "date1"

is "date2"

is "discipline"

is "docno"

is "doctype"

name is "filename" .

when attribute name is "fileSize"
when attribute name is "fileType"

is "forreview"

"markupdate"

"markupLastModifiedDate"

is "milestonedate"

"numberOfMarkups"

"packagenumber"
"percentComplete"

is "plannedsubmissiondate"

when attribute name is "printSize"

"projectField1"

"projectField2"

"projectField3"

is received"
is "reference"

is "registered"

is "reviewed"

"reviewSource"
Document shoulld be searchable

and sortable on the basis of
parameters value and attribute
field.

and sortable on the basis of
parameters and attribute field.
code
code
code
code
code
code
code
code
code
code

project with matching filter
condition

condition

condition

condition
condition

condition

condition

condition
Document result should be display
as pe Aconex existing API

New document id should be
created when document id
doesn't exist in document
number.
Existing document id should be
updated
Existing document number should

be updated based on defined field
value
value

value

value

value

value
code
code
code
code
code
Attribute Length Attribute data type Searchable Sortable
documentId 50 String Yes Yes
documentNumber 50 String Yes Yes
title 50 String Yes No
documentType 50 String Yes Yes
documentSubType 50 String No Yes
discipline 50 String Yes Yes
documentStatus 50 String Yes Yes
dateIssued 0 date Yes Yes
comments 50 String No Yes
dateOnDocument 0 date Yes Yes

uploadDate 0 date No Yes
dateReceived 0 date No Yes
originatingCompany 50 String yes No
versionNumber 38 Integer No No
current 0 boolean No Yes
revision 50 String Yes Yes
revisionDate 0 date Yes Yes
authorisedBy 50 String Yes Yes
accessList 50 String No No
confidential 0 boolean Yes Yes
accessControl 50 String Yes Yes

securityClass 50 String Yes Yes
responsiblePerson 50 String Yes Yes
dateForReview 0 date Yes Yes
reviewSource 50 String Yes Yes
reviewStatus 50 String Yes Yes
dateReviewed 0 date Yes Yes
dateApproved 0 date Yes Yes
contractNumber 50 String Yes Yes
trackingId 50 String Yes Yes
tagNumber 50 String Yes Yes
GSCode 50 String No Yes

locatorCode 50 String Yes Yes
contractDeliverable 0 boolean No Yes
documentRequirements 50 String Yes Yes
milestoneDate 0 date Yes Yes
plannedSubmissionDate 0 date Yes Yes
markupDate 0 date Yes Yes
numberOfMarkups 38 Integer No No
clientDocumentNumber 50 String No No
clientDocumentRevision 50 String No No
toClientDate 0 date Yes Yes
supplierDocumentNumber 50 String No No
supplierRevision 50 String No No
subType 50 String No No
fileName 50 String No No
fileType 50 String No No
fileSize 38 Integer No No
printSize 50 String No No
scale 50 String Yes Yes

Pass Invalid Value in Field
searchType=Full
(For eg. Number, Filter Document with
Pass Valid in pass single and multiple
Field Value AlphaNumeric,Null,Character single and multiple field with valid/Invalid
,Float,Special field
value
char,arithmetic,space)
Errorcode
INVALID_PARAMETER_VALUE
message should be display
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

Errorcode
Pass Yes Pass

searchType=Number_Limited searchType=Paged pass single search_Type=Count_Only pass
pass single and multiple field and multiple field with single and multiple field with
with Valid/Invalid value Valid/Invalid value Valid/Invalid value
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass

Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass

Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass

Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass

Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass
Pass Pass Pass

showDocumentHistory sortDirection
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
1 DESC/ASC
TestCase ID Type
EIP_248_01 Manual
EIP_248_02 Manual
EIP_248_03 Manual
EIP_248_04 Manual
EIP_248_05 Manual
EIP_248_06 Manual
EIP_248_07 Manual
EIP_248_08 Manual
EIP_248_09 Manual
EIP_248_10 Manual
EIP_248_11 Manual
EIP_248_12 Manual
EIP_248_13 Manual
EIP_248_14 Manual
EIP_248_15 Manual
EIP_248_16 Manual
EIP_248_17 Manual
EIP_248_18 Manual
EIP_248_19 Manual
EIP_248_20 Manual
EIP_248_21 Manual
EIP_248_22 Manual
EIP_248_23 Manual
EIP_248_24 Manual
EIP_248_25 Manual
EIP_248_26 Manual
EIP_248_27 Manual
EIP_248_28 Manual
EIP_248_29 Manual
EIP_248_30 Manual
EIP_248_31 Manual
EIP_248_32 Manual
EIP_248_33 Manual
EIP_248_34 Manual
EIP_248_35 Manual
EIP_248_36 Manual
EIP_248_37 Manual
EIP_248_38 Manual
EIP_248_39 Manual
EIP_248_40 Manual
EIP_248_41 Manual
EIP_248_42 Manual
EIP_248_43 Manual
EIP_248_44 Manual
EIP_248_45 Manual
EIP_248_46 Manual
EIP_248_47 Manual
EIP_248_48 Manual
EIP_248_49 Manual
EIP_248_50 Manual
EIP_248_51 Manual
EIP_248_52 Manual
EIP_248_53 Manual
EIP_248_54 Manual
EIP_248_55 Manual
EIP_248_56 Manual
EIP_248_57 Manual
EIP_248_58 Manual
EIP_248_59 Manual
EIP_248_60 Manual
EIP_248_61 Manual
EIP_248_62 Manual
EIP_248_63 Manual
EIP_248_64 Manual
EIP_248_65 Manual
EIP_248_66 Manual
EIP_248_67 Manual
EIP_248_68 Manual
EIP_248_69 Manual
EIP_248_70 Manual
EIP_248_71 Manual
EIP_248_72 Manual
EIP_248_73 Manual
EIP_248_74 Manual
EIP_248_75 Manual
EIP_248_76 Manual
EIP_248_77 Manual
EIP_248_78 Manual
EIP_248_79 Manual
EIP_248_80 Manual
EIP_248_81 Manual
EIP_248_82 Manual
EIP_248_83 Manual
EIP_248_84 Manual
EIP_248_85 Manual
EIP_248_86 Manual
EIP_248_87 Manual
EIP_248_88 Manual
EIP_248_89 Manual
EIP_248_90 Manual
EIP_248_91 Manual
EIP_248_92 Manual
EIP_248_93 Manual
EIP_248_94 Manual
EIP_248_95 Manual
EIP_248_96 Manual
EIP_248_97 Manual
EIP_248_98 Manual
EIP_248_99 Manual
EIP_248_100 Manual
EIP_248_101 Manual
EIP_248_102 Manual
EIP_248_103 Manual
EIP_248_104 Manual
EIP_248_105 Manual
EIP_248_106 Manual
EIP_248_107 Manual
Description
Verify in TEAMWorks that commodity attributes have been correctly

Inserted,Updated,Upserted,Deleted when single or multiple attribute is
passed with tag using POST method under Batch Service based on defined
Request Body in XML
Commodity Name can be Bulkpipe,Spool,Valve
Refer Coloumn E under TEAMWorks Facade POST API Matrix Workbook

Verify in TEAMWorks that commodity attributes have been correctly
Inserted,Updated,Upserted,Deleted when single or multiple attribute is
passed with tag using POST method under Batch Service based on defined
Request Body in JSON.
Refer Coloumn E under TEAMWorks Facade POST API Matrix Workbook

Verify in TEAMWorks that in a case when only commodity attribute 'tag' of
duplicate value is being passed in Request body with XML using POST method
under Batch Service, a message should be displayed about the duplicate tag
entry and no such tag value should get inserted.

Verify in TEAMWorks that in a case when only commodity attribute 'tag' of
duplicate value is being passed in Request body with JSON using POST
method under Batch Service, a message should be displayed about the
duplicate tag entry and no such tag value should get inserted.

Verify in TEAMWorks that in a case when only commodity attribute tag of
new entry is passed in Request body with XML using POST method under
Batch Service, a success message should be displayed about new tag entry
and tag value should get correctly inserted.

new entry is passed in Request body with JSON using POST method under
Batch Service, a success message should be displayed about new tag entry
and tag value should get correctly inserted.

Verify in TEAMWorks that in a case when tag commodity attribute is blank in
Request body with XML using POST method under Batch Service, Failure
message should display about tag attribute which can't be left blank

Verify in TEAMWorks that in a case when tag commodity attribute is blank in
Request body with JSON using POST method under Batch Service, Failure
message should display about tag attribute which can't be left blank

Verify in TEAMWorks that commodity attributes should not be
Inserted,Updated,Upserted,Deleted when commodity attribute is passed
without tag attribute in Request Body with XML using POST method under
Batch Service
Verify in TEAMWorks that commodity attributes should not be
Inserted,Updated,Upserted,Deleted when commodity attribute is passed
without tag attribute in Request Body with JSON using POST method under
Batch Service
Verify in TEAMWorks that commodity attributes have been correctly Inserted
when single or multiple commodity attributes is passed with tag attribute in
Request Body with XML using POST method under Entity Service, "a success
message should be displayed" and attribute value should get inserted
Refer Coloumn H under TEAMWorks Facade POST API Matrix Workbook

Verify in TEAMWorks that commodity attributes have been correctly Inserted
when single or multiple commodity attributes is passed with tag attribute in
Request Body with JSON using POST method under Entity Service," a success
message should be displayed" and attribute value should get inserted

Verify in TEAMWorks that commodity attributes have been Inserted when
only commodity attribute tag is passed in Request body with XML using POST
method under Entity Service.
If tag value entry is new then, "Success message should be displayed" and tag
value should get inserted otherwise it will show duplicate entry in response.
Verify in TEAMWorks that commodity attributes have been Inserted when
only commodity attribute tag is passed in Request body with JSON using
POST method under Entity Service.
If tag value entry is new then, "Success message should be displayed" and tag
value should get inserted otherwise it will show duplicate entry in response.
blank value is passed in Request body with JSON using POST method under
Entity Service, a message should be displayed, "primary key cannot be null"
and no such tag value should get inserted
blank value is passed in Request body with XML using POST method under
Entity Service, a message should be displayed, "primary key cannot be null"
and no such tag value should get inserted
Verify in TEAMWorks that in a case when only tag attribute is blank with
single or multiple commodity attributes in Request Body with XML using
POST method under Entity Service, Failure message should display about tag
is primary key that can not be null
Verify in TEAMWorks that in a case when only tag attribute is blank with
single or multiple commodity attributes in Request Body with JSON using
POST method under Entity Service, Failure message should display about tag
is primary key that can not be null"
Verify in TEAMWorks when commodity attribute is passed without tag
attribute in Request Body with XML using POST method under Entity Service,
in that case a failure message should display tag is mandatory attribute and
no such attribute should get inserted.
Verify in TEAMWorks when commodity attribute is passed without tag
attribute in Request Body with JSON using POST method under Entity Service,
in that case a failure message should display tag is mandatory attribute and
no such attribute should get inserted
Verify in TEAMWorks that commodity attribute is inserted when special
character is passed in commodity attribute using POST method under Entity
Service in Request Body with XML
character is passed in commodity attribute using POST method under Entity
Service in Request Body with JSON
Verify in TEAMWorks when commodity attributes contains null value in
Request Body with XML using POST method under Entity Service, in that case
a Success message should display and null value should get inserted.
Here tag attribute is of string type so null is string for tag attribute
Verify in TEAMWorks when commodity attributes contains null value in
Request Body with JSON using POST method under Entity Service, in that case
a Success message should display and null value should get inserted.
Here tag attribute is of string type so null is string for tag attribute
Verify in TEAMWorks when random value is passed in commodity attribute in
Request Body with XML using POST method under Entity Service, in that case
a sucess message should be displayed value should get inserted
Refer Coloumn G under TEAMWorks Facade POST API Matrix Workbook

Verify in TEAMWorks when random value is passed in commodity attribute in
Request Body with JSON using POST method under Entity Service, in that case
a sucess message should be displayed value should get inserted

Verify in TEAMWorks that commodity attribute should is inserted when
special character is passed in commodity attribute using POST method under
Batch Service based on defined Request Body in XML

character is passed in commodity attribute using POST method under Batch
Service based on defined Request Body in JSON.

Verify in TEAMWorks when null value is passed in commodity attribute using
POST method under Batch Service based on defined Request Body with XML,
in that case a failure message should be displayed that "primary key cannot
be null"

Verify in TEAMWorks when null value is passed in commodity attribute using
POST method under Batch Service based on defined Request Body with JSON,
in that case a failure message should be displayed that "primary key cannot
be null"

Verify in TEAMWorks when date commodity attribute contains incorrect date
format using POST method under Batch Service in Request Body with XML, in
that case a message should display about incorrect date format in response.

format using POST method under Batch Service in Request Body with JSON,
in that case a message should display about incorrect date format in
response.

Verify in TEAMWorks when dateRequestDelivery commodity attribute
contains incorrect date format using POST method under Batch Service in
Request Body with JSON, in that case a message should display about
incorrect date format in response.

contains incorrect date format using POST method under Batch Service in
Request Body with XML, in that case a message should display about

Verify in TEAMWorks when dateRevision commodity attribute contains
incorrect date format using POST method under Batch Service in Request
Body with JSON, in that case a message should display about incorrect date
format in response.

Body with XML, in that case a message should display about incorrect date
format in response.

Verify in TEAMWorks when dateLastUpdated commodity attribute contains
Body with XML, in that case a message should be displayed about incorrect
date format in response.

Verify in TEAMWorks when dateLastUpdated commodity attribute contains
format in response.

format using POST method under Entity Service in Request Body with XML,
response.
format using POST method under Entity Service in Request Body with JSON,
response.
contains incorrect date format using POST method under Entity Service in
incorrect date format using POST method under Entity Service in Request
Body with XML, in that case a message should be displayed about incorrect
date format in response.
incorrect date format using POST method under Entity Service in Request
format in response.
Verify in TEAMWorks when dateLastUpdated format commodity attribute
Verify in TEAMWorks when dateLastUpdated format commodity attribute
Validate data type of all commodity attributes by replacing string data type
values with double,integer,float type so on using POST method under Batch
Service based on defined Request Body with XML, in that case a failure
message about invalid data type should display
Refer Coloumn I under TEAMWorks Facade POST API Matrix Workbook for
Attribute Data Type deatail of each commodity attribute
values with double,integer,float type so on using POST method under Batch
Service based on defined Request Body with JSON, in that case a failure
Validate data type of all commodity attributes by replacing double data type
values with String type using POST method under Batch Service based on
defined Request Body with XML, in that case a failure message about invalid
data type should display
values with String type using POST method under Batch Service based on
defined Request Body with JSON, in that case a failure message about invalid
values with double,integer,float type so on using POST method under Entity
Service based on defined Request Body with XML, in that case a failure
values with double,integer,float type so on using POST method under Entity
Service based on defined Request Body with JSON, in that case a failure
values with String type using POST method under Entity Service based on
defined Request Body with XML, in that case a failure message about invalid
values with String type using POST method under Entity Service based on
defined Request Body with JSON, in that case a failure message about invalid
Vaidate data length of each commodity attribute using POST method under
Batch service based on defined Request Body with XML
Refer Coloumn C under TEAMWorks Facade POST API Matrix Workbook for
Length deatail of each commodity attribute
Batch service based on defined Request Body with JSON
Entity service based on defined Request Body with XML
Entity service based on defined Request Body with JSON
Extract list of TEAMWorks projects that are configured in MCDB using GET
method based on defined WADL containing contexts and validate data
response with MCDB
Extract specific details of TEAMWorks project that are configured in MCDB

using GET Method based on defined WADL containing {context Name} param
and validate data response with MCDB
Verify when null value is passed in contextName param using GET method
based on defined WADL in that case an error should display
Verify when special character value is passed in contextName param using
GET method based on defined WADL in that case an error should display
Verify when String,float,int,char value is passed in contextName param using

GET method based on defined WADL in that case an error should display
Verify when space value is passed in contextName param using GET method
based on defined WADL in that case an error should display
Verify that when unsecure protocol http is passed in WADL then an error
should return using GET method upon trying to extract list of TEAMWorks
project that are configured in MCDB
should return using GET method upon trying to extract specific details of
TEAMWorks project that are configured in MCDB
Verify that when MCDB is not connected with TEAMWorks then an error
should return using GET method upon trying to extract list of TEAMWorks
project that are configured in MCDB
Verify that when MCDB is not connected with TEAMWorks then an error
should return using GET method upon trying to extract specific details of
TEAMWorks project that are configured in MCDB
A list of TEAMWorks projects should not return that are configured in MCDB
using GET method when incorrect WADL is passed in that case an error should
return
A specific details of TEAMWorks projects should not return that are

configured in MCDB using GET method when incorrect WADL is passed in that
case an error should return
Validate the XML/JSON response which is getting from TEAMWorks side it

should be correct and human readable
Extract project specific commodity records from TEAMWorks using GET
method, based on provided param values as per below
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
sort=xxxxxxxx
approvalStatus=xxxxxxx

method based on provided param without field filter
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
sort=xxxxxxxx

Extract project specific commodity records from TEAMWorks in ASC and DESC
order using GET method based on provided sort param
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
sort=xxxxxxxx
order using GET method based on provided filter attribute field
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
sort=xxxxxxxx
approvalStatus=xxxxxxxx
order using GET method based on provided filter with multiple attribute field
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
sort=xxxxxxxx
tag=xxxxxxxxx

method, based on the provided pageSize and page Index param without any
field
contextName=xxxxxx
pageSize=xxxxxxx
pageIndex=xxxxxxx

method, based on the provided only page size param
contextName=xxxxxx
pageSize=xxxxxxx

method, based on the provided only page Index param
contextName=xxxxxx
pageIndex=xxxxxxx

method, based on the provided sort param without any paging values
contextName=xxxxxx
sort=xxxxxx

method when blank value is passed in all param
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
sort=xxxxxxxx
approve status=xxxxxxxxx
Verify that project specific commodity records should not return from
TEAMWorks using GET method when special character value is passed in all
param, in that case an error should return
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
sort=xxxxxxxx

TEAMWorks using GET method when special character value is passed in
context and commodity param and remaining is blank, in that case an error
should return
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
sort=xxxxxxxx
Extract project specific commodity records should not return from

TEAMWorks using GET method, when invalid value is passed in contextName
and Commodity Name and remaining param is blank
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
sort=xxxxxxxx
approvalStatus=xxxxxxx
TEAMWorks using GET method when string,float,char is passed in pageSize
and pageIndex
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx

method when pageSize param cross default pageSize value (like 150 size)
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx

TEAMWorks using GET method when pageIndex param contains either
negative or zero value
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
pageIndex param
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
TEAMWorks using GET method when any statement is passed in pageIndex
param
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx

method when blank value is passed in pageIndex param
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
TEAMWorks using GET method when float,char,Integer value is passed in sort
filter param
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
sort=xxxxxxxx

Extract that project specific commodity records from TEAMWorks using GET
method when blank value is passed in sort param
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
sort=xxxxxxxx
TEAMWorks using GET method when special character value is passed in sort
param
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
sort=xxxxxxxx
TEAMWorks using GET method when random value is passed in sort param
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
sort=xxxxxxxx
TEAMWorks using GET method when random statement is passed in sort
param
contextName=xxxxxx
pageSize=xxxxxx
pageIndex=xxxxxx
sort=xxxxxxxx

method when blank value is passed in pageSize param
contextName=xxxxxx
pageSize=xxxxxx
pageSize param
contextName=xxxxxx
pageSize=xxxxxx
TEAMWorks using GET method when any statement is passed in pageSize
filter param
contextName=xxxxxx
pageSize=xxxxxx

method using filter attribute field only
contextName=xxxxxx
tag=xxxxxxxxx
TEAMWorks using GET method when special character value is passed in filter
field
contextName=xxxxxx
tag=xxxxxxxxx

TEAMWorks using GET method when random value is passed in filter field
contextName=xxxxxx
tag=xxxxxxxxx
TEAMWorks using GET method when any statement is passed in filter field
contextName=xxxxxx
tag=xxxxxxxxx

Verify Default value should be provided for pageSize and pageIndex
should return using GET method upon trying to extract specific commodity
records from TEAMWorks using GET method

Extract project specific commodity records should not return from

TEAMWorks using GET method when incorrect WADL is passed in Request
Request Body Method
<?xml version="1.0" encoding="UTF-8"?> POST

<t1:entityBatchAction
xmlns:t1="http://www.bechtel.com/JSON/Facade/EntityInterface">
-
<t1:entityOperation>
<t1:operationType>insert</t1:operationType>
<t1:operationContext>3456</t1:operationContext>
<t1:entityName>Commodity Name</t1:entityName>
-
<t1:entity>
<t1:tag>xxxxxxxxx</t1:tag>
<t1:plantIdentifier>xxxxxx</t1:plantIdentifier>
<t1:pipeRun>xxxxxxxx</t1:pipeRun>
</t1:entity>
</t1:entityOperation>
-
<t1:operationType>update</t1:operationType>
-
<t1:entity>
<t1:plantIdentifier>xxxxx</t1:plantIdentifier>
<t1:pipeRun>xxxxxx</t1:pipeRun>
</t1:entity>
-
<t1:operationType>upsert</t1:operationType>
-
<t1:entity>
<t1:tag>xxxxxxxxxxxx</t1:tag>
<t1:plantIdentifier>xxxxxxx</t1:plantIdentifier>
</t1:entity>
-
<t1:operationType>delete</t1:operationType>
-
<t1:entity>
<t1:tag>xxxxxxxx</t1:tag>
<t1:pipeRun>xxxxxxxxx</t1:pipeRun>
</t1:entity>
</t1:entityBatchAction>
{ POST
"entityOperation": [
{
"operationType": "insert",
"operationContext": "3456",
"entityName": "Commodity Name",
"entity": {
"tag": "xxxx",
"pipeRun": "xxxxxx",
"plantIdentifier": "xxxx"
}
},
{
"operationType": "update",
"entity": {
"tag": "xxxxx",
"pipeRun": "xxxxxxx",
"plantIdentifier": "xxxxxxx"
}
},
{
"operationType": "upsert",
"entity": {
"tag": "xxxxxx",
"plantIdentifier": "xxxxxxxxx"
}
},
{
"operationType": "delete",
"entity": {
"tag": "xxxxxxx",
"pipeRun": "xxxxxxxxxx",
}
}
]
}
-
-
<t1:entity>
<t1:tag>xxxxxx</t1:tag>
</t1:entity>
-
-
-
<t1:entity>
</t1:entity>
-
{
{
"entity": {
"tag": "xxxxxx"
}
},
{
"entity": {
"tag": "xxxxxx"
}
},
]
}
<?xml version="1.0" encoding="UTF-8"?>
-
-
<t1:entity>
</t1:entity>
-
-
-
<t1:entity>
</t1:entity>
-
{ POST
{
"entity": {
"tag": "xxxxxx"
}
},
{
"entity": {
"tag": "xxxxxx"
}
},
]
}
-
-
<t1:entity>
<t1:tag></t1:tag>
</t1:entity>
-
-
<t1:entity>
<t1:tag></t1:tag>
</t1:entity>
-
-
<t1:entity>
<t1:tag></t1:tag>
</t1:entity>
-
-
<t1:entity>
<t1:tag></t1:tag>
</t1:entity>
{ POST
{
"entity": {
"tag": ""
}
},
{
"entity": {
"tag": ""
}
},
{
"entity": {
"tag": ""
}
},
{
"entity": {
"tag": ""
}
}
]
}
-
<t1:entityName>BulkPipe</t1:entityName>
-
<t1:entity>
<t1:plantIdentifier></t1:plantIdentifier>
<t1:pipeRun></t1:pipeRun>
</t1:entity>
-
-
<t1:entity>
</t1:entity>
-
-
<t1:entity>
</t1:entity>
-
-
<t1:entity>
</t1:entity>
{ POST
{
"entity": {
}
},
{
"entity": {
}
},
{
"entity": {
}
},
{
"entity": {
"pipeRun": "xxxxxxxxxx",
}
}
]
}
<?xml version="1.0"?> POST
-<entityAction
-<entities>
-<entity>
<tag>xxxxxx</tag>
<plantIdentifier>xxxxxx</plantIdentifier>
<pipeRun>xxxxxx</pipeRun>
</entity>
-<entity>
<tag>xxxxxx</tag>
</entity>
-<entity>
<tag>xxxxxx</tag>
</entity>
-<entity>
<tag>xxxxxx</tag>
</entity>
</entities>
</entityAction>
{ POST
"entities": {
"entity": [
{
"tag": "xxxxxx",
"plantIdentifier": "xxxxxx",
"pipeRun": "xxxxxx"
},
{
"tag": "xxxxxx",
"pipeRun": "xxxxxx"
},
{
"tag": "xxxxxx",
"pipeRun": "ECU"
},
{
"tag": "xxxxxx",
"pipeRun": "xxxxxx"
}
]
}
}
-<entityAction
-<entities>
-<entity>
<tag>xxxxxx</tag>
</entity>
-<entity>
<tag>xxxxxx</tag>
</entity>
-<entity>
<tag>xxxxxx</tag>
</entity>
-<entity>
<tag>xxxxxx</tag>
</entity>
</entities>
</entityAction>
{ POST
"entities": {
"entity": [
{
"tag": "xxxxxx"
},
{
"tag": "xxxxxx"
},
{
"tag": "xxxxxx"
},
{
"tag": "xxxxxx"
}
]
}
}
{ POST
"entities": {
"entity": [
{
"tag": ""
},
{
"tag": ""
},
{
"tag": ""
},
{
"tag": ""
}
]
}
}
<entityAction
-<entities>
-<entity>
<tag></tag>
</entity>
-<entity>
<tag></tag>
</entity>
-<entity>
<tag></tag>
</entity>
-<entity>
<tag></tag>
</entity>
</entities>
</entityAction>
<entityAction
-<entities>
-<entity>
<tag></tag>
<pipeRun>xxxxx</pipeRun>
</entity>
-<entity>
<tag></tag>
</entity>
-<entity>
<tag></tag>
</entity>
-<entity>
<tag></tag>
</entity>
</entities>
</entityAction>
{ POST
"entities": {
"entity": [
{
"tag": "",
"pipeRun": "xxxxxx"
},
{
"tag": "",
"pipeRun": "xxxxxx"
},
{
"tag": "",
"pipeRun": "xxxxxx"
},
{
"tag": "",
"pipeRun": "xxxxxx"
}
]
}
}
<entityAction
-<entities>
-<entity>
</entity>
-<entity>
<plantIdentifier>xxxxx</plantIdentifier>
</entity>
-<entity>
</entity>
-<entity>
</entity>
</entities>
</entityAction>
{ POST
"entities": {
"entity": [
{
"pipeRun": "xxxxxx"
},
{
"pipeRun": "xxxxxx"
},
{
"plantIdentifier": "xxxxxxx",
"pipeRun": "xxxxxx"
},
{
"pipeRun": "xxxxxxx"
}
]
}
}
<entityAction
-<entities>
-<entity>
<tag>erfedfd345334@$@$</tag>
<plantIdentifier>fdgfggg4554</plantIdentifier>
<pipeRun>trtrfgthyt879</pipeRun>
</entity>
-<entity>
<tag>hghgh454566#%^&</tag>
<plantIdentifier>fghfhgfhg565</plantIdentifier>
<pipeRun>utyugh</pipeRun>
</entity>
-<entity>
<tag>ytutyu$%565432434</tag>
<plantIdentifier>yuyuy56765$^#%#</plantIdentifier>
{ POST
"entities": {
"entity": [
{
"tag": "erfedfd345334@$@$",
"plantIdentifier": "fdgfggg4554"",
"pipeRun": "trtrfgthyt879"
},
{
"tag": "hghgh454566#%^&",
"plantIdentifier": ""fghfhgfhg565",
"pipeRun": "utyugh"
},
{
"tag": "ytutyu$%565432434",
"plantIdentifier": ""yuyuy56765$^#%#",
"pipeRun": "uytuty454#@%%$"
},
{
"tag": "gtytytrsaer#%@$%45457657",
"plantIdentifier": ""67675675hygfh%$$",
"pipeRun": "tryftytry3432#%@%"
}
]
}
}
<entityAction
-<entities>
-<entity>
<tag>null</tag>
<plantIdentifier>null</plantIdentifier>
<pipeRun>null</pipeRun>
</entity>
-<entity>
<tag>null</tag>
</entity>
-<entity>
<tag>null</tag>
</entity>
{ POST
"entities": {
"entity": [
{
"tag": "null",
"plantIdentifier": "null",
"pipeRun": "null"
},
{
"tag": "null",
"pipeRun": "null"
},
{
"tag": "null",
"pipeRun": "null"
},
{
"tag": "null",
"pipeRun": "null"
}
]
}
}
<?xml version="1.0"?>
<entityAction
-<entities>
-<entity>
<tag>00000+++++</tag>
<plantIdentifier>00000+++++</plantIdentifier>
<pipeRun>00000+++++</pipeRun>
</entity>
-<entity>
<tag>00000+++++</tag>
</entity>
-<entity>
<tag>00000+++++</tag>
</entity>
{ POST
"entities": {
"entity": [
{
"tag": "00000+++++",
"plantIdentifier": "00000+++++",
"pipeRun": "00000+++++"
},
{
"tag": "00000+++++",
"pipeRun": "00000+++++"
},
{
"tag": "00000+++++",
"pipeRun": "00000+++++"
},
{
"tag": "00000+++++",
"pipeRun": "00000+++++"
}
]
}
}
-
-
<t1:entity>
<t1:tag>jgkfgkfngke4535"</t1:tag>
<t1:plantIdentifier>rgtrtggfh</t1:plantIdentifier>
<t1:pipeRun>gfdgHBDHB595</t1:pipeRun>
</t1:entity>
-
-
<t1:entity>
<t1:tag>jgkfgkfngke4535</t1:tag>
</t1:entity>
-
-
<t1:entity>
<t1:tag>jgkfgkfngke4535</t1:tag>
{ POST
{
"entity": {
"tag": "jgkfgkfngke4535",
"pipeRun": "rgtrtggfh",
"plantIdentifier": "gfdgHBDHB595"
}
},
{
"entity": {
}
},
{
"entity": {
}
},
{
-
-
<t1:entity>
<t1:tag>null</t1:tag>
<t1:plantIdentifier>null</t1:plantIdentifier>
<t1:pipeRun>null</t1:pipeRun>
</t1:entity>
-
-
<t1:entity>
</t1:entity>
-
-
<t1:entity>
POST
}
},
{
"entity": {
"tag": "null",
"pipeRun": "null",
"plantIdentifier": "null"
}
},
{
"entity": {
"tag": "null",
"pipeRun": "null",
}
},
{
"entity": {
"tag": "null",
"pipeRun": "null",
}
}
]
}
-
-
<t1:entity>
<t1:tag></t1:tag>
<t1:date></t1:date>
</t1:entity>
-
-
<t1:entity>
<t1:tag></t1:tag>
<t1:date></t1:date>
</t1:entity>
-
-
<t1:entity>
<t1:tag></t1:tag>
<t1:date></t1:date>
</t1:entity>
{ POST
{
"entity": {
"tag": "",
"date": "",
}
},
{
"entity": {
"tag": "",
"date": "",
}
},
{
"entity": {
"tag": "",
"date": ""
}
},
{
"entity": {
"tag": "",
"date": "",
{ POST
{
"entity": {
"tag": "",
"dateRequestDelivery": "",
}
},
{
"entity": {
"tag": "",
}
},
{
"entity": {
"tag": "",
"dateRequestDelivery": ""
}
},
{
"entity": {
"tag": "",
<t1:entityBatchAction POST
-
-
<t1:entity>
<t1:dateRequestDelivery></t1:dateRequestDelivery>
</t1:entity>
-
-
<t1:entity>
</t1:entity>
-
-
<t1:entity>
</t1:entity>
-
{ POST
{
"entity": {
"tag": "",
"dateRevision": "",
}
},
{
"entity": {
"tag": "",
"dateRevision": "",
}
},
{
"entity": {
"tag": "",
"dateRevision": ""
}
},
{
"entity": {
"tag": "",
"dateRevision": "",
<t1:entityBatchAction POST
-
-
<t1:entity>
<t1:tag></t1:tag>
<t1:dateRevision></t1:dateRevision>
</t1:entity>
-
-
<t1:entity>
<t1:tag></t1:tag>
</t1:entity>
-
-
<t1:entity>
<t1:tag></t1:tag>
</t1:entity>
-
-
-
<t1:entity>
<t1:tag></t1:tag>
<t1:dateLastUpdated></t1:dateLastUpdated>
</t1:entity>
-
-
<t1:entity>
<t1:tag></t1:tag>
</t1:entity>
-
-
<t1:entity>
<t1:tag></t1:tag>
</t1:entity>
-
"entityName": "Commodity Name", POST
"entity": {
"tag": "",
"dateLastUpdated": "",
}
},
{
"entity": {
"tag": "",
}
},
{
"entity": {
"tag": "",
"dateLastUpdated": ""
}
},
{
"entity": {
"tag": "",
}
}
]
}
<entityAction
-<entities>
-<entity>
<tag></tag>
<date></date>
</entity>
-<entity>
<tag></tag>
<date></date>
</entity>
-<entity>
<tag></tag>
<date></date>
</entity>
-<entity>
<tag>null</tag>
<date></date>
{ POST
"entities": {
"entity": [
{
"tag": "",
"date": ""
},
{
"tag": "",
"date": ""
},
{
"tag": "",
"date": ""
},
{
"tag": "",
"date": ""
}
]
}
}
-<entities> POST
-<entity>
<tag></tag>
<dateRequestDelivery></dateRequestDelivery>
</entity>
-<entity>
<tag></tag>
</entity>
-<entity>
<tag></tag>
</entity>
-<entity>
<tag></tag>
</entity>
</entities>
</entityAction>
{ POST
"entities": {
"entity": [
{
"tag": "",
},
{
"tag": "",
},
{
"tag": "",
},
{
"tag": "",
}
]
}
}
<entityAction
-<entities>
-<entity>
<tag></tag>
<dateRevision></dateRevision>
</entity>
-<entity>
<tag></tag>
</entity>
-<entity>
<tag></tag>
</entity>
-<entity>
<tag></tag>
{ POST
"entities": {
"entity": [
{
"tag": "",
"dateRevision": ""
},
{
"tag": "",
"dateRevision": ""
},
{
"tag": "",
"dateRevision": ""
},
{
"tag": "",
"dateRevision": ""
}
]
}
}
<entityAction
-<entities>
-<entity>
<tag></tag>
<dateLastUpdated></dateLastUpdated>
</entity>
-<entity>
<tag></tag>
</entity>
-<entity>
<tag></tag>
</entity>
-<entity>
<tag></tag>
{ POST
"entities": {
"entity": [
{
"tag": "",
},
{
"tag": "",
},
{
"tag": "null",
},
{
"tag": "",
}
]
}
}
-
-
<t1:entity>
<t1:tag></t1:tag>
</t1:entity>
-
-
<t1:entity>
<t1:tag></t1:tag>
</t1:entity>
-
-
<t1:entity>
<t1:tag></t1:tag>
{ POST
{
"entity": {
"tag": "",
"pipeRun": "",
"plantIdentifier": ""
}
},
{
"entity": {
"tag": "",
"pipeRun": "",
}
},
{
"entity": {
"tag": "",
"pipeRun": "",
}
},
{
-
-
<t1:entity>
<t1:tag></t1:tag>
<t1:throughLength></t1:throughLength>
</t1:entity>
-
-
<t1:entity>
<t1:tag></t1:tag>
</t1:entity>
-
-
<t1:entity>
<t1:tag></t1:tag>
{ POST
{
"entity": {
"tag": "",
"pipeRun": "",
"throughLength": ""
}
},
{
"entity": {
"tag": "",
"pipeRun": "",
"throughLength": ""
}
},
{
"entity": {
"tag": "",
"pipeRun": "",
"throughLength": ""
}
},
{
<entityAction
-<entities>
-<entity>
<tag></tag>
<plantIdentifier></plantIdentifier>
<pipeRun></pipeRun>
</entity>
-<entity>
<tag></tag>
<pipeRun></pipeRun>
</entity>
-<entity>
<tag></tag>
<pipeRun></pipeRun>
</entity>
{ POST
"entities": {
"entity": [
{
"tag": "",
"plantIdentifier": "",
"pipeRun": ""
},
{
"tag": "",
"pipeRun": ""
},
{
"tag": "",
"pipeRun": ""
},
{
"tag": "",
"pipeRun": ""
}
]
}
}
<entityAction
-<entities>
-<entity>
<tag></tag>
<throughLength></throughLength>
</entity>
-<entity>
<tag></tag>
</entity>
-<entity>
<tag></tag>
</entity>
{ POST
"entities": {
"entity": [
{
"tag": "",
"throughLength": ""
},
{
"tag": "",
"throughLength": ""
},
{
"tag": "",
"throughLength": ""
},
{
"tag": "",
"throughLength": ""
}
]
}
}
-
-
<t1:entity>
<t1:plantIdentifier>xxxxxx</t1:plantIdentifier>
</t1:entity>
-
-
<t1:entity>
<t1:plantIdentifier>xxxxx</t1:plantIdentifier>
<t1:pipeRun>xxxxxx</t1:pipeRun>
</t1:entity>
-
-
<t1:entity>
<t1:tag>xxxxxxxxxxxx</t1:tag>
{ POST
{
"entity": {
"tag": "xxxx",
}
},
{
"entity": {
"tag": "xxxxx",
}
},
{
"entity": {
"tag": "xxxxxx",
}
},
{
-<entityAction
-<entities>
-<entity>
<tag>xxxxxx</tag>
</entity>
-<entity>
<tag>xxxxxx</tag>
</entity>
-<entity>
<tag>xxxxxx</tag>
{ POST
"entities": {
"entity": [
{
"tag": "xxxxxx",
"pipeRun": "xxxxxx"
},
{
"tag": "xxxxxx",
"pipeRun": "xxxxxx"
},
{
"tag": "xxxxxx",
"pipeRun": "ECU"
},
{
"tag": "xxxxxx",
"pipeRun": "xxxxxx"
}
]
}
}
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
GET
Operation Name TEAMWorks POST API Facade Call Reference/Query
Batch Service
Batch Service
Batch Service
Batch Service
Batch Service
Batch Service
Batch Service
Batch Service
Batch Service
Batch Service
Entity Service
Entity Service
Entity Service
Entity Service
Entity Service
Entity Service
Entity Service
Entity Service
Entity Service
Entity Service
Entity Service
Entity Service
Entity Service
Entity Service
Entity Service
Entity Service
Batch Service
Batch Service
Batch Service
Batch Service
Batch Service
Batch Service
Batch Service
Batch Service
Batch Service
Batch Service
Batch Service
Batch Service
Entity Service
Entity Service
Entity Service
Entity Service
Entity Service
Entity Service
Entity Service
Entity Service
Batch Service
Batch Service
Batch Service
Batch Service
Entity Service
Entity Service
Entity Service
Entity Service
Batch service
Batch service
Entity service
Entity service
GET Contexts /
osb/TEAMWorks/CommmodityService/conte
xts
GET Context /
xts/{contextName}
GET Context /
xts/{contextName}
GET Context /
xts/{contextName}
GET Context /
xts/{contextName}
GET Context /
xts/{contextName}
GET Contexts /
xts
GET Context /
xts/{contextName}
GET Contexts /
xts
GET Context /
xts/{contextName}
GET Contexts /
xts
GET Context /
xts/{contextName}
GET Contexts /
xts
GET Context /
xts/{contextName}
GET Commodity /
xts/{contextName}/{commodityName}?
pageSize=xxxxxx&pageIndex=xxxxxx&sort=xx
xxxx&approvalStatus=xxxxxxx
GET Commodity /
xxxx
GET Commodity /
xxxx
GET Commodity /
GET Commodity /
xxxx&approvalStatus=xxxxxxx&tag=xxxxxxxx
GET Commodity /
pageSize=xxxxxx&pageIndex=xxxxxx
GET Commodity /
pageSize=xxxxxx
GET Commodity /
pageIndex=xxxxxx
GET Commodity /
sort=xxxxxx
GET Commodity /
GET Commodity /
GET Commodity /
GET Commodity /
GET Commodity /
GET Commodity /
GET Commodity /
GET Commodity /
GET Commodity /
GET Commodity /
GET Commodity /
xxxxx
GET Commodity /
xxxxx
GET Commodity /
xxxxx
GET Commodity /
xxxxx
GET Commodity /
xxxxx
GET Commodity /
pageSize=xxxxxx
GET Commodity /
pageSize=xxxxxx
GET Commodity /
pageSize=xxxxxx
GET Commodity /
approvalStatus=xxxxxx&tag=xxxxxxx
GET Commodity /
GET Commodity /
GET Commodity /
GET Commodity /
pageSize=100&pageIndex=1
GET Commodity
GET Commodity /
GET Commodity /
Expected Status Code Expected Response Actual Result
200 Commodity Attributes should

be inserted,
updated,Upserted,Deleted in
database
be inserted,
updated,Upserted,Deleted in
database
200 Duplicate entry message
should be displayed in the
Response body.
200 Duplicate entry message
should be displayed in the
Response body.
200 Commodity attribute should
be inserted in database
be inserted in database
200 Failure message should be
displayed in the Response
body.
body.
body.
body.
be Inserted
be Inserted
be Inserted
be Inserted
body.
body.
body.
body.
body.
body.
200 Commodity attribute value
should be inserted in database
with success message
be inserted in database with
success message
success message
success message
success message
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
body.
200 Exceeded length value should
give error in Response
200 Data response should be

match with TEAMWorks
MCDB database
200 Data response should be

match with TEAMWorks
MCDB database
200 applicationInstance is null

should be displayed
should be displayed

should be displayed

should be displayed
400 An error message should be
displayed

displayed

return

return

return

return
200 XML/JSON Response should

be valid
200 XML/JSON Response should
be valid
200 Commodity records should be
displayed in response from
TEAMWorks based on
provided param

TEAMWorks based on
provided param
TEAMWorks based on
provided param

TEAMWorks based on
provided param

TEAMWorks based on
provided param

TEAMWorks based on
provided param
TEAMWorks based on
provided param

TEAMWorks based on
provided param

TEAMWorks based on
provided param
200 Error message should be

displayed
400 commodity data not found

error message should be
displayed
displayed in response


200 page count should be

displayed as per passed
parameter's values
400 The request parameter (start
or limit) contains an incorrect
or unknown value message
should be displayed in
response



TEAMWorks based on
provided param

TEAMWorks based on
provided param



TEAMWorks based on
provided param
404 Error message shouild be

404 Error message shouild be


TEAMWorks based on
provided param
400 Commodity data not found

displayed
displayed

displayed
200
Commodity records should be
displayed by providing default
values
displayed
200 XML/JSON response should be

valid

displayed
User Story Link
EIP-248
EIP-262
EIP-262
EIP-273
Entity Code Commodity Attrributes DATA_LENGTH
Bulk
hydroPackageNumber 50
Spool
BulkPipe
Bulk
heatTraceRequirementsLine 50
Valve
Spool
BulkPipe
Valve
MWR 10
Spool
MWR 10
Bulk
subContractAcquisitionName 25
Spool
BulkPipe
Spool
vendorShipNo 6
Bulk
revisionIsometricDwg 3
Valve
Spool
BulkPipe
Bulk
pipeRun 100
Valve
pipeRun 100
Spool
pipeRun 100
BulkPipe
pipeRun 100
Valve
actuator 10
Bulk
dateRequestDelivery 0
Valve
BulkPipe
Bulk
moduleNumber 10
Valve
moduleNumber 10
Spool
moduleNumber 10
BulkPipe
moduleNumber 10
Valve
MRR 10
Spool
MRR 10
Bulk
pipeSchedule 15
Valve
pipeSchedule 15
Spool
pipeSchedule 15
BulkPipe
pipeSchedule 15
Bulk
materialSpec 15
Spool
materialSpec 15
BulkPipe
materialSpec 15
Bulk
trainNo 2
Valve
trainNo 2
BulkPipe
trainNo 2
Bulk
endUserDeletedBy 32
Valve
endUserDeletedBy 32
Spool
endUserDeletedBy 32
BulkPipe
endUserDeletedBy 32
Bulk
model 10
Valve
model 10
Spool
model 10
BulkPipe
model 10
Bulk
areaClassification 20
Spool
BulkPipe
Bulk
throughLength 10
Spool
throughLength 12
BulkPipe
throughLength 10
Bulk
materialSpecLineClient 10
Valve
BulkPipe
Bulk
lengthUOM 4
Valve
lengthUOM 2
Spool
lengthUOM 4
BulkPipe
lengthUOM 4
Bulk
aboveBelowRack 1
Spool
aboveBelowRack 1
BulkPipe
aboveBelowRack 1
Bulk
materialSpecDescription 35
Spool
BulkPipe
Bulk
systemStartup 20
Spool
systemStartup 15
BulkPipe
systemStartup 20
Bulk
heatTraceRequirements 50
Valve
Spool
BulkPipe
Valve
length 5
Valve
quantity 2
Bulk
date 0
Valve
date 0
Spool
date 0
BulkPipe
date 0
Bulk
codeFluid 4
Valve
codeFluid 4
Spool
codeFluid 4
BulkPipe
codeFluid 4
Spool
destination 10
Bulk
codeColor 10
Valve
codeColor 5
Spool
codeColor 10
BulkPipe
codeColor 10
Bulk
isometricDrawing 25
Valve
isometricDrawing 25
Spool
isometricDrawing 30
BulkPipe
isometricDrawing 25
Bulk
thicknessInsulation 5
Valve
Spool
BulkPipe
Spool
dateWorkPackageROS 0
Valve
dateForecastDelivery 0
Spool
dateForecastDelivery 0
Spool
dateVendorForecastShip 0
Spool
dateVendorActualShip 0
Valve
codeComGrp 2
Spool
dateVendorStartFab 0
Valve
designSubArea 4
Spool
tagPieceMarkNo 2
Spool
weightVendorPiece 6
Bulk
deleteStatus 1
Valve
deleteStatus 1
Spool
deleteStatus 1
BulkPipe
deleteStatus 1
Spool
tagVendor 30
Bulk
codeCostAccountLineTest 30
Spool
BulkPipe
Bulk
errorStatus 128
Valve
errorStatus 128
Spool
errorStatus 128
BulkPipe
errorStatus 128
Valve
codeStock 20
Bulk
vendor 20
Spool
vendor 20
BulkPipe
vendor 20
Bulk
insulationMaterial 10
Valve
Spool
BulkPipe
Spool
dateVendorReadyToShip 0
Bulk
fabricationCategory 10
Spool
BulkPipe
Spool
sheetVendorSpool 5
Valve
storageArea 10
Spool
storageArea 10
Bulk
unit 1
Valve
unit 4
Spool
unit 4
BulkPipe
unit 1
Bulk
subContract 25
Spool
subContract 25
BulkPipe
subContract 25
Valve
purchaseOrder 10
Spool
purchaseOrder 25
Bulk
tag 55
Valve
tag 25
Spool
tag 40
BulkPipe
tag 55
Bulk
tagLineID 30
Valve
tagLineID 30
Spool
tagLineID 40
BulkPipe
tagLineID 30
Spool
surplus 1
Bulk
dateRevision 0
Valve
dateRevision 0
Spool
dateRevision 0
BulkPipe
dateRevision 0
Valve
roleValve 6
Bulk
updateFlag 1
Valve
updateFlag 1
Spool
updateFlag 1
BulkPipe
updateFlag 1
Bulk
PID 40
Valve
PID 25
Spool
PID 30
BulkPipe
PID 40
Spool
dateVendorEndFab 0
Spool
dateVendorReceipt 0
Bulk
codeCostAccountLineTestMH 30
Spool
BulkPipe
Bulk
designArea 4
Valve
designArea 4
Spool
designArea 4
BulkPipe
designArea 4
Valve
sequenceNumber 5
Spool
sequenceNumber 6
Bulk
heatTraceMedia 50
Valve
heatTraceMedia 3
Spool
heatTraceMedia 20
BulkPipe
heatTraceMedia 50
Bulk
codeCostAccountMH 30
Spool
BulkPipe
Bulk
codePaint 10
Valve
codePaint 5
Spool
codePaint 10
BulkPipe
codePaint 10
Spool
MWRIssuedDate 0
Bulk
workPackage 50
Spool
workPackage 50
BulkPipe
workPackage 50
Bulk
nominalDiameter 7
Valve
nominalDiameter 7
Spool
nominalDiameter 7
BulkPipe
nominalDiameter 7
Spool
dateVendorMatlRelease 0
Valve
materialSpecLine 3
Bulk
flushPackageNumber 50
Spool
BulkPipe
Bulk
dateLastUpdated 0
Valve
dateLastUpdated 0
Spool
dateLastUpdated 0
BulkPipe
dateLastUpdated 0
Valve
endPreparation 4
Valve
dateDelivery 0
Spool
dateDelivery 0
Bulk
endUser 32
Valve
endUser 32
Spool
endUser 32
BulkPipe
endUser 32
Bulk
isometricNumber 40
Valve
isometricNumber 40
Spool
isometricNumber 40
BulkPipe
isometricNumber 40
Valve
tagVisibleSpool 30
Bulk
sequenceNumberLine 6
Valve
BulkPipe
Valve
purchaseOrderItem 25
Spool
purchaseOrderItem 10
Bulk
codeCostAccount 20
Spool
codeCostAccount 30
BulkPipe
codeCostAccount 20
Bulk
approvalStatus 20
Valve
approvalStatus 20
Spool
approvalStatus 20
BulkPipe
approvalStatus 20
Bulk
nominalDiameterUOM 2
Valve
Spool
BulkPipe
Bulk
engSys 3
Valve
engSys 4
Spool
engSys 4
BulkPipe
engSys 3
Spool
dateVendorPaint 0
Bulk
endUserUpdateBy 32
Valve
endUserUpdateBy 32
Spool
endUserUpdateBy 32
BulkPipe
endUserUpdateBy 32
Bulk
plantIdentifier 5
Valve
plantIdentifier 5
Spool
plantIdentifier 5
BulkPipe
plantIdentifier 5
Valve
uniqueObjectID3DApp 50
Spool
uniqueObjectID3DApp 50
Bulk
roleInsulation 5
Valve
roleInsulation 5
Spool
roleInsulation 5
BulkPipe
roleInsulation 5
Verify in the TEAMWorks commodity
attributes have been correctly Inserted,
DB_ATTR_Name
Updated, Upserted,Deleted performed
under Batch Service
Insert, Update, Upsert,Delete action

HYDRO_PKG shoule be performed in database
HYDRO_PKG

HYDRO_PKG shoule be performed in database
HEAT_TRACEREQLINE
HEATTRACEREQLINE
HEAT_TRACEREQLINE

HEAT_TRACEREQLINE shoule be performed in database
MWR
MWR
SUB_CONT_NAME
SUB_CONT_NAME

SUB_CONT_NAME shoule be performed in database
VSHIP_NO
ISO_CREV
ISO_CREV
ISO_CREV

ISO_CREV shoule be performed in database
PIPE_RUN
PIPE_RUN
PIPERUN

PIPE_RUN shoule be performed in database
ACTUATOR
RDELIVER
RDELIVER

RDELIVER shoule be performed in database
MODULENO
MODULENO
MODULENO

MODULENO shoule be performed in database
MRR
MRR
SCHEDULE
SCHEDULE
SCHEDULE

SCHEDULE shoule be performed in database
CLASS
CLASS

CLASS shoule be performed in database
TRAIN_NUM
TRAIN_NUM

TRAIN_NUM shoule be performed in database
DEL_BY
DEL_BY
DEL_BY
DEL_BY shoule be performed in database
MODELNO
MODELNO
MODELNO

MODELNO shoule be performed in database
DESAREA_TYPE
DESAREA_TYPE

DESAREA_TYPE shoule be performed in database
CLLENGTH
CLLENGTH

CLLENGTH shoule be performed in database
PIPESPEC
PIPESPEC

PIPESPEC shoule be performed in database
UOM_CLLENGTH
UOM_LENGTH
UOM_CLLENGTH

UOM_CLLENGTH shoule be performed in database
ABV_BEL_RACK
ABV_BEL_RACK

ABV_BEL_RACK shoule be performed in database
MAT_TYPE
MAT_TYPE

MAT_TYPE shoule be performed in database
STARTUP
STARTUP

STARTUP shoule be performed in database
HEAT_TRACEREQ
HEAT_TRACEREQ
HEAT_TRACEREQ
HEAT_TRACEREQ shoule be performed in database
LENGTH
QUANTITY
ISO_IFCDATE
ISO_IFCDATE
ISO_IFCDATE

ISO_IFCDATE shoule be performed in database
FLUIDCODE
FLUIDCODE
FLUIDCODE

FLUIDCODE shoule be performed in database
DEST
COLORCODE
COLOR_CODE
COLORCODE

COLORCODE shoule be performed in database
ISO_DWG
ISO_DWG
ISO_DWG

ISO_DWG shoule be performed in database
INS_THK
INS_THK
INS_THK

INS_THK shoule be performed in database
RDELIVER
FCDELIVER
FCDELIVER
VFCSHIP
VACT_SHIP
COMM_CODE
VSTART_FAB
DESSUBAREA
SPOOLPCNO
VPCWGHT
DELETED
DELETED
DELETED

DELETED shoule be performed in database
VEND_TAG
COA_TEST
COA_TEST
COA_TEST shoule be performed in database
NULL
NULL
NULL

NULL shoule be performed in database
STOCK_CODE
VENDOR
VENDOR

VENDOR shoule be performed in database
INSL_MATL
INSL_MATL
INSL_MATL

INSL_MATL shoule be performed in database
VREAD_SHIP
FAB_CAT
FAB_CAT

FAB_CAT shoule be performed in database
VSPOOLSHT
STOR_LOC
STOR_LOC
UNITCODE
UNITCODE
UNITCODE

UNITCODE shoule be performed in database
SUB_CONT
SUB_CONT

SUB_CONT shoule be performed in database
PO
PO
BP_ID
TAGNO
TAGNO

BP_ID shoule be performed in database
LINEID
LINEID
LINEID

LINEID shoule be performed in database
SURPLUS
ISO_CREVDATE
ISO_CREVDATE
ISO_CREVDATE

ISO_CREVDATE shoule be performed in database
TYPE
UPDATED
UPDATED
UPDATED

UPDATED shoule be performed in database
PID
PID
PID

PID shoule be performed in database
VEND_FAB
VDWGRCVE
COA_TEST_MH
COA_TEST_MH

COA_TEST_MH shoule be performed in database
DESAREA
DESAREA
DESAREA

DESAREA shoule be performed in database
SEQ_NO
LINESEQNO
HEAT_TRACE
HEAT_TRACE
HEAT_TRACE

HEAT_TRACE shoule be performed in database
COA_MH
COA_MH

COA_MH shoule be performed in database
PAINTSYSTEM
PAINT_CODE
PAINTSYSTEM

PAINTSYSTEM shoule be performed in database
MWR_DATE
WORK_PKG
WORK_PKG

WORK_PKG shoule be performed in database
DIAMETER
DIAMETER
DIAMETER
DIAMETER shoule be performed in database
VMATL_REL
LINECLASS
FLUSH_PKG
FLUSH_PKG

FLUSH_PKG shoule be performed in database
DATED
DATED
DATED

DATED shoule be performed in database
END_PREP
DELIVER
DELIVER
CUSER
CUSER
CUSER

CUSER shoule be performed in database
IW_ISO_DWG
IW_ISO_DWG
IW_ISO_DWG
IW_ISO_DWG shoule be performed in database
SPOOLPC
LINESEQNO
LINESEQNO

LINESEQNO shoule be performed in database
ITEM
ITEM
COA
COA

COA shoule be performed in database
APPROVAL_STATUS
APPROVAL_STATUS
APPROVAL_STATUS

APPROVAL_STATUS shoule be performed in database
UOM_DIAMETER
UOM_DIAM
UOM_DIAM

UOM_DIAMETER shoule be performed in database
ENG_SYS
ENG_SYS
ENG_SYS

ENG_SYS shoule be performed in database
VPAINT_COMPL
UPDATED_BY
UPDATED_BY
UPDATED_BY

UPDATED_BY shoule be performed in database
FACILITY
FACILITY
FACILITY

FACILITY shoule be performed in database
SP3D_ID
SP3D_ID
INSL_PURP
INSL_PURP
INSL_PURP

INSL_PURP shoule be performed in database
Verify in TEAMWorks when
passing single or multiple
Verify in the TEAMWorks when Passing Commodity Attributes with tag
Invalid Value in Commodity Attributes under Batch and Entity Service
(For eg.
BG_ATTR_TYPE
Number,AlphaNumeric,Null,Character,Float,S
pecial char,arithmetic,space) Under Batch and
Entity Action Service
Errorcode INVALID_PARAMETER_VALUE
string
string
Randomly coomodity attributes

action should be performed in
database string
string
string
string

database string
string
string
string
string
database string
string
string
string
string

database string
string
string
string

database string
string
date
date

database date
string
string
string

database string
string
string
string
string
string

database string
string
string

database string
string
string

database string
string
string
string

database string
string
string
string

database string
string
string

database string
double
double
database double
string
string
database string
string
string
string
database string
string
string
database string
string
string

database string
string
string
message should be display Randomly coomodity attributes
database string
string
string
string
database string
double
long
date
date
date
database date
string
string
string
database string
string
string
string
string
database string
string
string
string
database string
double
double
double
database double
date
date
date
date
date
string
date
string
string
double
string
string
string
database string
string
string
string
database string
string
string
string
database string
string
string
string
database string
string
string
string
database string
date
string
string
database string
string
string
string
string
string
string
database string
string
string
database string
string
string
string
string
string
database string
string
string
string
database string
string
date
date
date
database date
string
string
string
string
database string
string
string
string
database string
date
date
string
string
database string
string
string
string
database string
string
string
string
string
string
database string
string
string
database string
string
string
string
database string
date
string
string
database string
double
double
double
database double
date
string
string
string
database string
date
date
date
database date
string
date
date
string
string
string
database string
string
string
string
database string
string
string
string
database string
string
string
string
string
database string
string
string
string
database string
string
string
string
database string
string
string
string
database string
date
string
string
string
database string
string
string
string
database string
string
string
string
string
string
database string
TestCaseID Type Description
EIP_267_01 Manual Verify that Informatica webservice call should return
arguments based on the execution results.
1> Success
2> Failure
3> Error Messages
EIP_267_02 Manual Verify the rowcount in SQL server tables should

match the count in Aconex for given input
parameters.
1> With filters
2> without filters
3> Invalid arguments (should give proper error
messages)
EIP_267_03 Manual Verify Multi-value attributes and PickList values

should match with Aconex
EIP_267_04 Manual Verify all attributes are captured in SQL Server tables
same as in Aconex
EIP_267_05 Manual Verify data is stored in single or multiple tables in SQL

Server DB as per approved design
EIP_267_06 Manual Verify data types and precision for all attributes in
SQL Server tables match with Aconex
EIP_267_07 Manual Verify all attribute values in SQL Server tables exactly
match with that in Aconex
EIP_267_08 Manual Verify all table constraints like Primary key, Foreign
key etc. in SQL Server tables are as per Design.
EIP_267_09 Manual Verify data length of all attribute in SQL Server should
exactly match with Aconex
EIP_267_10 Manual Verify value of all attribute in SQL Server should
exactly match with Aconex
Steps to Reproduce Method API Facade Call
TBD GET
TBD GET
TBD GET
TBD GET
TBD GET
TBD GET
TBD GET
TBD GET
TBD GET
TBD GET
Reference Query Expected Status Code Expected Result
Data response should exactly
matched with Aconex
Export rows count should exactly

matched with Aconex
Multi-value attributes and PickList

value should exactly match with
Aconex
Count of all attribute in SQL Server

should be matched with Aconex
Data should be stored in single or

multiple tables as per design
Data types and precision for all

attributes should be matched with
Aconex
All attribute values in SQL Server

tables should be exactly matched
with Aconex
Table constraints like Primary key,

Foreign key etc. should be matched
with Aconex
Length of all attribute should be

matched with Aconex
Value of all attribute should be
exactly matched with Aconex
Actual Result User Story Link
EIP-267 Design Test Cases for Aconex Export

Facade API Test Cases

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Facade API Test Cases

Uploaded by

Copyright:

Available Formats

Test Case ID Type Description

Verify in Aconex that a document is correctly upserted

Verify that when MCDB is not connected with Aconex

Refer Coloumn D under Aconex Facade GET API Matrix

Extract document from Aconex by perfoming filter

Extract document should not return from Aconex by

Extract document should not return from Aconex by

Extract document should not return from Aconex by

Extract document should not return from Aconex by

Extract document should not return from Aconex by

Extract document should not return from Aconex by

Extract document from Aconex by perfoming filter

Validate datatype of all attribute by replacing

Validate datatype length of all attribute in filter

Extract document from Aconex using GET method

Extract document from Aconex using GET method

Extract documentin ASC or DESC from Aconex using GET

Extract document from Aconex using GET method

Extract document from Aconex using GET method when

Extract document should not return from Aconex using

Extract document from Aconex using GET method when

Extract document from Aconex using GET method when

Verify that document should not return from Aconex

Commodity name can be Valve,Spool,Bulkpipe

Extract project specific commodity records from

Commodity name can be Valve,Spool,Bulkpipe

Commodity name can be Valve,Spool,Bulkpipe

This test case is to verify when we are passing

This test case is to verify when we are passing

Document details should not return from Aconex using

Extract document metadata from Aconex using GET

Document metadata should not return from Aconex

Document metadata should not return from Aconex

Document metadata should not return from Aconex

Document metadata should not return from Aconex

Document metadata should not return from Aconex

Verify that new document id gets created using POST

Verify that new document id gets created using POST

Verify that new document id gets created using POST

Verify that existing document id gets updated using

Verify that existing document number is updated using

Verify that existing document number is updated using

Verify that existing document number is updated using

Verify that existing document number is updated using

Verify that existing document number is updated using

Verify that existing document number is updated using

GET GET Contexts

GET GET Contexts

GET GET Contexts

GET GET Contexts

GET GET Context

GET GET Context

GET GET Context

GET GET Context

GET GET Context

GET GET Context

GET GET Context

GET GET Context

Document metadata should be

An error message should be

An error message should be

An error message should be

XML/JSON Response should be