As of ILLiad v9.1.2 & 9.0.4, ILLiad can now automatically update the Docline scripts as new versions become available. To enable this functionality, there are two Customization Keys that need to be configured first. To ensure ILLiad knows where to update the scripts, they are now being installed in a new default location C:\ProgramData\ILLiad\Docline\. If your library uses custom field translations (and DoclineAutoUpdateFieldTranslations is set to No), ILLiad will copy the field translation files present in C:\Program Files (x86)\ILLiad\Docline\ over to the new Docline script location when upgrading. The ILLiad Client 9.1.2 installer grants the 'Modify' permission to the new default Docline folder for the 'Users' group to ensure any ILLiad staff user can update the scripts. The Client installer should handle this by default; if this setting isn't correct users may see a message indicating that ILLiad was denied permission when trying to update the Docline scripts.
To enable this functionality, you will need to set the DoclineAutoUpdateEnabled and DoclineAutoUpdateFieldTranslations Customization Keys to yes. These keys are added during the 9.1.2 server update; however, they do not exist in 9.0.x installs by default; a New Record should be added to the table in the Customization Manager under System | General | Customization page.
If your ILLiad installation is a shared server, you will need to repeat this process for each NVTGC, updating the NVTGC field in each custkey as appropriate.
|Description:||Determines if the ILLiad Client should prompt the user to automatically update Docline scripts when available.|
Sites that modify their FieldTranslation.xml and LendingFieldTranslation.xml for customize field mapping should make sure the DoclineAutoUpdateFieldTranslations key is set to No.
|Description:||Determines if the ILLiad Client should overwrite the FieldTranslation.xml and LendingFieldTranslation.xml Docline files when updating their scripts. This key if ignored if DoclineAutoUpdateEnabled is set to No.|