File field "Upload New File" dialog shows only base FileAsset (System Workflow) actions — ignores folder's Default File Asset Type
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
When uploading a file via a content item's File field → Browse → "Upload New File", the upload dialog's workflow-action dropdown is populated from the base FileAsset content type (System Workflow) instead of the folder's "Default File Asset Type." If the folder's default file type uses a different workflow scheme, the user only sees System Workflow actions; executing one against the resulting content throws:
The Workflow Action [] is not related to any Workflow Scheme associated with the Content Type , content inode
PR #30451 made the uploaded file resolve to the correct folder default type server-side (UploadMultipleFilesAction.java), but the client-side dialog that builds the workflow dropdown was not fixed, so the mismatch persists.
Steps to Reproduce
Steps to Reproduce
Create a content type based on the File Asset base type (e.g. "Repro Files"); assign it only a non-System workflow scheme (e.g. Blogs).
Create a folder and set its Default File Asset Type to that content type.
Create another content type with a File field.
Content → Search → Add New Content → on the File field click Browse → navigate into the folder from step 2 → Upload New File.
Open the workflow-action dropdown in the Upload dialog.
Acceptance Criteria
The dropdown lists the workflow actions of the folder's Default File Asset Type (e.g. the Blogs scheme).
dotCMS Version
Reproduced on 26.06.06-01 (dotEvergreen / current release, June 2026). Originally reported on 24.08.27 (#30023).
Severity
Medium - Some functionality impacted
Links
Support ticket: https://dotcms.freshdesk.com/a/tickets/37524
Prior related ticket: https://dotcms.freshdesk.com/a/tickets/24385 (originated #30023)
Slack confirmation: https://dotcms.slack.com/archives/C08F8NZRK9S/p1781108899456709
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing UploadMultipleFilesAction.java and tracing the client-side Upload New File dialog described in the issue, focusing on how its workflow-action dropdown is populated. Reproduce the folder default file type scenario; done when the dropdown shows actions from that type's workflow scheme rather than the base FileAsset System Workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100