QESTonline - User contributions [en]

Template:QEST Platform 4.6.3051

2018-05-11T06:58:02Z

Stephen.riddell:

==QEST Platform 4.6.3051==
{| class="wikitable"
! Key !! Release Notes
|-
| QPM-1709 || "Relative Compaction" (AS 1289.5.4.1) test is now "Compaction Control Test-Dry Density Ratio, moisture variation and moisture ratio" (AS 1289.5.4.1) to align with Australian Standards
|-
| QPM-1854 || Assigned Maximum Dry Density test now uses the correct tolerance for OMC in accordance with the standard (1289.5.4.2)
|-
| QPM-1867 || QESTField Scheduler no longer fails to load technicians when attempting to use a laboratory with no field technicians.
|-
| QPM-1875 || External documents (printable worksheets, dynamic worksheets, external test reports, etc) no longer make use of long-lived record-sets. This helps to avoid a situation where a database transaction would be committed or rolled back while the record set is still in use, resulting in an error message "Catastrophic Failure".

Note that there are still other situations in QESTLab where this same error is known to occur, specifically QPM-1578, which can occur on some test screens if the screen is unloaded while the contents of dropdown list is loading.
|-
| QPM-1879 || The QESTField Start Curing Workflow for now uses the QESTLab Non Standard Curing Reasons list for its non standard curing reason selection for Australian Concrete Samples.
|-
| QPM-1882 || Reduced maximum density screens (1289.5.1.1 & 1289.5.2.1) are now able to be used in Assigned Maximum Density (AS 1289.5.4.2) calculations.
|}

Template:QEST Platform 4.5.3017

2018-04-09T03:39:20Z

Stephen.riddell:

==QEST Platform 4.5.3017==

{| class="wikitable"
! Issue key !! Release Notes
|-
| QPM-1737 || An issue that caused some concrete test reports to contain an extra page with no content has been fixed.
|-
| QPM-1752 || An issue, where the dropdown boxes with format "Yes;No" or "True;False" on reduced test screens did not work, has been fixed
|-
| QPM-1755 || An issue, where the MPUV phase of Concrete Sample workflow could not be loaded in QESTField, has been fixed.
|-
| QPM-1784 || A bug that could cause scheduler to be unable to load technicians under some circumstances has been fixed.
|-
| QPM-1791 || The missing table headers on Dry Density Ratio Report (18996) has been fixed.
|-
| QPM-1802 || A debugging equipment interface driver, 'DUMMY_COMPACTION', is now available for equipment Compression Machines.
|-
| QPM-1803 || A bug that caused out of specification concrete specimens not to set their sample to out of specification has been fixed.
|-
| QPM-1818 || An issue where users could not add aggregate type, cementitious material and admixture on Batch Plant Inspection workflow has been fixed.
|}

QEST Platform 4.5.3017

2018-04-09T03:38:09Z

Stephen.riddell:

QEST Platform 4.5.3017

2018-04-09T03:37:25Z

Stephen.riddell:

==QEST Platform 4.5.3017==

{| class="wikitable"
! Issue key !! Summary !! Release Notes
|-
| QPM-1737 || An issue that caused some concrete test reports to contain an extra page with no content has been fixed.
|-
| QPM-1752 || An issue, where the dropdown boxes with format "Yes;No" or "True;False" on reduced test screens did not work, has been fixed
|-
| QPM-1755 || An issue, where the MPUV phase of Concrete Sample workflow could not be loaded in QESTField, has been fixed.
|-
| QPM-1784 || A bug that could cause scheduler to be unable to load technicians under some circumstances has been fixed.
|-
| QPM-1791 || The missing table headers on Dry Density Ratio Report (18996) has been fixed.
|-
| QPM-1802 || A debugging equipment interface driver, 'DUMMY_COMPACTION', is now available for equipment Compression Machines.
|-
| QPM-1803 || A bug that caused out of specification concrete specimens not to set their sample to out of specification has been fixed.
|-
| QPM-1818 || An issue where users could not add aggregate type, cementitious material and admixture on Batch Plant Inspection workflow has been fixed.
|}

QEST Platform 4.5.3017

2018-04-09T01:24:12Z

