SYSTEM UPDATES

External Survey Release Notes for 2.9 release – 11 June 2007

MAR 796 - Disable Accredited/Non Accredited field in CRV_S03
MAR 1079 - Trap errors caused by User modifications in Plan Gen
MAR 1088 - Hide some traverse observations in Plan Gen Layout
MAR 1182 - Prevent capture of Unit Stage in certain conditions
MAR 1184 - Prevent Invalid characters in Plan Generation
MAR 1198 - Default 'Auto Refresh' to 'OFF' in the Capture Spatial Window
MAR 1199 - Change default Map Layer properties in Plan Generation
MAR 1201 - Display Existing Parcel Appellations in the Plan Layout Sheet Window
MAR 1205 - Truncate Bearing Only or Distance Only Observations
TPR 6819 - Icon change in Spatial Capture Window
TPR 6191 - Importing XML files with Replaced Marks captured
TPR 6213 - Plan Compilation Messages being deleted
TPR 6457 - Message 9005 Error Number 35 in Plan Generation
Remedy Call#525525 - Modified Certificates - Sec 224(f) Resource Management Act
Remedy Call#532243 - Modified Certificates - Sec 223 Resource Management Act

MAR 796 – Disable Accredited/Non Accredited field in CRV_S03

MAR 796 Description	Disable Accredited/Non Accredited field in CRV_S0
MAR 796 Explanation	Previously there was a mandatory field in CSL_S02 – Manage Survey Transaction screen that required the Lodging Surveyor to select Accredited or Non Accredited in the Survey Accredited field. Presently the surveyor status Non Accredited is invalid. The Surveyor Accredited field in CSL_S02 – Manage survey Transaction screen has been disabled. The entry in this field will default to 'Accredited'. No action is required of the Lodging Surveyor.

MAR 796 Description

Disable Accredited/Non Accredited field in CRV_S0

MAR 796 Explanation

Previously there was a mandatory field in CSL_S02 – Manage Survey Transaction screen that required the Lodging Surveyor to select Accredited or Non Accredited in the Survey Accredited field. Presently the surveyor status Non Accredited is invalid.

The Surveyor Accredited field in CSL_S02 – Manage survey Transaction screen has been disabled. The entry in this field will default to 'Accredited'. No action is required of the Lodging Surveyor.

MAR 1079 – Trap errors caused by User modifications in Plan Gen

MAR 1079 Description	Trap errors caused by User modifications in Plan Gen
MAR 1079 Explanation	Previously, where users had made modifications to Plan Gen Diagrams to create invalid line shapes, the Plan Generation Layout Window would not open. Examples of this are where a user, in Layout Sheets, has distorted a line so that it has self intersected or they have placed an end co-ordinate over a start co-ordinate in an endeavour to hide a system generated line. Such actions have become commonplace and are difficult for LINZ to investigate and resolve. The application has been changed to simply trap the Spatial data blade errors and allow the layout window to open even where self intersecting lines exist. No error will be reported to the user. Invalid shapes may reflect adversely on the graphical presentation of distorted diagrams but the correct digital data will have been recorded in Landonline.

MAR 1079 Description

Trap errors caused by User modifications in Plan Gen

MAR 1079 Explanation

Previously, where users had made modifications to Plan Gen Diagrams to create invalid line shapes, the Plan Generation Layout Window would not open. Examples of this are where a user, in Layout Sheets, has distorted a line so that it has self intersected or they have placed an end co-ordinate over a start co-ordinate in an endeavour to hide a system generated line.

Such actions have become commonplace and are difficult for LINZ to investigate and resolve.

The application has been changed to simply trap the Spatial data blade errors and allow the layout window to open even where self intersecting lines exist. No error will be reported to the user.

Invalid shapes may reflect adversely on the graphical presentation of distorted diagrams but the correct digital data will have been recorded in Landonline.

MAR 1088 - Hide some traverse observations in Plan Gen Layout

