Integration Data Mapping Template v1
Integration Data Mapping Template v1
which talks about main field/data mapping but can be extended to meet the need of diff
How to version this document - Versioning of this document is all depend on the collabo
confluence or sharepoint keep history of all changes made. If used this in plain excel form
version in the name of file to differentiate new version.
Overview - Details such as name of the use case, short description, preparer, etc can be a
Mapping - This sheet describes field/data specific mapping. It has multiple column to defi
systems considered for the mapping. Click on each column to know more about it.
SampleData- This sheet has sample data to get idea of, how the mapping sheet will look
exercise.
ctivity for any complex integration. It has Mapping sheet
d to meet the need of different system's mapping.
all depend on the collaboration tool used. Tools like
ed this in plain excel format, it is recommended to use
Short description
Prepared/Modified By
Date
References
Sr No Type Link
1 BRD
2 Design document
3 Postman Collection
Overall System 1
Way to extract or
Data Flow set data to/from Data Field Field Description Data Type
system
System 2
Notes
Overall
Way to extract or
Data Flow set data to/from Data Field Field Description Data Type
system
RESOLUTION_DT &
From Cayenta to Cityworks GetServiceOrder RESOLUTION_TM Resolution Date and YYYYMMDD &
RESOLUTION_DT &
From Cayenta to Cityworks GetServiceOrder RESOLUTION_TM Resolution Date and YYYYMMDD &
At least a RESOLUTION_DT is
required when populating the
Resolution code. If we do not
have a date value to send to CU
TIMESTAMP(7) 2019-07-16T08:21:50 0 we cannot resolve the work.
At least a RESOLUTION_DT is
required when populating the
Resolution code. If we do not
have a date value to send to CU
TIMESTAMP(7) 2019-07-16T08:21:50 0 we cannot resolve the work.
If the RESOLUTION_CD in
Cayenta is anything other than
CNCLD/Canceled or null we
need to close the SO/WO in
Cityworks as follows:
FALSE
Step 1: If the call fails, log an
exception and send an
email/heat ticket.
Step 2: If the database lookup
fails or the expected value is
blank, log an exception and
send an email/heat ticket.
Step 3: If the call fails or no
value is returned, log an
exception and send an
email/heat ticket.
Step 4: If the call fails, log an
exception and send an
NUMBER(10,0) 2256 0 email/heat ticket.
FALSE
Notes
This field mapping will rely on the EIP user of the CloseWorkOrder
call and will be used to signify closing the loop between systems.
Yes, passed.
Yes, passed.
Yes, passed.
Yes, passed.
Yes, passed.
Yes, passed.
Yes, passed.
Yes, passed.
Yes, passed.
Yes, passed.
Yes, passed.
Yes, passed.
Yes, passed.
Yes, passed.