This KB will serve as a guide for setting up new stores running PrismCloud, as well as common troubleshooting tips for existing PrismCloud Setups.

Synching Store Settings

In previous versions of Prism such as 8.x, it became common practice to fully cycle Prism after making a store side change (printing change, order type configuration change, etc.). With Prism Cloud, most of the time this is no longer necessary as changes made through the Management screen appear to save in real time. However, there are certain situations where changes made through the Prism Cloud Management screen stay “cached" to the browser and require a settings push in order to take effect, similar to cycling the Prism service on a 8.x system.

From the Management screen, go to System → Sync Options → Sync Menu and Settings. From here click on Sync Menu and Settings, and if successful you should receive a prompt that states “Update has been forced”

F9 Flags

F9 flags as we know them in 8.1 and previous versions are now labeled as Settings. To access the Settings menu, log into the “Management” screen for the Organization in question (Such as https://fattessantabarbara.prismcloud.net/). In the top right corner there is a dropdown arrow to the right of your user name. Click this arrow and go to Settings. By default this screen will show flags for the entire organization, so it is important to change the dropdown menu to the store in question and then hit Search.

Web Ordering Admin Changes

Many of the Web Admin settings have been moved to the PrismCloud Management screen. This includes setting web hours, web exceptions, prep times, and payment options.

Caller ID Configuration

The “Manager” computer will be running a service called PrismCloud.StoreService. This is similar to the Prismservice that would run on 8.x systems. For the most part, the caller ID service will function the same as it did in previous versions of Prism (Windows configuration, flags, etc.) However, The service (C:\PrismCloud\PrismCloud.StoreService.exe) must be added as a firewall exception to allow for Caller ID functionality. 

Gathering Debug Logs

Continuous logging should be enabled for all new Cloud setups going forward. As of right now, the most effective way to pull logs is to manually copy the log files from each computer. The log files are located on all machines at C:\PrismCloud\logs. If you are pulling logs from the Manager computer, you may need to stop the PrismCloud.StoreService, copy and save off the logs to the desktop, then reenable the PrismCloud.StoreService.