MAR 1088 Description	Hide some traverse observations in Plan Gen Layout
MAR 1088 Explanation	Users have complained of unnecessary 'clutter' caused particularly by GPS vectors in Plan Capture. Often multiple fixes of boundary and traverse mark positions are recorded in the traverse boundary capture list while it may not be appropriate to display all of these in Plan Layout. A new 'Exc' (exclude observation from Plan Gen) checkbox has been provided in the observation list of Traverse Boundary Capture screen to allow exclusion of Traverse (layer 0) observation types. The checkbox is not available for any other layer. The checkbox entry will default to unticked for each observation. Any observations selected using this feature will be excluded from the Layout data but will remain present in the Traverse Boundary Observation list and in the Spatial Capture window.

MAR 1088 Description

Hide some traverse observations in Plan Gen Layout

MAR 1088 Explanation

Users have complained of unnecessary 'clutter' caused particularly by GPS vectors in Plan Capture. Often multiple fixes of boundary and traverse mark positions are recorded in the traverse boundary capture list while it may not be appropriate to display all of these in Plan Layout.

A new 'Exc' (exclude observation from Plan Gen) checkbox has been provided in the observation list of Traverse Boundary Capture screen to allow exclusion of Traverse (layer 0) observation types. The checkbox is not available for any other layer.

The checkbox entry will default to unticked for each observation.

Any observations selected using this feature will be excluded from the Layout data but will remain present in the Traverse Boundary Observation list and in the Spatial Capture window.

MAR 1182 - Prevent capture of Unit Stage in certain conditions

MAR 1182 Description	Prevent capture of Unit Stage in certain conditions
MAR 1182 Explanation	The process developed within Landonline to manage the numbering of successive stages of a staged unit development was one of the most complicated parts in the building of Landonline. Physically it is possible to lodge an e-survey in Landonline with a plan referenced to a unit development that contains a pre-landonline number but Landonline was not designed to manage a combination of plan lodgement types (paper and e-survey) for a staged unit development. The "Previous Stage" field however was not designed to block plan references that precede 300000. Once a unit development has commenced with a particular lodgement type, the development was expected to be completed using the same lodgement type for all of the subsequent stages. The only way to change this requirement was to start a new development lodging new PUD and 1st stage plans. Survey conversion did not include the back capture of aspatial parcels associated to Unit Developments. Landonline simply recorded a plan label in the Spatial View. Currently, when a Unit Development Stage, with a plan reference that precedes 300000 is lodged, LINZ will back capture, (WIP) the previous stages prior to lodgement in order to process the new survey. This WIP action by LINZ remains a requirement even when a surveyor elects to Capture the survey using e-survey. This Enhancement will run a business rule to check that for a subsequent stage or redevelopment, the preceding or base plan has been captured in Landonline. If it has not been captured, a message instructs the surveyor to contact LINZ to request that a WIP action be completed. The new stage (or redevelopment) will not Submit until a WIP action has been completed. South Auckland Staged Unit plans have an additional factor to that already outlined. The South Auckland plans numbered <300,000 have a prefix of S, e.g. DPS 299999. When a subsequent stage or redevelopment unit plan is lodged, LINZ staff will temporarily remove the base plan prefix 'S'. The new plan is lodged, then the S is replaced after Deposit. This is a LINZ internal process that must remain. This Enhancement provides an additional business rule for South Auckland Unit plans numbered <300,000. The message to the surveyor is to contact LINZ to arrange for the predecessor activity to take place. LINZ will then manage the process and advise the customer action. If one or more of the previous stages has not been WIP'd or is Lodged in the incorrect order, serious repercussions may result. The Deposit of the survey may be delayed, if not prevented, from proceeding. Deposit of subsequent stages will also be affected. Utmost care is recommended when dealing with Unit plans of this nature.

MAR 1182 Description

Prevent capture of Unit Stage in certain conditions

MAR 1182 Explanation

