nService3 change history

How do you find out which release you have?

Click the “Powered by nService” link at the low left corner of any page on your nService website.

How to upgrade from one release of nService to another

  1. Go to IIS manager to pause the nService3 application pool.
  2. Download the new release and unzip it to temporary folder. A new subfolder called “nService3” should be created automatically under this temporary folder.
  3. Copy the entire folder of nService3 to \Inetpub\wwwroot\ to overwrite the old one. If Windows complains about not being able to overwrite bin\nServiceHelper.dll, delete this DLL from the temporary folder and retry the folder copy operation.
  4. Review the change history and apply the database changes directly on the nService3 database using SQL Server Enterprise Manager or SQL Server Management Studio.

Version 3.5 (January 10, 2007)

  1. Added ns3_call table to keep track of phone calls.

    CREATE TABLE ns3_call
    (
        call_id         INT PRIMARY KEY,
        call_caller     INT NULL REFERENCES ns3_user(usr_id),
        call_receiver   INT NULL REFERENCES ns3_user(usr_id),
        call_start      DATETIME NOT NULL DEFAULT getdate(),
        call_end        DATETIME NULL,
        call_status     TINYINT NOT NULL DEFAULT 1,
        call_last_sr    INT NULL REFERENCES ns3_service_request(sr_id),
        call_note       VARCHAR(250) NULL,
        call_deleted    BIT NOT NULL DEFAULT 0
    )
    GO

  2. Added ns3_sr_note.srn_call_id to link the service request history to phone calls.

    srn_call_id INT NULL REFERENCES ns3_call(call_id),

  3. Added phone call handling and management module.
  4. Added localization support. You can now translate nService to your language.

Version 3.4 (December 22, 2006)

  1. Added ns3_req_query.rq_ref_date and ns3_req_query.rq_usr_grp to support Age30x4 reports and report users respectively. Please apply the same change to your database.

    rq_ref_date DATETIME NULL,
    rq_usr_grp INT NULL REFERENCES ns3_group(grp_id),

  2. Renamed ns3_service.srv_tech_grp to ns3_service.srv_tech1_grp. Added ns3_service.srv_tech2_grp.

    srv_tech1_grp INT NOT NULL REFERENCES ns3_group(grp_id),
    srv_tech2_grp INT NOT NULL REFERENCES ns3_group(grp_id),

  3. Added the report module and two-tier technician groups support for services and request escalation.

Version 3.3 (December 16, 2006)

  1. Added ns3_service.srv_inherit_grp and changed the srv_*_grp fields to be required. When you apply changes to the database, you need to add the srv_inherit_grp field to the database using your database’s management tool first. Go back to the website to edit and save the service root record and the ones that have its own group settings. This populates the groups of the child services. Then go back to your database to change the srv_*_grp fields. (Don’t worry about the REFERENCES part. Just uncheck the “allow null” boxes in Enterprise Manager or SQL Server Management Studio.) Otherwise SQL Server won’t let you because there may be existing data that have NULL srv_*_grp fields.

    srv_user_grp     INT NOT NULL REFERENCES ns3_group(grp_id),
    srv_tech_grp     INT NOT NULL REFERENCES ns3_group(grp_id),
    srv_admin_grp    INT NOT NULL REFERENCES ns3_group(grp_id),
    srv_inherit_grp  BIT NOT NULL DEFAULT 1,

  2. Added ns3_req_query.rq_type. Replace ns3_req_query.rq_group_ with the last 5 columns below.

    rq_type             TINYINT NOT NULL DEFAULT 1,
    rq_group_by1        VARCHAR(30) NULL,
    rq_group_by1_type   TINYINT NOT NULL DEFAULT 3,
    rq_group_by2        VARCHAR(30) NULL,
    rq_group_by2_type   TINYINT NOT NULL DEFAULT 3,
    rq_top_group        TINYINT NOT NULL DEFAULT 0,

  3. Added the capability to import from multiple email addresses

Version 3.2 (December 10, 2006)

  1. Added ns3_kbase.kb_inherit_grp and changed the kb_*_grp fields to be required. When you apply changes to the database, you need to add the kb_inherit_grp field to the database using your database’s management tool first. Go back to the website to edit and save the kb root record and the ones that have its own group settings. This populates the groups of the child KB categories. Then go back to your database to change the kb_*_grp fields. (Don’t worry about the REFERENCES part. Just uncheck the “allow null” boxes in Enterprise Manager or SQL Server Management Studio.) Otherwise SQL Server won’t let you because there may be existing data that have NULL kb_*_grp fields.

    kb_user_grp     INT NOT NULL REFERENCES ns3_group(grp_id),
    kb_tech_grp     INT NOT NULL REFERENCES ns3_group(grp_id),
    kb_admin_grp    INT NOT NULL REFERENCES ns3_group(grp_id),
    kb_inherit_grp  BIT NOT NULL DEFAULT 1,

  2. Added the announcement module and discussion forum module.

Version 3.1 (December 4, 2006)

 

  1. Added database column: “ns3_service_request.sr_escalated_on DATETIME NULL”.
  2. Added database column: “ns3_req_query.rq_submitter_site INT NULL”.
  3. Added database column: “ns3_req_query.rq_group_by VARCHAR(30) NULL”.
  4. Added database column: “ns3_req_query.rq_row_per_page SMALLINT NOT NULL DEFAULT 15”.
  5. Changed database column ns3_req_query.rq_max_row from TINYINT to SMALLINT.
  6. Reworked service request management pages. Added group by column and order by columns on service request query page. Deleted “Service requests submitted by me” and “Service requests assigned to me”. Users can create these queries themselves by using the more flexible “Find service requests” command.

Version 3.0 (November 25, 2006)

First release of nService3.