QESTonline - User contributions [en]

QESTField 4.3.12, QESTNET Database Upgrade 4.3.1387.44966

2017-10-23T03:15:41Z

Iresha.jayasekara:

===QESTField 4.3.12, QESTNET Database Upgrade 4.3.1387.44966===

{|class="wikitable"
|- valign="top"
!Bug/CR ID
!Customer Code
!Customer Reference
!Product(s) Modified
!Name
!Release Notes

|- valign="top"
|style="background:white;"|Bug#6938
|style="background:white;"|USSME
|style="background:white;"|
|style="background:white;"|QESTField
|style="background:white;"|Field Density Report comments edits not being saved
|style="background:white;"|In Nuclear Density and Asphalt Density workflows, the Report comments edits were not saving unless the workflow was added for the first time. This has been fixed now.
|- valign="top"

|style="background:white;"|CR#3186
|style="background:white;"|AUHAN
|style="background:white;"|
|style="background:white;"|QESTLab
|style="background:white;"|Report Test Name and Method
|style="background:white;"|The option 'Report Test Name and Method' in the QEST Administration Console now has three options to select from:
<UL>
<LI>
Report Test Name and Method - Both the Test Name and the Test Method will be shown on the report
</LI>
<LI>
Report Test Name Only - Only the Test Name will be shown on the report.
</LI>
<LI>
Report Test Method Only - Only the Method will be shown on the report.
</LI>
</UL>
 
If the option had been previously set to True or False, the value will be updated to the correct option after a Database Upgrade.
|- valign="top"
|style="background:white smoke;"|CR#4071
|style="background:white smoke;"|USTWI
|style="background:white smoke;"|
|style="background:white smoke;"|QESTField
|style="background:white smoke;"|Errors Uploading Images on iOS v11
|style="background:white smoke;"|Errors uploading images to test reports on iOS v11 have been fixed.

|}

QESTField 4.3.12, QESTNET Database Upgrade 4.3.1387.44966

2017-10-23T03:10:35Z

Iresha.jayasekara:

{|class="wikitable"
|- valign="top"
!Bug/CR ID
!Customer Code
!Customer Reference
!Product(s) Modified
!Name
!Release Notes

|- valign="top"
|style="background:white;"|Bug#6938
|style="background:white;"|USSME
|style="background:white;"|
|style="background:white;"|QESTField
|style="background:white;"|Field Density Report comments edits not being saved
|style="background:white;"|In Nuclear Density and Asphalt Density workflows, the Report comments edits were not saving unless the workflow was added for the first time. This has been fixed now.
|- valign="top"

|style="background:white;"|CR#3186
|style="background:white;"|AUHAN
|style="background:white;"|
|style="background:white;"|QESTLab
|style="background:white;"|Report Test Name and Method
|style="background:white;"|The option 'Report Test Name and Method' in the QEST Administration Console now has three options to select from:
<UL>
<LI>
Report Test Name and Method - Both the Test Name and the Test Method will be shown on the report
</LI>
<LI>
Report Test Name Only - Only the Test Name will be shown on the report.
</LI>
<LI>
Report Test Method Only - Only the Method will be shown on the report.
</LI>
</UL>
 
If the option had been previously set to True or False, the value will be updated to the correct option after a Database Upgrade.
|- valign="top"
|style="background:white smoke;"|CR#4071
|style="background:white smoke;"|USTWI
|style="background:white smoke;"|
|style="background:white smoke;"|QESTField
|style="background:white smoke;"|Errors Uploading Images on iOS v11
|style="background:white smoke;"|Errors uploading images to test reports on iOS v11 have been fixed.

|}

QESTField 4.3.12, QESTNET Database Upgrade 4.3.1387.44966

2017-10-23T03:07:36Z

Iresha.jayasekara:

{|class="wikitable"
|- valign="top"
!Bug/CR ID
!Customer Code
!Customer Reference
!Product(s) Modified
!Name
!Release Notes

|- valign="top"
|style="background:white;"|Bug#6938
|style="background:white;"|USSME
|style="background:white;"|
|style="background:white;"|QESTField
|style="background:white;"|Field Density Report comments edits not being saved
|style="background:white;"|In Nuclear Density and Asphalt Density workflows, the Report comments edits were not saving unless the workflow was added for the first time. This has been fixed now.
|- valign="top"
|style="background:white smoke;"|Bug#6949
|style="background:white smoke;"|USPSI
|style="background:white smoke;"|
|style="background:white smoke;"|Construction Hive
|style="background:white smoke;"|The Merge Account Utility is Timing Out
|style="background:white smoke;"|Problems with merging Construction Hive accounts due to database timeouts have been fixed.
|- valign="top"
|style="background:white;"|CR#3186
|style="background:white;"|AUHAN
|style="background:white;"|
|style="background:white;"|QESTLab
|style="background:white;"|Report Test Name and Method
|style="background:white;"|The option 'Report Test Name and Method' in the QEST Administration Console now has three options to select from:
<UL>
<LI>
Report Test Name and Method - Both the Test Name and the Test Method will be shown on the report
</LI>
<LI>
Report Test Name Only - Only the Test Name will be shown on the report.
</LI>
<LI>
Report Test Method Only - Only the Method will be shown on the report.
</LI>
</UL>
 
If the option had been previously set to True or False, the value will be updated to the correct option after a Database Upgrade.
|- valign="top"
|style="background:white smoke;"|CR#4071
|style="background:white smoke;"|USTWI
|style="background:white smoke;"|
|style="background:white smoke;"|QESTField
|style="background:white smoke;"|Errors Uploading Images on iOS v11
|style="background:white smoke;"|Errors uploading images to test reports on iOS v11 have been fixed.

|}

QESTField 4.3.12, QESTNET Database Upgrade 4.3.1387.44966

2017-10-23T03:04:18Z

Iresha.jayasekara:

[[Media:Release Notes 4.x.xxxx Bugs.xlsx|4.x.xxxx Release Notes - Bugs]] [[Media:Release Notes 4.x.xxxx CRs.xlsx|4.x.xxxx Release Notes - CRs]] 
{|class="wikitable"
|- valign="top"
!Bug/CR ID
!Customer Code
!Customer Reference
!Product(s) Mod

|- valign="top"
|style="background:white;"|Bug#6938
|style="background:white;"|USSME
|style="background:white;"|
|style="background:white;"|QESTField
|style="background:white;"|Field Density Report comments edits not being saved
|style="background:wh
|- valign="top"
|style="background:white smoke;"|Bug#6949
|style="background:white smoke;"|USPSI
|style="background:white smoke;"|
|style="background:white smoke;"|Construction Hive
|style="background:white smoke;"|The Merge Account Utility is Timing
|- valign="top"
|style="background:white;"|CR#3186
|style="background:white;"|AUHAN
|style="background:white;"|
|style="background:white;"|QESTLab
|style="background:white;"|Report Test Name and Method
|style="background:white;"|The option 'Report Te
|- valign="top"
|style="background:white smoke;"|CR#4071
|style="background:white smoke;"|USTWI
|style="background:white smoke;"|
|style="background:white smoke;"|QESTField
|style="background:white smoke;"|Errors Uploading Images on iOS v11
|style="

|}

