Workflow Improvements

• have one app that can do copy/move/etc (so it's a "complete" rules - action - argument thing)

@jospoortvliet I understand what you mean is to have one, unified GUI for any app that takes advantage of the workflow engine

Missing pieces from #16682

Backend

• Dispatcher Events: currently we rely on GenericEvents, but it is not reliable (i.e. tagging is using the deprecated Disptacher's Event subclass) and we actually have an offical API subclass (based on GenericAPI). These needs to be ironed out to work generally:
  • WFE should either require \OCP\EventDispatcher\Event or find a good way for any of those. Related: https://github.com/nextcloud/server/pull/17085
  • switch File events (and move event names to constants)
  • maybe change tagging events to be based on \OCP\EventDispatcher\Event
• optimize File entity to fetch nodes from the respective userFolder, not rootFolder
• ensure user-scoped rules to not access foreign objects
• OCC command for admins to manipulate the workflow, at least to disable user workflows that might be stressful for the instance
• CompoundEntity – predefined for end users: an entity with one or more checkres, e.g. "Picture" (File + mimetype) or "One on one" (direct chat).
• add more entities (see use cases)
• add more operations (see use cases)

Frontend

• Move system tag selector to vue components https://github.com/nextcloud/nextcloud-vue/pull/568
• Handle validation on inputs before sending (enhancement)
• Check if fetching tags incremental is working
• Comments from https://github.com/nextcloud/server/pull/16706
• Remove additional style import https://github.com/nextcloud/server/pull/17367#discussion_r330947557

UX

• when choosing "Images" as mime type, the checker will only work when the operator is "matches", not "is"

App modifications

• files_accesscontrol
• workflow_script
• workflow_pdf_converter
• files_automatedtagging

Start by reviewing the unchecked Backend, Frontend, UX, and App modifications items, along with the referenced pull requests. The issue names no files, tests, or single entry point, so first identify one narrowly scoped missing piece. Done would require completing that piece and validating its related workflow behavior.