Document Drag-and-Drop should fire a document change event for the Event Subscription API

Description:

Workfront uses the Event Subscription API to transmit changes to our services when a document in created or updated on a project. Currently, when a file is moved (drag-and-drop) from one folder to another, it does not fire any event to indicate that this action occurred. The argument i got from support was that this just "changes the folderID field 'on' a document", and that their product was functioning as intended. However, changing the folder ID for a document is in fact a change TO the document, as you are changing critical information associated directly with the document. In computers, a file/document always exists within a folder. When you change where the document lives, in computer operating systems and workfront, it is always done by doing operations on the file icon itself, or specifying the file's path and/or name. Thus, it makes sense that changing the folder a document is in should be an notable enough be considered an "UPDATE" event in the Events Subscription API.

Why is this feature important to you:

This feature will be used heavily by the Marketing department at our University. Documents will be initially created in a "Campaign Notes" folder, and will later need to be transferred into a "Finalized Files" folder. After the transfer to Finalized Files, an event should be fired to our services that downloads said folder into storage in our University's infrastructure. It is necessary that an event fires to signify that an existing file was moved into that folder.

How would you like the feature to work:

When any document is drag-and-dropped between folders in a Workfront project, a Document UPDATE event should be sent using the Event Subscription API described in following link: https://experienceleague.adobe.com/docs/workfront/using/adobe-workfront-api/event-subscriptions/event-subs-api.html?lang=en

Current Behaviour:

Currently, UPDATE events are only sent when a new version is uploaded from an external source, and CREATE is only sent when a new document is uploaded from an external source. As an upload is simply a "move" operation from an external source into workfront, I'm not sure why the same logic wouldn't apply to fire an event for "moves" of the file within workfront, also.