QESTField 4.3.12, QESTNET Database Upgrade 4.3.1387.44966

2017-10-23T03:02:30Z

Iresha.jayasekara:

4.2

2016-06-09T06:19:50Z

Iresha.jayasekara:

==New Functionality==
===Concrete===
=====Concrete Shrinkage Screen and Test Report Redesign===== There will be a new QESTLab Test Screen and Test Report for Concrete Drying Shrinkage, designed to support the 2015 standards AS 1012.8.4 and AS 1012.13. The new screen is split into tabs to better separate the preparing and measurement steps. It includes support for selecting more equipment items, allowing data to be entered for humidity and evaporation rates, transportation history for specimens and other information required by the standards.

The new Concrete Shrinkage Test Report will support the requirements of the standards. When the preparing and measuring laboratories are not the same, it will be possible to produce separate reports for the preparation and the measurement. When one laboratory performs both, the different parts will appear on separate pages.
 

=====Concrete Batch Plant Inspection Ticket===== This introduces a new QESTLab Test Screen and Test Report to complement the existing QESTField Workflow.
The QESTLab Test screen has been created to mimic the existing QESTField Workflows functionality. It will allow the user to enter in details, create and remove mixtures of the three material types (Aggregate, Cementitious Materials and Admixtures), enter in Water details and add comments, which will be included on the report.

The 'Batch Plant Inspection Ticket Report' has also been created. This report will be automatically generated when the Ticket is created, whether in QESTField or QESTLab.

Finally, a new feature has been implemented to lock the Concrete Samples 'Mix Data' grid, when a child Batch Plant Inspection Ticket is present under the sample. This is due to the data that is entered on the Ticket being automatically exported to the Concrete Samples 'Mix Data' section. This occurs in both QESTField and QESTLab.
 

=====Inclusion of Load No. and Lift No. for US Concrete===== For any Aggregate/Soil Field Density workflow, the Lift No. will now also be available for data entry. It will be found in the Test Location section. 
The field "Load No", which can be used for entering the 'Load Number' from the concrete truck, has been made available on the Concrete Sample (ASTM/AASHTO) screen (1602). This field is also available for use in Bulk Entry, and for the various concrete workflows in QESTField.
 

=====Reporting of Density (MPUV) for AU Concrete===== Users will be able to conduct Mass per Unit Volume (MPUV) tests in QESTField for the AS1012.5 - 1999 and RMS T303 standards.

On the Field Data phase of the Concrete Workflow a drop down for Measured Density Method has been added. From this drop down the user can select either 'Full' or 'Reduced', which will add the Mass per Unit Volume full test or reduced test, corresponding to the selected Standard, to the concrete sample. This means that if the selected standard is RMS it will add the corresponding RMS T303 test and if the selected standard is AS (2015) it will add the corresponding AS 1012.5 test.

If the selected test is the reduced screen then a field will be shown for entry of the Measured Density. For the full test, a 'MPUV' phase will be added to the Concrete Workflow to provide the test's workflow. If no test is selected, 'Measured Density' can be entered directly as before.

In QESTLab the Concrete Sample (AU) will now import the Measured Density from the child MPUV test.

The following tests can be added:
<ul>
<li>Mass per Unit Volume of Freshly Mixed Concrete [AS 1012.5]</li>
<li>Mass Per Unit Volume (Yield) [AS 1012.5] *</li>
<li>Mass per Unit Volume of Freshly Mixed Concrete [RMS T303]</li>
<li>Mass Per Unit Volume (Yield) [RMS T303] *</li>
</ul>
 

=====Concrete Specimens Ordering===== Concrete and Masonry Specimens had the potential to appear ordered wrong, when created in QESTField and viewed in QESTLab (either on the test screens or test reports). In addition, in QESTLab, specimens could be added or changed such that they would appear out of order.

To address this problem, specimens created in QESTField will be ordered as follows when created before generating the Specimen IDs:
<ul>
<li>Type</li>
<li>Then Age (Days & Hours)</li>
<li>Then Created Date</li>
</ul>

QESTLab will order the specimens in the same order by default, but the user can choose any of the following options from the “Sort Order” drop down list; which is a new feature added to the Concrete Sample screen.
<ul>
<li>ID (the default)</li>
<li>Type then ID</li>
<li>Type then Age</li>
<li>ID then Age</li>
<li>Type, then Age, then ID</li>
</ul>

Once the below criteria has been filled out on the concrete sample to indicate the field work is complete, specimens will no longer be editable in QESTField, but other sample data will be.
The criteria for completion is:
<ul>
<li>Date Received set on the sample</li>
<li>QestComplete set on any specimen</li>
<li>Any specimen has Area or Strength value calculated</li>
<li>QestCheckedBy is set on any specimen</li>
</ul>
 

===Publishing===
=====Test Report Email Subject===== A new option, "Email Subject Format", has been added in the QEST Administrator Console (accessible via Configuration -> Options -> Publishing -> Email) that gives customers the ability to configure the Subject of the Email when sending Test Reports directly from QESTLab. 
The option lets users configure which database fields appear in the subject line by including the field name within double box brackets. 
 
E.g. If the option is configured as "Report No: <nowiki>[[ReportNo]]</nowiki> of Client: <nowiki>[[ClientName]]</nowiki>" then it will generate the following email subject line; "Report No: WO-12345S01 of Client: My Test Client ABC". 
 
The fields that can be included in the subject line are restricted to the following:
<ul>
<li>ReportNo</li>
<li>WorkOrderID</li>
<li>ClientCode</li>
<li>ClientName</li>
<li>ProjectCode</li>
<li>ProjectName</li>
<li>LabName</li>
</ul>
If an incorrect field or format is entered then the entire Subject will revert to the default value which is, "Test Report <nowiki>[[ReportNo]]</nowiki>"

==Updated Test Methods==
=====Florida Department of Transport (FDOT) Standards=====
{| border="0"
|[FM 5-515 - 2015] || Limerock Bearing Ratio
|}

=====American Association of State Highway and Transportation Officials (AASHTO) Standards=====
{| border="0"
|[AASHTO T 84 - 2013] || Specific Gravity and Absorption of Fine Aggregate
|-
|[AASHTO T 85 - 2013] || Specific Gravity and Absorption of Coarse Aggregate
|-
|[AASHTO T 99 - 2015] || Proctor - Standard
|-
|[AASHTO T 180 - 2015] || Proctor - Modified
|}

=====American Society for Testing and Materials (ASTM) Standards=====
{| border="0"
|[ASTM D 1556 - 2015] || Sand-Cone Method
|}

==Release Notes==
{{QESTLab:4.2 TP 1}}

4.2

2016-06-09T06:18:54Z

Iresha.jayasekara:

==New Functionality==
===Concrete===
=====Concrete Shrinkage Screen and Test Report Redesign===== There will be a new QESTLab Test Screen and Test Report for Concrete Drying Shrinkage, designed to support the 2015 standards AS 1012.8.4 and AS 1012.13. The new screen is split into tabs to better separate the preparing and measurement steps. It includes support for selecting more equipment items, allowing data to be entered for humidity and evaporation rates, transportation history for specimens and other information required by the standards.

