[ 
https://issues.apache.org/jira/browse/NIFI-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16125840#comment-16125840
 ] 

ASF GitHub Bot commented on NIFI-3780:
--------------------------------------

Github user moranr commented on the issue:

    https://github.com/apache/nifi/pull/2081
  
    This will be a nice addition from a usability perspective.
    
    It could be helpful to go ahead and generate a default name for the service 
following some type of simple naming convention (e.g., 
StandardSSLContextService**-1**, StandardSSLContextService**-2**, and so on). 
This would actually be helpful to follow for _any_ controller service that is 
created, not just if it is created via a processor/service configuration 
dialog. 
    
    I also notice in the dialog that the name field is at the bottom of the 
dialog and not seen unless scrolled to. It would be helpful see that field at 
or near the top so the user can immediately relate to the new service by its 
name.


> Should be able to specify Service name when I create a new Controller Service 
> within a Processor/Service configuration dialog
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-3780
>                 URL: https://issues.apache.org/jira/browse/NIFI-3780
>             Project: Apache NiFi
>          Issue Type: Sub-task
>          Components: Core UI
>            Reporter: Mark Payne
>
> When I am configuring a Processor (or a Controller Service) and a Property 
> Descriptor allows me to create a new Controller Service, that New Controller 
> Service dialog allows me to choose which service type to create. However, we 
> often have a few different instances of the same Controller Service type. In 
> such a case, it is then confusing which service I'm looking at.
> I would like that New Controller Service dialog to have a field for 
> specifying the name of the Controller Service. That field could either be 
> pre-populated with the class name and allow me to change it, or the field 
> could be blank and the class name can simply be used if nothing is entered.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to