Component : nisp-utilityservice-v2

Overview
Endpoints
post notifications
Sequence Diagram
Unit Testing
Decisions:
Caching
Pagination
Error Handling
API Testing
Description
post send_email
Sequence Diagram
Unit Testing
Decisions:
Caching
Pagination
Error Handling
API Testing
Description
generate_send_email endpoint [ Depricated ]
Sequence Diagram
Unit Testing
Decisions:
Caching
Pagination
Error Handling
API Testing
Description
generate_send_sms endpoint [ Depricated ]
Sequence Diagram
Unit Testing
Decisions:
Caching
Pagination
Error Handling
API Testing
Description
poller-batch-email-generation-pc
Component Diagram
Sequence Diagram
Unit Testing
Decisions:
Caching
Pagination
Error Handling
API Testing
Description
 poller-batch-email-generation-bcFlow
Sequence Diagram
Unit Testing
Decisions:
Caching
Pagination
Error Handling
API Testing
Description
poller-batch-sms-generation-bc
Sequence Diagram
Unit Testing
Decisions:
Caching
Pagination
Error Handling
API Testing
Description
poller-batch-sms-generation-pc
Sequence Diagram
Unit Testing
Decisions:
Caching
Pagination
Error Handling
API Testing
Description
Deploy: How do we build this?
Description
Cloudhub: How does this live in our iPaaS
Operate: How do we support this?
Description
Change Log
Description

Overview
This document provides detailed information of the nisp-utilityservices-v2 design.

High-Level Context <Link to all HLDs where the component is used >

End-End Business Process Flow <Link to all Business Process Map>

Source code repository Mule 3:

https://bitbucket.org/icarensw/nisp-utilityservices-v1/src/master/

Mule 4

https://bitbucket.org/icarensw/nisp-utilityservices-v2/src/master/

API Specification Exchange URL: nisp-utilityservices (mulesoft.com)

API Policies:

Interface Repository URL: Not created yet

Design Center URL: Design Center (mulesoft.com)

Endpoint URL(s) Mule 3:

PROD DLB: https://api.icare.nsw.gov.au/nisp-utilityservices/*

NON-PROD DLB: https://{env}.api.nonprod.icare.nsw.gov.au/v1/nisp-utilityservices/*

Mule Worker endpoint: http://mule-worker-internal-icare-{env}-nisp-utilityservices-v1.au.cloudhub.io:8091/workersinsurance/1.0/*

Mule 4:

PROD DLB: https://api.icare.nsw.gov.au/nisp-utilityservices/*

NON-PROD DLB: https://{env}.api.nonprod.icare.nsw.gov.au/v1/nisp-utilityservices/*

Mule Worker endpoint: http://mule-worker-internal-icare-{env}-nisp-utilityservices-v2.au.cloudhub.io:8091/workersinsurance/1.0/*

Base Path Mule 3:

Base Path Of Component: /workerinsurance/1.0/*

Base Path of DLB: /v1/nisp-utilityservices/

Mule 4:

Base Path Of Component: /workerinsurance/1.0/*

Base Path of DLB: /v1/nisp-utilityservices/

Endpoints

post notifications
REST URI | SOAP Endpoint /notifications

REST METHOD/ POST

SOAP OPERATION

Consumer nisp-policyservices-v1

Endpoint:

mad1-sf-quotes-pollerSub_Flow

adapter-portal-wi-policy-v1

Endpoint:

/me/quotes//save

nisp-ecmservices-async-v1

nisp-externaluser-v1

Endpoint:

/users

/users/password

Provider exstream-ot-proxy-v1

adapter-exstream-v1

Endpoint: /v1/exstreamproxy/cc-channels/SOAPGateway
Operations: getDocuments

AWS SES

Provider Security Policies Security:

exstream-ot-proxy-v1: None (internal)

adapter-exstream-v1 : None (internal)

Key Identifiers Headers:

TransactionId
subscriber-identifier

Payload

policyNumber

Sensitive Attributes

Policies ExStream-Custom-Routing-Policy
client Id and context Validation
Configuration same as nisp-utilityservices-v1

Property Name Description Property Type Value

ot.endpoint OpenText Exstream Proxy HTTP Configuration dynamic Refer to global config

hpex.endpoint hpex endpoint dynamic Refer to global config

sms.accesskey.id SMS dynamic Refer to global config

sms.accesskey.secret SMS static XXXXXXXXXXXXXXXXXXXXXXXXXX

SES dynamic Refer to global config

ses.accesskey.id

ses.accesskey.secret SES static XXXXXXXXXXXXXXXXXXXXXXXXXXXXX

aws.ses.max.error.retry aws static 2

aws.ses.connection.timeout aws static 10000

aws.ses.connection.max.idle aws static 60000

Sample request Scenario 1 (subscriber-identifier=PTL_OAUTH_USER)

{
"GenericNotificationRequest": {
"DeliveryChannel": "email",
"ArchivalRequired": "no",
"EmailNotification": {
"EmailAddress": "john.doe@icare.nsw.gov.au",
"ContactName": "john doe",
"PolicyNumber": "140979201",
"SubjectLine": "Welcome to the icare workers insurance online portal",
"Url": "https://policyportal-sit3.icare.nsw.gov.au/set-password-and-security-question?token=LU3CpqlOqx8iehkSE3gR&uid=00ukbtvozszzzc4bP0h7",
"TemplateID": "PORTAL_NEW_POLICY_INVITATION_155a"
}
}
}

Scenario 2 Negative Test (subscriber-identifier=<>)

Failure:

{
"GenericNotificationRequest": {
"DeliveryChannel": "email",
"ArchivalRequired": "no",
"EmailNotification": {
"EmailAddress": "john.doe@icare.nsw.gov.au",
"ContactName": "john doe",
"SubjectLine": "Welcome to the icare workers insurance online portal",
"TemplateID": "PORTAL_NEW_POLICY_INVITATION_155a"
}
}
}

Sample Response Scenario 1

Success:

"GenericNotificationResponse": {
"GenericNotificationDetails": {
"NotificationStatus" : "Success"
}

Scenario 2

Failure:

{
"GenericNotificationResponse": {
"error": {
"application_code": "nisp-icare-notification",
"EIL": {
"system_name" : "ESB",
"error-code": "001",
"error-type": "Business Exception",
"error-description": "Object has missing or invalid header information subscriber-identifier"
}
}
}
}
Data Mapping Data Mapping -nisp-utilityservices-notfications-endpoint v2.0 - Portal.xlsx

Component Diagram

Sequence Diagram
Unit Testing

Test Case Title Expected Result Test Case Source File Test Case Source

<Test Case Scenario Title> <Insert Expected Result Description> <Munit Test Suite File> <Munit Test Case Name> | <Java Test Method> | <Groovy Test Method>

| <Java Test File> | <Groovy Test File>

Decisions:
The list below outlines the technical considerations and principles considered in the design of this component

Caching
<Describe the need for cache and cache strategy used>

Pagination
<Describe the need for pagination and how it is implemented>

Error Handling
<Custom Exception Handling Implementation>

API Testing

Description
Below Test Suite is used to test COMPONENT REPO NAME : ENDPOINT LOGICAL NAME

API Tests to run Non Integrated Environment : <Component Test Suite Repo Link>

Integrated Environment : <Component Test Suite Repo Link>

API Security Test ( Integrated environment) : <Component Test Suite Repo Link>

API Security Test ( Prod environment) : <Component Test Suite Repo Link>

Test Result <Date> : <Test Suite Name> <Insert Result Screenshot Link>
post send_email

REST URI | SOAP /send_email

Endpoint

REST METHOD/ POST

SOAP OPERATION

Consumer NA

Provider AWS SES

Provider NA
Security Policies

Key Identifiers Headers:

TransactionId
subscriber-identifier

Sensitive NA
Attributes

Policies ExStream-Custom-Routing-Policy
client Id and context Validation

Configuration use the same config as nisp-utilityservices-v1

Property Name Description Property Type Value

ot.endpoint OpenText Exstream Proxy HTTP Configuration dynamic Refer to global configuration

hpex.endpoint hpex endpoint dynamic Refer to global configuration

sms.accesskey.id SMS dynamic Refer to global configuration

sms.accesskey.secret SMS static XXXXXXXXXXXXXXXXXXXXXXXXXX

SES dynamic Refer to global configuration

ses.accesskey.id

ses.accesskey.secret SES static XXXXXXXXXXXXXXXXXXXXXXXXXXXXX

aws.ses.max.error.retry aws static 2

aws.ses.connection.timeout aws static 10000

aws.ses.connection.max.idle aws static 60000

 Sample request {
"toMail": "john.doe@icare.nsw.gov.au",
"fromMail": "No-Reply.Test@icare.nsw.gov.au",
"subject": "Testing EmailAPI ",
"body": "SGkgV2VsY29tZSB0byBpQ2FyZSE=",
"attachments": [
{
"name": "attachment1.pdf",
"mimeType": "application/pdf",
"content": ""
},
{
"name": "attachment2.pdf",
"mimeType": "application/pdf",
"content": ""
}
]
}

Sample Response Positive response:

{
}

Negative response:

{ "error": { "application_code": "nisp-icare-notification", "transaction_Id": "e2e601b0-b0e4-11ed-9e27-02830a416d42", "EIL": { "system_name": "ESB", "error-code": "004", "error-description": "Provider Service
currently unavailable. Please try sometime later.", "error-type": "Application Error" } } }

Data Mapping Data Mapping -nisp-utilityservices-send-email-endpoint v1.0 - Portal.xlsx

Component Diagram

This endpoint is not called from any internal or external apis.

Sequence Diagram
Unit Testing

Test Case Title Expected Result Test Case Source File Test Case Source

<Test Case Scenario Title> <Insert Expected Result Description> <Munit Test Suite File> <Munit Test Case Name> | <Java Test Method> | <Groovy Test Method>

| <Java Test File> | <Groovy Test File>

Decisions:
The list below outlines the technical considerations and principles considered in the design of this component
Caching
<Describe the need for cache and cache strategy used>

Pagination
<Describe the need for pagination and how it is implemented>

Error Handling
<Custom Exception Handling Implementation>

API Testing

Description
Below Test Suite is used to test COMPONENT REPO NAME : ENDPOINT LOGICAL NAME

API Tests to run Non Integrated Environment : <Component Test Suite Repo Link>

Integrated Environment : <Component Test Suite Repo Link>

API Security Test ( Integrated environment) : <Component Test Suite Repo Link>

API Security Test ( Prod environment) : <Component Test Suite Repo Link>

Test Result <Date> : <Test Suite Name> <Insert Result Screenshot Link>

generate_send_email endpoint [ Depricated ]

REST URI | /generate_send_email

SOAP Endpoint

REST METHOD/ POST

SOAP
OPERATION

Consumer NA

Provider adapter-exstream-v1

Endpoint: /v1/exstreamproxy/cc-channels/SOAPGateway
Operations: getDocuments

AWS SES
Provider exstream-ot-proxy-v1: None (internal)
Security Policies
adapter-exstream-v1 : None (internal)

Key Identifiers Headers:

TransactionId
subscriber-identifier

Payload

policyNumber

Sensitive
Attributes

Policies Security:

exstream-ot-proxy-v1: None (internal)

adapter-exstream-v1 : None (internal)

Configuration
Property Name Description Property Type Value

ot.endpoint OpenText Exstream Proxy HTTP Configuration dynamic Refer to global config

hpex.endpoint hpex endpoint dynamic Refer to global config

sms.accesskey.id SMS dynamic Refer to global config

sms.accesskey.secret SMS static XXXXXXXXXXXXXXXXXXXXXXXXXX

SES dynamic Refer to global config

ses.accesskey.id

ses.accesskey.secret SES static XXXXXXXXXXXXXXXXXXXXXXXXXXXXX

aws.ses.max.error.retry aws static 2

aws.ses.connection.timeout aws static 10000

aws.ses.connection.max.idle aws static 60000

Sample request {

"contactName":"FirstName LastName",

"policyNumber": "1234567",

"url": "http://mydomain.com/activationurl",

"templateId": "template1234",

"toAddress":"sundeep.enugula@abc.com",

"fromAddress":"No-Reply.Test@icare.nsw.gov.au",

"subjectLine":"Test"

}
Sample Success scenario ideally:
Response

{
}

Actual output via postman :

"PD94bWwgdmVyc2lvbj0nMS4wJyBlbmNvZGluZz0nVVRGLTgnPz4KPEdlbmVyaWNOb3RpZmljYXRpb25SZXNwb25zZT4KICA8ZXJyb3I+CiAgICA8YXBwbGljYXRpb25fY29kZT5uaXNwLWljYXJlLW5vdGlmaWNhdGlvbjwvYXBwbGljYXRpb25fY

Data Mapping Mapping is not required as discussed

Reason: Fields in subflow are not accessible since those fields are not mapped in mainflow

Component Diagram:

Sequence Diagram
Unit Testing

Test Case Title Expected Result Test Case Source File Test Case Source

<Test Case Scenario Title> <Insert Expected Result Description> <Munit Test Suite File> <Munit Test Case Name> | <Java Test Method> | <Groovy Test Method>

| <Java Test File> | <Groovy Test File>

Decisions:
The list below outlines the technical considerations and principles considered in the design of this component

Caching
<Describe the need for cache and cache strategy used>

Pagination
<Describe the need for pagination and how it is implemented>

Error Handling
<Custom Exception Handling Implementation>

API Testing

Description
Below Test Suite is used to test COMPONENT REPO NAME : ENDPOINT LOGICAL NAME

API Tests to run Non Integrated Environment : <Component Test Suite Repo Link>

Integrated Environment : <Component Test Suite Repo Link>

API Security Test ( Integrated environment) : <Component Test Suite Repo Link>

API Security Test ( Prod environment) : <Component Test Suite Repo Link>

Test Result <Date> : <Test Suite Name> <Insert Result Screenshot Link>

generate_send_sms endpoint [ Depricated ]

REST URI | SOAP /generate_send_sms

Endpoint

REST METHOD/ POST

SOAP OPERATION

Consumer NA

Provider AWS SNS

Provider NA
Security Policies
Key Identifiers Headers:

subscriber-identifier

Payload:

contactNumber

Sensitive Attributes

Attribute Name Request Payload Path Description

contactNumber payload.contactNumber contact Number of insuree

Policies ExStream-Custom-Routing-Policy
client Id and context Validation

Configuration same as nisp-utilityservices-v1

Property Name Description Property Type Value

sms.accesskey.id SMS dynamic Refer to global config

sms.accesskey.secret SMS dynamic Refer to global config

sms.type SMS static Transactional

sms.senderId SMS static ICARE

Sample request {
"smsContactNumbers": {
"contactNumber": [
"+919618350361",
"+919502147654",
"+919441243265",
"+919652523451"
]
},
"message":"Hi Welcome to iCare!"
}

Sample Response Positive scenario: Output in CSV format

contactNumber,messageId,transactionId

919618350361,123123,123131

Negative scenario:

{ "error": { "application_code": "nisp-icare-notification", "transaction_Id": "bc51eda0-b0d2-11ed-9e27-02830a416d42", "EIL": { "system_name": "ESB", "error-code": "004", "error-description": "Provider Service
currently unavailable. Please try sometime later.", "error-type": "Application Error" } } }

Data Mapping Data Mapping -nisp-utilityservices-send-sms-endpoint v1.0 - Portal.xlsx

Component Diagram
Sequence Diagram

Unit Testing
 Test Case Title Expected Result Test Case Source File Test Case Source

<Test Case Scenario Title> <Insert Expected Result Description> <Munit Test Suite File> <Munit Test Case Name> | <Java Test Method> | <Groovy Test Method>

| <Java Test File> | <Groovy Test File>

Decisions:
The list below outlines the technical considerations and principles considered in the design of this component

Caching
<Describe the need for cache and cache strategy used>

Pagination
<Describe the need for pagination and how it is implemented>

Error Handling
<Custom Exception Handling Implementation>

API Testing

Description
Below Test Suite is used to test COMPONENT REPO NAME : ENDPOINT LOGICAL NAME

API Tests to run Non Integrated Environment : <Component Test Suite Repo Link>

Integrated Environment : <Component Test Suite Repo Link>

API Security Test ( Integrated environment) : <Component Test Suite Repo Link>

API Security Test ( Prod environment) : <Component Test Suite Repo Link>

Test Result <Date> : <Test Suite Name> <Insert Result Screenshot Link>

poller-batch-email-generation-pc
Below endpoint describes a poller running every 2 minutes to fetch file details from sftp location to generate emails.

Poller poller-batch-email-generation-pc
Frequency 2 minutes

Source exstream-ot-proxy-v1

adapter-onbase-v1

Provider AWS SES

Provider Security Policies NA

Configuration

mft.batch.email.pc.inputPath email static /exstream/inbound/email/policyCenter

mft.email.failure.path email static /Exstream/failure/PolicyCenter

mft.fileloc email static /exstream/inbound/email/policyCenter

xstream.pc.mftinboundlocation email static /Exstream/Outbound/PolicyCenter

onbase.pc.mftinboundlocation email static /Onbase/Outbound/PolicyCenter

aws.ses.max.error.retry email static 2

aws.ses.connection.timeout email static 10000

aws.ses.connection.max.idle email static 60000

aws.ses.socket.timeout email static 180000

mft.username email static mulesoft_t

mft.password email dynamic Refer to global config

mft.host email static localhost

mft.port email static 2255

Sample request IC_METADATAEMAILREPORT_BATCH_4022023_164432_9749.meta

Sample Response Since this is poller there's no sample payload response instead email will be sent to users

Data Mapping Data Mapping -nisp-utilityservices-poll-batch-email-endpoint v1.0 (1).xlsx

Component Diagram
Sequence Diagram
Unit Testing
 Test Case Title Expected Result Test Case Source File Test Case Source

<Test Case Scenario Title> <Insert Expected Result Description> <Munit Test Suite File> <Munit Test Case Name> | <Java Test Method> | <Groovy Test Method>

| <Java Test File> | <Groovy Test File>

Decisions:
The list below outlines the technical considerations and principles considered in the design of this component

Caching
<Describe the need for cache and cache strategy used>

Pagination
<Describe the need for pagination and how it is implemented>

Error Handling
<Custom Exception Handling Implementation>

API Testing

Description
Below Test Suite is used to test COMPONENT REPO NAME : ENDPOINT LOGICAL NAME

API Tests to run Non Integrated Environment : <Component Test Suite Repo Link>

Integrated Environment : <Component Test Suite Repo Link>

API Security Test ( Integrated environment) : <Component Test Suite Repo Link>

API Security Test ( Prod environment) : <Component Test Suite Repo Link>

Test Result <Date> : <Test Suite Name> <Insert Result Screenshot Link>

poller-batch-email-generation-bcFlow

Poller poller-batch-email-generation-bcFlow

Frequency 2 minutes
Source exstream-ot-proxy-v1

adapter-onbase-v1

Provider AWS SES

Provider NA

Security Policies

Configuration

mft.batch.email.pc.inputPath email static /exstream/inbound/email/billingCenter

mft.email.failure.path email static /Exstream/failure/billingCenter

mft.fileloc email static /exstream/inbound/email/BillingCenter

xstream.pc.mftinboundlocation email static /Exstream/Outbound/BillingCenter

onbase.pc.mftinboundlocation email static /Onbase/Outbound/BillingCenter

aws.ses.max.error.retry email static 2

aws.ses.connection.timeout email static 10000

aws.ses.connection.max.idle email static 60000

aws.ses.socket.timeout email static 180000

mft.username email static mulesoft_t

mft.password email static XXXXXXXXX

mft.host email static localhost

mft.port email static 2255

Policies NA

Sample request No active file received in production

Sample Email notification will be sent to corresponding users

Response

Data Mapping Data Mapping -nisp-utilityservices-poll-batch-email-endpoint v1.0.xlsx

Component Diagram
Sequence Diagram
Unit Testing

Test Case Title Expected Result Test Case Source File Test Case Source

<Test Case Scenario Title> <Insert Expected Result Description> <Munit Test Suite File> <Munit Test Case Name> | <Java Test Method> | <Groovy Test Method>

| <Java Test File> | <Groovy Test File>

Decisions:
The list below outlines the technical considerations and principles considered in the design of this component

Caching
<Describe the need for cache and cache strategy used>

Pagination
<Describe the need for pagination and how it is implemented>

Error Handling
<Custom Exception Handling Implementation>

API Testing

Description
Below Test Suite is used to test COMPONENT REPO NAME : ENDPOINT LOGICAL NAME

API Tests to run Non Integrated Environment : <Component Test Suite Repo Link>

Integrated Environment : <Component Test Suite Repo Link>

API Security Test ( Integrated environment) : <Component Test Suite Repo Link>

API Security Test ( Prod environment) : <Component Test Suite Repo Link>

Test Result <Date> : <Test Suite Name> <Insert Result Screenshot Link>
poller-batch-sms-generation-bc

Poller poller-batch-sms-generation-bc

Frequency 2 minutes

Source exstream-ot-proxy-v1

Provider AWS SNS

Provider Security Policies NA

Configuration

mft.batch.sms.bc.inputPath sms static /exstream/inbound/sms/BillingCenter

mft.email.failure.path sms static /Exstream/failure/BillingCenter

mft.fileloc sms static /exstream/inbound/email/BillingCenter

xstream.bc.mftinboundlocation sms static /Exstream/Outbound/BillingCenter

onbase.bc.mftinboundlocation sms static /Onbase/Outbound/BillingCenter

aws.ses.max.error.retry sms static 2

aws.ses.connection.timeout sms static 10000

aws.ses.connection.max.idle sms static 60000

aws.ses.socket.timeout sms static 180000

amazon.sns.sys sms static Amazon SNS

mft.username sms static mulesoft_t

mft.password sms dynamic Refer to global config

mft.host sms static localhost

mft.port sms static 2255

Sample Request Sample request not recieved yet

Sample Response Sample response should be CSV as per code

contactNumber,messageId,transactionId

919618350361,12342324,1234241344

Data Mapping NA

Component Diagram
Process Flow Diagram

Sequence Diagram
Unit Testing

Test Case Title Expected Result Test Case Source File Test Case Source

<Test Case Scenario Title> <Insert Expected Result Description> <Munit Test Suite File> <Munit Test Case Name> | <Java Test Method> | <Groovy Test Method>

| <Java Test File> | <Groovy Test File>

Decisions:
The list below outlines the technical considerations and principles considered in the design of this component

Caching
<Describe the need for cache and cache strategy used>

Pagination
<Describe the need for pagination and how it is implemented>

Error Handling
<Custom Exception Handling Implementation>
API Testing

Description
Below Test Suite is used to test COMPONENT REPO NAME : ENDPOINT LOGICAL NAME

API Tests to run Non Integrated Environment : <Component Test Suite Repo Link>

Integrated Environment : <Component Test Suite Repo Link>

API Security Test ( Integrated environment) : <Component Test Suite Repo Link>

API Security Test ( Prod environment) : <Component Test Suite Repo Link>

Test Result <Date> : <Test Suite Name> <Insert Result Screenshot Link>

poller-batch-sms-generation-pc

Poller poller-batch-sms-generation

Frequency 2 minutes

Source exstream-ot-proxy-v1 ( no security)

Provider

AWS SNS

Provider Security Policies NA

Configuration

mft.batch.sms.bc.inputPath sms static /exstream/inbound/sms/PolicyCenter

mft.email.failure.path sms static /Exstream/failure/PolicyCenter

mft.fileloc sms static /exstream/inbound/email/PolicyCenter

xstream.bc.mftinboundlocation sms static /Exstream/Outbound/PolicyCenter

onbase.bc.mftinboundlocation sms static /Onbase/Outbound/PolicyCenter

aws.ses.max.error.retry sms static 2

aws.ses.connection.timeout sms static 10000

aws.ses.connection.max.idle sms static 60000

aws.ses.socket.timeout sms static 180000

amazon.sns.sys sms static Amazon SNS

mft.username sms static mulesoft_t

mft.password sms dyamic Refer to global config

mft.host sms static localhost

mft.port sms static 2255

Sample request
Sample request not recieved yet

Sample Response Sample response should be CSV as per code

contactNumber,messageId,transactionId

919618350361,12342324,1234241344

Data Mapping NA

Component Flow Diagram:

Process Flow Diagram

Sequence Diagram
Unit Testing

Test Case Title Expected Result Test Case Source File Test Case Source

<Test Case Scenario Title> <Insert Expected Result Description> <Munit Test Suite File> <Munit Test Case Name> | <Java Test Method> | <Groovy Test Method>

| <Java Test File> | <Groovy Test File>

Decisions:
The list below outlines the technical considerations and principles considered in the design of this component

Caching
<Describe the need for cache and cache strategy used>

Pagination
<Describe the need for pagination and how it is implemented>

Error Handling
<Custom Exception Handling Implementation>
API Testing

Description
Below Test Suite is used to test COMPONENT REPO NAME : ENDPOINT LOGICAL NAME

API Tests to run Non Integrated Environment : <Component Test Suite Repo Link>

Integrated Environment : <Component Test Suite Repo Link>

API Security Test ( Integrated environment) : <Component Test Suite Repo Link>

API Security Test ( Prod environment) : <Component Test Suite Repo Link>

Test Result <Date> : <Test Suite Name> <Insert Result Screenshot Link>

Deploy: How do we build this?

Description
<Description of the Build Job>

Job <Build Job URL>

Cloudhub: How does this live in our iPaaS

Business Group <TBF>

Access Level <Partner | Public | Private | Internal VPC >

Security Policy Authentication Authorization Endpoint Description

<Include the Endpoint Documentation>

Operate: How do we support this?

Description
Description of component monitoring and alerts

Health Check <Component Health Check Endpoint >

Splunk Dashboard <Splunk Dashboard Link to monitor metrics for the Component>

Splunk Alerts <Splunk Alerts for the Component Link>

Change Log
Description
Summary of the change history to this component

Version Change Description Release Type Release Date User Stories | EREM

Incident Number

1.0 Initial Release Mule 4 Upgrade Project 15-01-2023

1.X <Description of Changes> <Project Name>