FS 311581 Diagnosis Narrative Extended Length: Difference between revisions

From Calidus HUB
(v0.1 - Initial Creation)
 
mNo edit summary
 
Line 6: Line 6:
{{#vardefine:Version|0.1}}
{{#vardefine:Version|0.1}}
{{#vardefine:Date|29th August 2013}}
{{#vardefine:Date|29th August 2013}}
{{#vardefine:Reference|311574 309371-12}}
{{#vardefine:Reference|311581 309371-12}}
{{#vardefine:Year|2013}}
{{#vardefine:Year|2013}}
</div>
</div>

Latest revision as of 15:23, 5 September 2013





Aptean Logo.png







Lanemark

Diagnosis Narrative Extended Length


CALIDUS eSERV

29th August 2013 - 0.1
Reference: FS 311581 309371-12












































Functional Overview

Client Requirement

The Diagnosis field will be extended to allow as many characters as the users desires, rather than be limited to 100 characters.

Solution Overview

The change will be made across the whole product to remove any length restriction from the Diagnosis Narrative field. Additionally, a style will be created for Lanemark, to allow for field labelling in the Android Client to be set as required for the customer. In this case, the label will become "Comments".

Scope

  • These changes will be made in the latest version of the CALIDUS eSERV product only.
  • The changes will be made to the Android eSERV client only.


Set-up

Pre-requisites

Menu Structure

Data

Functional Description

Database and DAL

The database table EPOD_SERVICE should be modified as follows:

  • Change EPL_DIAGNOSIS_NARRATIVE to nvarchar(MAX).

The database should have procedures that use an EPL_DIAGNOSIS_NARRATIVE parameter changed to reflect an unlimited length. This includes but may not be limited to:

  • EPOD_SERVICE_INSERT
  • EPOD_SERVICE_JOB_SEARCH
  • EPOD_SERVICE_JOB_SELECT

The EPOD_SERVICE DAL object should have each parameter function (identified as functions that begin "GetParameters") checked for the new length of the EPL_DIAGNOSIS_NARRATIVE parameter. Note that this applies also to the DAL object EPOD_SERVICE_JOB.

Server

The length of the EPL_DIAGNOSIS_NARRATIVE field needs to be modified throughout all the .NET projects, to ensure that the length remains unlimited.

  • Length parameters must removed or modified, for example:
    • Utilites.cs(677): public static int EPL_DIAGNOSIS_NARRATIVE = 255
    • EPOD_UTILS.cs(110): public static int EPL_DIAGNOSIS_NARRATIVE = 255;

All XSDs used in export and import should be modified to identify that there is now no restriction on the EPL_DIAGNOSIS_NARRATIVE field. These include but are not limited to:

  • EPOD_EXPORT_JOB.XSD
  • EPOD_EXPORT_JOB_RESPONSE.XSD
  • EPOD_EXPORT_LOAD.XSD
  • EPOD_EXPORT_LOAD_RESPONSE.XSD
  • XMLUpload.XSD

Android Client

The Services module will be modified to remove maxlength from vars.DiagTB.

A new language tag should be added to any strings.xml files in the i18n (multi-lingual) folder, as follows:

  • <string name="Comments">Comments</string>

This should be added to all languages' xml files found under the i18n folder.

A new Style (called "LANE") will be added to the Style module - this will be similar to the PLINK style, replacing the following:

  • Login_Logo/Login_Logo_land - insert the Lanemark Logo into the product.
  • Service_DiagLB/Service_DiagLB_land - property "text" set to Ti.App.style.getLabel("Comments")

Note Note: Others will be added to this in other specifications.


Appendix A: TEST PLAN

Test Script / Scenario ReferenceDiagnosis Narrative Extended LengthCall Number(s): 311581 309371-12
Test Script / Scenario DescriptionTo show unrestricted data entry for Diagnosis NarrativePASS / ISSUES / FAIL
Menu AccessServices 
Pre-requisitesNoneTested By:
 
Test ObjectiveTo test that more than 255 characters can be entered against a diagnosis narrativeDate:
 


Step Action Result Remarks P/F
1 PDA Services      
  Create a service and assign to a user      
1.01 Logon to the PDA and perform a Service, entering a diagnosis of greater than 255 characters. The narrative is saved in the database, displayed in the Service and Job screens correctly, and on any Service Reports.    


Appendix B: Quote & Document References

Cost Details
Activity No. of Days Rate per Day (£) Cost (£ Exc. VAT)
Requirements 0.00 0 £0.00
Change Request Evaluation 0.00 0 £0.00
Functional Specification 0.25 0 £0.00
Technical Specification 0.00 0 £0.00
Development 1.00 0 £0.00
Testing and Release 0.25 0 £0.00
Implementation 0.00 0 £0.00
Project Management First argument to "number_format" must be a number. 0 £First argument to "number_format" must be a number.
 
TOTAL First argument to "number_format" must be a number.   £First argument to "number_format" must be a number.
Estimate excludes training, release to live and go live support.

B.1 References

Ref NoDocument Title & IDVersionDate
1UG 291094 EPOD Admin User Guide2.04/4/2012
2UG 291097 EPOD Client User Guide3.023/4/2013
3REQ 309371 Lanemark eSERV Requirements0.429/08/2013


B.2 Glossary

Term Definition
EPOD Electronic Proof of Delivery. The OBS EPOD system is CALIDUS ePOD.
CALIDUS eSERV The OBS mobile system to complete Service functionality in the field. This is part of the CALIDUS ePOD system.
PDA The mobile device on which the C-ePOD system will run in the field. This can be a Phone, EDA or industrial PDA, running Android.
DAL Data Access Layer. A mechanism for accessing data by the system that is removed from the application, allowing for simplified access and providing protection to the data, as only approved DAL methods can be used to modify it.
GPS Global Positioning System. A mechanism of retrieving accurate positioning information in the form of Latitude and Longitude (Lat-Long) co-ordinates from a device.
GPRS, 3G, HSDPA, Data Service All terms referring to mobile device network connectivity, and the speed at which the device connects to the internet.


B.3 Authorised By


Julie Taylor

OBS Project Manager
_____________________________

Jeff Foster

Client Representative
_____________________________

Alan Thompson

Client Representative
_____________________________