Extra information
System documentation:Connector package documentation
Setting up SOAP Client FashionMaster Retail
Steps
- In Alumio Dashboard, go to Clients > SOAP Clients. Create a new SOAP Client and select FashionMaster SOAP Client as the prototype of the SOAP Client.
- Fill in the WSDL URI, Soap Version (Default is SOAP 1.1), and Storage for cache (Optional).
- Save and Continue. Note: The authentications needs the Alumio IP to be whitelisted, to get the IP go to Settings > Info > Environment
Subscribing to Entities from FashionMaster Retail
Steps
- Go to Connections -> Incoming and create a new incoming configuration and select FashionMaster Retail Subscriber as the subscriber.
- Select the soap Method you want to subscribe to from FashionMaster Retail.
- Add any request data needed to subscribe to the entity (optional).
- You can optionally add a transformer to transform the request parameters into something you need.
- Select the FashionMaster Retail SOAP Client to use.
General Concept
We follow FashionMaster Retail documentation on building this connector so you can easily use the connector based on FashionMaster Retail API Reference. Entity It’s the entity you want to subscribe to from FashionMaster Retail. Please refer to the entities in Management APIs from FashionMaster Retail API Reference page. Request Parameters These are the parameters you can provide to get the needed entity based on FashionMaster Retail API Reference. Please look at the example below on how to fill the Request Parameters field when subscribing GetCustomerDetails entity
Publishing Entity to FashionMaster Retail
Steps
- Go to Connections -> Outgoing, create a new outgoing configuration, and select FashionMaster Retail Publisher as the publisher.
- Select the action that you want the publisher to do with the data.
- Select the FashionMaster Retail entity you want the data to be published.
- Select the SOAP Client to use.
General Concept
Like the subscriber, the publisher has similar methods on how to use it. The difference is the payload that will be submitted by the publisher originating from the data (from routes, from transformers in outgoing configuration). Entity We support publishing to most FashionMaster Retail endpoints but not with publishing binary files at the moment. Please refer to the entities in Management APIs from the FashionMaster Retail API Reference page. Based on the documentation, some endpoints may need one or more path parameters. For endpoints that require an object as the request payload, please look at the example below. For example, we want to Create a AmendCustomer. Please select “CreateAmendCustomer” as the entity of the publisher.