The new Concrete Shrinkage Test Report will support the requirements of the standards. When the preparing and measuring laboratories are not the same, it will be possible to produce separate reports for the preparation and the measurement. When one laboratory performs both, the different parts will appear on separate pages.
 

=====Concrete Batch Plant Inspection Ticket===== This introduces a new QESTLab Test Screen and Test Report to complement the existing QESTField Workflow.
The QESTLab Test screen has been created to mimic the existing QESTField Workflows functionality. It will allow the user to enter in details, create and remove mixtures of the three material types (Aggregate, Cementitious Materials and Admixtures), enter in Water details and add comments, which will be included on the report.

The 'Batch Plant Inspection Ticket Report' has also been created. This report will be automatically generated when the Ticket is created, whether in QESTField or QESTLab.

Finally, a new feature has been implemented to lock the Concrete Samples 'Mix Data' grid, when a child Batch Plant Inspection Ticket is present under the sample. This is due to the data that is entered on the Ticket being automatically exported to the Concrete Samples 'Mix Data' section. This occurs in both QESTField and QESTLab.
 

=====Inclusion of Load No. and Lift No. for US Concrete===== For any Aggregate/Soil Field Density workflow, the Lift No. will now also be available for data entry. It will be found in the Test Location section. 
The field "Load No", which can be used for entering the 'Load Number' from the concrete truck, has been made available on the Concrete Sample (ASTM/AASHTO) screen (1602). This field is also available for use in Bulk Entry, and for the various concrete workflows in QESTField.
 

=====Reporting of Density (MPUV) for AU Concrete===== Users will be able to conduct Mass per Unit Volume (MPUV) tests in QESTField for the AS1012.5 - 1999 and RMS T303 standards.

On the Field Data phase of the Concrete Workflow a drop down for Measured Density Method has been added. From this drop down the user can select either 'Full' or 'Reduced', which will add the Mass per Unit Volume full test or reduced test, corresponding to the selected Standard, to the concrete sample. This means that if the selected standard is RMS it will add the corresponding RMS T303 test and if the selected standard is AS (2015) it will add the corresponding AS 1012.5 test.

If the selected test is the reduced screen then a field will be shown for entry of the Measured Density. For the full test, a 'MPUV' phase will be added to the Concrete Workflow to provide the test's workflow. If no test is selected, 'Measured Density' can be entered directly as before.

In QESTLab the Concrete Sample (AU) will now import the Measured Density from the child MPUV test.

The following tests can be added:
<ul>
<li>Mass per Unit Volume of Freshly Mixed Concrete [AS 1012.5]</li>
<li>Mass Per Unit Volume (Yield) [AS 1012.5] *</li>
<li>Mass per Unit Volume of Freshly Mixed Concrete [RMS T303]</li>
<li>Mass Per Unit Volume (Yield) [RMS T303] *</li>
</ul>
 

=====Concrete Specimens Ordering===== Concrete and Masonry Specimens had the potential to appear ordered wrong, when created in QESTFieldand viewed in QESTLab (either on the test screens or test reports). In addition, in QESTLab, specimens could be added or changed such that they would appear out of order.

To address this problem, specimens created in QESTField will be ordered as follows when created before generating the Specimen IDs:
<ul>
<li>Type</li>
<li>Then Age (Days & Hours)</li>
<li>Then Created Date</li>
</ul>

QESTLab will order the specimens in the same order by default, but the user can choose any of the following options from the “Sort Order” drop down list; which is a new feature added to the Concrete Sample screen.
<ul>
<li>ID (the default)</li>
<li>Type then ID</li>
<li>Type then Age</li>
<li>ID then Age</li>
<li>Type, then Age, then ID</li>
</ul>

Once the below criteria has been filled out on the concrete sample to indicate the field work is complete, specimens will no longer be editable in QESTField, but other sample data will be.
The criteria for completion is:
<ul>
<li>Date Received set on the sample</li>
<li>QestComplete set on any specimen</li>
<li>Any specimen has Area or Strength value calculated</li>
<li>QestCheckedBy is set on any specimen</li>
</ul>
 

===Publishing===
=====Test Report Email Subject===== A new option, "Email Subject Format", has been added in the QEST Administrator Console (accessible via Configuration -> Options -> Publishing -> Email) that gives customers the ability to configure the Subject of the Email when sending Test Reports directly from QESTLab. 
The option lets users configure which database fields appear in the subject line by including the field name within double box brackets. 
 
E.g. If the option is configured as "Report No: <nowiki>[[ReportNo]]</nowiki> of Client: <nowiki>[[ClientName]]</nowiki>" then it will generate the following email subject line; "Report No: WO-12345S01 of Client: My Test Client ABC". 
 
The fields that can be included in the subject line are restricted to the following:
<ul>
<li>ReportNo</li>
<li>WorkOrderID</li>
<li>ClientCode</li>
<li>ClientName</li>
<li>ProjectCode</li>
<li>ProjectName</li>
<li>LabName</li>
</ul>
If an incorrect field or format is entered then the entire Subject will revert to the default value which is, "Test Report <nowiki>[[ReportNo]]</nowiki>"

==Updated Test Methods==
=====Florida Department of Transport (FDOT) Standards=====
{| border="0"
|[FM 5-515 - 2015] || Limerock Bearing Ratio
|}

=====American Association of State Highway and Transportation Officials (AASHTO) Standards=====
{| border="0"
|[AASHTO T 84 - 2013] || Specific Gravity and Absorption of Fine Aggregate
|-
|[AASHTO T 85 - 2013] || Specific Gravity and Absorption of Coarse Aggregate
|-
|[AASHTO T 99 - 2015] || Proctor - Standard
|-
|[AASHTO T 180 - 2015] || Proctor - Modified
|}

=====American Society for Testing and Materials (ASTM) Standards=====
{| border="0"
|[ASTM D 1556 - 2015] || Sand-Cone Method
|}

==Release Notes==
{{QESTLab:4.2 TP 1}}

4.2

2016-06-09T06:17:59Z

Iresha.jayasekara:

==New Functionality==
===Concrete===
=====Concrete Shrinkage Screen and Test Report Redesign===== There will be a new QESTLab Test Screen and Test Report for Concrete Drying Shrinkage, designed to support the 2015 standards AS 1012.8.4 and AS 1012.13. The new screen is split into tabs to better separate the preparing and measurement steps. It includes support for selecting more equipment items, allowing data to be entered for humidity and evaporation rates, transportation history for specimens and other information required by the standards.

The new Concrete Shrinkage Test Report will support the requirements of the standards. When the preparing and measuring laboratories are not the same, it will be possible to produce separate reports for the preparation and the measurement. When one laboratory performs both, the different parts will appear on separate pages.
 

=====Concrete Batch Plant Inspection Ticket===== This introduces a new QESTLab Test Screen and Test Report to complement the existing QESTField Workflow.
The QESTLab Test screen has been created to mimic the existing QESTField Workflows functionality. It will allow the user to enter in details, create and remove mixtures of the three material types (Aggregate, Cementitious Materials and Admixtures), enter in Water details and add comments, which will be included on the report.

