CONNECTED SERVICE RESPONSES · Workflow idea
When a connected service requests a response, organize the required information and return it as an XML document. Keep the response limited to the agreed fields and provide a clear outcome when expected information is missing.
01 / The starting point
A request from a connected service that needs a prepared response
“Prepare the agreed information as XML and return it to the requesting service in a clearly identified response.”
02 / The work
Takes a service request, prepares the relevant information in XML form, and returns that document as the response.
Start when a connected service asks for the information covered by the agreed response.
Use the approved information for the request and leave out unrelated or unauthorized details.
Arrange the information in the agreed XML structure so the receiving service can read it.
Use the agreed response when required details are unavailable or the request cannot be understood.
Provide the XML response to the service that made the request.
03 / The result
A structured XML document containing the prepared information, ready for the connected service to interpret.
Documents · Example outcome
A structured XML document containing the prepared information, ready for the connected service to interpret.
Confirm which information may be shared and what the receiving service expects. Use an approved response for missing or unexpected details rather than returning misleading information.
04 / Make it yours
A few choices shape the work around your team.
Document what information may be returned and which details are required for each supported request.
Agree with the receiving service on the expected fields and their organization.
Choose a clear outcome for missing details, unfamiliar requests, or information that should not be shared.
Review successful, incomplete, and unexpected examples with the receiving team before relying on live responses.