When creating a new usecase in the admin portal you have the option of saving pictures locally or in a cloud storage. This option can be found in Pictures Setup.
When choosing the Local option you must define the name under which the image will be saved. For this you have many presets to choose from (Reference, Number, Date, etc.). The name functions as a directory into which the pictures will be placed.
Normally during a SightCall session, the default location into which the pictures get saved is:
When saving a picture locally during a call, it will open the picture location automatically.
If you are experiencing dificulties successfully saving images this can be linked to a variety of reasons. Most of the time it is due to the setup of your workstation in your corporate environment. The amount of (admin) rights, or lack thereof can possible dictate if pictures get saved successfully in the correct local directory or not.
There are some steps we recommend you take if pictures aren't being saved correctly:
- When troubleshooting local save issues, it can sometimes be good to test multiple configurations, including adding a "/" to create a folder structure in the picture name/directory. You might not have sufficient user rights in your workspace to allow the SightCall application to place images in your Pictures folder, so adding a Pictures/ infront of the name can force the application to find the correct directory (see example below):
- When in doubt, always grab a Coredump log, this is especially useful soon after the issue appears. When pictures are saved locally the SightCall application opens the file directory which allows the agent to verify in real time if the picture shows up or not. If this isn't the case a coredump log will give SightCall Support the means to gain more insight into the issue. After collecting the necessary information you can open a Support Ticket, send the data and explain the issue.
- It might be good to check for automatic CoreDumps incase any additional information is stored. there which could explain why the images aren't being properly stored.
- Setting up a Cloud Storage with a Media Endpoint as an alternative method can be considered.