The 'Batch Plant Inspection Ticket Report' has also been created. This report will be automatically generated when the Ticket is created, whether in QESTField or QESTLab.

Finally, a new feature has been implemented to lock the Concrete Samples 'Mix Data' grid, when a child Batch Plant Inspection Ticket is present under the sample. This is due to the data that is entered on the Ticket being automatically exported to the Concrete Samples 'Mix Data' section. This occurs in both QESTField and QESTLab.
 

=====Inclusion of Load No. and Lift No. for US Concrete===== For any Aggregate/Soil Field Density workflow, the Lift No. will now also be available for data entry. It will be found in the Test Location section. 
The field "Load No", which can be used for entering the 'Load Number' from the concrete truck, has been made available on the Concrete Sample (ASTM/AASHTO) screen (1602). This field is also available for use in Bulk Entry, and for the various concrete workflows in QESTField.
 

=====Reporting of Density (MPUV) for AU Concrete===== Users will be able to conduct Mass per Unit Volume (MPUV) tests in QESTField for the AS1012.5 - 1999 and RMS T303 standards.

On the Field Data phase of the Concrete Workflow a drop down for Measured Density Method has been added. From this drop down the user can select either 'Full' or 'Reduced', which will add the Mass per Unit Volume full test or reduced test, corresponding to the selected Standard, to the concrete sample. This means that if the selected standard is RMS it will add the corresponding RMS T303 test and if the selected standard is AS (2015) it will add the corresponding AS 1012.5 test.

If the selected test is the reduced screen then a field will be shown for entry of the Measured Density. For the full test, a 'MPUV' phase will be added to the Concrete Workflow to provide the test's workflow. If no test is selected, 'Measured Density' can be entered directly as before.

In QESTLab the Concrete Sample (AU) will now import the Measured Density from the child MPUV test.

The following tests can be added:
<ul>
<li>Mass per Unit Volume of Freshly Mixed Concrete [AS 1012.5]</li>
<li>Mass Per Unit Volume (Yield) [AS 1012.5] *</li>
<li>Mass per Unit Volume of Freshly Mixed Concrete [RMS T303]</li>
<li>Mass Per Unit Volume (Yield) [RMS T303] *</li>
</ul>
 

=====Concrete Specimens Ordering===== Concrete and Masonry Specimens had the potential to appear ordered wrong, when created in QESTFieldand viewed in QESTLab (either on the test screens or test reports). In addition, in QESTLab, specimens could be added or changed such that they would appear out of order.

To address this problem, specimens created in QESTField will be ordered as follows when created before generating the Specimen IDs:
<ul>
<li>Type</li>
<li>Then Age (Days & Hours)</li>
<li>Then Created Date</li>
</ul>

QESTLab will order the specimens in the same order by default, but the user can choose any of the following options from the “Sort Order” drop down list; which is a new feature added to the Concrete Sample screen.
<ul>
<li>ID (the default)</li>
<li>Type then ID</li>
<li>Type then Age</li>
<li>ID then Age</li>
<li>Type, then Age, then ID</li>
</ul>
 

Once the below criteria has been filled out on the concrete sample to indicate the field work is complete, specimens will no longer be editable in QESTField, but other sample data will be.
The criteria for completion is:
<ul>
<li>Date Received set on the sample</li>
<li>QestComplete set on any specimen</li>
<li>Any specimen has Area or Strength value calculated</li>
<li>QestCheckedBy is set on any specimen</li>
</ul>
 
===Publishing===
=====Test Report Email Subject===== A new option, "Email Subject Format", has been added in the QEST Administrator Console (accessible via Configuration -> Options -> Publishing -> Email) that gives customers the ability to configure the Subject of the Email when sending Test Reports directly from QESTLab. 
The option lets users configure which database fields appear in the subject line by including the field name within double box brackets. 
 
E.g. If the option is configured as "Report No: <nowiki>[[ReportNo]]</nowiki> of Client: <nowiki>[[ClientName]]</nowiki>" then it will generate the following email subject line; "Report No: WO-12345S01 of Client: My Test Client ABC". 
 
The fields that can be included in the subject line are restricted to the following:
<ul>
<li>ReportNo</li>
<li>WorkOrderID</li>
<li>ClientCode</li>
<li>ClientName</li>
<li>ProjectCode</li>
<li>ProjectName</li>
<li>LabName</li>
</ul>
If an incorrect field or format is entered then the entire Subject will revert to the default value which is, "Test Report <nowiki>[[ReportNo]]</nowiki>"

==Updated Test Methods==
=====Florida Department of Transport (FDOT) Standards=====
{| border="0"
|[FM 5-515 - 2015] || Limerock Bearing Ratio
|}

=====American Association of State Highway and Transportation Officials (AASHTO) Standards=====
{| border="0"
|[AASHTO T 84 - 2013] || Specific Gravity and Absorption of Fine Aggregate
|-
|[AASHTO T 85 - 2013] || Specific Gravity and Absorption of Coarse Aggregate
|-
|[AASHTO T 99 - 2015] || Proctor - Standard
|-
|[AASHTO T 180 - 2015] || Proctor - Modified
|}

=====American Society for Testing and Materials (ASTM) Standards=====
{| border="0"
|[ASTM D 1556 - 2015] || Sand-Cone Method
|}

==Release Notes==
{{QESTLab:4.2 TP 1}}

4.2

2016-06-06T05:01:05Z

Iresha.jayasekara:

==New Functionality==
===Concrete===
=====Concrete Shrinkage Screen and Test Report Redesign===== There will be a new QESTLab Test Screen and Test Report for Concrete Drying Shrinkage, designed to support the 2015 standards AS 1012.8.4 and AS 1012.13. The new screen is split into tabs to better separate the preparing and measurement steps. It includes support for selecting more equipment items, allowing data to be entered for humidity and evaporation rates, transportation history for specimens and other information required by the standards.

The new Concrete Shrinkage Test Report will support the requirements of the standards. When the preparing and measuring laboratories are not the same, it will be possible to produce separate reports for the preparation and the measurement. When one laboratory performs both, the different parts will appear on separate pages.
 

=====Concrete Batch Plant Inspection Ticket===== This introduces a new QESTLab Test Screen and Test Report to complement the existing QESTField Workflow.
The QESTLab Test screen has been created to mimic the existing QESTField Workflows functionality. It will allow the user to enter in details, create and remove mixtures of the three material types (Aggregate, Cementitious Materials and Admixtures), enter in Water details and add comments, which will be included on the report.

The 'Batch Plant Inspection Ticket Report' has also been created. This report will be automatically generated when the Ticket is created, whether in QESTField or QESTLab.

Finally, a new feature has been implemented to lock the Concrete Samples 'Mix Data' grid, when a child Batch Plant Inspection Ticket is present under the sample. This is due to the data that is entered on the Ticket being automatically exported to the Concrete Samples 'Mix Data' section. This occurs in both QESTField and QESTLab.
 

