Put topics about this connector package here.
Always check the ‘How to use the Alumio connector packages’ topic.
Extra information
System documentation: REST API for developers - AFAS Help Center
Find shared AFAS configurations in our Exchange configuration category.
Connector package documentation
Table of Contents
-
1. Setting up HTTP Client AFAS
- 1.1 Steps
-
2. Subscribing to Entities from AFAS
- 2.1 Steps
- 2.2 General Concept
-
3. Publishing Entity to AFAS
- 3.1 Steps
- 3.2 General Concept
1. Setting up HTTP Client AFAS
1.1 Steps
-
In Alumio Dashboard, go to Clients → HTTP Clients.
-
Create a new HTTP Client and select AFAS Client as the prototype of the HTTP Client.
-
AFAS has URL with environment ID that needs to be filled in and Base64 of AFAS token that you would like to use.
2. Subscribing to Entities from AFAS
2.1 Steps
-
Go to Connections → Incoming and create a new incoming configuration and select AFAS Subscriber as the subscriber.
-
Select the AFAS HTTP Client to use.
-
Add any request parameters needed to subscribe to the entity (optional).
-
You can optionally add a transformer to transform the request parameters into something you need.
2.2 General Concept
AFAS uses custom connector for using subscriber please fill the Entity based on the Connector Name in AFAS application
Entity
Fill in the connector name that you created in AFAS application.
Request Parameters
It’s the parameters you can provide to get the needed entity based on AFAS API Docs. As example we can fill like this to get Order which date in the year 2022.
Input Transformer
Any transformer’s set here will be executed after the Request Parameters loaded. So, you basically can add any transformer to provide and transform the request parameters into anything you need either as path parameters and/or as query parameters of an entity.
HTTP Client
It’s the HTTP Client configuration you will use to access AFAS.
3. Publishing Entity to AFAS
3.1 Steps
- Go to Connections → Outgoing, create a new outgoing configuration and select AFAS – Entity Publisher as the publisher.
- You can also optionally add any transformers to transform the data into anything you need before submitting it to AFAS.
- Select the AFAS HTTP Client to use
- Fill in the AFAS Connector Name the same as the one created in AFAS application
3.2 General Concept
AFAS uses custom connector for using publisher please fill the Entity based on the Connector Name in AFAS application.
Method
You can select the method of Post, Update or Delete to do what you want with the Publisher.
Entity
To fill data using Alumio AFAS connector we need to use the Alumio standard pathing and fill the payload with the data we want to add to AFAS as example when we creating order
Alumio will send an API request to AFAS based on the setting
HTTP Client
It’s the HTTP Client configuration you will use to access AFAS.