Stephen.riddell:

==QEST Platform 4.5.3017==

{| class="wikitable"
! Issue key !! Summary !! Release Notes
|-
| QPM-1737 || Concrete Test Report displays extra blank page || An issue that caused some concrete test reports to contain an extra page with no content has been fixed.
|-
| QPM-1752 || Reduced entry screen dropdown (Yes/No) || An issue, where the dropdown boxes with format "Yes;No" or "True;False" on reduced test screens did not work, has been fixed
|-
| QPM-1755 || Unable to progress past MPUV screen in QESTField || An issue, where the MPUV phase of Concrete Sample workflow could not be loaded in QESTField, has been fixed.
|-
| QPM-1784 || Scheduler - Error Fetching Technicians: Cannot Read Property 'name' of undefined || A bug that could cause scheduler to be unable to load technicians under some circumstances has been fixed.
|-
| QPM-1791 || DDR Report ID 18993 Section Headers Missing || The missing table headers on Dry Density Ratio Report (18996) has been fixed.
|-
| QPM-1802 || Provide a debugging equipment interface driver || A debugging equipment interface driver, 'DUMMY_COMPACTION', is now available for equipment Compression Machines.
|-
| QPM-1803 || QestStatusFlags do not seem to be updating on Concrete Specimens || A bug that caused out of specification concrete specimens not to set their sample to out of specification has been fixed.
|-
| QPM-1818 || QESTNET Error parsing null unit, with default supplied. || An issue where users could not add aggregate type, cementitious material and admixture on Batch Plant Inspection workflow has been fixed.
|}

QEST Platform 4.5.3017

2018-04-09T01:23:50Z

Stephen.riddell:

==QEST Platform 4.5.3017==

{| class="wikitable"
! Issue key !! Summary !! Release Notes
|-
| QPM-1737 || Concrete Test Report displays extra blank page || An issue that caused some concrete test reports to contain an extra page with no content has been fixed.
|-
| QPM-1752 || Reduced entry screen dropdown (Yes/No) || An issue, where the dropdown boxes with format â€œYes;Noâ€ or "True;False" on reduced test screens did not work, has been fixed
|-
| QPM-1755 || Unable to progress past MPUV screen in QESTField || An issue, where the MPUV phase of Concrete Sample workflow could not be loaded in QESTField, has been fixed.
|-
| QPM-1784 || Scheduler - Error Fetching Technicians: Cannot Read Property 'name' of undefined || A bug that could cause scheduler to be unable to load technicians under some circumstances has been fixed.
|-
| QPM-1791 || DDR Report ID 18993 Section Headers Missing || The missing table headers on Dry Density Ratio Report (18996) has been fixed.
|-
| QPM-1802 || Provide a debugging equipment interface driver || A debugging equipment interface driver, 'DUMMY_COMPACTION', is now available for equipment Compression Machines.
|-
| QPM-1803 || QestStatusFlags do not seem to be updating on Concrete Specimens || A bug that caused out of specification concrete specimens not to set their sample to out of specification has been fixed.
|-
| QPM-1818 || QESTNET Error parsing null unit, with default supplied. || An issue where users could not add aggregate type, cementitious material and admixture on Batch Plant Inspection workflow has been fixed.
|}

QEST Platform 4.5.3017

2018-04-09T01:23:31Z

Stephen.riddell:

==QEST Platform 4.5.3017==

{| class="wikitable"
! Issue key !! Summary !! Custom field (Release Notes)
|-
| QPM-1737 || Concrete Test Report displays extra blank page || An issue that caused some concrete test reports to contain an extra page with no content has been fixed.
|-
| QPM-1752 || Reduced entry screen dropdown (Yes/No) || An issue, where the dropdown boxes with format â€œYes;Noâ€ or "True;False" on reduced test screens did not work, has been fixed
|-
| QPM-1755 || Unable to progress past MPUV screen in QESTField || An issue, where the MPUV phase of Concrete Sample workflow could not be loaded in QESTField, has been fixed.
|-
| QPM-1784 || Scheduler - Error Fetching Technicians: Cannot Read Property 'name' of undefined || A bug that could cause scheduler to be unable to load technicians under some circumstances has been fixed.
|-
| QPM-1791 || DDR Report ID 18993 Section Headers Missing || The missing table headers on Dry Density Ratio Report (18996) has been fixed.
|-
| QPM-1802 || Provide a debugging equipment interface driver || A debugging equipment interface driver, 'DUMMY_COMPACTION', is now available for equipment Compression Machines.
|-
| QPM-1803 || QestStatusFlags do not seem to be updating on Concrete Specimens || A bug that caused out of specification concrete specimens not to set their sample to out of specification has been fixed.
|-
| QPM-1818 || QESTNET Error parsing null unit, with default supplied. || An issue where users could not add aggregate type, cementitious material and admixture on Batch Plant Inspection workflow has been fixed.
|}

