Simplicity F.A.Q  

Not without creating an exception. All of the communication with our server is through Web services (port 80) at simplicity.kassonkeller.com (IP address 24.97.36.201). If you are behind a proxy server, an exception must be made for traffic to / from that address.

There is no difference between Kas-Kel Simplicity, Kas-Kel Simplicity Plus, and Kas-Kel Paradigm Plus. Your program / directory may be named differently depending on which installer was originally used, but each program has been automatically updated to the latest version.

At this point, this should be considered a bug in Simplicity causing it to be unable to properly deal with high resolution screens. We are eagerly awaiting a fix from the software vendor. There is an option to magnify text in recent versions of Windows, but it does not work correctly with Simplicity. Unfortunately at this time, the only really viable workaround is to change your screen resolution to a lower value.

To access quotes which were not created on your local machine, you will have to import them from the server. Here is what you want to do:

1. Click Find Quote in the main toolbar

2. Enter search criteria

• If you are looking for a specific quote, use the quote number. You can also look up by Project Name or Quote Name, among other ways. For something like a Project Name or Quote Name, you can use * as a wildcard. For example, searching the Project Name for *river* would get you quotes with a Project Name which contains the word “river” anywhere inside it. Combining search criteria can be powerful. You could dig up all quotes created by a specific user within the last three months which are still Active (not yet ordered), for example.

3. Hit Find Now

• A list of matching quotes will appear below.

4. Select one or more quotes

• You can import multiple quotes at a time by highlighting more than one (CTRL + click a quote to highlight it in addition to the current selection, or SHIFT + click a quote to select a range).

5. Hit Open

• Simplicity will start importing the selected quotes. It will open the first two it downloads. If you had more than two selected, it will continue to import the others, but it won’t open more than two at once. When it has finished downloading all of the selected quotes, they will all show up in the Projects pane along the left edge of the interface. If you are importing a large number of quotes, it could take several minutes before they show up.

No, you can not drag a quote from one project and drop it into another. Be warned that the Simplicity user interface makes it look like this works when it really does not.

If you drag a quote from one project to another, save changes, and close the program, it will still be in the original project when you re-open the program.

To actually move a quote from one project to another, you must edit the quote, go to the “Sold to” tab, and change the “Project Name” field to be the same as the project to which you wish to move the quote.

The custom logo image is taken from a file named “dealerlogo.bmp”. It is an image file saved as a “Bitmap” (or “BMP”) image type.

Place such a file in the Simplicity Plus directory to use a custom logo on the paperwork. Just make sure the image is in the proper image format, is named “dealerlogo.bmp”, and is placed in the Simplicity Plus directory (see “Where is the Simplicity Plus Directory on My Computer?“).

The address info is taken from a file named “dealerinfo.txt”. (To download this file right click on the following link and save it as dealerinfo.txt: dealerinfo.txt)

If you look at it, it has six lines to hold different pieces of information (a line for the name, a line for the street address, a line for the city/state/zip, etc.). Simply fill out that information (put your information to the right side of the ‘=’ characters).

Do not remove the ‘=’ characters or alter the words to the left of the ‘=’ characters (or the custom information won’t show). Put your “dealerinfo.txt” file in the Simplicity Plus directory (see “Where is the Simplicity Plus Directory on My Computer?“).

WTS Base Camp is a program that WTS provides to update one or multiple Paradigm installations during off-hours so that users will not have to wait for updates to be applied when they log in. It does this by automatically detecting all Paradigm client installations on the hard drive and letting the administrator of the system schedule Autoloader jobs to run them long enough to receive updates at the time most convenient for the user.

WTS Base Camp, however, mistakenly detects Kas-Kel Simplicity as a server application instead of a client application because of the existence of the file “ServerManifest.xml” in the SimplicityPlus directory, thus refusing to try to update it. This can easily be remedied by deleting or renaming the “ServerManifest.xml” file in the SimplicityPlus directory (see “Where is the SimplicityPlus Directory on My Computer?”).

The SimplicityPlus directory is usually in one of the following locations (depending on your operating system and the installer that was originally used):

C:\Kas~Kel\SimplicityPlus


C:\Program Files (x86)\KasKel\KasKelParadigmPlus


C:\Program Files\KasKel\KasKelParadigmPlus

When SimplicityPlus is launched via terminal server, there are some differences in the way the program works:

• First, the program will not update itself when a client logs in. This is because there could be other users running at the same time, and the updating processes would need exclusive access to the application’s files to update them appropriately. Because of this, the process of updating the server’s installation must be done server-side, and it should be done when nobody is logged in via terminal server. The typical recommendation is to setup a Scheduled Task to run at some point at night.

• Second, each user logged in via terminal server results in the creation of some database files somewhere on the server which contain the data specific to each client logging in. If multiple users were using the same database files, weird things could happen. You can control the location of these files with some configuration (discussed later on).

Setting up the server to update the application:

On the server, get to the Control Panel, go to Administrative Tools, and open Scheduled Tasks (A.K.A. Task Scheduler). You want the scheduled task to target Autoloader.exe which is in the SimplicityPlus directory. We would suggest running it sometime at night. You’ll have to provide Windows credentials with which to run the task. You should run this as an administrator (or any user which has full permissions to the files within SimplicityPlus). When you are done creating the task, you should go to its properties and edit the line which shows the target. You will have to add some arguments / parameters. You need to change it from something like:

“C:\Kas~Kel\SimplicityPlus\Autoloader.exe”

to something like:

“C:\Kas~Kel\SimplicityPlus\Autoloader.exe” username password None 1 --scheduledtask

The “username” and “password” should be SimplicityPlus credentials which will be used when it logs into the server for updates. There should be exactly one space between each item in that list of arguments. Capitalization is important on the last few items. “None” really does need a capital ‘N’.

Setting up the configuration file to control the user database creation location and auto-logoff-for-update settings:

There is a way to setup the program to auto-log-off connected users before the server runs its updates and to control the location for user database files. You need to do some configuration file setup on the server-side to accomplish this. The file is named TerminalServerPaths.xml. You can find an example file here. The settings in this file will not work as is and need to be changed to appropriate values.

• TSDatabasePath: This is the server’s path in which to store the database files which are generated for each user logged in remotely. Do not place this directory anywhere within the SimplicityPlus folder.

• portfilespath: Simplicity will not allow the users to initiate the auto-update stuff during login, so the updates must be scheduled to run on the server. Simplicity can warn and auto-logout the clients when the time comes to run the updates on the server. This setting is a path in which files will be stored to allow the server to warn the clients of the impending auto-logoff.

• forcetsshutdown: This setting controls whether or not the server automatically logs off the clients when the updates are to be run. This should be either “true” or “false”.

• minutesfromwarningtoshutdown: This numeric value is the number of minutes granted to logged-in clients to heed the auto-logoff warning before the auto-logoff actually occurs.

• emailto: If something goes wrong on the server during the update process, this is the e-mail address to which to send error notifications / descriptions.

• emailfrom: Error e-mails will appear to be sent from this address.

• emailserver: This is the SMTP server to use while sending the e-mail.Fill out the appropriate values. You will then need to put a copy of this XML file in the following six locations:
  1. SimplicityPlus
  2. SimplicityPlus\Configurators\LP\LP1
  3. SimplicityPlus\Configurators\ML\ML1
  4. SimplicityPlus\Configurators\NP\NP1
  5. SimplicityPlus\Configurators\PP\PP1
  6. SimplicityPlus\Configurators\PT\PT1

Please follow This Link: .Net Framewark 2.o

Please follow This Link: Simplicity Config Changer

Please follow This Link: Simplicity Shortcut Creator