This article provides step-by-step instructions on replacing the default Venio logos with your custom logos for both the login page and the case dashboard. Follow these procedures carefully to ensure a smooth update.
C:\inetpub\wwwroot\VenioWeb).tbl_pj_ControlSetting table in the Venio database.The login page uses a vertical logo file stored in the following location:
File Location:
C:\inetpub\wwwroot\VenioWeb\assets\img\venio-logo-full-vertical.png
Backup Original File:
Create a backup of venio-logo-full-vertical.png in case you need to roll back the changes.
Prepare the New Logo:
Ensure your new logo is in PNG format and has similar dimensions to the original (approx. 148px by 123px). Rename it to exactly:
venio-logo-full-vertical.png
Replace the File:
Copy your new logo file into the folder:
C:\inetpub\wwwroot\VenioWeb\assets\img\
Replace the existing file.
Clear Cache and Restart IIS:
iisreset in PowerShell or Command Prompt (as Administrator) to restart IIS.The case dashboard (or launchpad) logo should be a PNG stored at:
File Location:
C:\inetpub\wwwroot\VenioWeb\OnDemand\Images\<your-logo-name>.png
Prepare the New Logo:
Ensure it’s in PNG format.
Backup VenioPCD:
It is recommended to backup the VenioPCD before modifying the tbl_pj_ControlSetting table.
Prepare Update of Database Setting:
The system uses a file path stored in the tbl_pj_ControlSetting table. Update it to ensure the new logo is referenced correctly. Execute the following SQL query against your Venio database:
BEGIN TRANSACTION;
UPDATE tbl_pj_ControlSetting
SET [Value] = 'ondemand/Images/<your-logo-name>.png' -- replace <your-logo-name> with the actual file name
WHERE [Key] = 'LOGO_PATH';
Select * from tbl_pj_ControlSetting
-- If an error is encountered before committing, execute:
ROLLBACK TRANSACTION;
-- If everything is correct, finalize the changes:
COMMIT TRANSACTION;
iisreset.By following these detailed steps, you should be able to successfully replace the default Venio logos with your custom logos on both the login page and the case dashboard. If issues persist, recheck the file paths and database entries to ensure they match the requirements.