The process developed within Landonline to manage the numbering of successive stages of a staged unit development was one of the most complicated parts in the building of Landonline.

Physically it is possible to lodge an e-survey in Landonline with a plan referenced to a unit development that contains a pre-landonline number but Landonline was not designed to manage a combination of plan lodgement types (paper and e-survey) for a staged unit development.

The "Previous Stage" field however was not designed to block plan references that precede 300000.

Once a unit development has commenced with a particular lodgement type, the development was expected to be completed using the same lodgement type for all of the subsequent stages. The only way to change this requirement was to start a new development lodging new PUD and 1st stage plans.

Survey conversion did not include the back capture of aspatial parcels associated to Unit Developments. Landonline simply recorded a plan label in the Spatial View. Currently, when a Unit Development Stage, with a plan reference that precedes 300000 is lodged, LINZ will back capture, (WIP) the previous stages prior to lodgement in order to process the new survey. This WIP action by LINZ remains a requirement even when a surveyor elects to Capture the survey using e-survey.

This Enhancement will run a business rule to check that for a subsequent stage or redevelopment, the preceding or base plan has been captured in Landonline. If it has not been captured, a message instructs the surveyor to contact LINZ to request that a WIP action be completed. The new stage (or redevelopment) will not Submit until a WIP action has been completed.

South Auckland Staged Unit plans have an additional factor to that already outlined. The South Auckland plans numbered <300,000 have a prefix of S, e.g. DPS 299999. When a subsequent stage or redevelopment unit plan is lodged, LINZ staff will temporarily remove the base plan prefix 'S'. The new plan is lodged, then the S is replaced after Deposit. This is a LINZ internal process that must remain.

This Enhancement provides an additional business rule for South Auckland Unit plans numbered <300,000. The message to the surveyor is to contact LINZ to arrange for the predecessor activity to take place. LINZ will then manage the process and advise the customer action.

If one or more of the previous stages has not been WIP'd or is Lodged in the incorrect order, serious repercussions may result. The Deposit of the survey may be delayed, if not prevented, from proceeding. Deposit of subsequent stages will also be affected.

Utmost care is recommended when dealing with Unit plans of this nature.

MAR 1184 - Prevent Invalid characters in Plan Generation

MAR 1184 Description	Prevent Invalid characters in Plan Generation
MAR 1184 Explanation	This enhancement will prevent the use of certain invalid characters in Plan Layout. Numerous production calls have been raised because users have been prevented from opening the Layout Sheets due to the presence of invalid characters entered in Layout Sheets. These are termed invalid characters because they are commonly utilised for specific purposes in software coding. The system will now show a message to users, when saving their Plan Layout Sheets, if invalid characters have been used. Message 126036 appears: In order for the Layout sheets to be saved, or plans to be generated, the user must remove the invalid characters from the Layout Sheets. The invalid characters that have been identified are: Alt 248 = ° Alt 0176 = ° Alt 0186 = ° (not apparent here but appears with an underscore in Plan Gen.) Alt 253 = ² Alt 0178 = ². It should also be noted that aside from the requirement not to use Alt 253 or Alt 0178, all areas must be recorded in decimals of a Hectare. The absence of the availability of a degree symbol (°) should not present a problem if occupation diagrams requiring the addition of non-captured bearings are added as Supporting documents. User added bearings should not be added to a layout sheet because these are system generated from capture. If they are not present on the diagram being laid out then either the wrong diagram is being used or the bearing is not required for that diagram.

MAR 1184 Description

Prevent Invalid characters in Plan Generation

MAR 1184 Explanation

This enhancement will prevent the use of certain invalid characters in Plan Layout. Numerous production calls have been raised because users have been prevented from opening the Layout Sheets due to the presence of invalid characters entered in Layout Sheets. These are termed invalid characters because they are commonly utilised for specific purposes in software coding.

The system will now show a message to users, when saving their Plan Layout Sheets, if invalid characters have been used.

Message 126036 appears:

