...
- diff functionality for XML files (comparison of XML inside workflow and XML inside actor)
- storing new XML inside workflow
- at the moment, XML stored inside workflow is always treated as most recent one
- in case changes inside XSD/XML, in the actor, we may end up with situation where XML stored inside workflow is incompatible with required format
- we can't easily update this information (note that there were different solutions suggested but no final decision was taken)
- it's possible to use Kepler's parsing engine to update information inside workflow "as it would be modified by Kepler
there will be new feature that will allow to "inject" new code parameters into workflow
Code Block workflow-editor -updatexml file.xml -workflow ~/workflow_ets.xml -actor name_of_the_actor
- validation of workflow's XML against actor's XSD
- this feature will allow us to determine whether code parameters inside workflow make any sense when it comes to actor's requirements
- it will allow to verify workflow's compatibility against different releases of Kepler + actors
- error handling
- proper handling of missing actor inside workflow
- proper handling of missing actor inside Kepler
- proper handling of actor that was not generated with new FC2K features (extracted code parameters)
- helper scripts
- listing all the actors that are "broken"
- extracting XSD/XML/Default XML from workflow in human readable format (all at once)
- adding feature that will allow to analyze Kepler installaion
- list all ITM/IMAS based actors
- validate all the actors inside Kepler