# Setting up a Prima Solutions connection
## Introduction
Typically, connectors are defined with endpoints which determine exactly what data is being requested (pull customer records, post product details, etc.). However, the Prima Solutions connector works in a different way, with two generic endpoints:
* comwsomhandler
* wsomhandler
The actual data required for a request must be passed into the Prima Solutions connection shape, as part of your process flow. You do this via a [manual payload](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/manual-payload-shape.md) shape.
{% hint style="info" %}
Whatever is defined for the manual payload is passed into the body of the subsequent Prima Solutions connection request.
{% endhint %}
Finally - once a successful connection is made - the response must be converted from XML to JSON, ready for onward processing.
With this in mind, a process flow that needs to pull data from Prima Solutions will usually require three shapes in the following sequence:
1. **Manual payload** shape, which includes the required [request data](#request-data) in an XML string
2. **Connection** shape, configured with a Prima Solutions endpoint
3. **Script** shape, configured with an [XML to JSON conversion script](#converting-response-xml-to-json)
For example:
## Request data
Request data to be passed into a Prima Solutions connection shape must be based on the *Prima Web Services XML Schema Definition*. Some examples are shown below.
Example: NewOrder
The example below shows a `NewOrder` request (XML string):
{% code title="With HTML entities" overflow="wrap" lineNumbers="true" %}
```xml
```
{% endcode %}
{% code title="Without HTML entities" overflow="wrap" lineNumbers="true" %}
```html
```
{% endcode %}
Example: ProductAvailableToSell
The example below shows a `ProductAvailableToSell` request (XML string):
{% code title="With HTML entities" overflow="wrap" lineNumbers="true" %}
```xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<Request RequestType="ProductAvailableToSell">
<Data ProductFrom="" ProductTo="" WareHouse="" IncludeDisallowed="" IncludeProhibited=""/>
</Request>
```
{% endcode %}
{% code title="Without HTML entities" overflow="wrap" lineNumbers="true" %}
```html
```
{% endcode %}
The response would be in the form below:
{% code title="With HTML entities" overflow="wrap" lineNumbers="true" %}
```xml
```
{% endcode %}
Notice that the response is returned as an XML string. For onward processing you must [convert this to a JSON payload, using a custom script](#converting-response-xml-to-json).
## Converting response XML to JSON
Before the response from a Prima Solutions request can be be processed, it must be converted to a JSON payload. To do this, you should create an XML to JSON conversion script and add this to a [script shape](/product-documentation/process-flows/building-process-flows/process-flow-shapes/advanced-shapes/script-shape.md) in your process flow.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://doc.wearepatchworks.com/product-documentation/connectors-and-instances/patchworks-connectors/prima-solutions-prebuilt-connector/setting-up-a-prima-solutions-connection.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.