|
Area |
Names |
|
Format |
Field list |
|
Description |
Determines required fields on the Person.awp (user's Profile) page. Fields from Names and NameUDFs tables can be included. Names table fields mapped to text boxes (with a "txt" prefix) should be entered with the field name minus the NM designation. For example: Name1, Name2, Name3, Firm, Title, Badge, Addr1, City, County, State, Zip, Country, Day Phone, Evening Phone, Cell Phone, Email. Other fields, such as drop downs, check boxes, and any NameUDFS field, should be entered with the full HTML name, preceded by a period. E.g. .lstNmEthnic, .chkNudfl1, .txtNudfc1. Birthdate - the default person.awp form uses 3 fields for the Birthdate entry. To require any of the birthdate fields, you must enter the appropriate field names, preceded by a period:
Other parametersNEW: - to leave a field optional for returning users, while requiring it for first-time users, prefix the field name with NEW:, e.g. NEW:FIRM. :VALIDATE - if this flag is added to the end of the RequiredFields list, existing users with blank entries in required fields will have to supply the missing data before they can complete their registration.
User Friendly NamesYou can set user friendly names. The friendly names will be used when the system reports Missing Data Entries during the enrollment process. Note: if you use the friendly names option, it must be applied to all required fields. Fields must be entered in FieldName:User Friendly name format. Separate field pairs with semi-colons. E.g. NAME1:First Name;NAME3:Last Name
|
|
Sample |
RequiredFields=NAME1,NAME3,ADDR1,CITY,STATE,ZIP,EMAIL,DPHONE:VALIDATE RequiredFields=NAME1,NAME3,ADDR1,CITY,STATE,ZIP,EMAIL,NEW:FIRM:VALIDATE RequiredFields=NAME1,NAME3,ZIP,EMAIL,.txtBMo,.txtBYr,.lstNmEthnic,.txtNudfc1:VALIDATE RequiredFields=NAME1:First Name;NAME3:Last Name;ADDR1:Address;CITY:City;STATE:State;ZIP:Zip Code;dphone:Day Phone;EMAIL:Email:VALIDATE |
