Skip to main content

Miscellaneous Mini Guides

📄️ Making merchant credentials unique to business

Some Rossware clients run multiple businesses, each managed by a separate ServiceDesk (SD) setup, but from the same set of computers within the same network. Almost without exception, each such SD instance keeps track of its particular business's underlying data within a folder structure that's particular to that business, so there is never interference (cross-talking, overwriting of data, etc.) between instances for different businesses. Storage or payment gateway merchant credentials, however, is an exception -- because the Virtual Terminal program (VT) is programmed to store such credentials in what's called the Windows System Registry. This is, essentially, a storage place that's specific to each particular Windows-User login (as opposed to any particular folder or business). Because of this method, it's impossible for a station that's running multiple instances of SD to recognize different merchant credentials for different businesses (absent, at least, the expedient as described here).

📄️ Regarding data conversions

Generally speaking, there are three potential categories of information we like to get from whatever system a client prior used, for insertion into ServiceDesk so that, on beginning a new life in ServiceDesk, there is already a context of operational data in place. Each situation varies in regard to what detail of information is available. We here describe what we consider it ideal to obtain. If we can’t obtain each item in every instance, we can usually optimize to work with whatever is available. In some instances we may likewise be able to make beneficial use of further information, not necessarily listed here.