Registry Job Progress Viewer (sys-viewer-vjbprgrss)


Registry entry for controlling the order of the line data in the Job Progress Viewer.

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 Fields:

Id:   sys-viewer-vjbprgrss

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.

Control Order of Child Lines

Setting Key: OrderBy Setting Value: list of column names

If this registry option is not implemented, the system will use the default ordering as follows:

 jbbllngitm_rprt_sqnce, jbcstcde_id, jbbllngitm_id, jbcstctgry_type, jbcstctgry_id, jbcstcde_nme

This option enables you to override the default line order. The re-ordering is restricted to the fields named above in the default example.  As shown in following example, it's not necessary to include all the fields.


Setting Key: OrderBy Setting Value: jbcstctgry_id, jbcstcde_id, jbbllngitm_id

 Option to Allow >100% Complete

By default when Actual + Committed equals or exceeds existing Projected Cost, then the Over/Under adjustment is "forced" to bring the projection in line with Actual (Actual + Committed becomes the projection line IS 100% Complete): the following message will appear when a Job with this criteria is accessed:

One or more lines required adjustments to prevent Actual Costs
from exceeding Projected Costs.  If you exit this viewer without
saving, these adjustments will be discarded and will not appear
on subsequently produced job reports.

There may be cases when the Over/Under adjustment should not be forced: for example, assume that a budget line has more actual cost than budgeted, but revising the "projected costs" to the higher value is NOT desired. Perhaps there is material on site that is expected to be returned, vendor credit or rebates expected to be realized in the future, etc.  This new registry allows the system to reflect >100% complete with a negative CostToComplete "projection".  An additional option allows the user to control the message which appears on the new Messages column on the Job Progress Viewer child tab.

NOTE: The system will NOT automatically calculate Over/Under Adjustments for you when this registry is in effect!

Id: sys-viewer-vjbprgrss

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

This option enables the option to permit >100% complete.

Setting Key: ActualExceedsProjectedMessage   Setting Value: message

This registry allows the default message (Actual > Projected) to be customized.

For example:

Setting Key: ActualExceedsProjectedMessage  
Setting Value: WARNING: Actual > Projected

Custom PM WorkBench

Certain Custom PM Workbench analytics depend on knowing which of a job's Cost Codes is designated as the 'Fee Code'. This analytic uses the following registry to determine which of the Cost Code User fields is being used (typically the User4 field).

Id: sys-viewer-vjbprgrss

Setting Key: LumpSumUsrFldNmbr   Setting Value: 4   (1,2 or 3 are also permitted)

In this case, the Job Cost User User4 field should be set to Y if it is designated as the 'Fee Code' record or N if it is not.