In order for the Layout sheets to be saved, or plans to be generated, the user must remove the invalid characters from the Layout Sheets.

The invalid characters that have been identified are:

Alt 248 = °
Alt 0176 = °
Alt 0186 = ° (not apparent here but appears with an underscore in Plan Gen.)
Alt 253 = ²
Alt 0178 = ².

It should also be noted that aside from the requirement not to use Alt 253 or Alt 0178, all areas must be recorded in decimals of a Hectare.

The absence of the availability of a degree symbol (°) should not present a problem if occupation diagrams requiring the addition of non-captured bearings are added as Supporting documents.

User added bearings should not be added to a layout sheet because these are system generated from capture. If they are not present on the diagram being laid out then either the wrong diagram is being used or the bearing is not required for that diagram.

MAR 1198 – Default 'Auto Refresh' to 'OFF' in the Capture Spatial Window

MAR 1198 Description	Default 'Auto Refresh' to 'OFF' in the Capture Spatial Window
MAR 1198 Explanation	Previously when the CSC_S10 - Spatial Display was opened it would default to 'Auto Refresh'. This default has a tendency to slow the Spatial refresh process by refreshing every open window each time an edit is made. Many users have chosen to turn 'Auto Refresh' off to help speed up the process. When the CSC_S10 - Spatial Display is first opened and the Capture option is selected from the toolbar, Refresh options will not be ticked. While the Spatial Display remains in focus, any edits made to the Traverse Boundary Capture, Mark Capture or Parcel Capture Screens will not be reflected spatially until the user has actions a deliberate Refresh or had pre selected Auto-Refresh before implementing the edits. If the Spatial Display is not in focus when data edits are made, restoring the focus will initiate a Spatial Display Refresh. N.B. Right mouse click menu options will not respond unless the Spatial Display has been brought into focus.

MAR 1198 Description

Default 'Auto Refresh' to 'OFF' in the Capture Spatial Window

MAR 1198 Explanation

Previously when the CSC_S10 - Spatial Display was opened it would default to 'Auto Refresh'. This default has a tendency to slow the Spatial refresh process by refreshing every open window each time an edit is made. Many users have chosen to turn 'Auto Refresh' off to help speed up the process.

When the CSC_S10 - Spatial Display is first opened and the Capture option is selected from the toolbar, Refresh options will not be ticked.

While the Spatial Display remains in focus, any edits made to the Traverse Boundary Capture, Mark Capture or Parcel Capture Screens will not be reflected spatially until the user has actions a deliberate Refresh or had pre selected Auto-Refresh before implementing the edits.

If the Spatial Display is not in focus when data edits are made, restoring the focus will initiate a Spatial Display Refresh.

N.B. Right mouse click menu options will not respond unless the Spatial Display has been brought into focus.

MAR 1199 – Change default Map Layer properties in Plan Generation

MAR 1199 Description	Change default Map Layer properties in Plan Generation
MAR 1199 Explanation	A change has been made in Plan Generation – Define Diagrams to default layer labelling to 'OFF'. Only the labelling layers are affected. This will ensure that the Spatial Window opens faster. Screenshot 1 Only the Road Name labels and the existing parcel boundaries will appear by default when the Define Diagrams window is opened.

MAR 1201 – Display Existing Parcel Appellations in the Plan Layout Sheet Window

MAR 1201 Description	Display Existing Parcel Appellations in the Plan Layout Sheet Window
MAR 1201 Explanation	In the Maintain Diagrams Layers of Plan Gen there is a Layer within the 'Available Layers list named 'Existing Parcels'. When a user selects 'Existing Parcels and adds to the Selected Layers, the underlying and abutting parcel boundaries and appellations will display in the Layout sheets. Users do not always wish to show this layer, preferring to manually add abutting boundary lines because of apparent distortion. Currently, If the layer is not selected, appellations will not display. This enhancement allows display of existing appellations without showing existing parcel boundary lines. The Existing Parcels layer, when added to the Selected Layers column, now shows a new checkbox to the right. The new checkbox is called 'Feature'. The checkbox 'Label' if checked (ticked) will mean that the existing parcel labels will appear in Layout Sheets. This can be unchecked if existing parcel labels are not required on Layout Sheets. The checkbox 'Feature' if checked (ticked) will mean that the existing parcel boundary lines will appear in Layout Sheets. This can be unchecked if existing parcel boundary lines are not required on Layout Sheets. This will allow manually drawn abuttal lines in Define Diagram to be used. A new 'Feature' checkbox column now appears in the Maintain Diagram Layers screen:

MAR 1201 Description

Display Existing Parcel Appellations in the Plan Layout Sheet Window

MAR 1201 Explanation

In the Maintain Diagrams Layers of Plan Gen there is a Layer within the 'Available Layers list named 'Existing Parcels'. When a user selects 'Existing Parcels and adds to the Selected Layers, the underlying and abutting parcel boundaries and appellations will display in the Layout sheets.

Users do not always wish to show this layer, preferring to manually add abutting boundary lines because of apparent distortion. Currently, If the layer is not selected, appellations will not display.

This enhancement allows display of existing appellations without showing existing parcel boundary lines. The Existing Parcels layer, when added to the Selected Layers column, now shows a new checkbox to the right. The new checkbox is called 'Feature'.

The checkbox 'Label' if checked (ticked) will mean that the existing parcel labels will appear in Layout Sheets. This can be unchecked if existing parcel labels are not required on Layout Sheets.

The checkbox 'Feature' if checked (ticked) will mean that the existing parcel boundary lines will appear in Layout Sheets. This can be unchecked if existing parcel boundary lines are not required on Layout Sheets. This will allow manually drawn abuttal lines in Define Diagram to be used.

A new 'Feature' checkbox column now appears in the Maintain Diagram Layers screen:

MAR 1205 – Truncate Bearing Only or Distance Only Observations

MAR 1205 Description	Truncate Bearing Only or Distance Only Observations
MAR 1205 Explanation	In Define Diagrams, when a single entity observation was captured (i.e. bearing or distance only), the System Generated Diagram would take its extents to where that distant point lies spatially. This could be some distance from the actual body of the survey. When the spatial window opened, the area of primary interest might appear as a black blob. This enhancement has been introduced to change the way that the System Generated Survey Diagram is defined in Define Diagrams. The calculated extent of the System Generated Diagram will be based only on observations that comprise both bearing and distance dimensions. Any observation of a single dimension will truncate automatically when the System Generated Survey Traverse Diagram is opened in the Layout Plan Sheet. The extent of the initial display in the Define Diagrams window will reflect the extent of the System Generated Survey Traverse Diagram. i.e The traditional pecked blue line will display the limits to which the diagram will extend. Where there is no System Generated Survey Traverse Diagram, the extents of the System Generated Non-Primary Diagram will be used. Screenshot 1 The System Generated Survey Traverse Diagram displays the true extent of observations. The pecked Blue line defines the extent to which the diagram will appear in the Layout Plan Sheet. Screenshot 2 The Layout Plan Sheet displaying the System Generated Survey Traverse Diagram with the bearing and distance only traverse observations truncated.

MAR 1205 Description

Truncate Bearing Only or Distance Only Observations

MAR 1205 Explanation

In Define Diagrams, when a single entity observation was captured (i.e. bearing or distance only), the System Generated Diagram would take its extents to where that distant point lies spatially. This could be some distance from the actual body of the survey. When the spatial window opened, the area of primary interest might appear as a black blob.

This enhancement has been introduced to change the way that the System Generated Survey Diagram is defined in Define Diagrams. The calculated extent of the System Generated Diagram will be based only on observations that comprise both bearing and distance dimensions. Any observation of a single dimension will truncate automatically when the System Generated Survey Traverse Diagram is opened in the Layout Plan Sheet.

