WU Details page does not allow editing of WU Scope
Field Tab
Administrator use only
Field Tab
Administrator use only
Description
Users may want to edit the Workunit Scope and this is no longer an editable field.
Conclusion
None
Activity
Show:
Kanghua Wang December 3, 2014 at 7:00 PM
I have created a subtask for ESP and legacy ECLwatch. Please check if you have to do anything in new ECLWatch.
Kanghua Wang August 21, 2014 at 1:00 PM
Yes, it is the second one – security-related WuScope. Therefore, I think that, if an HPCC environment without security being set, we should not display the WuScope and not allow a user to edit it.
Jim DeFabia August 21, 2014 at 12:20 PM
I was referring to security-related scope of a WU. A scope can be set initially (overriding the default) using #Workunit('scope','myscope'). I suggest we add a setWUScope to allow a user to change a WU scope for security's sake.
Richard Chapman August 21, 2014 at 10:14 AM
Actually there is no setScope, only a getScope (which retrieves the prefix from the cluster).
Richard Chapman August 21, 2014 at 10:12 AM
Looking at the sources in workunit.cpp, I see part of the reason for the confusion
There are methods setScope/getScope, that set or retrieve the PREFIX used for files that don't have a leading ~, and functions setWuScope/getWuScope that seem to be security-related.
I assume the scope field you are talking about is expected to set the latter?
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Users may want to edit the Workunit Scope and this is no longer an editable field.