=====Inclusion of Load No. and Lift No. for US Concrete===== For any Aggregate/Soil Field Density workflow, the Lift No. will now also be available for data entry. It will be found in the Test Location section. 
The field "Load No", which can be used for entering the 'Load Number' from the concrete truck, has been made available on the Concrete Sample (ASTM/AASHTO) screen (1602). This field is also available for use in Bulk Entry, and for the various concrete workflows in QESTField.
 

=====Reporting of Density (MPUV) for AU Concrete===== Users will be able to conduct Mass per Unit Volume (MPUV) tests in QESTField for the AS1012.5 - 1999 and RMS T303 standards.

On the Field Data phase of the Concrete Workflow a drop down for Measured Density Method has been added. From this drop down the user can select either 'Full' or 'Reduced', which will add the Mass per Unit Volume full test or reduced test, corresponding to the selected Standard, to the concrete sample. This means that if the selected standard is RMS it will add the corresponding RMS T303 test and if the selected standard is AS (2015) it will add the corresponding AS 1012.5 test.

If the selected test is the reduced screen then a field will be shown for entry of the Measured Density. For the full test, a 'MPUV' phase will be added to the Concrete Workflow to provide the test's workflow. If no test is selected, 'Measured Density' can be entered directly as before.

In QESTLab the Concrete Sample (AU) will now import the Measured Density from the child MPUV test.

The following tests can be added:
<ul>
<li>Mass per Unit Volume of Freshly Mixed Concrete [AS 1012.5]</li>
<li>Mass Per Unit Volume (Yield) [AS 1012.5] *</li>
<li>Mass per Unit Volume of Freshly Mixed Concrete [RMS T303]</li>
<li>Mass Per Unit Volume (Yield) [RMS T303] *</li>
</ul>
 

=====Concrete Specimens Ordering===== Concrete and Masonry Specimens had the potential to appear ordered wrong, when created in QESTFieldand viewed in QESTLab (either on the test screens or test reports). In addition, in QESTLab, specimens could be added or changed such that they would appear out of order.

To address this problem, specimens created in QESTField will be ordered as follows when created before generating the Specimen IDs:
<ul>
<li>Type</li>
<li>Then Age (Days & Hours)</li>
<li>Then Created Date</li>
</ul>

QESTLab will order the specimens in the same order by default, but the user can choose any of the following options from the “Sort Order” drop down list; which is a new feature added to the Concrete Sample screen.
<ul>
<li>ID (the default)</li>
<li>Type then ID</li>
<li>Type then Age</li>
<li>ID then Age</li>
<li>Type, then Age, then ID</li>
</ul>
 

===Publishing===
=====Test Report Email Subject===== A new option, "Email Subject Format", has been added in the QEST Administrator Console (accessible via Configuration -> Options -> Publishing -> Email) that gives customers the ability to configure the Subject of the Email when sending Test Reports directly from QESTLab. 
The option lets users configure which database fields appear in the subject line by including the field name within double box brackets. 
 
E.g. If the option is configured as "Report No: <nowiki>[[ReportNo]]</nowiki> of Client: <nowiki>[[ClientName]]</nowiki>" then it will generate the following email subject line; "Report No: WO-12345S01 of Client: My Test Client ABC". 
 
The fields that can be included in the subject line are restricted to the following:
<ul>
<li>ReportNo</li>
<li>WorkOrderID</li>
<li>ClientCode</li>
<li>ClientName</li>
<li>ProjectCode</li>
<li>ProjectName</li>
<li>LabName</li>
</ul>
If an incorrect field or format is entered then the entire Subject will revert to the default value which is, "Test Report <nowiki>[[ReportNo]]</nowiki>"

==Updated Test Methods==
=====Florida Department of Transport (FDOT) Standards=====
{| border="0"
|[FM 5-515 - 2015] || Limerock Bearing Ratio
|}

=====American Association of State Highway and Transportation Officials (AASHTO) Standards=====
{| border="0"
|[AASHTO T 84 - 2013] || Specific Gravity and Absorption of Fine Aggregate
|-
|[AASHTO T 85 - 2013] || Specific Gravity and Absorption of Coarse Aggregate
|-
|[AASHTO T 99 - 2015] || Proctor - Standard
|-
|[AASHTO T 180 - 2015] || Proctor - Modified
|}

=====American Society for Testing and Materials (ASTM) Standards=====
{| border="0"
|[ASTM D 1556 - 2015] || Sand-Cone Method
|}

==Release Notes==
{{QESTLab:4.2 TP 1}}

QESTNET Internal:Developer Setup QESTField

2016-02-08T01:26:09Z

Iresha.jayasekara:

===QESTField===
*Open '''~\qestnet\QESTField MVC\QESTField.sln'''
** If the solution does not load, check that .NET Framework 4.5 and ASP.NET MVC 4 are installed on your local machine. Use the Visual Studio 2012 CD to repair the installation.
*Build the solution. There should not be any errors
*Go to '''Debug > Exceptions'''
**Find '''System.ServiceModel.FaultException`1'''
**Uncheck '''User-unhandled'''. This will stop the debugger breaking on a fault exception catch every time you login. It is on a "to do" list somewhere to fix... really I (DL) promise.
*Start Debugging ('''F5'''). This will launch a web browser. The choice of web browser is configured in Visual Studio where Start Debugging is. Google Chrome is the recommended choice for QESTField development. The browser will take you to the web address of a local ASP.NET Development Server which Visual Studio has spun up. The login page of QESTField should be displayed. You can login using any QESTLab login credentials which are available in the database and have permission to use QESTField.

====Potential Errors====
{| class="wikitable"
!Error
!Solution
|-
|Error: "Underlying service failed to Open."
|Check the Event Viewer log. It is normally due to the QESTNET service credentials not having permission to access the QESTLab database.
|-
|Error: "No connection could be made because the target machine actively refused it 127.0.0.1:52525."
|The QESTNET service is not running. Ensure the service is running in Control Panel -> Services.
|-
|Error: "A project with an Output Type of Class Library cannot be started directly."
|Right-click the project "QESTField" in the Solution Explorer and select "Set as StartUp Project"
|-
|When you log into QESTField, an AJAX error message is sent with the title: "The filestore directory does not exist: C:\NEEDSTOEXIST"
|This directory is the storage location QESTField will use. To change the directory, edit the following line in the app.config file for the project QESTNET.Service\QESTNET:
:<add key="fileStorePath" value="C:\NEEDSTOEXIST" />
Then, rebuild QESTNET.Service and restart the QESTNET service.
|
|-
|Cannot log into QESTField, below error message is displayed for any username/password. "An error occurred while preparing the command definition. See the inner exception for details"
|
QESTLab_Data.Views are no longer up to date if the message says 'model no longer matches'- Generate Data Schema Or,
If this does not help,
Cleaning the bin folders and rebuilding QESTField fixed the issue.
C:\dev\qestnet\QESTNET\bin\Debug 
C:\dev\qestnet\QESTField MVC\QESTField\bin
|}

QESTNET Internal:Developer Setup QESTField

2016-02-08T01:23:59Z

Iresha.jayasekara:

