The frontline support team will be unavailable to answer questions on April 15th and 17th 2019. We will be back soon after. Thank you for your patience and we apologize for any inconvenience!
Release Notes can be found here.
Firecloud should be less "agressive" abount missing output fields in a method configuration
When a workflow has outputs they should up as fields in FireCloud, but sometimes as a configuration author I would like to ignore some of these outputs. While this is legal, there's a "scary" red error box ("Failed at line 1, column 1: `workspace.' expected but end of source found") when editing the method config. This error can be safely ignored if the output isn't wanted.
Training users that they can ignore red error boxes, is probably not a good thing (especially that if the error is in the inputs, the workflow will probably not work....)