Enterprise Object (EO) Naming Conventions for Controls

[Former Member]

Post Author: rnagahori

CA Forum: Nsite

When naming controls you should follow standard naming conventions. Good names

describe the control, such as prodName, effectiveDate, and dateRequired. Avoid

special characters like "-" ," /", "<" , or ">" when naming your controls.

[Former Member]

Post Author: arhuang

CA Forum: Nsite

Also please try to avoid using the same name for both the Form Control and also the Table Control (The input control for the column in the table).

[Former Member]

Post Author: rnagahori

CA Forum: Nsite

Additional notes ... Avoid using the following list of Reserved Variable Names:Application Builder uses several reserved variable names. Please do not use

these as the names of controls, or as variables within Action Builder

routines.

Reserved Names

sum

min

max

avg

abstract

boolean

break

byte

case

catch

char

class

const

continue

default

do

double

else

extends

false

final

finally

float

for

function

goto

if

implements

import

in

instanceof

int

interface

long

native

new

null

package

private

protected

public

return

short

static

super

switch

synchronized

this

throw

throws

transient

true

try

var

void

validate

while

with

_allowSubmitOnError

_fields

_form

_locked

_name

_queue.errorFields

_queue.errors

_queue.validation

_parent

_pointers

_showAlerts

_skipValidation

_status

obj

addEvent

addField

addMethod

addValidator

changedFields

checkForErrors

disabled

dump

forceValidation

hasChanged

getFields

optional

onSubmit

onValidate

removeField

required

reset

setFields

submit

submitCheck

description