===QESTField===
*Open '''~\qestnet\QESTField MVC\QESTField.sln'''
** If the solution does not load, check that .NET Framework 4.5 and ASP.NET MVC 4 are installed on your local machine. Use the Visual Studio 2012 CD to repair the installation.
*Build the solution. There should not be any errors
*Go to '''Debug > Exceptions'''
**Find '''System.ServiceModel.FaultException`1'''
**Uncheck '''User-unhandled'''. This will stop the debugger breaking on a fault exception catch every time you login. It is on a "to do" list somewhere to fix... really I (DL) promise.
*Start Debugging ('''F5'''). This will launch a web browser. The choice of web browser is configured in Visual Studio where Start Debugging is. Google Chrome is the recommended choice for QESTField development. The browser will take you to the web address of a local ASP.NET Development Server which Visual Studio has spun up. The login page of QESTField should be displayed. You can login using any QESTLab login credentials which are available in the database and have permission to use QESTField.

====Potential Errors====
{| class="wikitable"
!Error
!Solution
|-
|Error: "Underlying service failed to Open."
|Check the Event Viewer log. It is normally due to the QESTNET service credentials not having permission to access the QESTLab database.
|-
|Error: "No connection could be made because the target machine actively refused it 127.0.0.1:52525."
|The QESTNET service is not running. Ensure the service is running in Control Panel -> Services.
|-
|Error: "A project with an Output Type of Class Library cannot be started directly."
|Right-click the project "QESTField" in the Solution Explorer and select "Set as StartUp Project"
|-
|When you log into QESTField, an AJAX error message is sent with the title: "The filestore directory does not exist: C:\NEEDSTOEXIST"
|This directory is the storage location QESTField will use. To change the directory, edit the following line in the app.config file for the project QESTNET.Service\QESTNET:
:<add key="fileStorePath" value="C:\NEEDSTOEXIST" />
Then, rebuild QESTNET.Service and restart the QESTNET service.
|
|-
|Cannot log into QESTField, below error message is displayed for any username/password. "An error occurred while preparing the command definition. See the inner exception for details"
|
QESTLab_Data.Views are no longer up to date - Generate Data Schema Or,
If this does not help,
Cleaning the bin folders and rebuilding QESTField fixed the issue.
C:\dev\qestnet\QESTNET\bin\Debug 
C:\dev\qestnet\QESTField MVC\QESTField\bin
|}

QESTNET Internal:Developer Setup QESTField

2015-11-16T06:45:08Z

Iresha.jayasekara:

===QESTField===
*Open '''~\qestnet\QESTField MVC\QESTField.sln'''
** If the solution does not load, check that .NET Framework 4.5 and ASP.NET MVC 4 are installed on your local machine. Use the Visual Studio 2012 CD to repair the installation.
*Build the solution. There should not be any errors
*Go to '''Debug > Exceptions'''
**Find '''System.ServiceModel.FaultException`1'''
**Uncheck '''User-unhandled'''. This will stop the debugger breaking on a fault exception catch every time you login. It is on a "to do" list somewhere to fix... really I (DL) promise.
*Start Debugging ('''F5'''). This will launch a web browser. The choice of web browser is configured in Visual Studio where Start Debugging is. Google Chrome is the recommended choice for QESTField development. The browser will take you to the web address of a local ASP.NET Development Server which Visual Studio has spun up. The login page of QESTField should be displayed. You can login using any QESTLab login credentials which are available in the database and have permission to use QESTField.

====Potential Errors====
{| class="wikitable"
!Error
!Solution
|-
|Error: "Underlying service failed to Open."
|Check the Event Viewer log. It is normally due to the QESTNET service credentials not having permission to access the QESTLab database.
|-
|Error: "No connection could be made because the target machine actively refused it 127.0.0.1:52525."
|The QESTNET service is not running. Ensure the service is running in Control Panel -> Services.
|-
|Error: "A project with an Output Type of Class Library cannot be started directly."
|Right-click the project "QESTField" in the Solution Explorer and select "Set as StartUp Project"
|-
|When you log into QESTField, an AJAX error message is sent with the title: "The filestore directory does not exist: C:\NEEDSTOEXIST"
|This directory is the storage location QESTField will use. To change the directory, edit the following line in the app.config file for the project QESTNET.Service\QESTNET:
:<add key="fileStorePath" value="C:\NEEDSTOEXIST" />
Then, rebuild QESTNET.Service and restart the QESTNET service.
|
|-
|Cannot log into QESTField, below error message is displayed for any username/password. "An error occurred while preparing the command definition. See the inner exception for details"
|Cleaning the bin folders and rebuilding QESTField fixed the issue.
C:\dev\qestnet\QESTNET\bin\Debug 
C:\dev\qestnet\QESTField MVC\QESTField\bin
|}

QESTNET Internal:Developer Setup QESTField

2015-11-16T06:43:37Z

Iresha.jayasekara:

===QESTField===
*Open '''~\qestnet\QESTField MVC\QESTField.sln'''
** If the solution does not load, check that .NET Framework 4.5 and ASP.NET MVC 4 are installed on your local machine. Use the Visual Studio 2012 CD to repair the installation.
*Build the solution. There should not be any errors
*Go to '''Debug > Exceptions'''
**Find '''System.ServiceModel.FaultException`1'''
**Uncheck '''User-unhandled'''. This will stop the debugger breaking on a fault exception catch every time you login. It is on a "to do" list somewhere to fix... really I (DL) promise.
*Start Debugging ('''F5'''). This will launch a web browser. The choice of web browser is configured in Visual Studio where Start Debugging is. Google Chrome is the recommended choice for QESTField development. The browser will take you to the web address of a local ASP.NET Development Server which Visual Studio has spun up. The login page of QESTField should be displayed. You can login using any QESTLab login credentials which are available in the database and have permission to use QESTField.

====Potential Errors====
{| class="wikitable"
!Error
!Solution
|-
|Error: "Underlying service failed to Open."
|Check the Event Viewer log. It is normally due to the QESTNET service credentials not having permission to access the QESTLab database.
|-
|Error: "No connection could be made because the target machine actively refused it 127.0.0.1:52525."
|The QESTNET service is not running. Ensure the service is running in Control Panel -> Services.
|-
|Error: "A project with an Output Type of Class Library cannot be started directly."
|Right-click the project "QESTField" in the Solution Explorer and select "Set as StartUp Project"
|-
|When you log into QESTField, an AJAX error message is sent with the title: "The filestore directory does not exist: C:\NEEDSTOEXIST"
|This directory is the storage location QESTField will use. To change the directory, edit the following line in the app.config file for the project QESTNET.Service\QESTNET:
:<add key="fileStorePath" value="C:\NEEDSTOEXIST" />
Then, rebuild QESTNET.Service and restart the QESTNET service.
|
|-
|When you log into QESTField, an error message is displayed: "An error occurred while preparing the command definition. See the inner exception for details"
|Cleaning the bin folders and rebuilding QestField fixed the issue.
C:\dev\qestnet\QESTNET\bin\Debug 
C:\dev\qestnet\QESTField MVC\QESTField\bin
|}

QESTNET Internal:Developer Setup QESTField

2015-11-16T06:41:58Z

Iresha.jayasekara:

