-
Notifications
You must be signed in to change notification settings - Fork 15
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
Dynamic Workflows #215
Dynamic Workflows #215
Conversation
I did some testing and can confirm that our workflows work as expected. But I would strongly suggest some design optimizations (see mockup for a suggestion):
@ferishili: What do you think of this suggestions? |
Thanks a lot @dagraf. I am going apply the changes ASAP |
Hi @dagraf, |
Thanks for the changes, which look good. Only the "Configuration Panel" is not yet renamed. But for the moment I suggest we leave it as it is and change the wording at a later stage. Therefore and @Amstutz: Can you please review this PR and comment it if needed or merge it. Thx! |
Thank you. |
Renaming of Configuration Panel: I did refresh the languages but maybe some cache settings is playing a trick on me. I will retest later and comment here if needed. |
I also tested the changes to the configuration panel with our workflows, they look fine. Thanks for coming up with the improvement @dagraf and @ferishili |
PR in elan-ev#4 to resolve conflicts |
This PR fixes #13
Description
see description in issue.
Solution
Now configuration panel is loaded, converted into ILIAS style and presented to users directly from Opencast, so you will have dynamic parameters to interact with and then those values will be sent back to opencast.
the whole concept/approach is that:
Admins:
workflow_selection_text_{workflow definition identifier}
e.g.workflow_selection_text_{republish-metadata}#:#Veröffentlicht
in the lang strings.Users:
NOTE:
This PR increase the plugin version to 5.3.2 and a db update No. 43, so it might have conflicts with current PRs!