The extent of the initial display in the Define Diagrams window will reflect the extent of the System Generated Survey Traverse Diagram. i.e The traditional pecked blue line will display the limits to which the diagram will extend.

Where there is no System Generated Survey Traverse Diagram, the extents of the System Generated Non-Primary Diagram will be used.

Screenshot 1
The System Generated Survey Traverse Diagram displays the true extent of observations. The pecked Blue line defines the extent to which the diagram will appear in the Layout Plan Sheet.

Screenshot 2
The Layout Plan Sheet displaying the System Generated Survey Traverse Diagram with the bearing and distance only traverse observations truncated.

TPR 6819 – Icon change in Spatial Capture Window

TPR 6819 Description	Icon change in Spatial Capture Window
TPR 6819 Explanation	Due to an upgrade to Power Builder application, there is a slight difference in the Spatial Capture Window for internal and external users when performing Parcel Linking. When linking parcels at capture a 'Continue' icon appears at the top of the window. This was shown as a thin black sharply pointed arrow head. This icon now appears as a fat green softly rounded arrow head.

TPR 6191 – Importing XML files with Replaced Marks captured

TPR 6191 Description	Importing XML files with Replaced Marks captured
TPR 6191 Explanation	When XML files are imported, and contain Replaced/Disturbed marks, the functionality is not being completed in Landonline after the data is imported. The user has to manually go and edit these marks in the Mark Detail screen and complete the Mark Reliability Details correctly. These marks should also not be linked spatially (have a box around the mark). Now, when a surveyor provides the following information in their XML import file, all the Mark Reliability Details information will be correctly filled out and the user does not have to manually do anything more to these marks. For Replaced Marks: The XML import file will expect a Mark Id in the 'replacedMonument' attribute of the 'SurveyMonument' element. NOTE: Mark Id = oID of the monument element found in the Extracted XML file from Landonline <SurveyMonument mntRef="PEG (9) DP 31775" purpose="boundary" state="replaced" replacedMonument="25206216" replacedDate="2005-04-02" replacedAnnotation="testing the XML replaced functionality" /> For Disturbed Marks: The XML import file will expect a Mark Id in the 'disturbedMonument' attribute of the 'SurveyMonument' element. <SurveyMonument mntRef="PEG (7) DP 36755" purpose="traverse" state="disturbed" disturbedMonument="25208631" disturbedDate="2005-04-01" disturbedAnnotation="testing the XML disturbed functionality" /> In addition, for a given 'SurveyMonument' element, the 'replacedMonument' and 'disturbedMonument' attributes cannot both be populated. If they are both populated for a given 'SurveyMonument' then an error message upon import will occur stating this.

TPR 6191 Description

Importing XML files with Replaced Marks captured

TPR 6191 Explanation

When XML files are imported, and contain Replaced/Disturbed marks, the functionality is not being completed in Landonline after the data is imported. The user has to manually go and edit these marks in the Mark Detail screen and complete the Mark Reliability Details correctly. These marks should also not be linked spatially (have a box around the mark).

Now, when a surveyor provides the following information in their XML import file, all the Mark Reliability Details information will be correctly filled out and the user does not have to manually do anything more to these marks.

For Replaced Marks: The XML import file will expect a Mark Id in the 'replacedMonument' attribute of the 'SurveyMonument' element.

NOTE: Mark Id = oID of the monument element found in the Extracted XML file from Landonline

<SurveyMonument mntRef="PEG (9) DP 31775" purpose="boundary" state="replaced" replacedMonument="25206216" replacedDate="2005-04-02" replacedAnnotation="testing the XML replaced functionality" />

For Disturbed Marks:
The XML import file will expect a Mark Id in the 'disturbedMonument' attribute of the 'SurveyMonument' element.

<SurveyMonument mntRef="PEG (7) DP 36755" purpose="traverse" state="disturbed" disturbedMonument="25208631" disturbedDate="2005-04-01" disturbedAnnotation="testing the XML disturbed functionality" />