===QESTField===
*Open '''~\qestnet\QESTField MVC\QESTField.sln'''
** If the solution does not load, check that .NET Framework 4.5 and ASP.NET MVC 4 are installed on your local machine. Use the Visual Studio 2012 CD to repair the installation.
*Build the solution. There should not be any errors
*Go to '''Debug > Exceptions'''
**Find '''System.ServiceModel.FaultException`1'''
**Uncheck '''User-unhandled'''. This will stop the debugger breaking on a fault exception catch every time you login. It is on a "to do" list somewhere to fix... really I (DL) promise.
*Start Debugging ('''F5'''). This will launch a web browser. The choice of web browser is configured in Visual Studio where Start Debugging is. Google Chrome is the recommended choice for QESTField development. The browser will take you to the web address of a local ASP.NET Development Server which Visual Studio has spun up. The login page of QESTField should be displayed. You can login using any QESTLab login credentials which are available in the database and have permission to use QESTField.

====Potential Errors====
{| class="wikitable"
!Error
!Solution
|-
|Error: "Underlying service failed to Open."
|Check the Event Viewer log. It is normally due to the QESTNET service credentials not having permission to access the QESTLab database.
|-
|Error: "No connection could be made because the target machine actively refused it 127.0.0.1:52525."
|The QESTNET service is not running. Ensure the service is running in Control Panel -> Services.
|-
|Error: "A project with an Output Type of Class Library cannot be started directly."
|Right-click the project "QESTField" in the Solution Explorer and select "Set as StartUp Project"
|-
|When you log into QESTField, an AJAX error message is sent with the title: "The filestore directory does not exist: C:\NEEDSTOEXIST"
|This directory is the storage location QESTField will use. To change the directory, edit the following line in the app.config file for the project QESTNET.Service\QESTNET:
:<add key="fileStorePath" value="C:\NEEDSTOEXIST" />
Then, rebuild QESTNET.Service and restart the QESTNET service.
|
|-
|When you log into QESTField, an error message is displayed: "An error occurred while preparing the command definition. See the inner exception for details"
|Cleaning the bin folders and rebuilding QestField fixed the issue.
C:\dev\qestnet\QESTNET\bin\Debug
C:\dev\qestnet\QESTField MVC\QESTField\bin
|}

QESTNET Internal:Developer Setup QESTField

2015-11-16T06:41:26Z

Iresha.jayasekara:

===QESTField===
*Open '''~\qestnet\QESTField MVC\QESTField.sln'''
** If the solution does not load, check that .NET Framework 4.5 and ASP.NET MVC 4 are installed on your local machine. Use the Visual Studio 2012 CD to repair the installation.
*Build the solution. There should not be any errors
*Go to '''Debug > Exceptions'''
**Find '''System.ServiceModel.FaultException`1'''
**Uncheck '''User-unhandled'''. This will stop the debugger breaking on a fault exception catch every time you login. It is on a "to do" list somewhere to fix... really I (DL) promise.
*Start Debugging ('''F5'''). This will launch a web browser. The choice of web browser is configured in Visual Studio where Start Debugging is. Google Chrome is the recommended choice for QESTField development. The browser will take you to the web address of a local ASP.NET Development Server which Visual Studio has spun up. The login page of QESTField should be displayed. You can login using any QESTLab login credentials which are available in the database and have permission to use QESTField.

====Potential Errors====
{| class="wikitable"
!Error
!Solution
|-
|Error: "Underlying service failed to Open."
|Check the Event Viewer log. It is normally due to the QESTNET service credentials not having permission to access the QESTLab database.
|-
|Error: "No connection could be made because the target machine actively refused it 127.0.0.1:52525."
|The QESTNET service is not running. Ensure the service is running in Control Panel -> Services.
|-
|Error: "A project with an Output Type of Class Library cannot be started directly."
|Right-click the project "QESTField" in the Solution Explorer and select "Set as StartUp Project"
|-
|When you log into QESTField, an AJAX error message is sent with the title: "The filestore directory does not exist: C:\NEEDSTOEXIST"
|This directory is the storage location QESTField will use. To change the directory, edit the following line in the app.config file for the project QESTNET.Service\QESTNET:
:<add key="fileStorePath" value="C:\NEEDSTOEXIST" />
Then, rebuild QESTNET.Service and restart the QESTNET service.
|
|-
|When you log into QESTField, an error message is displayed: "An error occurred while preparing the command definition. See the inner exception for details"
|Cleaning the bin folders and rebuilding QestField fixed the issue.
C:\dev\qestnet\QESTNET\bin\Debug
:&l;C:\dev\qestnet\QESTField MVC\QESTField\bin
|}

QESTNET Internal:Developer Setup QESTField

2015-11-16T06:40:46Z

Iresha.jayasekara:

===QESTField===
*Open '''~\qestnet\QESTField MVC\QESTField.sln'''
** If the solution does not load, check that .NET Framework 4.5 and ASP.NET MVC 4 are installed on your local machine. Use the Visual Studio 2012 CD to repair the installation.
*Build the solution. There should not be any errors
*Go to '''Debug > Exceptions'''
**Find '''System.ServiceModel.FaultException`1'''
**Uncheck '''User-unhandled'''. This will stop the debugger breaking on a fault exception catch every time you login. It is on a "to do" list somewhere to fix... really I (DL) promise.
*Start Debugging ('''F5'''). This will launch a web browser. The choice of web browser is configured in Visual Studio where Start Debugging is. Google Chrome is the recommended choice for QESTField development. The browser will take you to the web address of a local ASP.NET Development Server which Visual Studio has spun up. The login page of QESTField should be displayed. You can login using any QESTLab login credentials which are available in the database and have permission to use QESTField.

====Potential Errors====
{| class="wikitable"
!Error
!Solution
|-
|Error: "Underlying service failed to Open."
|Check the Event Viewer log. It is normally due to the QESTNET service credentials not having permission to access the QESTLab database.
|-
|Error: "No connection could be made because the target machine actively refused it 127.0.0.1:52525."
|The QESTNET service is not running. Ensure the service is running in Control Panel -> Services.
|-
|Error: "A project with an Output Type of Class Library cannot be started directly."
|Right-click the project "QESTField" in the Solution Explorer and select "Set as StartUp Project"
|-
|When you log into QESTField, an AJAX error message is sent with the title: "The filestore directory does not exist: C:\NEEDSTOEXIST"
|This directory is the storage location QESTField will use. To change the directory, edit the following line in the app.config file for the project QESTNET.Service\QESTNET:
:<add key="fileStorePath" value="C:\NEEDSTOEXIST" />
Then, rebuild QESTNET.Service and restart the QESTNET service.
|
|-
|When you log into QESTField, an error message is displayed: "An error occurred while preparing the command definition. See the inner exception for details"
|Cleaning the bin folders and rebuilding QestField fixed the issue.
C:\dev\qestnet\QESTNET\bin\Debug
C:\dev\qestnet\QESTField MVC\QESTField\bin
|}

QESTNET Internal:Developer Setup QESTField

2015-11-16T06:40:29Z

Iresha.jayasekara:

