Russell, Additional details are supported for any of the extension types. I can't tell from your message what's happening but I can point you to an example. [1] is an example of additional details for the CSVReader Controller Service. When that directory structure is followed, it should get unpacked into <NIFI_HOME>/work/nar/extensions/nifi-record-serialization-services-nar-2.7.0-SNAPSHOT.nar-unpacked/META-INF/docs/additional-details directory. You could check that directory in your NiFi instance and see what the contents look like. It may help point in the right direction.
Matt [1] https://github.com/apache/nifi/blob/main/nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.csv.CSVReader/additionalDetails.md On Fri, Oct 3, 2025 at 4:05 PM Russell Bateman <[email protected]> wrote: > I write very few service controllers and have never tried to associate > /additionalDetails.html/ (or /additionalDetails.md/) with a controller, > but today I need to do just that (if supported). > > I have a perfectly working (new) controller service, its interface, > tests for it (duh) and also: > > - > > /*resources/META-INF/services/org.apache.nifi.controller.ControllerService*/ > containing /packagepath.ServiceControllerName/ to the new service > > - /*resources/docs/*packagepath*.controller.*ServiceControllerName/ > with > > * /additionalDetails.html/ (for NiFi 1.x) > * /additionalDetails.md/ (for NiFi 2.x) > > It appears in the NiFi UI (I'm working presently in 1.28.1), is > configurable, etc. > > This is in direct imitation of all my custom processors whose additional > details content has long been served up. > > I am reaching my service controller Usage via: > > hamburger -> Controller Settings -> MANAGEMENT CONTROLLER SERVICES > -> Usage (book icon) > > but there is no link to _/Additional Details.../_ > > Are additional details just not supported for service controllers? > > Thanks for any help, comments, etc. >
