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 7 Next »

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

Customer Signup

The customer signup form currently looks like this :

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 customization available on that form.

Property Registration

The property registration form currently looks like this :

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

  • enableTenantRegistrations” Allows you to register as a tenant against a property (on by default).

  • showAddRegistrationThirdPartyAuthority” Indicates that the user signing is a third party authority (on 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 tenants.

  • If “enableAutomaticRegistrationProcessing” is set to true, then a process of automatic verification begins.

The following fields are configurable/ available as property registration fields :

  • enableTenantRegistrations”: Allows you to register as a tenant against a property (on by default)

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

  • showAddRegistrationAddress”: Show/hide address filed (not sure why anyone would ever do this – on by default)

  • showAddRegistrationSignupCode”: Show/hide the signup code (off by default)

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

  • showAddRegistrationAccountName”: Show/hide account mode (only works in account mode, off by default)

  • showAddRegistrationAccountNumber”: Show/hide account number (only works in account mode, off by default)

  • showAddRegistrationAssessmentNumber”: Show/hide assessment number (on by default)

  • showAddRegistrationCheckDigit”: Show/hide assessment check digit (off by default)

  • showAddRegistrationRateableValue”: Show/hide property valuation (on by default)

  • showAddRegistrationThirdPartyAuthority”: Indicates that the user signing is a third party authority. (on by default)

  • waterNoticeName”: The name of water notices.

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.

  • 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