When I create a registry file for use by our desktop administration team there seems to be an issue with the ReplaceInFileName and FileName Template keys. The FileName Template key is created in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hummingbird\PowerDOCS\Core\Plugins\Fusion\Settings to resolve the ReplaceInFileName issue however this should create the ReplaceInFileName key in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hummingbird\PowerDOCS\Settings and there appears to be nothing created to resolve the actual FileName Template issue. When following the link given in the textbox to the OT knowledge center (https://knowledge.opentext.com/go/768426) this resolves to a ECM looking 404 page. Below is an example of the created key.
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hummingbird\PowerDOCS\Core\Plugins\Fusion\Settings]
"FileName Template"="%LibraryName%-#%DocumentNumber%-v%VersionLabel%-%DocumentName%"
If I inject this key as created into the registry the result is that the ReplaceInFileName key is still missing and that FileName Template is incorrect and should contain library, document, and version (the same message as before injection). \\Settasdffdsaasdfdsaadsfdsaasdfdsaasdfasdaa that the ReplaceIn File
