I believe the behavior originally was to not delete original, then it was changed to delete original, then recently not delete original, and now delete original again.
I have suggested this in the past: Turn off behaviours of Fibery app - #2 by RonMakesSystems, and I think it can be relevant here. If the architect could see the default Fibery actions in the buttons menu of the database, they could turn specific buttons on or off, or configure specific settings for those buttons.
For example: “Delete original entity after conversion” option settable per DB.
I personally do not understand the point of the “Convert” action, if others (@Jonathan1) can chip in here that would be great. What is the added value of using the “Convert” as opposed to making a custom action button and manually mapping out the fields?
For one-off mistakes I understand, but if its a repeatable process, why not a single button to convert to desired entity which is the next thing in the process? Trying to understand use cases here.
Just my 2 cents :))
And we know that a small release just means there’s big things in the work (or a well deserved break). Waiting patiently.