I have to send email addresses as input from Appian to external system and the external system validates those email address and send back the ids of those email address. How i can implement the design ,what all are needed ,can someone help?
Discussion posts and replies are publicly visible
Hi,I recommend using the integration object. Please refer to the below documentation:https://docs.appian.com/suite/help/23.4/Integration_Object.html#
Hi Mathurambika M , integration object is used to pass the email addresses to external system but how can i save the external system responses in Appian db (if all email address are correct then external system api passes the employee ids of those email address which needs to be stored back in appian db)
You can create a process model to invoke your integration by passing the required inputs (email addresses in your case). Retrieve the resulting IDs from the output tab. Upon successful execution of the integration, write the output email IDs to your table.https://docs.appian.com/suite/help/23.4/Call_Integration_Smart_Service.html
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