Table of Contents | |
---|---|
|
Version 2.6 Upgrade
Warning | ||
---|---|---|
| ||
Bear in mind that remark codes in version 2.5 ONLY considered the Density test result. In version 2.6, the Moisture test result is also considered. Take this into consideration when deciding what to do with your legacy (version 2.5 or prior) remark codes. If you modify the business rules associated with these legacy codes, you run the risk of changing a prior test to have a code that is no longer representative of the real result. Example... Test code A was for passing density tests. If you modify test code A to be for passing density / failed moisture, that means all of your prior tests assigned to remark code A will be considered as tests with passing moisture and failed density (regardless of the actual moisture result on past test). Consideration - Consider inactivating your legacy codes as part of your deployment and starting fresh with a new set of codes. Bear in mind you now have up to 5 characters for a code and the new public code / description are the ones displayed on the report. |
Purpose
Remarks are used to provide field technicians and project managers a defined list of comments (remarks) that can be assigned to a particular test based on the results of the test. Codes will default on test records based on the business rules applied to them. Public remark codes appear on density test reports with a footnote disclosing the description of each code.
Field | Description | ||
---|---|---|---|
Test Type |
| ||
Code |
| ||
Description |
| ||
Public Code |
Info | | title | Version 2.6 Upgrade Only
Public Code will default to existing Code value Public Description |
Info | | |
| |||
Density Rule |
| ||
Moisture Rule |
|
Considerations
When defining and mapping out remark codes, consider all combinations of density and moisture test results.
...