Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

The following page contains information regarding the Customer Sign up and Property Registration process in MiWater Public.

Customer Signup

By default, the customer signup form appears as it is shown on the right.

There is an option available in settings called “showDateOfBirth”. This can be used to show or hide the “Date of Birth” field if you decide that you don’t require it. This is the only customisation available on that form.

Property Registration

By default, the property registration form appears as it is shown on the right. Your are able to show and hide a number of fields on this form in order to customise the information that users are required to provide when registering a property in the customer portal.

The following options are available within MiWater for configuration of this form:

  • “enableTenantRegistrations” Provides the option for users to register as a tenant against a property (on by default).

  • “showAddRegistrationThirdPartyAuthority” Provides the option for users to indicate that they have third party authority (on by default).

  • “waterNoticeName”: The name of water notices displayed to the user.

  • “showAddRegistrationRateableValue”: Show or hide property valuation field for the user (on by default)

  • “rateableValueName”: Used to name the above field according to its rateable value name. (“Valuation” by default)

  • “showAddRegistrationAddress”: Show or hide address field for the user (on by default)

  • “showAddRegistrationAssessmentNumber”: Show or hide assessment number for the user (on by default)

  • “showAddRegistrationSignupCode”: Show or hide the signup code for the user (off by default)

  • “showAddRegistrationMeterCode”: Show or hide the meter code for the user (off by default)

  • “showAddRegistrationCheckDigit”: Show or hide assessment check digit for the user (off by default)

  • “showAddRegistrationAccountName”: Show or hide account name for the user (only works in account mode, off by default)

  • “showAddRegistrationAccountNumber”: Show or hide account number for the user (only works in account mode, off by default)

The other configurable option is whether property registrations should be automatically processed or manually processed. This can be configured in MiWater via the system constant “enableAutomaticRegistrationProcessing”.

  • If “enableAutomaticRegistrationProcessing” is set to false, then every customer registration will need to be verified by a council staff member. The only exception is where “enableTenantRegistrations” (described above) is turned on. In these cases, the owner or agent confirms tenant access.

  • If “enableAutomaticRegistrationProcessing” is set to true, then a process of automatic verification begins. The two stages of automatic property registration are described below.

The Automatic Property Registration Process

Stage 1: MiWater checks for an exact match to the fields provided by the user.

This is a mandatory check performed on all registration requests when “enableAutomaticRegistrationProcessing” is set to true.

  • “BPay Registration Number” is matched against the “registrationSignupCode” provided in the DLT for the property that they are requesting access to.

  • “Property Number” is matched against the “assessmentNo” provided in the DLT for the property that they are requesting access to.

Stage 2: MiWater checks for a match between the user’s sign up details (name, DOB, email, phone etc) and the customer details in the DLT for the property that they are requesting access to.

This second stage check is optional and can be turned on and off via the system constant “autoApproveRegistrationCustomerRecordRequired”.

By default a “match” occurs when 2 or more of the items on the following list match what the user has entered. The number of items that constitute a match is controlled by the system constant “autoApproveRegistrationNumMatchingDataRequired”.

  • “First Name” is matched against the “customerGivenName” field provided in the DLT for the property that the user is requesting access to.

  • “Last Name” is matched against the “customerSurname” field provided in the DLT for the property that the user is requesting access to.

  • “Phone Number” is matched against the “customerHomePhone” field provided in the DLT for the property that the user is requesting access to.

  • “Mobile Number” is matched against the “customerMobilePhone” field provided in the DLT for the property that the user is requesting access to.

  • “Email Address” is matched against the “customerEmail” field provided in the DLT for the property that the user is requesting access to.

  • “Date of Birth” (if enabled via “showDateOfBirth” mentioned above) is matched against the “dateOfBirth” field provided in the DLT for the property that the user is requesting access to.

NOTE: If this second stage is enabled then the quality of your customer data within the DLT needs to be fairly high. At this point in time, MWRC has not provided phone, mobile, email or date of birth details within the tblCustomers tab of the DLT, so the only fields that we would be able to match on would be first name and last name.

If the user’s registration can not be processed automatically then it will be put into a queue of requests for manual verification.

  • No labels

© Tyeware Pty Ltd 2019