Registration (sign-up) page

The registration page of the web-app was designed to receive New Clients (leads) into the CRM module and to other modules as necessary (like Trading Platform or Bank account).
This page is fully configurable and can be used as landing page. We have two types of pages: Real Account (most common) and Demo Account when relevant.
The url for this page is: Domain/realreg. When the demo account registration page is available accordingly, url is Domain/DemoReg.
The website supports cellular devices and allows its users to manage their accounts by using their cellphones (scroll down to image no. 3).

Image 1: Real Account on PC

Registration page for Real Account / Standard Client

Image 2: Demo Account on PC

Registration page for Demo Account

Image 3: Real Account on Smart-phone

Registration page for Real Account / Standard Client, on smartphone

Web Page Structure

The header is defined as Static Text Element content ID: Create_Real_Header_eng (or Create_Demo_Header_eng for the DemoReg page).
The list of form fields for this web page, is defined in the Client record Fields Matrix.
Use this tool to set the order of the fields and to determine which of the fields are mandatory.
A captcha verification is always included.

Check Boxes Section

In this section you can have the following check boxes:
  • Terms of Use: In this check box the web-user declares that he has read the terms of use.
    This check box will be visible if you set the Terms_of_use_checkbox_eng content.
  • Indenture Contract: In this check box the user declares that he has read the contract and accept it, on Real account page.
    This check box will be visible if you set the Real_Account_Contract_checkbox_eng content.
  • Agree to receive information by Email: This check box is a permanent check box on the form, and its definition updates the value of "Accept Commercial info by these channels" field to "EMail" (2) OR "None" (0).

Submit Button

Once pressing the Submit button, the following tests process will be executed by the system. The process will be stopped when failing a test and an error message will be displayed accordingly.
  1. The system checks whether the mandatory fields are filled.
  2. If the "Email" message and the "Confirm Email" field are displayed, the system verifies that the these mail addresses are identical.
  3. Email Address - The system checks whether the Email address is valid.
  4. Phone Number - The system checks the phone number and verifies that it includes only digits and has a length of 7-13 chars.
  5. If International Site is ON, it verifies that the "First Name" and the "Last Name" fields contain English letters only.
  6. Birthday - If this field was defined to be displayed in this page, it calculates the clients age and verifies that he is 18 years of age or above.
  7. Password - The system checks the password strength. It verifies that the password has a minimum length of 6 chars and that it includes at least 2 digits and 3 English letters (lowercase or uppercase).
  8. If the "Confirm Password" field is defined, the system compares it with the Password field and verifies that the passwords are identical.
  9. Terms of Use Check box - If this check box was defined, the system verifies that it was checked by the client.
  10. Real Account Contract Check box - If this check box was defined, the system verifies that is was checked by the client.
  11. Captcha - The system checks and verifies the captcha code without case sensitivity.
After passing these tests, the system progress to the following process:

Create a New Client process

  1. Password Generation.
    The web-app checks if any password was defined and whether it includes less than 6 chars. In this case, a new 8 chars password will be created.
  2. Duplicity Check.
    The web-app will search for already exist client records (can be real clients or just basic leads), According to the setting New Client Dup-Check by.
    Basic Lead is a client record without any monetary transaction or obligation to the company.
    • IF a basic lead was found, then the Web-App will merge the current registration form with the data left on the lead record.
      When more lead records are found on the clients table - they will be deleted !
    • IF a real client found (even one of multiple records on DB), then the Web-App will act according to the setting When an exist client try to register again.
      The browser will get a pop-up dialog (or json api response) with a message like: "Account is already exist (Real/Demo). Recommend password recovery tool".
      A Task or Opportunity record will be created for both 'Default Sales Agent' and 'Default Relationship Manager' of the first client record found !
    • Behind the scene, the Real_Client_Try_Reg_Again event is being fired...
  3. Creating a New Client record.
    The following fields are automatically taken care of:
    Field Name Description
    Created on
    Created by
    If no merge was executed (as described in the previous section), these fields will be updated in the client record.
    Created by string will always get the English string "Website Real Reg Page" (or "Demo Reg" for the demo page).
    Client Full Name will be modified according to the "First Name" and "Last Name" fields.
    Handling Status If the current handling status of the client is 0-3, the Real reg page will set value to "Follow Up + Meeting / P.Offer" (2). the Demo reg page will set value to "Follow Up" (1).
    Approved Credit This field will be reset.
    Use Currency by Default This field will receive the bookkeeping Currency or USD on international site !
    Committed to pay VAT / GST Value is set to YES, unless the web-app is configured as Financial type (TP Broker / Hedge fund), then the value will be set to NO.
    International Document by Default Value will be set according to the International Site setting.
    Data Source Value will be copied from the Default TP Data Source setting, unless TP_Source parameter was passed to the form.
  4. Create a New TP Account.
    According to the Website Create TP Account on NEW client reg setting, It will create a command for the TP to open a new account (Real / Demo account accordingly).
  5. Thank You Page Content into "Website Inbox".
    An Email message with the content Real_Registration_Thanks_eng, is written into the Inbox of the client ("hyp_Website Mail to Client" table).
  6. Thank you page OR Continue to next registration page.
    According to the setting Website Registration Steps, The browser will be redirected to the next registration step, OR to url Registration_Thanks, which will display the content of Real_Registration_Thanks_eng...
  7. A registration email is sent to the client.
    In case that the Login system OR Account verification uses Email, An Email content New_Client_Registration_On_Website_eng will be sent to the 'EMail' address field.
    This message is also used for demo accounts.
  8. A registration SMS is sent to the client's cellphone.
    In case that the Login system OR Account verification uses Cellphone, An SMS content SMS_New_Client_Registration_On_Website_eng will be sent to the number on "1st phone" field.
  9. Behind the scene, the WebApi_New_Client_Reg event is being fired...

