User Registry Tab Entries


These fields may be used to add to / override sys-ffv-global-settings for this User. Since these settings are loaded when the user logs on, he or she must log on after User Registry changes are made to see them in effect.

DBAnalytics: User registry entries also override entries in the sys-dashboard registry setting.

Testing Your Registry Entries
The system does not verify the validity of registry entries. Be sure to test your registry entries after completing them to verify that they are functioning correctly.

Setting Values are Uppercase-Lowercase Sensitive:
The Setting Value is case-sensitive: be sure that you enter the value exactly as specified in the documentation. If the documentation specifies a value of true, do NOT enter True or TRUE.

Related Registry Options:

See Registry Global Settings (sys-ffv-global-settings) for additional options that may be used on this tab.

User Registry Option to Specify Maximum Dollar Amount of Released PO’s

Key: maxpoamount Value: limit in dollars

If this User Registry entry not implemented (and the User is flagged as a Purchasing Agent), the user is not limited to the dollar amount of a PO that he can save as Released.

If this User Registry is implemented for a User flagged as a Purchasing agent, the PO cannot be released if the PO amount exceeds this field; the PO must be saved as Unreleased. A User (who is also a Purchase Agent) with a higher maxpoamount can edit and release the PO in this situation.

Example: To specify a $600 maximum release PO limit for this User:

User Registry: Key: maxpoamount Value: 600

NOTE: the dollar amount of the released PO may also be limited by the PO Limit per WO found in the Vendor record.

Credit Manager Rights

If the Credit Manager? Boolean is checked in the User upper setting, the User is considered a Credit Manager for ALL order types. In this release, the User Registry tab settings allows COP or Work Order Credit Manager rights to be specified as follows:

If the Credit Manager flag is unchecked but the User Registry Tab has the following setting, then the user is allowed to approve credit on COP orders.

Key: CreditManagerCOP Value: true

Note: For Client Orders, the user should enter all lines BEFORE flagging the Credit Approved box on the AR tab since the COP Credit Approval is for the specific amount entered on the order.

If the Credit Manager flag is unchecked but the User Registry Tab record has the following setting, then the user is allowed to approve credit on work orders

Setting Key: CreditManagerWO Value: true

CRMAnywhere Gmail Calendar Interface

See Registry CRM Gmail Calendar for setting up an interface between CRMAnywhere and a Gmail calendar.

DB Analytics Registry Options

Except for StartDashboard, the following options override in those found in Registry DB Analytics Dashboard .

Start DB Analytics when Launching SAM Pro

Key: StartDashboard Value: true

This option launches the user’s DB Analytics Dashboard and logs them in when they log onto SAM Pro. The user will be automatically logged on with his/her SAM Pro password. If this option is not implemented, the user may start DB Analytics from SAM Pro by using the Starter function Start Dashboard Helper.

Specify Web Server Port by User for DB Analytics

Key: DashboardWebServerPort Value: NNNN

If multiple users running from the same terminal server will be accessing DB Analytics from an active SAM Pro session, each user on the server must have a unique web server port value on the server machine.

Enter a unique four digit port number for this user. It must be different from the WebServerPort in the sys-dashboard registry entry, as well as the other DashboardWebServerPort settings in User’s record.

The setting values for these options will depend on your system’s implementation – consult with your support rep for detail.

Note: Most registry options defined in sys-dashboard may be overridden in the User Registry Tab by pre-pending the Key Value with Dashboard. For example:

In sys-dashboard Setting Key is WebServerPort

In User Registry, Key is DashboardWebServerPort

Specify DBAnalytics Browser

Setting Key: DashboardBrowserName Setting Value: executable file

This setting overrides the default browser specified in the sys-dashboard registry. Note that DB Analytics users must have a current version of the browser specified in this setting.

Example: Chrome (preferred browser for DB Analytics)

Setting Key: DashboardBrowserName Setting Value: chrome.exe

Example: Firefox

Setting Key: DashBoardBrowserName Setting Value: firefox.exe

Example: Internet Explorer

Setting Key: DashboardBrowserName Setting Value: iexplore.exe

Enable Post History Processing (for ADP users)

The Post History button (in the Payroll Period) should only be enabled for payroll service users who export data, but do not print and post checks.  If you use the Post History function, you cannot print a paycheck for employees impacted by the post for the selected Payroll Period.

The new process replaces the print/post check functionality to enable use of certain payroll reports that present valid information such as workers compensation. When run, it sets the Payroll History Date Effective to the Last Check Date from the Payroll Period, and the Source Journal to registry setting described below or ‘ADP Export’ if the registry is not present.

User Registry Tab:

Key: OkToPostPRHistory                 Value: true

This functionality may be implemented for specific users via the User record’s Registry tab.

This functionality may alternately be implemented for all users with access to the Payroll Period:

Registry Id: sys-viewer-vpyrllprd

Setting Key: PostSourceDescription             Setting Value: Description

This registry option provides a description for Payroll History entries generated by clicking the Post History button. If this registry entry is not enabled, the default value of ‘ADP Export’ will be written to Payroll History.

Setting Key: OkToPostPRHistory                   Setting Value: true

This functionality may be enabled for all users with access to the Payroll Period by implementing this registry entry. The preferred method is to implement it for specific users via the User record’s Registry tab.

User Registry to Filter Which Employees a Foreman in TimeAnywhere 2.0 Can Manage

On the Registry tab of the Foreman’s User record, indicate the fields you would like to use to narrow down the number of Techs a Foreman can view from the field. Use any of the following fields in the Key column:



Value: The value or list of values in the key field of Employees the Foreman should be able to see

The Value column should list the field values of the Techs your Foreman will be able to see. Field values should be separated by commas (i.e. East,Wsest).

If a Foreman, for example, has a customized field placing him in the East district, he will be able to enter information for himself even if his User registry is set to West. For the Foreman to be able to enter information for other Techs in the East and West districts, his User registry should list both- East,West. Note that a Foreman will always be able to enter time for himself even if his value is not included in the User Registry.

Default Location/Tax Group for DBSellpoint

The Sales Tax Group on the default Client Site's COP tab is the one for the brick and mortar DBSellpoint location the DBSellpoint User is stationed at. This Sales Tax Group will be used for ALL DBSellpoint transactions. The default Site must be specified in the User's Registry tab for each DBSellpoint User.

Key:  defaultSite   Value: Site Id