[
https://issues.apache.org/jira/browse/NIFI-3941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153698#comment-16153698
]
ASF GitHub Bot commented on NIFI-3941:
--------------------------------------
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/2124
@yuri1969 @alopresto Just wanted to chime in that technically the
Controller Services in the Controller Settings are for Reporting Tasks and
other Controller Services denied there. For instance, a Reporting Task could
reference Controller Service A and Controller Service A could reference
Controller Service B. In this case, both Controller Service A and Controller
Service B would be defined in this listing. The existing sentence that
@yuri1969 mentioned states:
> Listed services are available to all Reporting Tasks and services defined
in the Controller Settings.
> Clarify tab name for controller level controller services dialog
> ----------------------------------------------------------------
>
> Key: NIFI-3941
> URL: https://issues.apache.org/jira/browse/NIFI-3941
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
> Affects Versions: 1.2.0
> Reporter: Andy LoPresto
> Priority: Minor
> Labels: label, ui
>
> As a follow-on to
> [NIFI-3911|https://issues.apache.org/jira/browse/NIFI-3911], I believe the
> *Controller Services* tab in the "global"/"controller level" *Controller
> Settings* dialog should be renamed to *Reporting Task Controller Services*
> and a sentence added above the table explaining that any controller services
> added here are only accessible by reporting tasks and not accessible by any
> components on the flow itself.
> {quote}
> Would it make sense to change the title of the tab in the global Controller
> Settings dialog to "Reporting Task Controller Services" and add a sentence
> description above the table stating that these controller services are only
> accessible by the Reporting Tasks?
> {quote}
> This is helpful for users who do not read the extensive documentation in the
> User Guide.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
