UploadHook improvement: let the developer decide whether to save the element or not

Dear FirstSpirit-community,

with the current implementation of the UploadHook solution (currently checked with FirstSpirit 5.1 R2 209), FirstSpirit always creates a new revision of the processed element by executing a save-action at the end - whether this step is useful or not.

Imagine, the goal is to get a released element finally. With the current FirstSpirit core implementation of the UploadHook solution, the element stays in an unreleased state at the end. Although, the processed element has been released within the code part of the custom UploadHook. Details can been shown in the following screenshot. There, it can be proven that the save action is not implemented in the custom upload hook solution but executed by FirstSpirit core:


This is not very useful.

That's why this feature request votes for omitting the implicit "save" action and give the developer the responsibility to decide if and when to save.

1 Comment
Crownpeak employee
Crownpeak employee

Hello Holger

thank you for your idea to improve FirstSpirit. It is important for us to learn from the experiences of our customers and partners. For this reason we appreciate feedback and any suggestion.

Several functions can be attached to one hook. Since the order is not known, each execution would have to be saved. This can quickly lead to problems. Therefore, we cannot consider your feature request at this time.

You can find more details about our feature selection process in our Features Policy.

Best regards