Content Management in Hyper

Build this content in Hyper's "WEB API Static Text Elements" tool, using the HTML editor.
It is recommended to start with an H1 html title and then to write some guidance.
Purpose Content ID Available Fields / Notes
Registration Page Header Create_Real_Header_eng
Create_Demo_Header_eng
None
Does web-user confirm "Terms of use" ? Terms_of_use_checkbox_eng Text for the check box title, like "I confirm the Terms of use".
Without this content record, the whole check-box will be hidden !
You can add a link tag <a> with an HREF to a file (pdf) OR other html page (use target="_blank").
Does web-user confirm any Legal Contract ? Real_Account_Contract_checkbox_eng Text for the check box title, like "I Read and Confirm the Legal Contract".
Without this content record, the whole check-box will be hidden !
You can add a link tag <a> with an HREF to a file (pdf) OR other html page (use target="_blank").
The "Thank you for opening a new account" page content. Real_Registration_Thanks_eng
Demo_Registration_Thanks_eng
The page text can include the following fields:
{#Client_Full_name} - Client full name (in the local language).
{#Eng_Client_Full_Name} - IF this field was defined on Clients table spare fields.
Welcome email for the new registered client New_Client_Registration_On_Website_eng This message can include the following fields:
{#Client_Full_name} - Client full name (in the local language).
{#Email} - EMail address.
{#Password} - The website (login) Password.
{#Eng_Client_Full_Name} - IF this field was defined on Clients table spare fields.
{#Token} - In case that Email Verification is set, include this field to export the confirmation link.
this token will be replaced with a link, with the text "click here" (translated to UI language).
Welcome SMS for the new registered client
Note that SMS length is up-to 500 chars!
SMS_New_Client_Reg_on_Website_eng This PLAIN TEXT (only line breaks are allowed) message can include the following fields:
{#Client_Full_name} - Client full name (in the local language).
{#Password} - The website (login) Password.
{#Eng_Client_Full_Name} - IF this field was defined on Clients table spare fields.
{#Token} - In case that Phone Verification is set, include this field to export the confirmation link.
this token will be replaced with a link, because of the behavior of smart-phones, the client will see the whole URL.
* without this content, the end user experience will be problematic and maybe not legal in some countries !

Affiliates and Landing Pages

You can land new leads into specific URLs and get the registration page on client's browser.
Behind the scene (on the server side = session) this page will be linked to the Affiliate and Lead Source (Ad details).
You can also post fields from the client record into this URLs and get these fields values on the presented page.
For the standard (= real = live) page, use Domain/Affiliate_Registration.
To land on "open demo account" page, use Domain/Affiliate_Demo_Registration, Currently available for TP Brokers.
The web-app support the following fields:
Field Description
lead_source String data about the AD source that land the client into the site.
aff_num This must be a pre defined Supplier on hyper (hyp_Suppliers table). Field Value is the supplier number on hyper DB (record key).
The web-app will load this record and copy the Affiliate details into the Client record fields "Middleman Account" and "Middleman Name".
TP_Source To select a Trading Platform (when you have more then one connected to hyper), pass the Data Source of the TP as defined on hyper (must be 2 chars string).
Any field from the Client record
e.g. "Agency" as integer
Read the API page to learn about passing field names OR explore the reg page html and extract the field names from the html code.

Examples for using the above parameters (both Http GET and POST supported):
DOMAIN/Affiliate_Registration?aff_num=10012&lead_source=facebook_AD_String
DOMAIN/Affiliate_Registration?lead_source=Google_AD_Words_Params

API

If you wish to build your own html, use "Server to Server API".