There are two ways of customizing software so that it fits an organization’s specific needs and requirements: configuration & customization.

While the terms are sometimes used interchangeably, we make a clear distinction in that configuration of Interact applications is done during implementation whereby settings and parameters are changed using the Policy Setup. Configuration can be done by consultants, implementation specialists and sometimes clients who have been trained on how to do so.

Customization on the other hand refers to actual changes to the source code of the software and this can only be done by programmers.

Interact HRMS and Interact SSAS are both Policy driven applications, which means that virtually all the behavior of the system depends on the settings defined in the Policy Setup. During the Definition phase of the project, Implementation Consultants will work with the client to fully understand a client’s business rules and obtain all the underlying foundation data which will be used to perform transactions in the system.

In the case of Interact HRMS for example, we will get your organization structure, your job classification, your time & leave policies, your payroll and compensation as well as deduction and tax policies and all other relevant policies that govern how a particular module should function. The system will then be configured to reflect those policies and business rules using the standard configuration options in the application.

Below is an example of a Leave Policy setup partial screen which allows a user to define the specific business rules which relate to a particular Leave Policy.

Like this, Interact HRMS has countless forms where business rules or “policies” can be defined for each and every aspect of the system so that an organization’s unique HR, Payroll, Time/Leave, Benefits, Risk and other requirements are covered with the existing system.

However, since Interact HRMS and Interact SSAS are global products which are sold all over the world and across all industries, there can always be unique requirements which a particular client has that are unique to their business, industry or country, either because of the legislation or changes in legislation or because of local practice.

If the unique outcome required is not available with the existing configuration of functionality, then customization may be required by making changes to the source code.

In order to ensure that you can benefit from all upgrades, continue to benefit from support and ongoing improvements to the product, we only customize by adding new generic functionality to the product which will be an integral part of the product build from then on and continue to be expanded with new releases.

There are many distinct benefits to this approach:

  • all Interact customers use the same product which means support resources are always aware of the details of your build
  • upgrade paths are unaffected by your customizations since they are included in the regular product roadmap
  • customizations are designed in a generic way so they can be used by other clients for similar but not identical purposes
  • because of the underlying architecture and design and the development tools used in Interact products, customization can be done at a much lower cost than what it would cost in other enterprise software environments