===QESTField===
*Open '''~\qestnet\QESTField MVC\QESTField.sln'''
** If the solution does not load, check that .NET Framework 4.5 and ASP.NET MVC 4 are installed on your local machine. Use the Visual Studio 2012 CD to repair the installation.
*Build the solution. There should not be any errors
*Go to '''Debug > Exceptions'''
**Find '''System.ServiceModel.FaultException`1'''
**Uncheck '''User-unhandled'''. This will stop the debugger breaking on a fault exception catch every time you login. It is on a "to do" list somewhere to fix... really I (DL) promise.
*Start Debugging ('''F5'''). This will launch a web browser. The choice of web browser is configured in Visual Studio where Start Debugging is. Google Chrome is the recommended choice for QESTField development. The browser will take you to the web address of a local ASP.NET Development Server which Visual Studio has spun up. The login page of QESTField should be displayed. You can login using any QESTLab login credentials which are available in the database and have permission to use QESTField.

====Potential Errors====
{| class="wikitable"
!Error
!Solution
|-
|Error: "Underlying service failed to Open."
|Check the Event Viewer log. It is normally due to the QESTNET service credentials not having permission to access the QESTLab database.
|-
|Error: "No connection could be made because the target machine actively refused it 127.0.0.1:52525."
|The QESTNET service is not running. Ensure the service is running in Control Panel -> Services.
|-
|Error: "A project with an Output Type of Class Library cannot be started directly."
|Right-click the project "QESTField" in the Solution Explorer and select "Set as StartUp Project"
|-
|When you log into QESTField, an AJAX error message is sent with the title: "The filestore directory does not exist: C:\NEEDSTOEXIST"
|This directory is the storage location QESTField will use. To change the directory, edit the following line in the app.config file for the project QESTNET.Service\QESTNET:
:<add key="fileStorePath" value="C:\NEEDSTOEXIST" />
Then, rebuild QESTNET.Service and restart the QESTNET service.
|
|-
|When you log into QESTField, an error message is displayed: "An error occurred while preparing the command definition. See the inner exception for details"
|Cleaning the bin folders and rebuilding QestField fixed the issue.
C:\dev\qestnet\QESTNET\bin\Debug

C:\dev\qestnet\QESTField MVC\QESTField\bin
|}

QESTNET Internal:Developer Setup QESTField

2015-11-16T06:39:41Z

Iresha.jayasekara:

===QESTField===
*Open '''~\qestnet\QESTField MVC\QESTField.sln'''
** If the solution does not load, check that .NET Framework 4.5 and ASP.NET MVC 4 are installed on your local machine. Use the Visual Studio 2012 CD to repair the installation.
*Build the solution. There should not be any errors
*Go to '''Debug > Exceptions'''
**Find '''System.ServiceModel.FaultException`1'''
**Uncheck '''User-unhandled'''. This will stop the debugger breaking on a fault exception catch every time you login. It is on a "to do" list somewhere to fix... really I (DL) promise.
*Start Debugging ('''F5'''). This will launch a web browser. The choice of web browser is configured in Visual Studio where Start Debugging is. Google Chrome is the recommended choice for QESTField development. The browser will take you to the web address of a local ASP.NET Development Server which Visual Studio has spun up. The login page of QESTField should be displayed. You can login using any QESTLab login credentials which are available in the database and have permission to use QESTField.

====Potential Errors====
{| class="wikitable"
!Error
!Solution
|-
|Error: "Underlying service failed to Open."
|Check the Event Viewer log. It is normally due to the QESTNET service credentials not having permission to access the QESTLab database.
|-
|Error: "No connection could be made because the target machine actively refused it 127.0.0.1:52525."
|The QESTNET service is not running. Ensure the service is running in Control Panel -> Services.
|-
|Error: "A project with an Output Type of Class Library cannot be started directly."
|Right-click the project "QESTField" in the Solution Explorer and select "Set as StartUp Project"
|-
|When you log into QESTField, an AJAX error message is sent with the title: "The filestore directory does not exist: C:\NEEDSTOEXIST"
|This directory is the storage location QESTField will use. To change the directory, edit the following line in the app.config file for the project QESTNET.Service\QESTNET:
:<add key="fileStorePath" value="C:\NEEDSTOEXIST" />
Then, rebuild QESTNET.Service and restart the QESTNET service.
|
|-
|When you log into QESTField, an error message is displayed: "An error occurred while preparing the command definition. See the inner exception for details"
|Cleaning the bin folders and rebuilding QestField fixed the issue
C:\dev\qestnet\QESTNET\bin\Debug
C:\dev\qestnet\QESTField MVC\QESTField\bin.
|}

QESTNET Internal:Developer Setup QESTField

2015-11-16T06:35:00Z

Iresha.jayasekara:

===QESTField===
*Open '''~\qestnet\QESTField MVC\QESTField.sln'''
** If the solution does not load, check that .NET Framework 4.5 and ASP.NET MVC 4 are installed on your local machine. Use the Visual Studio 2012 CD to repair the installation.
*Build the solution. There should not be any errors
*Go to '''Debug > Exceptions'''
**Find '''System.ServiceModel.FaultException`1'''
**Uncheck '''User-unhandled'''. This will stop the debugger breaking on a fault exception catch every time you login. It is on a "to do" list somewhere to fix... really I (DL) promise.
*Start Debugging ('''F5'''). This will launch a web browser. The choice of web browser is configured in Visual Studio where Start Debugging is. Google Chrome is the recommended choice for QESTField development. The browser will take you to the web address of a local ASP.NET Development Server which Visual Studio has spun up. The login page of QESTField should be displayed. You can login using any QESTLab login credentials which are available in the database and have permission to use QESTField.

====Potential Errors====
{| class="wikitable"
!Error
!Solution
|-
|Error: "Underlying service failed to Open."
|Check the Event Viewer log. It is normally due to the QESTNET service credentials not having permission to access the QESTLab database.
|-
|Error: "No connection could be made because the target machine actively refused it 127.0.0.1:52525."
|The QESTNET service is not running. Ensure the service is running in Control Panel -> Services.
|-
|Error: "A project with an Output Type of Class Library cannot be started directly."
|Right-click the project "QESTField" in the Solution Explorer and select "Set as StartUp Project"
|-
|When you log into QESTField, an AJAX error message is sent with the title: "The filestore directory does not exist: C:\NEEDSTOEXIST"
|This directory is the storage location QESTField will use. To change the directory, edit the following line in the app.config file for the project QESTNET.Service\QESTNET:
:<add key="fileStorePath" value="C:\NEEDSTOEXIST" />
Then, rebuild QESTNET.Service and restart the QESTNET service.
|
|-
|When you log into QESTField, an AJAX error message is sent with the title: "The filestore directory does not exist: C:\NEEDSTOEXIST"
|This directory is the storage location QESTField will use. To change the directory, edit the following line in the app.config file for the project QESTNET.Service\QESTNET:
:<add key="fileStorePath" value="C:\NEEDSTOEXIST" />
Then, rebuild QESTNET.Service and restart the QESTNET service.
|}

File:ConcreteSampelAS.PNG

2015-04-07T03:36:37Z

Iresha.jayasekara:

File:Email for QestLab Invoicing.png

2015-04-07T02:01:19Z

Iresha.jayasekara: