System Settings

March 14, 2014 , by

The Settings page provides following functionalities

Test Center

Pistachio's Test Center section contains a variety of tools to test various aspects of a Pistachio installation. These tools check the validity of Application's configuration.

ID Management

Pistachio contains database tables with and without auto-incrementing primary keys. Tables with primary keys that are not auto-incrementing are usually controlled by Pistachio's ID management capabilities. The platform contains a database table called ID_Table, which maintains a list of other database tables, their primary keys, and each one's last issued ID value.

On the front screen of the ID Management tool, there's a grid that displays each table managed by the ID Table, the highest primary key value in the actual database table, and the value stored in the ID table. In all circumstances, the Value In the ID Table should never be less than the Highest Value in Table. This type of ID mis-sync can occur if the actual database table has an influx of new records that were not handled by Pistachio directly.

At the bottom of the grid is a link titled Correct Under-Valued IDs. This link, when clicked, will insure the ID for each Value In the ID Table is not lower than the primary key value in the actual database table. As a safety precaution, this link should be clicked after every data migration involving a database that the Pistachio installation is configured to work with.

The second link, Correct All IDs, completely equalizes the two values, allowing the Value in ID Table ID to be reduced if necessary. While useful during the development stages of a project, this link should be used with care, as it might cause IDs to be reused within Pistachio if records in database tables being managed are deleted prior to the link being clicked.

Working with tables outside the Pistachio database

For each database table record in the ID Management tool, an Optional Fully Qualified Table Name can be specified. This field is necessary for managing the IDs of tables located in databases other than the Pistachio database. Below are examples of fully qualified table names.

databasename.owner.tablename
servername.databasename.owner.tablename

History Log

For all significant actions, Pistachio creates a history log entry cataloging the changes.

History log entries are created when records are added, edited, or deleted. For adds and edits, a summary of the field changes is contained in the "Comments" field.

Security Log

When users try to authenticate into Pistachio, their attempt is logged into the Sec_Log database table.
Pistachio records "SUCCESSFUL LOGIN" records upon the success of an automatic authentication via windows Authentication.

Encryption

This screen lets you resets the shared encryption key for this Pistachio installation. It will re-encrypt all of the Data Source connection strings, as well as update the datadecryptionkey setting stored in the administrative portal's web.config file. This setting will need to be added to the web.config file of each SharePoint installation that utilizes the Pistachio Web Part.

Environment

This screen lets you manage the environments Pistachio is running on. Environments are explained in detail here.