Expose data to external system

RE: Expose data to external system

Stefan Helzle — Tue, 30 Jan 2024 10:07:00 GMT

When we talk about implementing a web API that other systems can call to query data, I recommend to not store any data locally, but to let the other system decide what to put into the response. A frequently used approach is to add paging info like start index and batch size to the call. Then you API can fetch the requested data and send it back.

RE: Expose data to external system

harikumarm0002 — Tue, 30 Jan 2024 09:58:06 GMT

yes

RE: Expose data to external system

Harshit Bumb (Appyzie) — Tue, 30 Jan 2024 09:54:37 GMT

You are sending rows using a GET API?

RE: Expose data to external system

harikumarm0002 — Tue, 30 Jan 2024 09:43:59 GMT

Hi Harshit ,

we are using GET web api call smart services are not supporting

RE: Expose data to external system

harikumarm0002 — Tue, 30 Jan 2024 09:41:01 GMT

i am using expression rule to fetch the data from DB here applying some filters( related this data UI user can edit n number of times they can able to changes that many times sending data to external system). so if i set the flags if user not change anything will avoid that cases/ requests

RE: Expose data to external system

Harshit Bumb (Appyzie) — Tue, 30 Jan 2024 09:40:18 GMT

If you are calling this integration from the process model, you can simply update the rows you fetched earlier to send, set the flag, and update them back in the DB.

If you are doing it from the interface, you can use the integration rule's onSuccess parameter to call a!writeToDataStoreEntity or a!writeRecords and it should do the work.

RE: Expose data to external system

JayaPrakash Ravipati — Tue, 30 Jan 2024 09:25:57 GMT

Hi harikumarm0002 ,

Can you tell how you are passing , Assuming you are using queryrecord() you can have the filters and you can pass the required data to external system

RE: Expose data to external system

ganesh_sasank18 — Tue, 30 Jan 2024 09:24:14 GMT

Can i know how you are filtering data