-
Notifications
You must be signed in to change notification settings - Fork 465
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the ability to run a Workflow action async #29094
Labels
Comments
jdotcms
added a commit
that referenced
this issue
Jul 2, 2024
jdotcms
added a commit
that referenced
this issue
Jul 2, 2024
jdotcms
added a commit
that referenced
this issue
Jul 5, 2024
jdotcms
added a commit
that referenced
this issue
Jul 5, 2024
jdotcms
added a commit
that referenced
this issue
Jul 5, 2024
jdotcms
added a commit
that referenced
this issue
Jul 5, 2024
jdotcms
added a commit
that referenced
this issue
Jul 5, 2024
jdotcms
added a commit
that referenced
this issue
Jul 5, 2024
jdotcms
added a commit
that referenced
this issue
Jul 8, 2024
jdotcms
added a commit
that referenced
this issue
Jul 9, 2024
jdotcms
added a commit
that referenced
this issue
Jul 10, 2024
jdotcms
added a commit
that referenced
this issue
Jul 10, 2024
jdotcms
added a commit
that referenced
this issue
Jul 10, 2024
jdotcms
added a commit
that referenced
this issue
Jul 10, 2024
jdotcms
added a commit
that referenced
this issue
Jul 10, 2024
john-thomas-dotcms
changed the title
fea: Add the ability to run an action async
Add the ability to run a Workflow action async
Sep 4, 2024
john-thomas-dotcms
added
dotCMS : Workflow
OKR : Technical User Experience
Owned by Freddy
labels
Sep 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Parent Issue
No response
User Story
As an api user, I want to be able to run a workflow async
All subactions will be run in a separated thread
In addition on rest api call, the contentlet may have a flag to tell to async action to run sync (such as testing proposals)
On the wf portlet will add a check to be async or not (uncheck by default) [state will be saved on the wf action metadata]
changes on the UI (TDB)
Acceptance Criteria
The thread may run in a separated thread, the response will continue sync both the response will returns something to keep the status track on the future
Proposed Objective
Core Features
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: