System Parameters 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 in Jobpac

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

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

• a name or code used in configuration
• one or more valid values that control behaviour
• a defined impact on how a function operates

Some parameters are global across all WorkIDs, while others may affect only certain modules or specific environments, depending on how your 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

Often, if you see Jobpac behaving differently between environments or client sites, system parameters are part of the reason.

Good practices for managing system parameters

To keep Jobpac stable and predictable, parameters should be managed carefully.

Good practices include:

• 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

This approach reduces the chance of unexpected behaviour and makes it easier to support and troubleshoot the system over time.

What system parameters mean 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. In that case, your administrator or BuildingPoint Jobpac consultant can investigate and explain the configuration.