QESTNET.Upgrade Internal:Creating Build 1.0

2017-07-04T06:38:36Z

Stephen.riddell:

==QESTNET.Upgrade 1.0 Release Build Process (Fugro 4.0)==

'''''This content is now somewhat outdated. The scripts for qestnet.upgrade and the executable have been separated. The manifest file in the qestnet database should be manually updated with the required database version (increment for each release). The application files can be reused from any previous release, or rebuilt from the qestnet.upgrade repository until the new scriptrunner is publicly released. The database upgrade scripts and manifest can be produced in one convenient (if confusingly named) zip file from the Legacy Qestnet Database Script Packages project. The specific instructions should be updated by someone who goes through the whole process.'''''

<ol>
<li>Checkout the approriate branch for the build from qestnet.upgrade repository. E.g. fugro-dbb.</li>
<li>Ensure the branch is at the current origin head and all required commits for the build are present.</li>
<li>Update the build parameter in '''package_development.bat''' and '''package_release.bat''' in the root directory with the new build version number. E.g.,
<blockquote>C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe build.proj /t:SetVersion;RebuildAll /p:Configuration=Development;MajorVersion=1;MinorVersion=0;Build='''205'''
</blockquote></li>
<li>Run '''package_release.bat'''.</li>
<li>Copy '''QESTNET.Upgrade.dll''', '''QESTNET.Upgrade.UI.exe''' and '''QESTNET.Upgrade.UI.exe.Config''' in '''~\QESTNET.Upgrade\bin\Release\''' to a temporary folder for zipping.</li>
<li>Copy the folder (and contents) '''Scripts''' in the root directory to this temporary folder.</li>
<li>Update the '''QESTNET.Upgrade.UI.exe.Config''' file to the below xml.

<blockquote><pre>
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" />
</startup>
<appSettings>
<add key="manifestPath" value="./Scripts/database_upgrade.qn.manifest" />
</appSettings>
<connectionStrings>

</connectionStrings>
</configuration>
</pre></blockquote>
</li>
<li>Zip the contents of the temporary folder and name the zip '''QESTNET.Upgrade v1.0.XXX.zip''' where XXX is the build version number.</li>
<li>Copy the zip file to '''\\adls0003\Development\Product Distribution\QESTNET.Upgrade\'''. This will make the release publicly available.</li>
<li>Commit the qestnet.upgrade branch changes to git with commit message 'Prepare release v1.0.XXX' where XXX is the build version number. The AssemblyVersion classes, database_upgrade.qn.manifest and package batch files would have changed.</li>
<li>Tag the commit with 'v1.0.XXX' where XXX is the build version number.</li>
<li>Push the commit to github.</li>
<li>Push the tag to github (tags need to be pushed explicitly).</li>
<li>Inform appropriate parties of the new release build.</li>
<li>Have a non-alcoholic beverage as this was too easy.</li>
</li>
</ol>

QESTNET.Upgrade Internal:Creating Build 1.0

2017-07-04T06:37:52Z

Stephen.riddell:

==QESTNET.Upgrade 1.0 Release Build Process (Fugro 4.0)==

'''''This content is now somewhat outdated. The scripts for qestnet.upgrade and the executable have been separated. The manifest file in the qestnet database should be manually updated with the required database version (increment for each release). The application files can be reused from any previous release, or rebuilt from the qestnet.upgrade repository until the new scriptrunner is publicly released. The database upgrade scripts and manifest can be produced in one convenient (if confusingly named) zip file from the Legacy Qestnet Database Script Packages project'''''

<ol>
<li>Checkout the approriate branch for the build from qestnet.upgrade repository. E.g. fugro-dbb.</li>
<li>Ensure the branch is at the current origin head and all required commits for the build are present.</li>
<li>Update the build parameter in '''package_development.bat''' and '''package_release.bat''' in the root directory with the new build version number. E.g.,
<blockquote>C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe build.proj /t:SetVersion;RebuildAll /p:Configuration=Development;MajorVersion=1;MinorVersion=0;Build='''205'''
</blockquote></li>
<li>Run '''package_release.bat'''.</li>
<li>Copy '''QESTNET.Upgrade.dll''', '''QESTNET.Upgrade.UI.exe''' and '''QESTNET.Upgrade.UI.exe.Config''' in '''~\QESTNET.Upgrade\bin\Release\''' to a temporary folder for zipping.</li>
<li>Copy the folder (and contents) '''Scripts''' in the root directory to this temporary folder.</li>
<li>Update the '''QESTNET.Upgrade.UI.exe.Config''' file to the below xml.

<blockquote><pre>
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" />
</startup>
<appSettings>
<add key="manifestPath" value="./Scripts/database_upgrade.qn.manifest" />
</appSettings>
<connectionStrings>

</connectionStrings>
</configuration>
</pre></blockquote>
</li>
<li>Zip the contents of the temporary folder and name the zip '''QESTNET.Upgrade v1.0.XXX.zip''' where XXX is the build version number.</li>
<li>Copy the zip file to '''\\adls0003\Development\Product Distribution\QESTNET.Upgrade\'''. This will make the release publicly available.</li>
<li>Commit the qestnet.upgrade branch changes to git with commit message 'Prepare release v1.0.XXX' where XXX is the build version number. The AssemblyVersion classes, database_upgrade.qn.manifest and package batch files would have changed.</li>
<li>Tag the commit with 'v1.0.XXX' where XXX is the build version number.</li>
<li>Push the commit to github.</li>
<li>Push the tag to github (tags need to be pushed explicitly).</li>
<li>Inform appropriate parties of the new release build.</li>
<li>Have a non-alcoholic beverage as this was too easy.</li>
</li>
</ol>

File:Release Notes 4.0.29 CRs.xlsx

2017-04-21T04:18:37Z

Stephen.riddell:

File:Release Notes 4.0.29 Bugs.xlsx

2017-04-21T04:18:03Z

Stephen.riddell:

File:Release Notes 4.0.28 CRs.xlsx

2017-04-02T09:26:17Z

Stephen.riddell:

File:Release Notes 4.0.27 CRs.xlsx

2017-03-20T07:01:10Z

Stephen.riddell:

File:Release Notes 4.0.27 Bugs.xlsx

2017-03-20T07:01:05Z

Stephen.riddell:

File:Release Notes 4.0.26 CRs.xlsx

2017-03-02T02:38:03Z

Stephen.riddell:

File:Release Notes 4.0.26 Bugs.xlsx

2017-03-02T02:34:55Z

Stephen.riddell:

QESTNET 4.0.25.1 Release Notes (hotfix)

2017-02-13T03:51:51Z

Stephen.riddell:

The 4.0.25.1 release modifies QESTNET.Custom.Fugro.DataBackbone.dll to maintain compatibility with the current release of the Fugro DataBackbone

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

|- valign="top"
|style="background:white;"|CR#3512
|style="background:white;"|GLFUG
|style="background:white;"|FUG-1201
|style="background:white;"|QESTNET
|style="background:white;"|Export test start and completion dates to fdbb
|style="background:white;"|Start and completion dates are based on the completion dates of stages. Start date is the completion of the last stage preceding the stages of the test. e.g. a material preparation stage or equipment preparation stage. If there are none of these stages, the first stage of the test is used. The completion date for the test is the completion date of the final stage of the test, before any checking or material finalisation stages.<BR>
Removes old performedAtDate from exports.

|}

File:Release Notes 4.0.25 Bugs.xlsx

2017-02-08T04:32:15Z

Stephen.riddell: