webapi /integration design for requirement

Hi,

To achieve this,use integration to communicate with an external system. Send your request body (input parameters) to the external system and receive the correct response if all the email addresses are correct. Retrieve the results from the output section and store them in the Appian database using write smart services.

Here is the reference : 

Calling Integration :


Fetching Result :

Hi   /Mathurambika M  : from the integration i will get response(output) as many employeeids which needs to be stored in db .

In the db i need to store all this employeedsid, if i use datatype as int ,max limit is only 255 . how to store the data.

can you please suggest 

Hello,

You can store employee IDs as text type and later cast it to integer whenever you need to use it.

If i give datatype as int(11) will it not store all the employeesid {1234567 ,1234657 ,1325476...............upto 100 employeeids} ?

The 'int(11)' datatype in DB specifies an integer with a display width of 11 digits, but it doesn't limit the range of values that can be stored. It means the display width is 11 characters, but the actual storage and range of values are determined by the integer type.

For 'int(11)', you can store integers ranging from -2147483648 to 2147483647. If your employee IDs are within this range (which is highly likely), it will be suitable for storing them. In your case, with employee IDs like 1234567, 1234657, etc., 'int(11)' should work without any issues.

Wouldn't you have 1 row per email where you can put the associated id?

Ideally that service would send you back a list of ids that are associated to emails which you can then use to update your DB.

Otherwise, you would have to rely on the order on which it was sent and recieved which I don't recommend.

the emails are stored in db  in one line (not 1 email per line ) and those emails it will be passed to the api ,the api sends back the employee ids (as array seperated by ; ) of those email addresses present 

Is there any particular reason why that can't be a table instead?

All those emailadresses will be pasted from excel to interface (paragraph field)

All those emailadresses will be pasted from excel to interface (paragraph field)

Is the API able to respond with the a list of the emails and corresponding ids?

API work is still  in progress  by third party

I would request that they send you a response that includes the email + id. You can then just store that in a table on your side after your receive the response and still capture the initial emails in a paragraph.

{
    {
      email: "test2@test.com",
      id: 1
    },
    {
      email: "tes2@test.com",
      id: 2
    }
  }

Basically i wilI be creating a request on site  by adding emailaddresses and upon click of submit it should be sending the emails addresses (line delimited) to the email validation API, and if all emails are valid then it store the EmployeeIds in the db .  

Mathieu Drouin :Not able understand your point .can you please elaborate

Unsure what your requirement is but having a table with two text fields with comma delimited values is not a recommended design.

You can capture the emails and them in a comma delmited format to the API but I would request to the 3rd party that they send you the response in the format outlined above so that you know which ID is associated to which email.