#228 Concrete created based on Template is not bound by all restrictions

[Noam Weingarten]

A Concrete workflow created based on a Template is not bound by all restrictions specified in the configuration of the basing Template.

The scenario is:

I have created workflow – even just a simple workflow.
I created a template based on that concrete workflow – leaving all settings “closed”.
I then create a concrete workflow based on that template.

I am now trying to configure the templatized workflow (or Genuine Embeded workflows as the gUSE User Manual describes it).

Most details of jobs cannot be modified – as should be the case.

But from the Job Configuration page, I can change the “Job is” detail (ie. whether it is a “binary” or a “workflow” ) – even though on the template the “Job is” set as “close”.

From the Job I/O page, for input ports, I am free to change the source of the input type (“Upload”, “Remote”, “Value” or “SQL”) – but not to actually change chose a different input file, change the location of the remote file, enter a new value or change the SQL details.

For output ports, I am free to change the “Storage type” between “permanent” and “volatile” – even though on the template the “Storage type” is set as “close”.

I do not think this has been touched since 3.3.3, and so would effect all gUSE portals - of all versions 3.3.3 onwards.

PS. I am using browser Chrome v. 35.0.1916.114 m and Windows 7

[Gabor Hermann]

Yes, I confirm the ticket.