In addition, for a given 'SurveyMonument' element, the 'replacedMonument' and 'disturbedMonument' attributes cannot both be populated. If they are both populated for a given 'SurveyMonument' then an error message upon import will occur stating this.

TPR 6213 – Plan Compilation Messages being deleted

TPR 6213 Description	Plan Compilation Messages being deleted
TPR 6213 Explanation	When details for the Surveyor and Primary Contact are entered into the CSL_S02 Manage Survey Transaction screen, and these are two different people, it was identified that if one of these users deleted a Plan Compilation Message from their 'My Messages' in Workspace, it also deleted the same Plan Compilation Message from the other users 'My Messages'. Now, when the Surveyor and Primary Contact details are entered and if they are two different people and one person deletes Plan Compilation Messages from their 'My Messages', messages will remain in the other users 'My Messages'.

TPR 6213 Description

Plan Compilation Messages being deleted

TPR 6213 Explanation

When details for the Surveyor and Primary Contact are entered into the CSL_S02 Manage Survey Transaction screen, and these are two different people, it was identified that if one of these users deleted a Plan Compilation Message from their 'My Messages' in Workspace, it also deleted the same Plan Compilation Message from the other users 'My Messages'.

Now, when the Surveyor and Primary Contact details are entered and if they are two different people and one person deletes Plan Compilation Messages from their 'My Messages', messages will remain in the other users 'My Messages'.

TPR 6457 – Message 9005 Error Number 35 in Plan Generation

TPR 6457 Description	Message 9005 Error Number 35 in Plan Generation
TPR 6457 Explanation	This error message was raised from a Production call (Remedy parent call 475833). When users were saving edits in their Layout sheets they constantly received this message. When the users closed the message down, Landonline also closed down and all edits were lost. A fix has been introduced into this release. Users should now be able to save their Layout Sheets without any further problems.

Remedy Call#525525 – Modified Certificates - Sec 224(f) Resource Management Act

Remedy Call#525525 Description	Modified Certificates - Sec 224(f) Resource Management Act
Remedy Call#525525 Explanation	Some users have reported that the online TA-cert wording for the Sec 224(f) certificate was out of date. Both options were included in CSL_S07a – Manage TA Certification screen, the screen has been modified to make the options more apparent. Though ..."the provisions of the building code specified in Section 46(4) of the Building Act 1991" is superceded by ...."the provisions of the building code specified in Section 116A of the Building Act 2004", there may be outstanding Certifications whereby the Building Act 1991 certification remains appropriate. For this reason both certificates remain available for selection from the All Certificates list. The Names of the Certificates have been enhanced to make them more apparent. i.e. 224(f)-1991 and 224(f)-2004.

Remedy Call#525525 Description

Modified Certificates - Sec 224(f) Resource Management Act

Remedy Call#525525 Explanation

Some users have reported that the online TA-cert wording for the Sec 224(f) certificate was out of date. Both options were included in CSL_S07a – Manage TA Certification screen, the screen has been modified to make the options more apparent.

Though ..."the provisions of the building code specified in Section 46(4) of the Building Act 1991" is superceded by ...."the provisions of the building code specified in Section 116A of the Building Act 2004", there may be outstanding Certifications whereby the Building Act 1991 certification remains appropriate.

For this reason both certificates remain available for selection from the All Certificates list. The Names of the Certificates have been enhanced to make them more apparent. i.e. 224(f)-1991 and 224(f)-2004.

Remedy Call#532243 – Modified Certificates - Sec 223 Resource Management Act

Remedy Call#532243 Description	Modified Certificates - Sec 223 Resource Management Act
Remedy Call#532243 Explanation	The Section 224(c)NC Certificate has been withdrawn and has been replaced with Section 223NC Certificate. The 224(c)NC certification was creating issues for some customers in some Territorial Authorities. After discussions with the RGL it was decided that a new certificate should be created and correctly refer to Sec 223.