System Parameters Overview

Simona Riftin

Updated 08 June 2026 12:34

System Administration

System parameters overview

What system parameters are, why they matter, and how they should be managed in Jobpac.

Overview

Jobpac uses a large set of system parameters to control how the software behaves for each organisation. This article explains what system parameters are, why they matter, and how they should be managed.

What are system parameters

System parameters are configuration settings that determine how different functions in Jobpac operate. They allow the same software to support a wide range of business structures, processes and statutory requirements.

Examples of what system parameters can influence:

How periods and dates are handled
How transactions flow between modules
Which options are available in certain screens
How reporting and posting rules behave

Because system parameters work behind the scenes, users often notice their impact without seeing the settings themselves.

How system parameters are organised

Jobpac includes a very large number of parameters spread across functional areas such as projects, finance, payroll and reporting. Each parameter has:

Name or code	Used in configuration to identify the parameter.
Valid values	One or more values that control the behaviour of that function.
Scope	Some parameters are global across all WorkIDs. Others affect only certain modules or environments depending on how the system is configured.

Who manages system parameters

Because system parameters can significantly change how Jobpac works, they are usually managed by experienced administrators or consultants. Typical responsibilities include:

Setting parameters during implementation and major changes
Reviewing parameter settings when business requirements change
Testing the impact of parameter changes in a non-production environment
Documenting parameter decisions for future reference

Users without specific responsibility for system configuration should not change parameters without guidance.

Examples of parameter-driven behaviour

System parameters can affect many aspects of daily work in Jobpac. For example, parameters can:

Control whether certain validation checks are applied during data entry
Define how intercompany postings are generated
Influence how cost or revenue information appears in enquiries and reports
Determine how certain processes behave at period end

If Jobpac behaves differently between environments or client sites, system parameters are often part of the reason.

Good practices for managing system parameters

Limit who can change parameters to a small group of knowledgeable administrators or consultants.
Test changes in a training or test environment before applying them to production.
Document the purpose and chosen value for key parameters, especially those with broad impact.
Review parameter settings when business processes, regulatory requirements or module usage change.

What this means for everyday users

Everyday Jobpac users do not usually need to work directly with system parameters, but they are affected by them. System parameters help ensure that:

✓ Screens, options and workflows match your organisation's processes

✓ Data entry is validated in a way that supports quality and compliance

✓ Project and financial information is captured consistently over time

If something in Jobpac appears to behave differently than expected, it may be due to a parameter setting. Your administrator or BuildingPoint Jobpac consultant can investigate and explain the configuration.