Bryan, That makes sense, but I missed that subtly in the 0.x to 1.x changes. I ran into some questions while trying to get it straight in my head.
* How do the global controller services differ from those in the root process group? * Are the global controller services only available to reporting tasks? * Are reporting tasks unable to use any process group controller services? (I think you said they can't, just want to confirm.) * Can any user reference the global controller services or does that carry a separate authorization policy? Regards, Joe On Thu, Mar 2, 2017 at 4:11 PM, Bryan Bende <[email protected]> wrote: > Hi Mark, > > Controller services from the global menu are only for use by reporting > tasks that might use a controller service. For example, the > SiteToSiteProvenanceReportingTask uses an optional SSLContextService, > which would need to be defined at the global level. > > All controller services used by processors are created from context > palette and are based on the process group you are in at the given > time (the root canvas is the root process group). This is done for > security purposes so that access to the controller services can be > inherited by access to the process group if desired. > > Thanks, > > Bryan > > > On Thu, Mar 2, 2017 at 3:56 PM, Mark Bean <[email protected]> wrote: > > Can someone please clarify the difference between the Global Menu -> > > Controller Settings -> Controller Services tab and Root Canvas -> > > Configuration button from palette -> Controller Services tab? > > > > I would expect that a Controller Service added via the Global Menu would > be > > available at all levels of the graph. However, this does not seem to be > the > > case. (It is the case for Controller Services added through the palette > > Configuration button.) > > > > Thanks, > > Mark >
