anchor.diff:  
   Some processors also have an Advanced User Interface (UI) built into them. For example, the UpdateAttribute processor has an Advanced UI. To access the Advanced UI, click the `Advanced` button that appears at the bottom of the Configure Processor window. Only processors that have an Advanced UI will have this button.
   
  -Some processors have properties that refer to other components, such as Controller Services, which also need to be configured. For example, the GetHTTP processor has an SSLContextService property, which refers to the StandardSSLContextService controller service. When DFMs want to configure this property but have not yet created and configured the controller service, they have the option to create the service on the spot, as depicted in the image below. For more information about configuring Controller Services, see the <<Controller_Services_and_Reporting_Tasks>> section.
  +Some processors have properties that refer to other components, such as Controller Services, which also need to be configured. For example, the GetHTTP processor has an SSLContextService property, which refers to the StandardSSLContextService controller service. When DFMs want to configure this property but have not yet created and configured the controller service, they have the option to create the service on the spot, as depicted in the image below. For more information about configuring Controller Services, see the <<Controller_Services>> section.
   
   image:create-service-ssl-context.png["Create Service", width=700]
   
  
positive.code: ).
  
  Stopping a component does not interrupt its currently running tasks. Rather, it stops scheduling new tasks to
  be performed. The number of active tasks is shown in the top-right corner of the Processor (see <<processor_anatomy>>
  for more information).
  
  === Enabling/Disabling a Component
  
negative.code: -------------------------
  
  In addition to the Summary Page, Data Provenance Page, Template Management Page, and Bulletin Board Page, there are
  other tools in the Global Menu (see <<User_Interface>>) that are useful to the DFM. Select Flow Configuration History to view
  all the changes that have been made to the dataflow. The history can aid in troubleshooting, such as if a
  recent change to the dataflow has caused a problem and needs to be fixed. The DFM can see what changes have been made and
  adjust the flow as needed to fix the problem. While NiFi does not have an "undo" feature, the DFM can make new changes to the
  dataflow that will fix the problem.
  
  Two other tools in the Global Menu are Controller Settings and Users. The Controller Settings page provides the ability to change
  the name of the NiFi instance, add comments describing the NiFi instance, and set the maximum number of threads that are available
  to the application. It also provides tabs where DFMs may add and configure <<Controller_Services>> and <<Reporting_Tasks>>. The Users page is used to manage user access, which is described in
  the link:administration-guide.html[System Administrator's Guide].
  