Registry Job and Job Cloning (sys-viewer-vjb)

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.


Important Note on Registry Options:
Registry options specified in sys-viewer-vjb will also impact the Project Manager Workbench unless overridden by that option in sys-viewer-vjbpm. See Registry Project Manager Workbench for details.

Job Id Auto-Sequencing:
Registry entries are available to generate auto-sequenced Job Id's: please consult your support representative for details.

Related Registry Entries:

By default, data entry in the State / Province address field is limited to the official abbreviations of the US States and Canadian Provinces. See the State / Province Field Validation Registry if you need to add to or change the list of valid State / Province codes.

Global Setting for Alternate Prevailing Wage Calculations (NY)

Registry to Prevent Selection of Completed Cost Codes / Billing Items

Refine Job Cost Calculation for Labor

Important Fields

Registry Id: sys-viewer-vjb

See the Standard Registry section in Registry Viewer for additional Registry Id formats to allow entries for specific Users, Branches, Security, or User Groups to override the main entry.

Set Cloned Job's Branch from Site instead of Job  

By default,when a Job is cloned via the Clone Job button in the Job record, the new Job's Branch Id defaults from the Job (or Job Template) it was cloned from.  If the following registry is enabled, the new Job's Branch will be derived from the Site selected in the Clone Job wizard.

Registry Id: sys-viewer-vjb
Setting Key: UseCloneSiteBranchForClonedJob   Setting Value: true (default false)

Prevent Copy From Client Button from Setting Job's Sales Tax Group from Client

The Job Viewer's Copy From Client button has been changed so that the Sales Tax Group, Service Zone and Branch will be set from the Zipcode table (if enabled). For Commercial / Industrial Jobs, this is not desirable. The following registry changes default behavior so that only Client Address fields are set when Job viewer's Copy From Client button is clicked.

Registry Id: sys-viewer-vjb

Setting Key: JustSetAddressFromClient    Setting Value: true     (default false)

Registry for Small Jobs Processing Modification to use Job Date Completed

This enhancement modifies way Small Jobs processing is handled. Instead of using the Job Date Closed as the trigger date for Small Jobs revenue recognition, the Date Completed will be used instead. The Job's Date Completed field is implemented via the v.cus file as a special, non-database field that is used to update a Job User field (specified via registry), ensuring that the Job User field is set to the correct date format.  Note that a revised v.cus file is required to support this functionality.

In addition to the customized v.cus file with the Job Date Completed, the following registry is also required to define the Job User field used to sort the Date Completed.

Registry Id: sys-viewer-vjb

Setting Key: DateCompletedUserField   Setting Value: 4

The following validation has been added when changing the new Job Date Completed field:

Change from Original Blank Date To New Non-Blank Date (OK)

Change from Original Non-Blank Date to New Non-Blank Date within same Accounting Period (OK)

If New Job Date Completed NOT in same Accounting Period as Original Date Completed:

If Non-Reversing JC EOM Entries found for Original Accounting Period (ERROR)

If Non-Reversing JC EOM Entries NOT found for Original Accounting Period and New Job Date Completed is blank (OK)

If Non-Reversing JC EOM Entries found for Date >= New Job Date Completed (ERROR)

Set Cost Code and Billing Item Date Completed when Job Closed

If the following registry is set, when the user sets the Date Closed in the Job record, a prompt will appear:

"Would you like to close all Job Cost Codes and Job Billing Items?"

If the user clicks Yes, if the Date Completed in the Job's Cost Codes and Billing Items is blank, it will be set to the Date Closed in the Job record. Note that clearly the Job's Date Closed will NOT clear the Date Completed in the Job Cost Codes and Billing Items.  

Registry Id: sys-viewer-vjb

Setting Key: SetCCBICompletedOnClose   Setting Value: true or false  (default is false)

Allow PM Billing and Inspection Schedules to be Cloned

By default, when new Site and Equipment records are created, the Site PM Billing and Equipment PM Scheduling tables will not be cloned from the originals. This registry entry enables to override the default and clone the Equipment PM and/or Site Billing Schedules.

Registry Id: sys-viewer-vjb

Setting Key: ClonePMBillingSchedule SettingValue: true

Setting Key: ClonePMInspectionSchedule SettingValue: true

Allow Cloning From Templates Only

When this registry option is set, cloning (using the Job record’s Clone Job button) will only be allowed from template jobs.

Registry Id: sys-viewer-vjb

Setting Key: CloneFromTemplatesOnly  Setting Value: true

Job Clone Option to Require Existing Client, Site

The Job viewer's Clone function verifies that the user has Add privileges or they can't create Client / Site records. The following registry option may be used to further restrict the ability to add Clients / Sites via the clone.

Registry Id: sys-viewer-vjb

Setting Key: CloneRequireExistingSite    Setting Value: true  (default is false)

Setting Key: CloneRequireExistingClient   Setting Value: true (default is false)

Clone Job’s Equipment if an Existing Site is Selected

Default behavior is to only clone equipment if a Site is NOT selected in the Clone Wizard form. This registry option changes the behavior to clone a job’s equipment with the Clone Job button if an existing Site is selected. Note that, if this registry setting is in effect, equipment Id’s will only be created if they do not already belong to the existing site.

