In reply to: Daniel Krüger (Cosmo Consult)
while I'm glad that an experienced partner joined the community I'm baffled by this suggestion.
I'm currently on vacation so I can't check it but those procedures I had a look at, did exactly what the name implied. Insert/Update/Delete of an entry in the table. I assume it's the same with the mentioned procedures. Therefore I would assume that you loose the history and therefore one of the great strength namely audit/traceability?
While I personally wouldn't use internal functionality which modifies data, you could achieve something similar using the default action to change an item list and use a custom SDK action for deleting speicif rows.
if you use Jva Script for this, traceability might also become problematic. The actions for adding, removing and changing item list entries only work on a per-instance basis. If you want to add an entry "from outside", these do not work. (e.g. assume a for-ech automation)
With the SQL procedures, the changes in the item list are at least visible, even if not under the name of the executing person.
Finally, there is still the use of the WEBCON REST API ... which can also be used to create item list entries.