|
|
|
|
|
 |
 |
 |
|
As you can see, 11 files from different parts of the world come together to make PayGo. To find out what they bring to the table and how you might be able to harness them, read the information below.
PayGo SP is designed using a data separation model, which means that the data is separate from the interface. This is nice, because as we update our features, you don't have to go through a data update process (most of the time).
Also - this model allows for the OpenSorta™ concept. Because all of your data is stored in one spot and you have access to all of your data (with the proper access priviledges) from an "outside" database, this means that YOU can build your own solutions around PayGo SP!
As an example; we use PayGo SP to sell PayGo SP! But we have a few special needs that are unique. We've been able to build a support and sales lead tracking solution that is fully integrated with our PayGo SP customer data! So, if someone has submitted a help request, we can track it on our custom designed help request database, and while in that database, we can read, edit or create information that is stored directly in the paygo_data.cji file!
Basically, OpenSorta allows us to concentrate on the basics of business, and you can work on the uniqueness of your (or your client's) business.
The Cast of PayGo SP Files!
Each file has a special meaning. Here are the files that you'll be interested in... |
|
 |
 |
 |
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
| |
| |
|
| |
| |
|
|