[DOCS] Document overrideConfiguration parameter

Some remarks regarding the overrideConfiguration parameter
have been documented.

Resolves: #89933
Releases: master, 10.4
Change-Id: Iabce22db2257fc85a415d1c7d74d2a9195586ae3
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70479


Tested-by: core-ci <typo3@b13.com>
Tested-by: Andreas Steiger <typo3@andreassteiger.de>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: Andreas Steiger <typo3@andreassteiger.de>
Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>

typo3/sysext/form/Documentation/I/Concepts/FrontendRendering/Index.rst

@@ -340,6 +340,21 @@ those).
      ...
 
 
+.. note::
+
+   In general, you can override each and every ``form definition`` with the help
+   of TypoScript (see ':ref:`TypoScript overrides<concepts-frontendrendering-runtimemanipulation-typoscriptoverrides>`').
+   This feature is not supported when you are rendering forms via the ``RenderViewHelper``.
+
+   Luckily, there is a solution for your problem: use the ':ref:`overrideConfiguration<apireference-frontendrendering-renderviewHelper-overrideconfiguration>`'
+   parameter instead. This way, you can override the form definition within your template.
+   Provide an according array as shown in the example below.
+
+   .. code-block:: html
+
+      <formvh:render persistenceIdentifier="EXT:my_site_package/Resources/Private/Forms/MyForm.yaml" overrideConfiguration="{renderables: {0: {renderables: {0: {label: 'My shiny new label'}}}}}"/>
+
+
 .. _concepts-frontendrendering-programmatically:
 
 Build forms programmatically