Registry Id: sys-viewer-vjb

Setting Key: CloneJobEquipmentExistingSite Setting Value: true

Default is false.


If the Site has Equipment Id GIZMO, and so does the Job you are cloning from, the existing site’s equipment record GIZMO will be retained.

If the Site has only an Equipment Id WIDGET, and the Job you are cloning from has equipment Id GIZMO, when the job is cloned the existing site will now have two equipment records: GIZMO and WIDGET.

Allow Change to Job with Retainage

In this release, if Retainage has been billed the Client Id cannot be changed.  This validation can be changed from an error to a warning with the following registry setting:

Registry Id: sys-viewer-vjb

Setting Key: AllowChangeToJobClient Setting Value: true

Default Budget Tab Effective Date

This registry option allows you to default the Effective Date that will be used when Budget entries are written to Job History from this tab. This registry also impacts the Project Manager's Workbench.

Registry Id: sys-viewer-vjb

Setting Key: BudgetEffectiveDate

Setting Value:   none or currentdate or DateOpened (Default none)

none – use the user-entered date from the Job budget Effective date field

currentdate – use today’s date from system date

DateOpened – use the date from Job’s Date Opened

Registry to Show Employee Name on the Job Revenues Tab

In this release, the Employee Name no longer appears on the Job Revenues tab to prevent sensitive pay information from being displayed. The following registry entry may be enabled so that the user or users eligible to see this information may have access to it.

Registry Id: sys-viewer-vjb-branchid-userid or  sys-viewer-vjb--userid

Setting Key: ShowEmployeeNames Setting Value: true

 Registry To Prevent Changing Overhead Flag for Jobs With Non-Zero History

By default, the user is warned when changing the Overhead? flag on a Job which has non-zero Job History based on the JCH Hours, Quantity, Total Cost and Total Revenue fields.

The following registry changes the warning to an error to prevent the user from changing the Overhead? flag for Jobs with non-zero history.

Registry Id: sys-viewer-vjb

Setting Key: ValidateOverheadChange    Setting Value: error or warning (default)

WBS (Work Breakdown Structure Registries)

Also see Registry WBS .

Disable Job Record Budget Reversals for WBS Import

This option should ONLY be implemented if the WBS Configurator/Import process is being used to import Job Budget Entry child lines.  Without this registry setting, the Budget Entry child posts like other 'journals'.  It makes new plus entries and offsets them with reversing entries to achieve the desired 'net effect'. With this registry setting, all Budget Entry Job History is completely replaced (deleted) by new lines posted from the child rows.

Registry Id: sys-viewer-vjb

Setting Key: NoReversing   Setting Value: true {Default is false}

Specify the Import WBS Cost Code GL Income Account

This registry is required for WBS imports.

Registry Id: sys-viewer-vjb

Setting Key: ImportWBSGLAccount  Setting Value: GLAccountId

This field should specify the value to be set in the Cost Code's GL Income Account.

WBS Import Registry to Specify Fee Code

The Job viewer's WBS Import process also needs to know which of the specific Cost Codes should be marked as the 'Fee Code'.  The following registry is used to enable this functionality.

Id: sys-viewer-vjb

Setting Key: ImportWBSFeeCodeCodeId   Setting Value:  JobCostCodeId

When BOTH this registry and the sys-viewer-vjbprgrss registry's LumpSumUsrFldNmbr options are present, the selected user-definable field will be marked with either a Y or N to indicate which of the cost codes is the 'Fee Code'.

Also see Registry WBS (sys-behavior) to Implement Optional Job Cost Burdening by Cost Code (Fab Shop Burden).

Registry to Set Job Cost Code's GL Entity from Discipline Id During WBS Import

When a new Job Cost Code is created in during the WBS Import, the GL Entity is set by default from the Job Entity on the Job's Financial tab. The following registry may be used to specify that the Cost Code's GL Entity instead comes from the Discipline Id specified in the Import.  

Id: sys-viewer-vjb

Setting Key: ForWBSGetEntityFromDiscipline    Setting Value: true  (default is false)

Note that if the WBS import is being used to update existing Job Cost Codes, the GL Entity will be left alone, regardless of whether or not this registry is set.

Enable WO Creator Tab for Job Scheduling

The following registry entry is required to make the new WO Creator tab (Scheduler child table) visible in the Job Viewer. Also see the Start Create Job Scheduler WOs Registry .

Id: sys-viewer-vjb

Setting Key:  ShowJobScheduler  Setting Value: true  (default is false)

Limit Techs Allowed on Job's WO Creator Tab

Id: sys-viewer-vjb

Setting Key:  JobCreatorTechnicianFilter   Setting Value: listoftechs

The Setting Value listoftechs would be replaced by a comma separated string of Technician Ids which are allowed to be entered on the Job's WO Creator tab. This registry may be used to force Work Orders to be created for "techs" representing areas or groups instead of actual Technicians.  Since the Date and Hours on Work Orders created from the WO Creator tab are generally estimates, some users may not wish to immediately assign them to real Techs.