-
Notifications
You must be signed in to change notification settings - Fork 602
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
Bulk Workflow MCP Process #1953
Comments
…ative path param is not respected for QueryBuilder query language type
One thing I've never been hip to was requiring a user to enter a query as text, but for a first pass that's fine. Are there any other considerations we should make? For example, we might want to consider adding reporting options (detailed vs. counts only) and a dry run option so that it's feature-parity with some of the more powerful MCP tools like Renovator. |
Sure you can add those features in later PR is you want. This was trying to achieve functional parity w BWM so we can start deprecating it. A dry run flag should be pretty easy for you to add. This feature may be moot soon anyhow so I’d think about that before investing too much time in it tho! |
Sounds good! Looks like we have this merged in already so I'll close this issue. |
* #1953 - Bulk Workflow MPC process
It would be nice to move Bulk Workflow Manager to MCP Process. This would mean Bulk Workflow would only support Synthetic Workflow (multi-threaded).
This will help clear out
/etc/acs-commons
and reduce the need to re-creating BWM on something more modern than AngularJS. Also, worth noting per #1951 BWM running AEM Workflow on 6.5 breaks (appears to result in . a number of Oak conflicts as the WF runs on the payloads)This UI would simplify the execution options to be:
.. Something like ..
The text was updated successfully, but these errors were encountered: