Field settings.php - Revision history

Jessogden: /* Examples */

2012-12-10T12:29:44Z

‎Examples

Jessogden: /* Class: action */

2012-12-10T12:26:57Z

‎Class: action

Jessogden: /* Examples */

2012-12-10T12:21:34Z

‎Examples

Stuarteve: /* Examples */

2012-06-01T15:35:39Z

‎Examples

Jessogden at 10:11, 20 November 2011

2011-11-20T10:11:50Z

Jessogden: /* Other Obligatory Settings */

2011-11-20T10:01:19Z

‎Other Obligatory Settings

Jessogden: /* Other Obligatory Settings */

2011-11-20T09:41:37Z

‎Other Obligatory Settings

Jessogden: /* Sorting */

2011-02-24T16:55:35Z

‎Sorting

Jessogden: /* Common/Obligatory Attributes */

2011-02-24T16:55:06Z

‎Common/Obligatory Attributes

Jessogden: /* Alias Settings */

2011-02-24T16:50:02Z

‎Alias Settings

@@ Line 57: / Line 57: @@
 <pre>$conf_field_desc =
      array(
          'dataclass' => 'txt',
          'classtype' => 'desc',
@@ Line 71: / Line 72: @@
 $conf_field_samplecondition =
      array(
          'dataclass' => 'attr',
          'classtype' => 'samplecondition',
@@ Line 85: / Line 87: @@
 $conf_field_total =
      array(
          'dataclass' => 'number',
          'classtype' => 'total',
@@ Line 99: / Line 102: @@
 $conf_field_issuedon =
      array(
          'dataclass' => 'date',
          'datestyle' => 'dd,mm,yr',
@@ Line 114: / Line 118: @@
 $conf_field_sameas =
     array(
         'dataclass' => 'span',
         'classtype' => 'sameas',
@@ Line 126: / Line 131: @@
 An example of a standard xmi field:
 <pre>
-$conf_field_romxmimus =
+$conf_field_plnxmicxt =
      array(
          'dataclass' => 'xmi',
          'classtype' => 'xmi_list',
@@ Line 134: / Line 140: @@
                  'alias_tbl' => 'cor_tbl_module',
                  'alias_col' => 'itemkey',
-                 'alias_src_key' => 'rom_cd',
+                 'alias_src_key' => 'pln_cd',
                  'alias_type' => '1',
          ),
-         'module' => 'mus',
+         'module' => 'cxt',
-         'xmi_mod' => 'rom',
+         'xmi_mod' => 'pln',
-         'force_var_itemkey' => 'rom_cd',
+         'force_var_itemkey' => 'pln_cd',
          'editable' => TRUE,
          'hidden' => FALSE,
@@ Line 151: / Line 157: @@
 $conf_field_file =
    array(
        'dataclass' => 'file',
        'classtype' => 'file',

@@ Line 171: / Line 171: @@
 <pre>$conf_field_issuedto =
      array(
          'dataclass' => 'action',
          'classtype' => 'issuedto',
-         'alias_tbl' => 'cor_lut_actiontype',
+         'aliasinfo' => FALSE,
          'actors_mod' => 'abk',
          'actors_type' => 'people',
@@ Line 182: / Line 181: @@
          'actors_elementclass' => 'txt',
          'actors_grp' => FALSE,
          'editable' => TRUE,
          'hidden' => FALSE,

@@ Line 59: / Line 59: @@
          'dataclass' => 'txt',
          'classtype' => 'desc',
-         'alias_tbl' => 'cor_lut_txttype',
+         'aliasinfo' => FALSE,
          'editable' => TRUE,
          'hidden' => FALSE,
@@ Line 76: / Line 73: @@
          'dataclass' => 'attr',
          'classtype' => 'samplecondition',
-         'alias_tbl' => 'cor_lut_attributetype',
+         'aliasinfo' => FALSE,
          'editable' => TRUE,
          'hidden' => FALSE,
@@ Line 94: / Line 87: @@
          'dataclass' => 'number',
          'classtype' => 'total',
-         'alias_tbl' => 'cor_lut_numbertype',
+         'aliasinfo' => FALSE,
          'editable' => TRUE,
          'hidden' => FALSE,
@@ Line 112: / Line 102: @@
          'datestyle' => 'dd,mm,yr',
          'classtype' => 'issuedon',
-         'alias_tbl' => 'cor_lut_datetype',
+         'aliasinfo' => FALSE,
          'editable' => TRUE,
          'hidden' => FALSE,
@@ Line 129: / Line 116: @@
         'dataclass' => 'span',
         'classtype' => 'sameas',
-        'alias_tbl' => 'cor_lut_spantype',
+        'aliasinfo' => FALSE,
         'editable' => TRUE,
         'hidden' => FALSE,
@@ Line 142: / Line 126: @@
 An example of a standard xmi field:
 <pre>
-$conf_field_romxmi =
+$conf_field_romxmimus =
      array(
          'dataclass' => 'xmi',
          'classtype' => 'xmi_list',
-         'alias_tbl' => 'cor_tbl_module',
+         'aliasinfo' =>
-        'alias_col' => 'itemkey',
+            array(
-        'alias_src_key' => 'rom_cd',
+                'alias_tbl' => 'cor_tbl_module',
-        'alias_type' => '1',
+                'alias_col' => 'itemkey',
          'module' => 'mus',
          'xmi_mod' => 'rom',
-         'op_xmi_itemkey' => 'rom_cd',
+         'force_var_itemkey' => 'rom_cd',
          'editable' => TRUE,
          'hidden' => FALSE,
          'add_validation' => $xmi_add_validation,
          'edt_validation' => $xmi_edt_validation
 );
 </pre>
@@ Line 179: / Line 153: @@
        'dataclass' => 'file',
        'classtype' => 'file',
-       'alias_tbl' => 'cor_tbl_col',
+       'aliasinfo' => FALSE,
        'editable' => TRUE,
        'hidden' => FALSE,

@@ Line 157: / Line 157: @@
          'add_validation' => $xmi_add_validation,
          'edt_validation' => $xmi_edt_validation
 );
 </pre>

@@ Line 35: / Line 35: @@
 *'''edt_validation''' = validation rules for this field when on an edt routine
-editable
+=====editable=====
 This is to with how the system processes As of v1.1 this variable only affects the way update_db processes fields - not the user interface.
-/TRUE - handles field as normal
+*'''1/TRUE''' - handles field as normal
-/FALSE - update_db will ignore this field (e.g. options field)
+*'''0/FALSE''' - update_db will ignore this field (e.g. options field)
 =====hidden=====
@@ Line 45: / Line 45: @@
 *'''0/FALSE''' - user input form displayed as normal
 *'''string''' - nname which adds the markup for label displayed in form, functions the same as TRUE
 ====Examples====

@@ Line 31: / Line 31: @@
 *'''editable''' = set TRUE to process this field in forms set FALSE for display only
-*'''hidden''' = set TRUE to make the field <input type="hidden" />
+*'''hidden''' = 1/TRUE | 0/FALSE/blank | string (see below)
 *'''add_validation''' = validation rules for this field when on an add routine
 *'''edt_validation''' = validation rules for this field when on an edt routine

@@ Line 13: / Line 13: @@
 ====Sorting====
-As of v0.8 fields now have the option of being made 'sortable' in the data view (search). In order to allow for ascending and descending sorting on fields a 'field_id' must be added to the fields of interest, rendering them sortable in the data view.
+As of v0.8 fields now have the option of being made 'sortable' in the data view (search). In order to allow for ascending and descending sorting on fields a 'field_id' must be added to the fields of interest, rendering them sortable in the search results table view.
 *'''field_id''' = This is set to the name of the field, i.e. for field 'conf_field_textdesc', the 'field_id' => 'conf_field_textdesc'

← Older revision		Revision as of 16:55, 24 February 2011
Line 11:		Line 11:

	There is not currently an ARK function to create new classtypes. In order to add a new classtype, please access the database using PHPMyAdmin and add the classtype directly in the cor_lut_classtype table (eg. cor_lut_actiontype, cor_lut_datetype, etc...).		There is not currently an ARK function to create new classtypes. In order to add a new classtype, please access the database using PHPMyAdmin and add the classtype directly in the cor_lut_classtype table (eg. cor_lut_actiontype, cor_lut_datetype, etc...).
		+
		+	====Sorting====
		+	As of v0.8 fields now have the option of being made 'sortable' in the data view (search). In order to allow for ascending and descending sorting on fields a 'field_id' must be added to the fields of interest, rendering them sortable in the data view.
		+
		+	*'''field_id''' = This is set to the name of the field, i.e. for field 'conf_field_textdesc', the 'field_id' => 'conf_field_textdesc'

	====Alias Settings====		====Alias Settings====

@@ Line 14: / Line 14: @@
 ====Alias Settings====
-The alias for the field requires the following 3 attributes:
+The alias for the field requires the following 4 attributes:
 *'''alias_tbl''' = the table for the getAlias call