Skip to content

Conditions for Future Development and Support Requests

Preconditions for Support

Effective support depends on the following being in place:

  • The client maintains a stable, supported hosting environment (Windows Server, IIS, .NET 4.8, SQL Server).
  • The client maintains current, verified database backups.
  • Any third-party changes to the codebase, database schema, or server configuration are disclosed when requesting assistance. Undisclosed changes may increase diagnostic time billed to the client.
  • The issue or change is described with sufficient detail: affected screen or module, steps to reproduce, error messages, and [Ref: guid] codes where available.

Request Process

  1. Document the issue: screen, module, user affected, error message (including [Ref: guid] if present), and steps to reproduce.
  2. Perform initial checks using the checklists in this documentation.
  3. Submit a written request to the developer via the agreed communication channel.
  4. The Developer will acknowledge the request, assess it, and provide an effort estimate for non-trivial work before commencing.
  5. Work is scheduled based on availability and agreed priority.

Scope Limitations

The Developer is not responsible for:

  • Issues caused by unsupported third-party modifications to the application code, database schema, or infrastructure.
  • Hosting provider outages or network problems outside the application.
  • Issues arising from the client operating the system in a manner inconsistent with this documentation or contrary to agreed practices.
  • Data corruption or data loss caused by client-side processes or direct database manipulation by unauthorised parties.

Change Control

For any significant change (new module, schema change, major UI change):

  1. The client submits a written change request describing the desired outcome.
  2. The Developer performs an impact assessment and provides a cost and effort estimate.
  3. The client approves the estimate before work begins.
  4. Changes are tested in a non-production environment before being deployed to production.
  5. The Developer documents the change in the relevant section of this documentation.

Rapid Application Development Framework Dependency

A proprietary Rapid Application Development Framework was used to develop CONPROSOFT. Significant structural changes to controllers, such as adding fields, regenerating business rules, or creating new views, require the RAD tool held by the Developer. Changes of this nature cannot be made practically by a generic .NET developer without access to the toolset and familiarity with the framework.

This is an important constraint for any future developer taking over the codebase.