awcg | 2019-01-11 16:16:19 UTC | #1
Hi everyone,
I was trying to use DELETE /api/v2/flows/datatables/{datatableId}/rows/{rowId} via Data Actions, but found that it was not accessible.
We are currently implementing a solution to temporary block hoax calls by using Data Tables as data source. Since a Data Table is limited to 250 entries, there has to be an option to delete the oldest entry, before inserting a new one (e.g. via Data Action in Agent Scripts). The limit of 250 entries is fine for us though, since similar commercial blockers also tend to limit between 50 and 500 blocking entries.
However, I do not understand the stated decision (https://developer.mypurecloud.com/forum/t/why-data-actions-does-not-support-delete-method/2073/2) that the DELETE verb is not accessible, to (basically) prevent the customer from harming himself. This should be up to the developer.
As a workaround I would now have to implement an external service that accepts e.g. GET to emit the DELETE action - thats not acceptable.
Does anyone have a similar use case and found a way to manage it - even with the stated limitation?
Also, I would like to challenge the stated decision.
Regards
Richard.Schott | 2019-01-11 20:02:09 UTC | #2
@awcg,
The decision to not allow the verb DELETE in data actions is rooted in the fact that interaction flows are still operated autonomously. Giving an autonomous process destructive capabilities in your system of record is not something we're keen on providing. The potential for irrevocable damage far outweighs the few potential use cases (this one included). You also have to keep in mind that if Deletes are supported in one integration, it would be required to be supported in all of them, as each integration utilizes the same underlying structure.
What you're describing is actually an ideal scenario for something like a Lambda that stacks several related web service calls together to delete the oldest row, insert a new row, then update the new row with the new data. This likely would simplify your implementation within the script, and probably lead to a cleaner implementation overall (the lambda could contain error handling, alternate cases, etc.).
system | 2019-02-11 20:02:13 UTC | #3
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 4334