UPDATE DATABASE "?" ADD SEQUENCE "seq_obj1" INITIAL 0 INCREMENT 1 CYCLE-ON-LIMIT yes MIN-VAL 0 MAX-VAL 999999999 ADD SEQUENCE "seq_obj2" INITIAL 0 INCREMENT 1 CYCLE-ON-LIMIT yes MIN-VAL 0 MAX-VAL 999999999 ADD SEQUENCE "seq_site_reverse" INITIAL 0 INCREMENT 1 CYCLE-ON-LIMIT yes MIN-VAL 0 MAX-VAL 999999999 ADD SEQUENCE "seq_site_division" INITIAL 0 INCREMENT 1 CYCLE-ON-LIMIT yes MIN-VAL 0 MAX-VAL 999999999 ADD SEQUENCE "seq_session_id" INITIAL 1 INCREMENT 1 CYCLE-ON-LIMIT yes MIN-VAL 1 MAX-VAL 999999999 ADD TABLE "gst_trigger_override" AREA "Schema Area" DESCRIPTION "This table facilitates the generic override of triggers for any table in the database. It is required because the trigger override statements can not be done generically. It also offers more flexibility over which triggers to override. Any comination of triggers is supported with * for all, e.g. create delete write find replication-create replication-delete replication-find replication-write Standard checks are included into triggers via the include file af/sup2/aftrgover.i which references this table and does a can find check on the table name, the transaction id (from dbtaskid) and also checks for a date range of 2 days from the current system date to ensure we do not find redundant data. A transaction id as generated from the dbtaskid statement. This is used so that the override functionality only works within the context of a single transaction. Records must therefore be created in this table within the same transaction that the triggers need to be overridden. Extra information is included in the table for audit purposes to track down problem areas if records get left in this table. One area where this is used is when dumping / loading data via xml files for deployment datasets that require ri triggers to be disabled. " DUMP-NAME "gstto" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsttotrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsttotrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsttotrigw.p" CRC "?" ADD FIELD "trigger_override_obj" OF "gst_trigger_override" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Trigger Override Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Trigger override obj" DECIMALS 6 ORDER 10 ADD FIELD "table_name" OF "gst_trigger_override" AS character DESCRIPTION "The table name (no database prefix) of the table to override triggers for." FORMAT "X(35)" INITIAL "" LABEL "Table Name" POSITION 3 SQL-WIDTH 70 VALMSG "s_name" HELP "Table name" ORDER 20 ADD FIELD "transaction_id" OF "gst_trigger_override" AS integer DESCRIPTION "A transaction id as generated from the dbtaskid statement. This is used so that the override functionality only works within the context of a single transaction. Records must therefore be created in this table within the same transaction that the triggers need to be overridden." FORMAT "->>>>>>>9" INITIAL "0" LABEL "Transaction Id" POSITION 4 SQL-WIDTH 4 VALMSG "n_integer_8" HELP "Transaction id" ORDER 30 ADD FIELD "override_date" OF "gst_trigger_override" AS date DESCRIPTION "The date the override record was created. This is used for audit porposes and also to ensure that we do not accidentally use redundant data not deleted from this table - in the event of a duplicate transaction id, which is highly unlikely. " FORMAT "99/99/9999" INITIAL "TODAY" LABEL "Override Date" POSITION 5 SQL-WIDTH 4 VALMSG "d_date_today" HELP "Override date" ORDER 40 ADD FIELD "override_trigger_list" OF "gst_trigger_override" AS character DESCRIPTION "This is a comma delimited list of the triggers that need to be overridden, from the following list: create delete write find replication-create replication-delete replication-find replication-write An * can be used to denote all triggers." FORMAT "X(70)" INITIAL "" LABEL "Override Trigger List" POSITION 6 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Override trigger list" ORDER 50 ADD FIELD "override_time" OF "gst_trigger_override" AS integer DESCRIPTION "The time the override was created." FORMAT ">>>>9" INITIAL "0" LABEL "Override Time" POSITION 7 SQL-WIDTH 4 VALMSG "n_time" HELP "Override time" ORDER 60 ADD FIELD "override_user" OF "gst_trigger_override" AS character DESCRIPTION "The user that created the override." FORMAT "X(20)" INITIAL "" LABEL "Override User" POSITION 8 SQL-WIDTH 40 VALMSG "s_string_20" HELP "Override user" ORDER 70 ADD FIELD "calling_stack" OF "gst_trigger_override" AS character DESCRIPTION "A stack trace for the procedure that created the override to assist with tracking down programs that do not correctly delete the override records once they have finished with them." FORMAT "X(500)" INITIAL "" LABEL "Calling Stack" POSITION 9 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Calling stack" ORDER 80 ADD INDEX "XPKgst_trigger_override" ON "gst_trigger_override" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "trigger_override_obj" ASCENDING ADD INDEX "XAK1gst_trigger_override" ON "gst_trigger_override" AREA "Schema Area" UNIQUE INDEX-FIELD "table_name" ASCENDING INDEX-FIELD "transaction_id" ASCENDING INDEX-FIELD "override_date" ASCENDING ADD INDEX "XIE1gst_trigger_override" ON "gst_trigger_override" AREA "Schema Area" INDEX-FIELD "override_date" ASCENDING INDEX-FIELD "override_time" ASCENDING ADD TABLE "gsm_site" AREA "Schema Area" DESCRIPTION "This table contain sites or locations where ICF software is running. Its use is to make certain data specific to a particular site, e.g. menu items, menu structures, report definitions, report formats, etc. specific to ICF. It can further define data specific to product and product modules. Sites could be further broken down to provide additional filtering by site location if required. Sites can either be development sites or customer sites. Only development sites need a unique site number. Every site you intend to deploy data to needs to be set up in this table as the site is used to track deployments. Every site must be allocated a totally unique number worldwide. This number will then be used as part of the object numbers in any databases used by that site for ICF applications. This will mean that you can safely deploy data to sites without fear of having conflicting object numbers. Any data modified by the site will never be overwritten as the object numbers will never clash. Also data could be returned to us safely with no fear of object number clashes. The site number must be uniqe worldwide to facilitate software houses developing with ICF releasing data to other software houses developing with ICF The ICFDB will contain two sequences, seq_site_reverse and seq_site_division that will have their current value set by the allocation of the site number. They will then never be changed, and the current value of the sequences used to calculate the decimal portion of the object number, making the object numbers unique within that site. See the description of the site number for details of the calculations required. A site will only ever have one version of the ICFDB database, ensuring they keep the same site number for all their ICF products. Any object numbers that do not conform to this new standard should be fixed immediately to avoid problems in the future. The data is linked to a site via the gsm_site_specific table in the ICFDB database which supports any type of data. The data being filtered is identified by the owning entity mnemonic, and the specific reference identifies the actual item of data being filtered. It is possible to make an item of data available to many sites. If the item of data does not exist in the table, then it will be assumed the data is applicable to all sites. The gsm_site_specific table is also used to allocate which sites a specific user is associated with. In this case the entity mnemonic would be GSMUS and the specific reference would be the user login name. Examples of data that may be specific to site codes are menu items, menu structures, report definitions and report formats. For any supported tables, e.g. menu items when building menus, a check will need to be made in the site specific data table for the appropriate entity mnemonic and unique reference. If any records exist at all, then the site codes allocated to the user must be checked to see that the user has a matching site code. If not, the data should be skipped over as it is not relevant. This table is in ICFDB because it is not specific to any product or workspace. The site specific data table is in ICFDB because it relates to the specific product and workspace data, allowing different workspaces to support different configurations of site specific data. The current site can always be found by checking the value of the site sequence." DUMP-NAME "gsmsi" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmsitrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmsitrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmsireplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmsirepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmsireplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmsitrigw.p" CRC "?" ADD FIELD "site_code" OF "gsm_site" AS character DESCRIPTION "A unique code to indentify the site / location." FORMAT "X(10)" INITIAL "" LABEL "Site Code" POSITION 2 SQL-WIDTH 20 VALMSG "s_code" HELP "Site code" ORDER 10 ADD FIELD "site_name" OF "gsm_site" AS character DESCRIPTION "The full name of the site." FORMAT "X(35)" INITIAL "" LABEL "Site Name" POSITION 3 SQL-WIDTH 70 VALMSG "s_name" HELP "Site name" ORDER 20 ADD FIELD "site_obj" OF "gsm_site" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Site Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Site obj" DECIMALS 6 ORDER 40 ADD FIELD "site_number" OF "gsm_site" AS integer DESCRIPTION "A unique number worldwide to identify the site and to be used as the decimal portion of object numbers generated for this site. To avoid the problem of site 1 and site 10 conflicting due to the decimal portion containing .1 and .10, we use 2 sequences to work out the decimal portion of the site number, whose current values are derived from the site number. The first sequence (seq_site_reverse) is set to the exact reverse of the site numer digits, e.g. 1 would be 1, 10 would be 01, 100 would be 001, etc. The second sequence (seq_site_division) is the number to divide by to get a decimal, e.g. 1 would be 10, 10 would be 100, 100 would be 1000, etc. Therefore 1 divided by 10 gives 0.1, 10 reversed as 01 divided by 100 gives .01, 100 reversed as 001 divided by 1000 gives .001, etc. The setting of this site number will generate a .d with the sequence current values calculated using the above. The site number is only applicable to development sites. " FORMAT "->>>>>9" INITIAL "0" LABEL "Site Number" POSITION 5 SQL-WIDTH 4 VALMSG "n_integer_6" HELP "Site number" ORDER 30 ADD FIELD "site_type" OF "gsm_site" AS character DESCRIPTION "This indicates the type of site as follows: DEV = Development Site CST = Customer Site" FORMAT "X(3)" INITIAL "" LABEL "Site Type" POSITION 6 SQL-WIDTH 6 VALMSG "s_type" HELP "Site type" ORDER 50 ADD INDEX "XPKgsm_site" ON "gsm_site" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "site_code" ASCENDING ADD INDEX "XAK1gsm_site" ON "gsm_site" AREA "Schema Area" UNIQUE INDEX-FIELD "site_number" ASCENDING ADD INDEX "XAK2gsm_site" ON "gsm_site" AREA "Schema Area" UNIQUE INDEX-FIELD "site_obj" ASCENDING ADD INDEX "XIE1gsm_site" ON "gsm_site" AREA "Schema Area" INDEX-FIELD "site_name" ASCENDING ADD INDEX "XIE2gsm_site" ON "gsm_site" AREA "Schema Area" INDEX-FIELD "site_type" ASCENDING INDEX-FIELD "site_code" ASCENDING ADD TABLE "gsc_deploy_dataset" AREA "Schema Area" DESCRIPTION "This table defines the sets of data that need to be deployed to end-user sites and migrated to different workspace databases. Usually it is static data that needs to be deployed. This table with its child table gsc_dataset_entity identify which data must be deployed as a set, i.e. has dependancies. For example, in order to deploy menu items, objects on the menu item would also need to be deployed. These tables also define the dataset for deployment of logical objects managed by the scm tool, e.g. the ryc_smartobject and related tables. To deploy and load the data, xml files will be generated for the dataset. The dataset must always have a main table that is being deployed, plus all related tables that need to be deployed with it, together with appropriate join information. Example datasets could be for SmartObjects, menus, objects, etc. It is likely that a seperate dataset will be defined for most data tables that need to be deployed, but that these datasets will include a parent dataset that includes this dataset. When automatically generating triggers from ERWin an entity-level UDP (DeployData) is used to indicate whether trigger code should be generated for the static tables to support data deployment. A flag also exists in the entity mnemonic table called deploy_data for the same purpose. For customer sites that receive a dataset deployment, the last deployment loaded for this dataset is record here. This helps identify at what version the current static data is for a particular database. Customers should not modify or deploy from datasets sent by suppliers. The customer can however create their own datasets containing the same tables and deploy from these datasets. As a dataset deployment includes an xml file registered as part of the deployment, the customer can simply utilise this xml file for their database and any subsequent databases and sites they wish to pass the data on to." DUMP-NAME "gscdd" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscddtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscddtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscddreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscddrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscddreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscddtrigw.p" CRC "?" ADD FIELD "deploy_dataset_obj" OF "gsc_deploy_dataset" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Deploy Dataset Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Deploy dataset obj" DECIMALS 6 ORDER 10 ADD FIELD "owner_site_code" OF "gsc_deploy_dataset" AS character DESCRIPTION "A unique code to indentify the site / location." FORMAT "X(10)" INITIAL "" LABEL "Owner Site Code" POSITION 3 SQL-WIDTH 20 VALMSG "s_code" HELP "Owner site code" ORDER 20 ADD FIELD "dataset_code" OF "gsc_deploy_dataset" AS character DESCRIPTION "This is a unique code by which this dataset is identified." FORMAT "X(10)" INITIAL "" LABEL "Dataset Code" POSITION 4 SQL-WIDTH 20 VALMSG "s_code" HELP "Dataset code" ORDER 30 ADD FIELD "dataset_description" OF "gsc_deploy_dataset" AS character DESCRIPTION "This is a free-text description of the dataset." FORMAT "X(35)" INITIAL "" LABEL "Dataset Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Dataset description" ORDER 40 ADD FIELD "disable_ri" OF "gsc_deploy_dataset" AS logical DESCRIPTION "If set to yes, all triggers are disabled before data is dumped and loaded for this dataset." FORMAT "YES/NO" INITIAL "YES" LABEL "Disable Ri" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Disable ri" ORDER 50 ADD FIELD "source_code_data" OF "gsc_deploy_dataset" AS logical DESCRIPTION "If this flag is set to YES, then the data to include in the deployment is identified by the SCM tool rather than the gst_record_version table. This would be the case for the ryc_smartobject dataset. " FORMAT "YES/NO" INITIAL "NO" LABEL "Source Code Data" POSITION 7 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Source code data" ORDER 60 ADD FIELD "deploy_full_data" OF "gsc_deploy_dataset" AS logical DESCRIPTION "If set to yes, this field indicates that the entire set of records contained in this primary and related tables must be deployed. This is primarily for datasets that are not directly related but contain low volumes of fairly static data. If set to no, then only records that have changed, as identified by the table version information in ICFDB will be deployed. Note that any filter criteria in the filter_where_clause on the gsc_dataset_entity will still be honored." FORMAT "YES/NO" INITIAL "NO" LABEL "Deploy Full Data" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Deploy full data" ORDER 70 ADD FIELD "xml_generation_procedure" OF "gsc_deploy_dataset" AS character DESCRIPTION "This field contains the name of a procedure that generates the XML for this dataset. If specified, this overrides the standard XML generation procedure supplied with the framework." FORMAT "X(70)" INITIAL "" LABEL "Xml Generation Procedure" POSITION 9 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Xml generation procedure" ORDER 80 ADD INDEX "XPKgsc_deploy_dataset" ON "gsc_deploy_dataset" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "deploy_dataset_obj" ASCENDING ADD INDEX "XAK1gsc_deploy_dataset" ON "gsc_deploy_dataset" AREA "Schema Area" UNIQUE INDEX-FIELD "owner_site_code" ASCENDING INDEX-FIELD "dataset_code" ASCENDING ADD INDEX "XIE1gsc_deploy_dataset" ON "gsc_deploy_dataset" AREA "Schema Area" INDEX-FIELD "dataset_description" ASCENDING ADD INDEX "XIE2gsc_deploy_dataset" ON "gsc_deploy_dataset" AREA "Schema Area" INDEX-FIELD "source_code_data" ASCENDING ADD TABLE "gsm_dataset_deployment" AREA "Schema Area" DESCRIPTION "This table registers a deployment created for a dataset, when it was created, by whom, whether it was a baseline including all data or whether it was incremental data including only data that had changed, plus the xml file that contains the dumped data. Deployments should only be created for datasets created and owned by your site. If a dataset is owned by another site, then you should use the xml file to load data and pass data on to other sites. If you wish to create your own xml files, then simply create a new dataset with the same tables and deploy from there. This will ensure we can track the versions of data deployed and loaded at the various sites. The xml file that contains the deployed data should be kept, registered in the SCM tool and deployed as part of the application. This facilitates incremental deployments of only data that has changed. If this is a baseline deployment, then the xml file will contain all the records in all the tables included in the dataset. If not, it will only contain records that have changed since the last deployment, as idenitified by the information in the gst_record_version table. This version table will only contain version records if the data in the table is being versioned. IF data is not being versioned, then the xml file will always have to contain the full data in the table. This table also registers when (and if) the deployment was loaded at the remote site and by whom." DUMP-NAME "gsmdd" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmddtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmddtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmddreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmddrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmddreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmddtrigw.p" CRC "?" ADD FIELD "dataset_deployment_obj" OF "gsm_dataset_deployment" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Dataset Deployment Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Dataset deployment obj" DECIMALS 6 ORDER 10 ADD FIELD "deploy_dataset_obj" OF "gsm_dataset_deployment" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Deploy Dataset Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Deploy dataset obj" DECIMALS 6 ORDER 20 ADD FIELD "deployment_number" OF "gsm_dataset_deployment" AS decimal DESCRIPTION "This is a sequential number starting from 1 within each dataset. It identifies the order the dataset deployments were produced and uniquely identifies the deployment for the dataset." FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Deployment Number" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Deployment number" DECIMALS 6 ORDER 30 ADD FIELD "deployment_description" OF "gsm_dataset_deployment" AS character DESCRIPTION "A free text description of the deployment, possibly including the reason for the deployment." FORMAT "X(35)" INITIAL "" LABEL "Deployment Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Deployment description" ORDER 40 ADD FIELD "deployment_date" OF "gsm_dataset_deployment" AS date DESCRIPTION "The date the deployment was created." FORMAT "99/99/9999" INITIAL "TODAY" LABEL "Deployment Date" POSITION 6 SQL-WIDTH 4 VALMSG "d_date_today" HELP "Deployment date" ORDER 50 ADD FIELD "deployment_time" OF "gsm_dataset_deployment" AS integer DESCRIPTION "The time the deployment was created." FORMAT ">>>>9" INITIAL "0" LABEL "Deployment Time" POSITION 7 SQL-WIDTH 4 VALMSG "n_time" HELP "Deployment time" ORDER 60 ADD FIELD "baseline_deployment" OF "gsm_dataset_deployment" AS logical DESCRIPTION "If this is set to YES then it is a baseline deployment and the xml file will contain the all records in all the tables included in the dataset. If NO, it will only contain records that have changed since the last deployment, as idenitified by the information in the gst_record_version table. This version table will only contain version records if the data in the table is being versioned. If data is not being versioned, then the xml file will always have to contain the full data in the table. " FORMAT "YES/NO" INITIAL "NO" LABEL "Baseline Deployment" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Baseline deployment" ORDER 70 ADD FIELD "xml_filename" OF "gsm_dataset_deployment" AS character DESCRIPTION "This is the name of the XML file containing the dumped data in the deployment, including data from all tables identified in the dataset. The XML filename will be structured based on the owning site code, the dataset code and the dataset deployment number together, with an extension of .xml" FORMAT "X(70)" INITIAL "" LABEL "Xml Filename" POSITION 9 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Xml filename" ORDER 80 ADD FIELD "xml_exception_file" OF "gsm_dataset_deployment" AS character DESCRIPTION "This is the name of the XML file containing the exception records that could not be loaded as part during the import. The XML filename will be structured based on the owning site code, the dataset code and the dataset deployment number together, suffixed with an ""e"" and an extension of .xml In the deployment XML file, this field contains the root filename. After the import into the remote database is completed, this field contains the absolute path to the file." FORMAT "X(70)" INITIAL "" LABEL "Xml Exception File" POSITION 10 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Xml exception file" ORDER 90 ADD FIELD "import_date" OF "gsm_dataset_deployment" AS date DESCRIPTION "This field contains the date that the deployment dataset was imported on the remote site. " FORMAT "99/99/9999" INITIAL "?" LABEL "Import Date" POSITION 11 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Import date" ORDER 100 ADD FIELD "import_time" OF "gsm_dataset_deployment" AS integer DESCRIPTION "This field contains the time that the deployment dataset was imported." FORMAT ">>>>9" INITIAL "0" LABEL "Import Time" POSITION 12 SQL-WIDTH 4 VALMSG "n_time" HELP "Import time" ORDER 110 ADD FIELD "import_user" OF "gsm_dataset_deployment" AS character DESCRIPTION "This field contains the name of the user that imported the dataset." FORMAT "X(20)" INITIAL "" LABEL "Import User" POSITION 13 SQL-WIDTH 40 VALMSG "s_string_20" HELP "Import user" ORDER 120 ADD INDEX "XPKgsm_dataset_deployment" ON "gsm_dataset_deployment" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "dataset_deployment_obj" ASCENDING ADD INDEX "XAK1gsm_dataset_deployment" ON "gsm_dataset_deployment" AREA "Schema Area" UNIQUE INDEX-FIELD "deploy_dataset_obj" ASCENDING INDEX-FIELD "deployment_number" ASCENDING ADD INDEX "XIE1gsm_dataset_deployment" ON "gsm_dataset_deployment" AREA "Schema Area" INDEX-FIELD "deployment_description" ASCENDING ADD INDEX "XIE2gsm_dataset_deployment" ON "gsm_dataset_deployment" AREA "Schema Area" INDEX-FIELD "deploy_dataset_obj" ASCENDING INDEX-FIELD "baseline_deployment" ASCENDING INDEX-FIELD "deployment_date" ASCENDING INDEX-FIELD "deployment_time" ASCENDING ADD TABLE "gsc_entity_mnemonic" AREA "Schema Area" DESCRIPTION "This table stores all the hard coded entity mnemonics allocated to every table in the application. It defines a meaningful short code and identifies the table name for each table. It also defines generic information about the entity used when generating dynamic or generic objects based on the table, auto generating triggers, etc." DUMP-NAME "gscem" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscemtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscemtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscemreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscemrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscemreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscemtrigw.p" CRC "?" ADD FIELD "entity_mnemonic_obj" OF "gsc_entity_mnemonic" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Entity Mnemonic Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Entity mnemonic obj" DECIMALS 6 ORDER 60 ADD FIELD "entity_mnemonic" OF "gsc_entity_mnemonic" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Entity Mnemonic" POSITION 3 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Entity mnemonic" ORDER 10 ADD FIELD "entity_mnemonic_short_desc" OF "gsc_entity_mnemonic" AS character DESCRIPTION "A short reference for the table used to lookup the table - this is a free text description" FORMAT "X(35)" INITIAL "" LABEL "Entity Mnemonic Short Description" POSITION 4 SQL-WIDTH 70 COLUMN-LABEL "Entity Mnemonic Short Desc" VALMSG "s_description" HELP "Entity mnemonic short description" ORDER 20 ADD FIELD "entity_mnemonic_description" OF "gsc_entity_mnemonic" AS character DESCRIPTION "This field should store the actual table name in full, e.g. gsm_user. The fact that this field contains the table name is relied upon within the framework." FORMAT "X(35)" INITIAL "" LABEL "Entity Mnemonic Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Entity mnemonic description" ORDER 30 ADD FIELD "auto_properform_strings" OF "gsc_entity_mnemonic" AS logical DESCRIPTION "Should all character fields be properformed, i.e. automatically tidy up the case of the value into correct upper and lower case." FORMAT "YES/NO" INITIAL "NO" LABEL "Auto Properform Strings" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Auto properform strings" ORDER 40 ADD FIELD "entity_mnemonic_label_prefix" OF "gsc_entity_mnemonic" AS character DESCRIPTION "An optional prefix to selectively replace the first word of screen labels for fields in the associated table. This will primarily be used for tables in the framework to provide more meaningful labels. For example a table gsm_region in a specfic application may be used for suburbs and have a label prefix of ""suburb"" rather than ""region"". The label prefix will actually replace the first word in the field label defined on the database. Where the table has more than one meaning, e.g. a gsm_person can be a member, a contact, a practioner, etc. then the label may be defined elsewhere." FORMAT "X(28)" INITIAL "" LABEL "Entity Mnemonic Label Prefix" POSITION 7 SQL-WIDTH 56 VALMSG "s_label" HELP "Entity mnemonic label prefix" ORDER 50 ADD FIELD "entity_description_field" OF "gsc_entity_mnemonic" AS character DESCRIPTION "The name of the description field for this entity. Armed with this information and the object number, we can dynamically return the description of any record in any table." FORMAT "X(70)" INITIAL "" LABEL "Entity Description Field" POSITION 8 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Entity description field" ORDER 70 ADD FIELD "entity_description_procedure" OF "gsc_entity_mnemonic" AS character DESCRIPTION "The name of a procedure to run in order to work out the description of the entity. This is only required in the event that the entity description spans multiple fields (potentially from related entities). If this field is specified, it will override the entity description field. A relative path to the procedure must be included. The procedure written must take the object number as an input parameter, and output a single character string containing the object description." FORMAT "X(70)" INITIAL "" LABEL "Entity Description Procedure" POSITION 9 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Entity description procedure" ORDER 80 ADD FIELD "entity_narration" OF "gsc_entity_mnemonic" AS character DESCRIPTION "A free text narration of the entity used to assist users in identifying the entity and what it is used for." FORMAT "X(500)" INITIAL "" LABEL "Entity Narration" POSITION 10 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Entity narration" ORDER 90 ADD FIELD "entity_object_field" OF "gsc_entity_mnemonic" AS character DESCRIPTION "The name of the unique object field for this entity used to join to other tables. Usually this field is the same as the tablename without the 4 character prefix and ends in _obj. The datatype of this field should be a decimal with at least decimals 6. If left blank, then the above assumption will be used to find the object field where required. " FORMAT "X(35)" INITIAL "" LABEL "Entity Object Field" POSITION 11 SQL-WIDTH 70 VALMSG "s_name" HELP "Entity object field" ORDER 100 ADD FIELD "table_has_object_field" OF "gsc_entity_mnemonic" AS logical DESCRIPTION "If set to NO, this table does not contain a generic object field used to join to generic tables, e.g. comments, auditing, etc. Usually this will be set to YES, but tables in existing databases that do not conform to the framework standards may have this field set to NO. " FORMAT "YES/NO" INITIAL "YES" LABEL "Table Has Object Field" POSITION 12 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Table has object field" ORDER 110 ADD FIELD "entity_key_field" OF "gsc_entity_mnemonic" AS character DESCRIPTION "The name of the unique key field for this entity. This should be a field other than the object field that could be used to uniquely find information in this entity. This would often be used in lookups, etc. so the code and description can be displayed to the user. This currently only supports a single key field value. " FORMAT "X(35)" INITIAL "" LABEL "Entity Key Field" POSITION 13 SQL-WIDTH 70 VALMSG "s_name" HELP "Entity key field" ORDER 120 ADD FIELD "entity_display_fields" OF "gsc_entity_mnemonic" AS character DESCRIPTION "This is a comma delimited list of field names for this entity that could be used when generically building browsers for the entity. This is actually used in the generic data security used by the framework. If left blank then all fields other than any object fields will be used." FORMAT "X(500)" INITIAL "" LABEL "Entity Display Fields" POSITION 14 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Entity display fields" ORDER 130 ADD FIELD "entity_display_labels" OF "gsc_entity_mnemonic" AS character DESCRIPTION "This is a chr(3) delimited list of field labels corresponding to the field names for this entity that could be used when generically building browsers for the entity. This is actually used in the generic data security used by the framework. If left blank then the labels from the metacshema will be used. If any labels are specified then the correct number of entries must be used as per the field list, leaving individual field labels blank to default to the metaschema label." FORMAT "X(500)" INITIAL "" LABEL "Entity Display Labels" POSITION 15 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Entity display labels" ORDER 140 ADD FIELD "entity_display_formats" OF "gsc_entity_mnemonic" AS character DESCRIPTION "This is a chr(3) delimited list of field formats corresponding to the field names for this entity that could be used when generically building browsers for the entity. This is actually used in the generic data security used by the framework. If left blank then the formats from the metacshema will be used. If any formats are specified then the correct number of entries must be used as per the field list, leaving individual field formats blank to default to the metaschema format" FORMAT "X(500)" INITIAL "" LABEL "Entity Display Formats" POSITION 16 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Entity display formats" ORDER 150 ADD FIELD "table_prefix_length" OF "gsc_entity_mnemonic" AS integer DESCRIPTION "This is the length of the table prefix appended to all table names as per the framework standards. The framework uses a 4 character table prefix - see the standards documentation for further details. " FORMAT "->9" INITIAL "0" LABEL "Table Prefix Length" POSITION 17 SQL-WIDTH 4 VALMSG "n_integer_2" HELP "Table prefix length" ORDER 160 ADD FIELD "field_name_separator" OF "gsc_entity_mnemonic" AS character DESCRIPTION "The basis of identifying what is used to break up field names into words. The framework standard is to separate fields with an underscore so this field would be set to ""_"". Some database designs separate fields by uppercasing the first character of each word and in this case the value of this field would be ""upper""." FORMAT "X(10)" INITIAL "" LABEL "Field Name Separator" POSITION 18 SQL-WIDTH 20 VALMSG "s_code" HELP "Field name separator" ORDER 170 ADD FIELD "auditing_enabled" OF "gsc_entity_mnemonic" AS logical DESCRIPTION "If set to YES, auditing will be enabled for this table and will be done via the generic triggers generated from ERwin. You should only enable auditing where required so as not to adversly affect the performance of the application." FORMAT "YES/NO" INITIAL "NO" LABEL "Auditing Enabled" POSITION 19 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Auditing enabled" ORDER 180 ADD FIELD "version_data" OF "gsc_entity_mnemonic" AS logical DESCRIPTION "If set to YES, this field indicates that the data in the table should be version-stamped. This will result in replication triggers on the table writing data to the gst_record_version table. This field corresponds to the entity level UDP setup in ERwin as VersionData. The version information is used to identify which records have changed for deployment purposes." FORMAT "YES/NO" INITIAL "NO" LABEL "Version Data" POSITION 20 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Version data" ORDER 190 ADD FIELD "deploy_data" OF "gsc_entity_mnemonic" AS logical DESCRIPTION "If set to yes, then data in this table needs to be deployed. Whether data has changed and needs to be deployed is identified by the existence of records in the gst_record_version table for this entity. What data gets deployed and how it relates to other data is specified via setting up deployment datasets." FORMAT "YES/NO" INITIAL "NO" LABEL "Deploy Data" POSITION 21 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Deploy data" ORDER 200 ADD FIELD "entity_dbname" OF "gsc_entity_mnemonic" AS character DESCRIPTION "This is the logical database name in which this table resides." FORMAT "X(35)" INITIAL "" LABEL "Entity Dbname" POSITION 22 SQL-WIDTH 70 VALMSG "s_name" HELP "Entity dbname" ORDER 210 ADD FIELD "replicate_entity_mnemonic" OF "gsc_entity_mnemonic" AS character DESCRIPTION "If SCM data versioning is to be enabled for this entity, then the FLA of the primary replication table should be specified, e.g. RYCSO for the ryc_smartobject table. For the primary table, the entity_mnemonic and this field will be the same. This field corresponds to the entity level UDP setup in ERwin as ReplicateFLA. If this field is defined and scm checking is enabled via the flag in the security control table, then modifications to data in this table will be prevented without a valid checked out scm object in a valid task." FORMAT "X(8)" INITIAL "" LABEL "Replicate Entity Mnemonic" POSITION 23 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Replicate entity mnemonic" ORDER 220 ADD FIELD "replicate_key" OF "gsc_entity_mnemonic" AS character DESCRIPTION "This field is only applicable if the replicate_entity_mnemonic field has been specified turning on SCM data versioning for this entity This is the join field to the primary replication table being versioned Usually this will be the same field as the primary key of the primary table, e.g. smartobject_obj, but if the foreign key field has been role named, as is the case with page table, it could be something else, e.g. container_smartobject_obj. Multiple primary key fields are supported and must be separated by commas. This field corresponds to the entity level UDP setup in ERwin as ReplicateKey. " FORMAT "X(70)" INITIAL "" LABEL "Replicate Key" POSITION 24 SQL-WIDTH 140 VALMSG "s_big_name" HELP "Replicate key" ORDER 230 ADD FIELD "scm_field_name" OF "gsc_entity_mnemonic" AS character DESCRIPTION "This field is only applicable if the replicate_entity_mnemonic field has been specified turning on SCM data versioning for this entity This is only required for the primary entity being versioned and is the unique field for the data that is also used as the object name in the SCM Tool. E.g. for ryc_smartobject this would be the object_filename, but in other tables it may be some unique reference field that identifies the data. This field corresponds to the entity level UDP setup in ERwin as SCMField " FORMAT "X(35)" INITIAL "" LABEL "Scm Field Name" POSITION 25 SQL-WIDTH 70 VALMSG "s_name" HELP "Scm field name" ORDER 240 ADD INDEX "XPKgsc_entity_mnemonic" ON "gsc_entity_mnemonic" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "entity_mnemonic" ASCENDING ADD INDEX "XAK1gsc_entity_mnemonic" ON "gsc_entity_mnemonic" AREA "Schema Area" UNIQUE INDEX-FIELD "entity_mnemonic_obj" ASCENDING ADD INDEX "XIE1gsc_entity_mnemonic" ON "gsc_entity_mnemonic" AREA "Schema Area" INDEX-FIELD "entity_mnemonic_short_desc" ASCENDING ADD INDEX "XIE2gsc_entity_mnemonic" ON "gsc_entity_mnemonic" AREA "Schema Area" INDEX-FIELD "entity_mnemonic_description" ASCENDING ADD INDEX "XIE3gsc_entity_mnemonic" ON "gsc_entity_mnemonic" AREA "Schema Area" INDEX-FIELD "deploy_data" ASCENDING INDEX-FIELD "entity_mnemonic" ASCENDING ADD INDEX "XIE4gsc_entity_mnemonic" ON "gsc_entity_mnemonic" AREA "Schema Area" INDEX-FIELD "replicate_entity_mnemonic" ASCENDING ADD INDEX "XIE5gsc_entity_mnemonic" ON "gsc_entity_mnemonic" AREA "Schema Area" INDEX-FIELD "version_data" ASCENDING INDEX-FIELD "entity_mnemonic" ASCENDING ADD TABLE "gsc_dataset_entity" AREA "Schema Area" DESCRIPTION "This table contains a complete list of tables that need to be deployed with the dataset. One of the tables in the dataset must be marked as primary, i.e. the main table in the dataset. The join information between the tables must also be specified. The data in this table can be filtered using the filter where clause." DUMP-NAME "gscde" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscdetrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscdetrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscdereplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscderepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscdereplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscdetrigw.p" CRC "?" ADD FIELD "dataset_entity_obj" OF "gsc_dataset_entity" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Dataset Entity Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Dataset entity obj" DECIMALS 6 ORDER 10 ADD FIELD "deploy_dataset_obj" OF "gsc_dataset_entity" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Deploy Dataset Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Deploy dataset obj" DECIMALS 6 ORDER 20 ADD FIELD "entity_sequence" OF "gsc_dataset_entity" AS integer DESCRIPTION "This field specifies the order in which the tables are dumped/loaded to or from the XML file." FORMAT "->>9" INITIAL "0" LABEL "Entity Sequence" POSITION 4 SQL-WIDTH 4 COLUMN-LABEL "Entity Seq." VALMSG "n_integer_3" HELP "Entity sequence" ORDER 30 ADD FIELD "entity_mnemonic" OF "gsc_dataset_entity" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Entity Mnemonic" POSITION 5 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Entity mnemonic" ORDER 40 ADD FIELD "primary_entity" OF "gsc_dataset_entity" AS logical DESCRIPTION "If set to YES this is the primary entity in the dataset. Each dataset must have at least 1 primary entity." FORMAT "YES/NO" INITIAL "NO" LABEL "Primary Entity" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Primary entity" ORDER 50 ADD FIELD "join_entity_mnemonic" OF "gsc_dataset_entity" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Join Entity Mnemonic" POSITION 7 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Join entity mnemonic" ORDER 60 ADD FIELD "join_field_list" OF "gsc_dataset_entity" AS character DESCRIPTION "If this record has the primary_entity flag switched on, this field contains a list of fields on the table whose values will be provided as an input parameter to the procedure that writes out the XML file. For example, if the primary table name were gsc_entity_mnemonic and the intention was to deploy datasets for specific entity_mnemonics only, this field would contain the entity_mnemonic field and the input parameter would be the value of the entity_mnemonic field. If this record is not the primary entity, this field contains a comma-separated list of field name pairs made as follows: The first entry in each pair contains the name of the field on this table with no prefix. The second entry in each pair contains a field on the join partner specified by the join_entity_mnemonic with no table prefix. " FORMAT "X(70)" INITIAL "" LABEL "Join Field List" POSITION 8 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Join field list" ORDER 70 ADD FIELD "filter_where_clause" OF "gsc_dataset_entity" AS character DESCRIPTION "This field contains a WHERE clause that can be applied to a QUERY-PREPARE method that filters the data in this table. eg: Only deploying data specific to a site, product, or product module." FORMAT "X(500)" INITIAL "" LABEL "Filter Where Clause" POSITION 9 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Filter where clause" ORDER 80 ADD INDEX "XPKgsc_dataset_entity" ON "gsc_dataset_entity" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "dataset_entity_obj" ASCENDING ADD INDEX "XAK1gsc_dataset_entity" ON "gsc_dataset_entity" AREA "Schema Area" UNIQUE INDEX-FIELD "deploy_dataset_obj" ASCENDING INDEX-FIELD "entity_sequence" ASCENDING ADD INDEX "XIE1gsc_dataset_entity" ON "gsc_dataset_entity" AREA "Schema Area" INDEX-FIELD "entity_mnemonic" ASCENDING ADD INDEX "XIE3gsc_dataset_entity" ON "gsc_dataset_entity" AREA "Schema Area" INDEX-FIELD "deploy_dataset_obj" ASCENDING INDEX-FIELD "primary_entity" ASCENDING INDEX-FIELD "entity_mnemonic" ASCENDING ADD INDEX "XIE4gsc_dataset_entity" ON "gsc_dataset_entity" AREA "Schema Area" INDEX-FIELD "join_entity_mnemonic" ASCENDING INDEX-FIELD "dataset_entity_obj" ASCENDING ADD TABLE "gsm_session_type" AREA "Schema Area" DESCRIPTION "A session type is a namespace for grouping specific types of sessions together. For example, a ""receipting workstation"" would be a specific session type while a ""salesman's web agent"" could be another. Each session type is combined with a physical session type that maps to a list of known Progress 4GL run-time environments. Thus, ""receipting workstation"" may be mapped to a 4GL GUI client while ""salesman's web agent"" could be mapped to a WebSpeed Transaction Agent. Thus you could create any number of session types mapping them to specific 4GL session types. Where different managers, etc. need to be pre-started for different applications, then the different applications would be defined as new session types. In order to run locally without appserver connections, etc. you would need to define a new session type that connects to appropriate databases and has no session service records for the appserver logical services thereby forcing them to not connect and rather simply use the session handle for code portability. Also, this new session type would define a different set of managers to run, i.e. run the server side managers locally. We will provide a facility to change the session type on the fly (if possible). " DUMP-NAME "gsmse" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmsetrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmsetrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmsereplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmserepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmsereplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmsetrigw.p" CRC "?" ADD FIELD "session_type_obj" OF "gsm_session_type" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Session Type Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Session type obj" DECIMALS 6 ORDER 10 ADD FIELD "session_type_code" OF "gsm_session_type" AS character DESCRIPTION "A unique code to identify the session type." FORMAT "X(10)" INITIAL "" LABEL "Session Type Code" POSITION 3 SQL-WIDTH 20 VALMSG "s_code" HELP "Session type code" ORDER 20 ADD FIELD "session_type_description" OF "gsm_session_type" AS character DESCRIPTION "A description of the session type." FORMAT "X(35)" INITIAL "" LABEL "Session Type Description" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Session type description" ORDER 30 ADD FIELD "physical_session_list" OF "gsm_session_type" AS character DESCRIPTION "This field contains a list of valid physical session types that this session may run on. It is a comma delimited list of codes selected from the following valid values: APP = AppServer WBC = WebClient GUI = GUI Client CUI = Character Client WBS = WebSpeed JOC = Java Open Client AOC = ActiveX Open Client BTC = Batch Client" FORMAT "X(70)" INITIAL "" LABEL "Physical Session List" POSITION 5 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Physical session list" ORDER 40 ADD FIELD "valid_os_list" OF "gsm_session_type" AS character DESCRIPTION "This field defines a list of operating systems that this session may be run on. The list may either be blank, in which case the session may run on any operating system, or the list may contain one or more of the following values: WIN32 = Win95,98,ME,NT or Win2000 UNIX = Any Progress supported UNIX OS400 = AS400 " FORMAT "X(15)" INITIAL "" LABEL "Valid OS List" POSITION 6 SQL-WIDTH 30 VALMSG "" HELP "Valid outstanding list" ORDER 50 ADD INDEX "XPKgsm_session_type" ON "gsm_session_type" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "session_type_obj" ASCENDING ADD INDEX "XAK1gsm_session_type" ON "gsm_session_type" AREA "Schema Area" UNIQUE INDEX-FIELD "session_type_code" ASCENDING ADD INDEX "XIE1gsm_session_type" ON "gsm_session_type" AREA "Schema Area" INDEX-FIELD "session_type_description" ASCENDING ADD TABLE "gsc_session_property" AREA "Schema Area" DESCRIPTION "This table contains the list of valid properties that may be specified in the ""properties"" node of the ICF configuration file (ICFCONFIG.XML). These property values can be set and retrieved using calls to the Session Manager. They can thus be used to alter the way that the session performs depending on the session type. " DUMP-NAME "gscsp" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscsptrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscsptrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscspreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscsprepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscspreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscsptrigw.p" CRC "?" ADD FIELD "session_property_obj" OF "gsc_session_property" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Session Property Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Session property obj" DECIMALS 6 ORDER 10 ADD FIELD "session_property_name" OF "gsc_session_property" AS character DESCRIPTION "This is a unique name for this session property. The property name becomes the input parameter to a function that will return the value of the property. Certain SESSION handle attributes can be set using these properties. For example, defining a property session_propath will cause the session manager to set the SESSION:PROPATH attribute, defining a session_date_format will change SESSION:DATE-FORMAT and so on." FORMAT "X(28)" INITIAL "" LABEL "Session Property Name" POSITION 3 SQL-WIDTH 56 VALMSG "s_string_28" HELP "Session property name" ORDER 20 ADD FIELD "session_property_description" OF "gsc_session_property" AS character DESCRIPTION "This field describes in full the use of the property within the application, including valid values, and so on." FORMAT "X(70)" INITIAL "" LABEL "Session Property Description" POSITION 4 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Session property description" ORDER 30 ADD FIELD "system_owned" OF "gsc_session_property" AS logical DESCRIPTION "If set to YES this record may only be maintained by users who are permitted to maintain system data - as identified by a flag on the user record. This is to prevent accidental deletion of data required for the framework to work correctly." FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 5 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 40 ADD FIELD "default_property_value" OF "gsc_session_property" AS character DESCRIPTION "This field contains the default value that should be applied to this property. " FORMAT "X(70)" INITIAL "" LABEL "Default Property Value" POSITION 6 SQL-WIDTH 140 VALMSG "s_string_70" HELP "Default property value" ORDER 50 ADD FIELD "always_used" OF "gsc_session_property" AS logical DESCRIPTION "This field indicates if this property should always be written to ICF configuration file. If set to YES, when a session's information is written to the configuration file, the value of this property will be written whether or not an associative record exists in the gsm_session_type_property table. If no gsm_session_type_property record exists, the value will be set to the value in the default_property_value field. If set to NO, this property will only be written to the ICF configuration file if an associative record exists in the gsm_session_type_parm table." FORMAT "YES/NO" INITIAL "NO" LABEL "Always Used" POSITION 7 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Always used" ORDER 60 ADD INDEX "XPKgsc_session_property" ON "gsc_session_property" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "session_property_obj" ASCENDING ADD INDEX "XAK1gsc_session_property" ON "gsc_session_property" AREA "Schema Area" UNIQUE INDEX-FIELD "session_property_name" ASCENDING ADD TABLE "gsm_session_type_property" AREA "Schema Area" DESCRIPTION "This table resolves the many-to-many relationship between gsc_session_property and gsm_session_type. If a record is found in this table for a property and a session type, the value specified in that record is written to the ICF configuration file for the parameter. If no record exists for a given property and session type, the always_used flag on the gsc_session_property table is checked. If the flag is on, the default value in the default_property_value field on the gsc_session_property table is used." DUMP-NAME "gsmsy" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmsytrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmsytrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmsyreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmsyrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmsyreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmsytrigw.p" CRC "?" ADD FIELD "session_type_property_obj" OF "gsm_session_type_property" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Session Type Property Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Session type property obj" DECIMALS 6 ORDER 10 ADD FIELD "session_type_obj" OF "gsm_session_type_property" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Session Type Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Session type obj" DECIMALS 6 ORDER 20 ADD FIELD "session_property_obj" OF "gsm_session_type_property" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Session Property Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Session property obj" DECIMALS 6 ORDER 30 ADD FIELD "property_value" OF "gsm_session_type_property" AS character DESCRIPTION "This field contains the value of the session-specific value of the property." FORMAT "X(70)" INITIAL "" LABEL "Property Value" POSITION 5 SQL-WIDTH 140 VALMSG "s_string_70" HELP "Property value" ORDER 40 ADD INDEX "XPKgsm_session_type_property" ON "gsm_session_type_property" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "session_type_property_obj" ASCENDING ADD INDEX "XAK1gsm_session_type_property" ON "gsm_session_type_property" AREA "Schema Area" UNIQUE INDEX-FIELD "session_property_obj" ASCENDING INDEX-FIELD "session_type_obj" ASCENDING ADD INDEX "XIE1gsm_session_type_property" ON "gsm_session_type_property" AREA "Schema Area" INDEX-FIELD "session_type_obj" ASCENDING ADD TABLE "gsc_multi_media_type" AREA "Schema Area" DESCRIPTION "This table contains information related to different types of multi media files." DUMP-NAME "gscmm" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscmmtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscmmtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscmmreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscmmrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscmmreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscmmtrigw.p" CRC "?" ADD FIELD "multi_media_type_obj" OF "gsc_multi_media_type" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Multi Media Type Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Multi media type obj" DECIMALS 6 ORDER 10 ADD FIELD "multi_media_type_code" OF "gsc_multi_media_type" AS character DESCRIPTION "This field contains a unique code to identify this type of multi media file." FORMAT "X(10)" INITIAL "" LABEL "Multi Media Type Code" POSITION 3 SQL-WIDTH 20 VALMSG "s_code" HELP "Multi media type code" ORDER 20 ADD FIELD "multi_media_type_description" OF "gsc_multi_media_type" AS character FORMAT "X(35)" INITIAL "" LABEL "Multi Media Type Description" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Multi media type description" ORDER 30 ADD FIELD "application_launch_command" OF "gsc_multi_media_type" AS character DESCRIPTION "This field contains the relative path and name of the application used to create files of this multi media type." FORMAT "X(70)" INITIAL "" LABEL "Application Launch Command" POSITION 5 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Application launch command" ORDER 40 ADD FIELD "file_extension" OF "gsc_multi_media_type" AS character DESCRIPTION "The multimedia type file extension e.g. ""BMP"" = Bitmap image file ""JPG"" = JPEG image file ""AVI"" = Audio visual (video) ""WAV"" = Wave (sound) file etc." FORMAT "X(3)" INITIAL "" LABEL "File Extension" POSITION 6 SQL-WIDTH 6 VALMSG "s_string_3" HELP "File extension" ORDER 50 ADD FIELD "template_extension" OF "gsc_multi_media_type" AS character DESCRIPTION "This field contans the file extension of the template files used to create this type of multi media file e.g. ""DOT"" for MS Word documents ""XLT"" for MS Excel spreadsheets" FORMAT "X(3)" INITIAL "" LABEL "Template Extension" POSITION 7 SQL-WIDTH 6 VALMSG "s_string_3" HELP "Template extension" ORDER 60 ADD INDEX "XPKgsc_multi_media_type" ON "gsc_multi_media_type" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "multi_media_type_obj" ASCENDING ADD INDEX "XAK1gsc_multi_media_type" ON "gsc_multi_media_type" AREA "Schema Area" UNIQUE INDEX-FIELD "multi_media_type_code" ASCENDING ADD INDEX "XIE1gsc_multi_media_type" ON "gsc_multi_media_type" AREA "Schema Area" INDEX-FIELD "multi_media_type_description" ASCENDING ADD TABLE "gsm_category" AREA "Schema Area" DESCRIPTION "A multi-purpose grouping mechanism for generic entities. Certain categories may be system owned / generated and may not be deleted. These are usually hard coded into programs. Additionally, some categories may not be associated with another generic entity. These are used to store hard coded valid value lists, lookup lists, etc. Where ever we have made use of hard coded mnemonics within the application, their usage and description will be defined in this table. Refer to the ""Generic Table Usage"" document for a detailed description and sample instance data." DUMP-NAME "gsmca" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmcatrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmcatrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmcareplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmcarepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmcareplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmcatrigw.p" CRC "?" ADD FIELD "category_obj" OF "gsm_category" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Category Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Category obj" DECIMALS 6 ORDER 10 ADD FIELD "related_entity_mnemonic" OF "gsm_category" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Related Entity Mnemonic" POSITION 3 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Related entity mnemonic" ORDER 20 ADD FIELD "category_type" OF "gsm_category" AS character DESCRIPTION "The category type is the 1st level of grouping available within a related_global_entity to identify the category. A type must be specified. " FORMAT "X(3)" INITIAL "" LABEL "Category Type" POSITION 4 SQL-WIDTH 6 VALMSG "s_type" HELP "Category type" ORDER 30 ADD FIELD "category_group" OF "gsm_category" AS character DESCRIPTION "The category group is the 2nd level of grouping available within a related_global_entity to identify the category. The group is not mandatory. " FORMAT "X(3)" INITIAL "" LABEL "Category Group" POSITION 5 SQL-WIDTH 6 VALMSG "s_mnemonic" HELP "Category group" ORDER 40 ADD FIELD "category_subgroup" OF "gsm_category" AS character DESCRIPTION "The category subgroup is the 3rd level of grouping available within a related_global_entity which finally uniquely identifies the category. The subgroup is not mandatory. " FORMAT "X(3)" INITIAL "" LABEL "Category Subgroup" POSITION 6 SQL-WIDTH 6 VALMSG "s_mnemonic" HELP "Category subgroup" ORDER 50 ADD FIELD "category_label" OF "gsm_category" AS character DESCRIPTION "The screen / report label to use when referencing this category subgroup." FORMAT "X(28)" INITIAL "" LABEL "Category Label" POSITION 7 SQL-WIDTH 56 VALMSG "s_label" HELP "Category label" ORDER 70 ADD FIELD "category_group_seq" OF "gsm_category" AS integer DESCRIPTION "This is the sequence of category subgroups within a category group. An example use of this is where the category is used for status's. The category type will indicate a status (STS), the group will indicate the status usage, e.g. INV, CRD, etc. and the subgroup will indicate the actual status, e.g. unposted, posted, etc. The sequence in this case will be used in business logic to determine the progression of the object through the status subgroups." FORMAT "->>>>>9" INITIAL "0" LABEL "Category Group Seq." POSITION 8 SQL-WIDTH 4 VALMSG "n_integer_6" HELP "Category group seq." ORDER 60 ADD FIELD "category_description" OF "gsm_category" AS character FORMAT "X(35)" INITIAL "" LABEL "Category Description" POSITION 9 SQL-WIDTH 70 VALMSG "s_description" HELP "Category description" ORDER 80 ADD FIELD "owning_entity_mnemonic" OF "gsm_category" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Owning Entity Mnemonic" POSITION 10 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Owning entity mnemonic" ORDER 90 ADD FIELD "system_owned" OF "gsm_category" AS logical DESCRIPTION "If this is set to YES, then this category may not be amended or deleted." FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 11 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 100 ADD FIELD "validation_min_length" OF "gsm_category" AS integer DESCRIPTION "In the cases where the data contents need validation, the minimum allowable length for the data. E.g. for comment_text to force entry of certain categories of comments." FORMAT "->>>>>>>9" INITIAL "0" LABEL "Validation Min. Length" POSITION 12 SQL-WIDTH 4 VALMSG "n_integer_8" HELP "Validation min. length" ORDER 110 ADD FIELD "validation_max_length" OF "gsm_category" AS integer DESCRIPTION "In the cases where the data contents need validation, the maximum allowable length for the data. E.g. for comment_text to limit entry of certain categories of comments." FORMAT "->>>>>>>9" INITIAL "0" LABEL "Validation Max. Length" POSITION 13 SQL-WIDTH 4 VALMSG "n_integer_8" HELP "Validation max. length" ORDER 120 ADD FIELD "view_as_columns" OF "gsm_category" AS integer DESCRIPTION "In the case where the data contains a large amount of text, this facilitates the displaying of that data using an editor widget." FORMAT "->>9" INITIAL "0" LABEL "View as Columns" POSITION 14 SQL-WIDTH 4 VALMSG "n_integer_3" HELP "View as columns" ORDER 130 ADD FIELD "view_as_rows" OF "gsm_category" AS integer DESCRIPTION "In the case where the data contains a large amount of text, this facilitates the displaying of that data using an editor widget." FORMAT "->9" INITIAL "0" LABEL "View as Rows" POSITION 15 SQL-WIDTH 4 VALMSG "n_integer_2" HELP "View as rows" ORDER 140 ADD FIELD "category_mandatory" OF "gsm_category" AS logical DESCRIPTION "Is entry of this type of information mandatory against the owning object type. E.g. a family must have an address, a member may have an alternative address. In the case of categories of status's, by their very nature they are mandatory if they are system owned. This flag could therefore be used to indicate whether objects at this status may be modified or not." FORMAT "YES/NO" INITIAL "NO" LABEL "Category Mandatory" POSITION 16 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Category mandatory" ORDER 150 ADD FIELD "category_active" OF "gsm_category" AS logical DESCRIPTION "Is this category active. At any time setting this field to NO will disable further use of anything associated with this category." FORMAT "YES/NO" INITIAL "YES" LABEL "Category Active" POSITION 17 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Category active" ORDER 160 ADD INDEX "XPKgsm_category" ON "gsm_category" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "category_obj" ASCENDING ADD INDEX "XAK1gsm_category" ON "gsm_category" AREA "Schema Area" UNIQUE INDEX-FIELD "related_entity_mnemonic" ASCENDING INDEX-FIELD "category_type" ASCENDING INDEX-FIELD "category_group" ASCENDING INDEX-FIELD "category_subgroup" ASCENDING ADD INDEX "XIE1gsm_category" ON "gsm_category" AREA "Schema Area" INDEX-FIELD "category_label" ASCENDING ADD INDEX "XIE2gsm_category" ON "gsm_category" AREA "Schema Area" INDEX-FIELD "category_description" ASCENDING ADD INDEX "XIE3gsm_category" ON "gsm_category" AREA "Schema Area" INDEX-FIELD "related_entity_mnemonic" ASCENDING INDEX-FIELD "category_type" ASCENDING INDEX-FIELD "category_group" ASCENDING INDEX-FIELD "category_group_seq" ASCENDING ADD INDEX "XIE4gsm_category" ON "gsm_category" AREA "Schema Area" INDEX-FIELD "related_entity_mnemonic" ASCENDING INDEX-FIELD "category_subgroup" ASCENDING ADD INDEX "XIE5gsm_category" ON "gsm_category" AREA "Schema Area" INDEX-FIELD "related_entity_mnemonic" ASCENDING INDEX-FIELD "owning_entity_mnemonic" ASCENDING INDEX-FIELD "category_type" ASCENDING INDEX-FIELD "category_group" ASCENDING INDEX-FIELD "category_subgroup" ASCENDING ADD TABLE "gsm_multi_media" AREA "Schema Area" DESCRIPTION "Generic multi media file linked to any entity." DUMP-NAME "gsmmm" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmmmtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmmmtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmmmtrigw.p" CRC "?" ADD FIELD "multi_media_obj" OF "gsm_multi_media" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Multi Media Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Multi media obj" DECIMALS 6 ORDER 10 ADD FIELD "owning_obj" OF "gsm_multi_media" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Owning Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Owning obj" DECIMALS 6 ORDER 30 ADD FIELD "category_obj" OF "gsm_multi_media" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Category Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Category obj" DECIMALS 6 ORDER 20 ADD FIELD "multi_media_type_obj" OF "gsm_multi_media" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Multi Media Type Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Multi media type obj" DECIMALS 6 ORDER 40 ADD FIELD "physical_file_name" OF "gsm_multi_media" AS character DESCRIPTION "The physical filename including the relative path and file extension." FORMAT "X(70)" INITIAL "" LABEL "Physical File Name" POSITION 6 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Physical file name" ORDER 50 ADD FIELD "multi_media_description" OF "gsm_multi_media" AS character FORMAT "X(35)" INITIAL "" LABEL "Multi Media Description" POSITION 7 SQL-WIDTH 70 VALMSG "s_description" HELP "Multi media description" ORDER 60 ADD FIELD "creation_date" OF "gsm_multi_media" AS date FORMAT "99/99/9999" INITIAL "TODAY" LABEL "Creation Date" POSITION 8 SQL-WIDTH 4 VALMSG "d_date_today" HELP "Creation date" ORDER 70 ADD INDEX "XPKgsm_multi_media" ON "gsm_multi_media" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "multi_media_obj" ASCENDING ADD INDEX "XIE1gsm_multi_media" ON "gsm_multi_media" AREA "Schema Area" INDEX-FIELD "category_obj" ASCENDING INDEX-FIELD "owning_obj" ASCENDING INDEX-FIELD "multi_media_type_obj" ASCENDING INDEX-FIELD "creation_date" ASCENDING ADD INDEX "XIE2gsm_multi_media" ON "gsm_multi_media" AREA "Schema Area" INDEX-FIELD "physical_file_name" ASCENDING ADD INDEX "XIE3gsm_multi_media" ON "gsm_multi_media" AREA "Schema Area" INDEX-FIELD "multi_media_description" ASCENDING ADD INDEX "XIE4gsm_multi_media" ON "gsm_multi_media" AREA "Schema Area" INDEX-FIELD "owning_obj" ASCENDING ADD TABLE "gsm_login_company" AREA "Schema Area" DESCRIPTION "This framework table defines login companies (organisations) and is used to provide a list of valid companies the user may log into at runtime. It is intended that this table will link into an external application database where additional details will be stored for the login company, e.g. address and contact information. The code or the object field could be used as the xref into the external application database. The table is required in the framework to facilitate the generic set-up of framework data specific to login companies, e.g. security allocations, automatic reference numbers, etc. The existence of a login company in the framework supports the concept of holding multiple company application data in a single database as apposed to having separate databases for each company. Application databases would further have to link to this table or a corresponding table in their database design to filter appropriate data for each login company. We only hold on this table the minimum details as required by the framework. Applications that also have an organisation table will need to replicate modifications from their full organisation table into this table in order to simplify and syncrhonise maintenance of this data. " DUMP-NAME "gsmlg" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmlgtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmlgtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmlgtrigw.p" CRC "?" ADD FIELD "login_company_obj" OF "gsm_login_company" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Login Company Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Login company obj" DECIMALS 6 ORDER 10 ADD FIELD "login_company_code" OF "gsm_login_company" AS character DESCRIPTION "A unique code to identify the login company. This may be used as an xref into an external application database where the full login company details are stored." FORMAT "X(35)" INITIAL "" LABEL "Login Company Code" POSITION 3 SQL-WIDTH 70 VALMSG "s_name" HELP "Login company code" ORDER 20 ADD FIELD "login_company_short_name" OF "gsm_login_company" AS character DESCRIPTION "A short description of the login company used for lookup purposes." FORMAT "X(15)" INITIAL "" LABEL "Login Company Short Name" POSITION 4 SQL-WIDTH 30 VALMSG "s_short_name" HELP "Login company short name" ORDER 30 ADD FIELD "login_company_name" OF "gsm_login_company" AS character DESCRIPTION "The full name of the login company used when displaying the login company name on reports, status bars, etc." FORMAT "X(70)" INITIAL "" LABEL "Login Company Name" POSITION 5 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Login company name" ORDER 40 ADD FIELD "login_company_email" OF "gsm_login_company" AS character DESCRIPTION "The email address for the login company used for automatic notification messages, etc." FORMAT "X(35)" INITIAL "" LABEL "Login Company Email" POSITION 6 SQL-WIDTH 70 VALMSG "s_description" HELP "Login company email" ORDER 50 ADD FIELD "login_company_disabled" OF "gsm_login_company" AS logical DESCRIPTION "If set to YES, further use of this login company will be disabled and logins into this login company will be prevented." FORMAT "YES/NO" INITIAL "NO" LABEL "Login Company Disabled" POSITION 7 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Login company disabled" ORDER 60 ADD INDEX "XPKgsm_login_company" ON "gsm_login_company" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "login_company_obj" ASCENDING ADD INDEX "XAK1gsm_login_company" ON "gsm_login_company" AREA "Schema Area" UNIQUE INDEX-FIELD "login_company_code" ASCENDING ADD INDEX "XIE1gsm_login_company" ON "gsm_login_company" AREA "Schema Area" INDEX-FIELD "login_company_short_name" ASCENDING ADD INDEX "XIE2gsm_login_company" ON "gsm_login_company" AREA "Schema Area" INDEX-FIELD "login_company_name" ASCENDING ADD TABLE "gsc_product" AREA "Schema Area" DESCRIPTION "This table contains information about the installed products with appropriate license details." DUMP-NAME "gscpr" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscprtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscprtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscprreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscprrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscprreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscprtrigw.p" CRC "?" ADD FIELD "product_obj" OF "gsc_product" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Product Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Product obj" DECIMALS 6 ORDER 10 ADD FIELD "product_code" OF "gsc_product" AS character DESCRIPTION "a unique code to identify this product" FORMAT "X(10)" INITIAL "" LABEL "Product Code" POSITION 3 SQL-WIDTH 20 VALMSG "s_code" HELP "Product code" ORDER 20 ADD FIELD "product_description" OF "gsc_product" AS character DESCRIPTION "A full description of the product" FORMAT "X(35)" INITIAL "" LABEL "Product Description" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Product description" ORDER 30 ADD FIELD "product_installed" OF "gsc_product" AS logical DESCRIPTION "Set to YES where this product is installed." FORMAT "YES/NO" INITIAL "NO" LABEL "Product Installed" POSITION 5 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Product installed" ORDER 40 ADD FIELD "number_of_users" OF "gsc_product" AS integer DESCRIPTION "The number of licenses purchased for this product. Whether these are concurrent or not depends on your licensing rules." FORMAT "->>>>>9" INITIAL "0" LABEL "Number of Users" POSITION 6 SQL-WIDTH 4 VALMSG "n_integer_6" HELP "Number of users" ORDER 50 ADD FIELD "db_connection_pf_file" OF "gsc_product" AS character DESCRIPTION "The database connection file to run when a program is first executed for this product, to automatically connect relevant databases. The login procedure would use this value if applicable." FORMAT "X(70)" INITIAL "" LABEL "Db Connection Pf File" POSITION 7 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Db connection pf file" ORDER 60 ADD FIELD "supplier_organisation_obj" OF "gsc_product" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Supplier Organisation Obj" POSITION 8 SQL-WIDTH 21 VALMSG "o_obj" HELP "Supplier organisation obj" DECIMALS 6 ORDER 70 ADD INDEX "XPKgsc_product" ON "gsc_product" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "product_obj" ASCENDING ADD INDEX "XAK1gsc_product" ON "gsc_product" AREA "Schema Area" UNIQUE INDEX-FIELD "product_code" ASCENDING ADD INDEX "XIE1gsc_product" ON "gsc_product" AREA "Schema Area" INDEX-FIELD "product_description" ASCENDING ADD INDEX "XIE2gsc_product" ON "gsc_product" AREA "Schema Area" INDEX-FIELD "supplier_organisation_obj" ASCENDING ADD TABLE "gsc_product_module" AREA "Schema Area" DESCRIPTION "This table contains information about the installed product modules with appropriate license details." DUMP-NAME "gscpm" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscpmtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscpmtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscpmreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscpmrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscpmreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscpmtrigw.p" CRC "?" ADD FIELD "product_module_obj" OF "gsc_product_module" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Product Module Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Product module obj" DECIMALS 6 ORDER 10 ADD FIELD "product_obj" OF "gsc_product_module" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Product Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Product obj" DECIMALS 6 ORDER 20 ADD FIELD "product_module_code" OF "gsc_product_module" AS character DESCRIPTION "A code to uniquely identify the product module" FORMAT "X(10)" INITIAL "" LABEL "Product Module Code" POSITION 4 SQL-WIDTH 20 VALMSG "s_code" HELP "Product module code" ORDER 30 ADD FIELD "product_module_description" OF "gsc_product_module" AS character DESCRIPTION "a full description of the product module" FORMAT "X(35)" INITIAL "" LABEL "Product Module Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Product module description" ORDER 40 ADD FIELD "product_module_installed" OF "gsc_product_module" AS logical DESCRIPTION "Set to YES where this product module is installed." FORMAT "YES/NO" INITIAL "NO" LABEL "Product Module Installed" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Product module installed" ORDER 50 ADD FIELD "number_of_users" OF "gsc_product_module" AS integer DESCRIPTION "The number of licenses purchased for this module. Whether these are concurrent or not depends on your licensing rules." FORMAT "->>>>>9" INITIAL "0" LABEL "Number of Users" POSITION 7 SQL-WIDTH 4 VALMSG "n_integer_6" HELP "Number of users" ORDER 60 ADD FIELD "db_connection_pf_file" OF "gsc_product_module" AS character DESCRIPTION "The database connection file to run when a program is first executed for this product module, to automatically connect relevant databases. The login procedure would use this value if applicable." FORMAT "X(70)" INITIAL "" LABEL "Db Connection Pf File" POSITION 8 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Db connection pf file" ORDER 70 ADD FIELD "relative_path" OF "gsc_product_module" AS character DESCRIPTION "This is the relative path to objects located in this product module. The path should be relative to the workspace root directory and should not contain a slash at the end, nor at the beginning. This relative path will be used as a default for objects in this product module." FORMAT "X(70)" INITIAL "" LABEL "Relative Path" POSITION 9 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Relative path" ORDER 80 ADD INDEX "XPKgsc_product_module" ON "gsc_product_module" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "product_module_obj" ASCENDING ADD INDEX "XAK1gsc_product_module" ON "gsc_product_module" AREA "Schema Area" UNIQUE INDEX-FIELD "product_module_code" ASCENDING ADD INDEX "XIE1gsc_product_module" ON "gsc_product_module" AREA "Schema Area" INDEX-FIELD "product_module_description" ASCENDING ADD INDEX "XIE2gsc_product_module" ON "gsc_product_module" AREA "Schema Area" INDEX-FIELD "product_obj" ASCENDING INDEX-FIELD "product_module_code" ASCENDING ADD TABLE "gsc_object_type" AREA "Schema Area" DESCRIPTION "This table defines the types of programs supported. A record will need to exist for the various support templates, e.g. ""Object Controller"", ""Menu Controller"", ""SmartFolder"", smartbrowser, smartviewer, smartdataobject, etc. When objects are created, they must be assigned an object type. The object type is used as a grouping mechanism for security, to allow restrictions to be created for certain types of objects, rather than having to setup security for every object. " DUMP-NAME "gscot" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscottrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscottrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscotreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscotrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscotreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscottrigw.p" CRC "?" ADD FIELD "object_type_obj" OF "gsc_object_type" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Type Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object type obj" DECIMALS 6 ORDER 10 ADD FIELD "object_type_code" OF "gsc_object_type" AS character DESCRIPTION "A unique code for this type of object. It would be sensible to use the same name as Roundtable subtypes here, e.g. ""SmartFolder"", ""SmartWindow"", etc." FORMAT "X(15)" INITIAL "" LABEL "Object Type Code" POSITION 3 SQL-WIDTH 30 VALMSG "s_short_name" HELP "Object type code" ORDER 20 ADD FIELD "object_type_description" OF "gsc_object_type" AS character FORMAT "X(35)" INITIAL "" LABEL "Object Type Description" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Object type description" ORDER 30 ADD FIELD "disabled" OF "gsc_object_type" AS logical DESCRIPTION "If set to YES, then this object type will not be checked, and full access will be granted." FORMAT "YES/NO" INITIAL "NO" LABEL "Disabled" POSITION 5 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Disabled" ORDER 40 ADD FIELD "layout_supported" OF "gsc_object_type" AS logical DESCRIPTION "If set to YES, this is a non container smartobject that may require a layout if built dynamically." FORMAT "YES/NO" INITIAL "NO" LABEL "Layout Supported" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Layout supported" ORDER 50 ADD INDEX "XPKgsc_object_type" ON "gsc_object_type" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "object_type_obj" ASCENDING ADD INDEX "XAK1gsc_object_type" ON "gsc_object_type" AREA "Schema Area" UNIQUE INDEX-FIELD "object_type_code" ASCENDING ADD INDEX "XIE1gsc_object_type" ON "gsc_object_type" AREA "Schema Area" INDEX-FIELD "object_type_description" ASCENDING ADD TABLE "gsc_object" AREA "Schema Area" DESCRIPTION "This table defines the objects (programs) that exist within your applications. Not every program needs to be added as an object - only programs that require security, or that need to appear on a dynamic menu need be setup. Objects must be assigned an object type and belong to a product module. This facilitates setting up security based on object types and modules, rather than having to secure every object individually. This table now supports both physical and logical objects. If the object is a physical object, then the link to the physical object will be set to 0. If the object is a dynamic object, then the link to the physical object will point at the object to use as the starting point when building the dynamic object. If the object is flagged as a generic object, i.e. a physical object that is the basis for dynamic objects, then no security allocations, menus, etc. may be allocated to it as it is useless without the dynamic portions being built first against the logical objects that use it. For logical objects, the object name will be specified without a file extension, and the path will not be relevant. This repository concept means that many more objects will exist in this table. " DUMP-NAME "gscob" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscobtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscobtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscobreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscobrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscobreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscobtrigw.p" CRC "?" ADD FIELD "object_obj" OF "gsc_object" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object obj" DECIMALS 6 ORDER 10 ADD FIELD "object_type_obj" OF "gsc_object" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Type Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object type obj" DECIMALS 6 ORDER 20 ADD FIELD "product_module_obj" OF "gsc_object" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Product Module Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Product module obj" DECIMALS 6 ORDER 30 ADD FIELD "object_description" OF "gsc_object" AS character DESCRIPTION "A description of the object. This description will be used as the default for the menu label. Do not add ... to it as this is done automatically. " FORMAT "X(35)" INITIAL "" LABEL "Object Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Object description" ORDER 40 ADD FIELD "object_filename" OF "gsc_object" AS character DESCRIPTION "The filename of the object, without the path, but with an extension, e.g. .w The filename must be unique, even across product modules. If a file is generic, it must be added to a generic product module. This does not stop it appearing on different menus in different modules. To provide a facilty for the same object to have different security settings, it is possible to use instance attributes setup in gsc_instance_attribute" FORMAT "X(35)" INITIAL "" LABEL "Object Filename" POSITION 6 SQL-WIDTH 70 VALMSG "s_program_name" HELP "Object filename" ORDER 50 ADD FIELD "object_path" OF "gsc_object" AS character DESCRIPTION "The relative path to the object. This must contain forward slashes for portability. A relative path should always be used rather than an absolute path. Thre path must be relative to the workspace root directory. " FORMAT "X(70)" INITIAL "" LABEL "Object Path" POSITION 7 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Object path" ORDER 60 ADD FIELD "toolbar_multi_media_obj" OF "gsc_object" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Toolbar Multi Media Obj" POSITION 8 SQL-WIDTH 21 VALMSG "o_obj" HELP "Toolbar multi media obj" DECIMALS 6 ORDER 70 ADD FIELD "toolbar_image_filename" OF "gsc_object" AS character DESCRIPTION "This contains the filename of the bitmap image to display on dynamic toolbars where applicable. The filename is stored here as well as on the multi media file for performance reasons." FORMAT "X(70)" INITIAL "" LABEL "Toolbar Image Filename" POSITION 9 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Toolbar image filename" ORDER 80 ADD FIELD "tooltip_text" OF "gsc_object" AS character DESCRIPTION "The tooltip text to display when this object is placed on a dynamic toolbar." FORMAT "X(70)" INITIAL "" LABEL "Tooltip Text" POSITION 10 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Tooltip text" ORDER 90 ADD FIELD "runnable_from_menu" OF "gsc_object" AS logical DESCRIPTION "If set to YES, this obejct can be run from a menu. Objects such as smartbrowers, smartviewers, etc may be set-up in here for security purposes, but cannot be run from a menu. Object controllers and menu controllers can always be run from the menu. Smart folders can sometimes be run from a menu, depending on whether they are maintaining a specific record or not. If this flag is set to NO, this object cannot be placed on a menu or dynamic toolbar. " FORMAT "YES/NO" INITIAL "YES" LABEL "Runnable From Menu" POSITION 11 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Runnable from menu" ORDER 100 ADD FIELD "disabled" OF "gsc_object" AS logical DESCRIPTION "If set to YES, access to this object will be disabled, regardless of any other security settings." FORMAT "YES/NO" INITIAL "NO" LABEL "Disabled" POSITION 12 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Disabled" ORDER 110 ADD FIELD "run_persistent" OF "gsc_object" AS logical DESCRIPTION "If set to YES, this object will be run persistently." FORMAT "YES/NO" INITIAL "YES" LABEL "Run Persistent" POSITION 13 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Run persistent" ORDER 120 ADD FIELD "run_when" OF "gsc_object" AS character DESCRIPTION "This option controls under what circumstances this program may be run as follows: ""ONE"" = Only 1 instance of this program may be run at a time. ""NOT"" = This program may only be run when there is no transaction open. ""ANY"" = This program can be run anytime ""NOR"" = This program may only be run when no other programs are running. Whilst it is running, no other programs may be started. " FORMAT "X(3)" INITIAL "" LABEL "Run When" POSITION 14 SQL-WIDTH 6 VALMSG "s_mnemonic" HELP "Run when" ORDER 130 ADD FIELD "security_object_obj" OF "gsc_object" AS decimal DESCRIPTION "If set-up then security is enabled for this object, and the security to use is determined by the object specified. This object may be point at itself, but the attribute allows the additional flexibility of allowing a number of objects to share the same security settings." FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Security Object Obj" POSITION 15 SQL-WIDTH 21 VALMSG "o_obj" HELP "Security object obj" DECIMALS 6 ORDER 140 ADD FIELD "container_object" OF "gsc_object" AS logical DESCRIPTION "If set to YES, this object is a container window. Only container windows can possibly appear on menu's, and only container windows can have a dynamic menu structure. " FORMAT "YES/NO" INITIAL "YES" LABEL "Container Object" POSITION 16 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Container object" ORDER 150 ADD FIELD "physical_object_obj" OF "gsc_object" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Physical Object Obj" POSITION 17 SQL-WIDTH 21 VALMSG "o_obj" HELP "Physical object obj" DECIMALS 6 ORDER 160 ADD FIELD "logical_object" OF "gsc_object" AS logical DESCRIPTION "If set to YES, this object is a dynamically created object built using the object repository, and must point at a physical object to use as the strating point when building the dynamic object. A logical object cannot be a generic object." FORMAT "YES/NO" INITIAL "NO" LABEL "Logical Object" POSITION 18 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Logical object" ORDER 170 ADD FIELD "generic_object" OF "gsc_object" AS logical DESCRIPTION "If set to YES, this is a physical generic object used as the starting point for building a dynamic object and is not a complete object in itself." FORMAT "YES/NO" INITIAL "NO" LABEL "Generic Object" POSITION 19 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Generic object" ORDER 180 ADD FIELD "required_db_list" OF "gsc_object" AS character DESCRIPTION "This is a comma delimited list of database logical names that must be connected in order to run this object. For example ICFDB, RVDB. If any databases are specified and the databases are not connected, then the program will be prevented from running, the menu option / buttons it appears on will be disabled, etc. This is to facilitate a mixture of db-aware and non-db-aware objects to exist in the same session, and for the appropriate objects to be disabled when the databases are not available, which would be the case in a WEBClient implementation that does not support client database connections. In future, no visual objects should require a database connection. This is really for the transitional phase." FORMAT "X(35)" INITIAL "" LABEL "Required Db List" POSITION 20 SQL-WIDTH 70 VALMSG "s_name" HELP "Required db list" ORDER 190 ADD INDEX "XPKgsc_object" ON "gsc_object" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "object_obj" ASCENDING ADD INDEX "XAK1gsc_object" ON "gsc_object" AREA "Schema Area" UNIQUE INDEX-FIELD "product_module_obj" ASCENDING INDEX-FIELD "object_filename" ASCENDING ADD INDEX "XAK2gsc_object" ON "gsc_object" AREA "Schema Area" UNIQUE INDEX-FIELD "object_filename" ASCENDING ADD INDEX "XIE10gsc_object" ON "gsc_object" AREA "Schema Area" INDEX-FIELD "generic_object" ASCENDING ADD INDEX "XIE2gsc_object" ON "gsc_object" AREA "Schema Area" INDEX-FIELD "object_description" ASCENDING ADD INDEX "XIE4gsc_object" ON "gsc_object" AREA "Schema Area" INDEX-FIELD "object_type_obj" ASCENDING INDEX-FIELD "object_filename" ASCENDING ADD INDEX "XIE5gsc_object" ON "gsc_object" AREA "Schema Area" INDEX-FIELD "product_module_obj" ASCENDING INDEX-FIELD "object_type_obj" ASCENDING INDEX-FIELD "object_filename" ASCENDING ADD INDEX "XIE6gsc_object" ON "gsc_object" AREA "Schema Area" INDEX-FIELD "runnable_from_menu" ASCENDING INDEX-FIELD "product_module_obj" ASCENDING INDEX-FIELD "object_type_obj" ASCENDING ADD INDEX "XIE7gsc_object" ON "gsc_object" AREA "Schema Area" INDEX-FIELD "security_object_obj" ASCENDING ADD INDEX "XIE8gsc_object" ON "gsc_object" AREA "Schema Area" INDEX-FIELD "logical_object" ASCENDING ADD INDEX "XIE9gsc_object" ON "gsc_object" AREA "Schema Area" INDEX-FIELD "container_object" ASCENDING ADD TABLE "gsc_service_type" AREA "Schema Area" DESCRIPTION "This entity describes the different types of services available to applications and provides the management procedures for the different types of connections. To illustrate, database services, AppServer services and JMS partitions are all different service types. The Database and AppServer services are system owned. The maintenance object defines the datafield object used to maintain the physical connection parameter attribute on the physical service table. For example, if this is a service type for database connections, then the datafield may allow the specifiction of -S -N and -H prompts independantly and then put the result as 1 field into the connection parameter. The management object is the api procedure that is responsible for making the physical connections to the service. In the case of an appserver partition, the default logical service could point at the default logical appserver partition to use. " DUMP-NAME "gscst" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscsttrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscsttrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscstreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscstrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscstreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscsttrigw.p" CRC "?" ADD FIELD "service_type_obj" OF "gsc_service_type" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Service Type Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Service type obj" DECIMALS 6 ORDER 10 ADD FIELD "service_type_code" OF "gsc_service_type" AS character DESCRIPTION "A unique code to identify the service type." FORMAT "X(10)" INITIAL "" LABEL "Service Type Code" POSITION 3 SQL-WIDTH 20 VALMSG "s_code" HELP "Service type code" ORDER 20 ADD FIELD "management_object_obj" OF "gsc_service_type" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Management Object Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Management object obj" DECIMALS 6 ORDER 40 ADD FIELD "service_type_description" OF "gsc_service_type" AS character DESCRIPTION "A free text description of the service type." FORMAT "X(35)" INITIAL "" LABEL "Service Type Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Service type description" ORDER 30 ADD FIELD "maintenance_object_obj" OF "gsc_service_type" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Maintenance Object Obj" POSITION 6 SQL-WIDTH 21 VALMSG "o_obj" HELP "Maintenance object obj" DECIMALS 6 ORDER 50 ADD FIELD "default_logical_service_obj" OF "gsc_service_type" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Default Logical Service Obj" POSITION 7 SQL-WIDTH 21 VALMSG "o_obj" HELP "Default logical service obj" DECIMALS 6 ORDER 60 ADD INDEX "XPKgsc_service_type" ON "gsc_service_type" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "service_type_obj" ASCENDING ADD INDEX "XAK1gsc_service_type" ON "gsc_service_type" AREA "Schema Area" UNIQUE INDEX-FIELD "service_type_code" ASCENDING ADD INDEX "XIE1gsc_service_type" ON "gsc_service_type" AREA "Schema Area" INDEX-FIELD "service_type_description" ASCENDING ADD INDEX "XIE4gsc_service_type" ON "gsc_service_type" AREA "Schema Area" INDEX-FIELD "default_logical_service_obj" ASCENDING ADD INDEX "XIE5gsc_service_type" ON "gsc_service_type" AREA "Schema Area" INDEX-FIELD "maintenance_object_obj" ASCENDING ADD INDEX "XIE6gsc_service_type" ON "gsc_service_type" AREA "Schema Area" INDEX-FIELD "management_object_obj" ASCENDING ADD TABLE "gsc_logical_service" AREA "Schema Area" DESCRIPTION "This table defines the logical services available to the application. A logical service is a separate process running either locally or remotely that requires connection parameters to establish communication between the client and the service. Logical service names are unique so that connection to the service can be completely abstracted from the developer. The physical service will determine the actual connection parameters. Which physical service is used is determined by combining the session type with the logical service. Logical services for appserver service types would in fact be appserver partition names. Logical services for database connection service types would be the logical database name. " DUMP-NAME "gscls" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsclstrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsclstrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsclsreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsclsrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsclsreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsclstrigw.p" CRC "?" ADD FIELD "logical_service_obj" OF "gsc_logical_service" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Logical Service Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Logical service obj" DECIMALS 6 ORDER 10 ADD FIELD "service_type_obj" OF "gsc_logical_service" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Service Type Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Service type obj" DECIMALS 6 ORDER 40 ADD FIELD "logical_service_code" OF "gsc_logical_service" AS character DESCRIPTION "A unique code to identify the logical service. This code may be referenced in application source code and so may never be modified once it has been used." FORMAT "X(10)" INITIAL "" LABEL "Logical Service Code" POSITION 4 SQL-WIDTH 20 VALMSG "s_code" HELP "Logical service code" ORDER 20 ADD FIELD "logical_service_description" OF "gsc_logical_service" AS character DESCRIPTION "A free text description of the logical service." FORMAT "X(35)" INITIAL "" LABEL "Logical Service Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Logical service description" ORDER 30 ADD FIELD "can_run_locally" OF "gsc_logical_service" AS logical DESCRIPTION "If set to YES then this logical service may run locally, i.e. we do not need to create entries in the session service table. If set to NO, then we must have an entry in the session service table to use this partition." FORMAT "YES/NO" INITIAL "YES" LABEL "Can Run Locally" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Can run locally" ORDER 50 ADD FIELD "system_owned" OF "gsc_logical_service" AS logical DESCRIPTION "If set to YES this record may only be maintained by users who are permitted to maintain system data - as identified by a flag on the user record. This is to prevent accidental deletion of data required for the framework to work correctly." FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 7 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 60 ADD FIELD "write_to_config" OF "gsc_logical_service" AS logical DESCRIPTION "If set to yes, this attribute will force the system to write the procedure type and its relative path to the configuration file that is used at startup. This allows overriding of the default management procedures, such as the session manager, context manager, etc." FORMAT "YES/NO" INITIAL "NO" LABEL "Write to Config" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Write to config" ORDER 70 ADD INDEX "XPKgsc_logical_service" ON "gsc_logical_service" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "logical_service_obj" ASCENDING ADD INDEX "XAK1gsc_logical_service" ON "gsc_logical_service" AREA "Schema Area" UNIQUE INDEX-FIELD "logical_service_code" ASCENDING ADD INDEX "XIE1gsc_logical_service" ON "gsc_logical_service" AREA "Schema Area" INDEX-FIELD "logical_service_description" ASCENDING ADD INDEX "XIE2gsc_logical_service" ON "gsc_logical_service" AREA "Schema Area" INDEX-FIELD "service_type_obj" ASCENDING ADD TABLE "gsm_physical_service" AREA "Schema Area" DESCRIPTION "A physical service provides the specific connection parameters that are required to connect a physical service to a session. The physical service is connected to a logical service and session type via the session service. The maintenance object on the service type defines the datafield object used to maintain the physical connection parameters attribute. For example, if this is a service type for database connections, then the datafield may allow the specifiction of -S -N and -H prompts independantly and then put the result as 1 field into the connection parameters. The management object on the service type is the api procedure that is responsible for making the physical connections to the service. " DUMP-NAME "gsmpy" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmpytrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmpytrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmpyreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmpyrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmpyreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmpytrigw.p" CRC "?" ADD FIELD "physical_service_obj" OF "gsm_physical_service" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Physical Service Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Physical service obj" DECIMALS 6 ORDER 10 ADD FIELD "service_type_obj" OF "gsm_physical_service" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Service Type Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Service type obj" DECIMALS 6 ORDER 40 ADD FIELD "physical_service_code" OF "gsm_physical_service" AS character DESCRIPTION "A unique code to identify the physical service." FORMAT "X(10)" INITIAL "" LABEL "Physical Service Code" POSITION 4 SQL-WIDTH 20 VALMSG "s_code" HELP "Physical service code" ORDER 20 ADD FIELD "physical_service_description" OF "gsm_physical_service" AS character DESCRIPTION "A free text description of the physical service" FORMAT "X(35)" INITIAL "" LABEL "Physical Service Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Physical service description" ORDER 30 ADD FIELD "connection_parameters" OF "gsm_physical_service" AS character DESCRIPTION "This field contains the parameters required to make the physical connection to a service. Where the connection parameter string contain multiple values, the values are delimited by CHR(1). This field is maintained by the maintenance object as identified in the service type table. " FORMAT "X(500)" INITIAL "" LABEL "Connection Parameters" POSITION 6 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Connection parameters" ORDER 50 ADD INDEX "XPKgsm_physical_service" ON "gsm_physical_service" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "physical_service_obj" ASCENDING ADD INDEX "XAK1gsm_physical_service" ON "gsm_physical_service" AREA "Schema Area" UNIQUE INDEX-FIELD "physical_service_code" ASCENDING ADD INDEX "XIE1gsm_physical_service" ON "gsm_physical_service" AREA "Schema Area" INDEX-FIELD "physical_service_description" ASCENDING ADD INDEX "XIE2gsm_physical_service" ON "gsm_physical_service" AREA "Schema Area" INDEX-FIELD "service_type_obj" ASCENDING ADD TABLE "gsm_session_service" AREA "Schema Area" DESCRIPTION "The session service table defines the different physical services for each session type in order to establish the logical service. For example, an AppServer may require a shared memory connection to the repository database whereas a client session would require a network connection to the same databases. The physical connection parameters are different for each of these. Therefore the logical service identifies the database that needs to be connected and the physical service describes the mechanism for the connection dependant on the session type. If no session service record exists then the logical service can only run locally. " DUMP-NAME "gsmsv" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmsvtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmsvtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmsvreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmsvrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmsvreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmsvtrigw.p" CRC "?" ADD FIELD "session_service_obj" OF "gsm_session_service" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Session Service Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Session service obj" DECIMALS 6 ORDER 10 ADD FIELD "logical_service_obj" OF "gsm_session_service" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Logical Service Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Logical service obj" DECIMALS 6 ORDER 30 ADD FIELD "physical_service_obj" OF "gsm_session_service" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Physical Service Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Physical service obj" DECIMALS 6 ORDER 40 ADD FIELD "session_type_obj" OF "gsm_session_service" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Session Type Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Session type obj" DECIMALS 6 ORDER 20 ADD INDEX "XPKgsm_session_service" ON "gsm_session_service" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "session_service_obj" ASCENDING ADD INDEX "XAK1gsm_session_service" ON "gsm_session_service" AREA "Schema Area" UNIQUE INDEX-FIELD "session_type_obj" ASCENDING INDEX-FIELD "logical_service_obj" ASCENDING ADD INDEX "XAK2gsm_session_service" ON "gsm_session_service" AREA "Schema Area" UNIQUE INDEX-FIELD "logical_service_obj" ASCENDING INDEX-FIELD "session_type_obj" ASCENDING ADD INDEX "XIE1gsm_session_service" ON "gsm_session_service" AREA "Schema Area" INDEX-FIELD "physical_service_obj" ASCENDING ADD TABLE "gsm_flow" AREA "Schema Area" DESCRIPTION "A flow is a set of steps that have to be performed in a certain order to result in certain desired behavior. This table groups the steps that have to be performed. af/sup2/afrun2.i takes a parameter (&FLOW) which maps to one of these flows and then executes the steps that make up the flow. A flow must ultimately map to a single transaction and therefore must be executed on a single physical partition or service. Example flows may be shipOrder, completeOrder, postTransaction, etc. " DUMP-NAME "gsmfw" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmfwtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmfwtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmfwreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmfwrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmfwreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmfwtrigw.p" CRC "?" ADD FIELD "flow_obj" OF "gsm_flow" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Flow Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Flow obj" DECIMALS 6 ORDER 10 ADD FIELD "flow_name" OF "gsm_flow" AS character DESCRIPTION "A unique name via which to reference the flow. This flow name will be referenced in code and so may never be changed once it has been used anywhere. This flow name will be passed as an insertion code into afrun2.i which is used to launch business logic." FORMAT "X(35)" INITIAL "" LABEL "Flow Name" POSITION 3 SQL-WIDTH 70 VALMSG "s_name" HELP "Flow name" ORDER 20 ADD FIELD "flow_description" OF "gsm_flow" AS character FORMAT "X(35)" INITIAL "" LABEL "Flow Description" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Flow description" ORDER 30 ADD FIELD "product_module_obj" OF "gsm_flow" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Product Module Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Product module obj" DECIMALS 6 ORDER 40 ADD FIELD "system_owned" OF "gsm_flow" AS logical DESCRIPTION "If set to YES this record may only be maintained by users who are permitted to maintain system data - as identified by a flag on the user record. This is to prevent accidental deletion of data required for the framework to work correctly." FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 50 ADD FIELD "flow_narration" OF "gsm_flow" AS character DESCRIPTION "This is a free text description of the flow describing the purpose of the flow and the API required to use the flow." FORMAT "X(500)" INITIAL "" LABEL "Flow Narration" POSITION 7 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Flow narration" ORDER 60 ADD INDEX "XPKgsm_flow" ON "gsm_flow" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "flow_obj" ASCENDING ADD INDEX "XAK1gsm_flow" ON "gsm_flow" AREA "Schema Area" UNIQUE INDEX-FIELD "flow_name" ASCENDING ADD INDEX "XAK2gsm_flow" ON "gsm_flow" AREA "Schema Area" UNIQUE INDEX-FIELD "product_module_obj" ASCENDING INDEX-FIELD "flow_name" ASCENDING ADD INDEX "XIE1gsm_flow" ON "gsm_flow" AREA "Schema Area" INDEX-FIELD "flow_description" ASCENDING ADD TABLE "gsm_flow_step" AREA "Schema Area" DESCRIPTION "This table contains the steps that have to be followed to complete a flow. Each step may involve the running of an object, the running of an internal procedure within an object, or the execution of another complete flow. The flow steps may be customised for specific login organisations so that entire steps may be replaced with custom specific code. The standard flow steps will be specified with a 0 login company. Within a single flow the login company can either be 0 or a specific company. When running each step it will first check for a customisation for the login company and if not found will just run the standard step. If a customisation is found, this may either be an additional step in which case the custom step will be run first, or else it will be a complete replacement of the standard step. It is also possible to add custom steps that do not have any standard code at all, i.e. no step with a 0 login company exists. This facilitates adding customisations after the standard behaviour. and so setting up company specific steps would involve copying the default flow steps to a specific login company in full and then customising the specific steps as required. If the standard flow is modified, customised steps would also need to be manually modified as appropriate. " DUMP-NAME "gsmfs" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmfstrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmfstrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmfsreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmfsrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmfsreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmfstrigw.p" CRC "?" ADD FIELD "flow_step_obj" OF "gsm_flow_step" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Flow Step Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Flow step obj" DECIMALS 6 ORDER 10 ADD FIELD "flow_obj" OF "gsm_flow_step" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Flow Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Flow obj" DECIMALS 6 ORDER 20 ADD FIELD "flow_step_order" OF "gsm_flow_step" AS integer DESCRIPTION "This is the order that the steps within a flow must be executed. " FORMAT "->>>9" INITIAL "0" LABEL "Flow Step Order" POSITION 4 SQL-WIDTH 4 VALMSG "n_integer_4" HELP "Flow step order" ORDER 30 ADD FIELD "login_company_obj" OF "gsm_flow_step" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Login Company Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Login company obj" DECIMALS 6 ORDER 40 ADD FIELD "replace_standard_step" OF "gsm_flow_step" AS logical DESCRIPTION "This flag is only applicable if the login company is not 0. It indicates whether the custom specific step is in addition to the standard step or replaces completely the standard step. Therefore, if set to YES, the custom setp would replace the standard step idenitified by a login company of 0. When the step is an additional step, the custom step will always run first." FORMAT "YES/NO" INITIAL "NO" LABEL "Replace Standard Step" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Replace standard step" ORDER 50 ADD FIELD "object_obj" OF "gsm_flow_step" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Obj" POSITION 7 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object obj" DECIMALS 6 ORDER 60 ADD FIELD "internal_procedure" OF "gsm_flow_step" AS character DESCRIPTION "This is the internal procedure to run within the object specified. It is only applicable if the flow step is running an object persistently. " FORMAT "X(35)" INITIAL "" LABEL "Internal Procedure" POSITION 8 SQL-WIDTH 70 VALMSG "s_name" HELP "Internal procedure" ORDER 70 ADD FIELD "flow_step_flow_obj" OF "gsm_flow_step" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Flow Step Flow Obj" POSITION 9 SQL-WIDTH 21 VALMSG "o_obj" HELP "Flow step flow obj" DECIMALS 6 ORDER 80 ADD INDEX "XPKgsm_flow_step" ON "gsm_flow_step" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "flow_step_obj" ASCENDING ADD INDEX "XAK1gsm_flow_step" ON "gsm_flow_step" AREA "Schema Area" UNIQUE INDEX-FIELD "flow_obj" ASCENDING INDEX-FIELD "flow_step_order" ASCENDING INDEX-FIELD "login_company_obj" ASCENDING ADD INDEX "XAK2gsm_flow_step" ON "gsm_flow_step" AREA "Schema Area" UNIQUE INDEX-FIELD "login_company_obj" ASCENDING INDEX-FIELD "flow_obj" ASCENDING INDEX-FIELD "flow_step_order" ASCENDING ADD INDEX "XIE1gsm_flow_step" ON "gsm_flow_step" AREA "Schema Area" INDEX-FIELD "object_obj" ASCENDING ADD INDEX "XIE2gsm_flow_step" ON "gsm_flow_step" AREA "Schema Area" INDEX-FIELD "flow_step_flow_obj" ASCENDING ADD TABLE "gsm_startup_flow" AREA "Schema Area" DESCRIPTION "This table defines a list of flows that have to be run at startup of the session after the management procedures have been initialized, in order to perform any specific session setup, e.g. caching of various information." DUMP-NAME "gsmsf" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmsftrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmsftrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmsfreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmsfrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmsfreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmsftrigw.p" CRC "?" ADD FIELD "startup_flow_obj" OF "gsm_startup_flow" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Startup Flow Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Startup flow obj" DECIMALS 6 ORDER 10 ADD FIELD "session_type_obj" OF "gsm_startup_flow" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Session Type Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Session type obj" DECIMALS 6 ORDER 20 ADD FIELD "startup_order" OF "gsm_startup_flow" AS integer DESCRIPTION "This is the order that the startup flows must be executed. " FORMAT "->>9" INITIAL "0" LABEL "Startup Order" POSITION 4 SQL-WIDTH 4 VALMSG "n_integer_3" HELP "Startup order" ORDER 30 ADD FIELD "flow_obj" OF "gsm_startup_flow" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Flow Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Flow obj" DECIMALS 6 ORDER 40 ADD INDEX "XPKgsm_startup_flow" ON "gsm_startup_flow" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "startup_flow_obj" ASCENDING ADD INDEX "XAK1gsm_startup_flow" ON "gsm_startup_flow" AREA "Schema Area" UNIQUE INDEX-FIELD "session_type_obj" ASCENDING INDEX-FIELD "startup_order" ASCENDING ADD INDEX "XAK2gsm_startup_flow" ON "gsm_startup_flow" AREA "Schema Area" UNIQUE INDEX-FIELD "flow_obj" ASCENDING INDEX-FIELD "session_type_obj" ASCENDING ADD TABLE "gsm_valid_object_partition" AREA "Schema Area" DESCRIPTION "This table defines a list of valid partitions in which a procedure can be run. A partition is a logical AppServer Partition. The list only contains records when the object is restricted to certain partitions. When the object may be run on any partition, there are no records in this table. The records in this table are only applicable to appserver session types." DUMP-NAME "gsmvp" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmvptrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmvptrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmvpreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmvprepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmvpreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmvptrigw.p" CRC "?" ADD FIELD "valid_object_partition_obj" OF "gsm_valid_object_partition" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Valid Object Partition Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Valid object partition obj" DECIMALS 6 ORDER 10 ADD FIELD "logical_service_obj" OF "gsm_valid_object_partition" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Logical Service Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Logical service obj" DECIMALS 6 ORDER 20 ADD FIELD "object_obj" OF "gsm_valid_object_partition" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object obj" DECIMALS 6 ORDER 30 ADD INDEX "XPKgsm_valid_object_partition" ON "gsm_valid_object_partition" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "valid_object_partition_obj" ASCENDING ADD INDEX "XAK1gsm_valid_object_partition" ON "gsm_valid_object_partition" AREA "Schema Area" UNIQUE INDEX-FIELD "logical_service_obj" ASCENDING INDEX-FIELD "object_obj" ASCENDING ADD INDEX "XAK2gsm_valid_object_partition" ON "gsm_valid_object_partition" AREA "Schema Area" UNIQUE INDEX-FIELD "object_obj" ASCENDING INDEX-FIELD "logical_service_obj" ASCENDING ADD TABLE "gsc_manager_type" AREA "Schema Area" DESCRIPTION "This table contains the definition of the standard managers that are used in the framework. A predefined set of managers will exist in this table that support the framework functionality. Only managers that directly affect the core functionality of the framework need to be defined as manager types. For example, without a session manager we cannot start any other code, without a security manager we cannot do user authentication, etc. " DUMP-NAME "gscmt" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscmttrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscmttrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscmtreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscmtrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscmtreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscmttrigw.p" CRC "?" ADD FIELD "manager_type_obj" OF "gsc_manager_type" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Manager Type Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Manager type obj" DECIMALS 6 ORDER 10 ADD FIELD "manager_type_code" OF "gsc_manager_type" AS character DESCRIPTION "This field uniquely identifies a manager type. When the session is started, the manager type is used as the unique identifier to a temp-table record that contains the handle of the procedure that is functioning in the role of the specific manager. It is therefore used to locate the handle of the running manager procedure in order to utilise the api calls provided by the manager." FORMAT "X(28)" INITIAL "" LABEL "Manager Type Code" POSITION 3 SQL-WIDTH 56 VALMSG "s_label" HELP "Manager type code" ORDER 20 ADD FIELD "manager_type_name" OF "gsc_manager_type" AS character DESCRIPTION "A free text description of the manager type" FORMAT "X(35)" INITIAL "" LABEL "Manager Type Name" POSITION 4 SQL-WIDTH 70 VALMSG "s_name" HELP "Manager type name" ORDER 30 ADD FIELD "system_owned" OF "gsc_manager_type" AS logical DESCRIPTION "If set to YES this record may only be maintained by users who are permitted to maintain system data - as identified by a flag on the user record. This is to prevent accidental deletion of data required for the framework to work correctly." FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 5 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 40 ADD FIELD "write_to_config" OF "gsc_manager_type" AS logical DESCRIPTION "If set to yes, this attribute will force the system to write the procedure type and its relative path to the configuration file that is used at startup. This allows overriding of the default management procedures, such as the session manager, context manager, etc. This attribute only needs to be set for procedures that are required prior to connecting to the repository." FORMAT "YES/NO" INITIAL "NO" LABEL "Write to Config" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Write to config" ORDER 50 ADD FIELD "static_handle" OF "gsc_manager_type" AS character DESCRIPTION "Certain managers are always prestarted by the framework and due to their extensive use may be referenced by a static shared variable for maximum efficiency. The list of managers that have a static handle variable is hard coded in af/sup2/afglobals.i and may not be extended. Additional pre-started managers handles are available via standard function calls within the framework. This field identifies which of the standard managers if any this manager type is for, selectable from the following valid values: The predefined list is: NON = No static handle available (norm) AS = gshAstraAppServer SM = gshSessionManager SEM = gshSecurityManager PM = gshProfileManager RM = gshRepositoryManager TM = gshTranslationManager WM = gshWebManager FM = gshFinManager GM = gshGenManager AM = gshAgnManager" FORMAT "X(3)" INITIAL "" LABEL "Static Handle" POSITION 7 SQL-WIDTH 6 VALMSG "s_type" HELP "Static handle" ORDER 60 ADD FIELD "manager_narration" OF "gsc_manager_type" AS character DESCRIPTION "A free text description to describe the use and purpose of the manager. Also should include pointers to documentation describing the manager APIs" FORMAT "X(500)" INITIAL "" LABEL "Manager Narration" POSITION 8 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Manager narration" ORDER 70 ADD INDEX "XPKgsc_manager_type" ON "gsc_manager_type" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "manager_type_obj" ASCENDING ADD INDEX "XAK1gsc_manager_type" ON "gsc_manager_type" AREA "Schema Area" UNIQUE INDEX-FIELD "manager_type_code" ASCENDING ADD INDEX "XIE1gsc_manager_type" ON "gsc_manager_type" AREA "Schema Area" INDEX-FIELD "manager_type_name" ASCENDING ADD TABLE "gsm_required_manager" AREA "Schema Area" DESCRIPTION "This table contains a list of the managers that are required to be started during the startup of the session and the order in which they must be started. Any manager types which need to be written to the config file must always be started first. The write_to_config attribute of the manager will cause this procedure name to be written to the config.xml file so that it can be started up before the session makes a connection to the runtime repository. The framework supports a standard set of managers that are required but specific applications may require the startup of additional managers for performance reasons, e.g. a financial system may require a frequently referenced financial manager api to be pre-started." DUMP-NAME "gsmrm" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmrmtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmrmtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmrmreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmrmrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmrmreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmrmtrigw.p" CRC "?" ADD FIELD "required_manager_obj" OF "gsm_required_manager" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Required Manager Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Required manager obj" DECIMALS 6 ORDER 10 ADD FIELD "session_type_obj" OF "gsm_required_manager" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Session Type Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Session type obj" DECIMALS 6 ORDER 20 ADD FIELD "startup_order" OF "gsm_required_manager" AS integer DESCRIPTION "This field indicates the order in which the managers should be started." FORMAT "->>9" INITIAL "0" LABEL "Startup Order" POSITION 4 SQL-WIDTH 4 VALMSG "n_integer_3" HELP "Startup order" ORDER 30 ADD FIELD "manager_type_obj" OF "gsm_required_manager" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Manager Type Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Manager type obj" DECIMALS 6 ORDER 40 ADD FIELD "object_obj" OF "gsm_required_manager" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Obj" POSITION 6 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object obj" DECIMALS 6 ORDER 50 ADD FIELD "system_owned" OF "gsm_required_manager" AS logical DESCRIPTION "If set to YES this record may only be maintained by users who are permitted to maintain system data - as identified by a flag on the user record. This is to prevent accidental deletion of data required for the framework to work correctly." FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 7 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 60 ADD INDEX "XPKgsm_required_manager" ON "gsm_required_manager" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "required_manager_obj" ASCENDING ADD INDEX "XAK1gsm_required_manager" ON "gsm_required_manager" AREA "Schema Area" UNIQUE INDEX-FIELD "session_type_obj" ASCENDING INDEX-FIELD "startup_order" ASCENDING ADD INDEX "XAK2gsm_required_manager" ON "gsm_required_manager" AREA "Schema Area" UNIQUE INDEX-FIELD "manager_type_obj" ASCENDING INDEX-FIELD "session_type_obj" ASCENDING ADD INDEX "XIE2gsm_required_manager" ON "gsm_required_manager" AREA "Schema Area" INDEX-FIELD "object_obj" ASCENDING ADD TABLE "gsc_delivery_method" AREA "Schema Area" DESCRIPTION "The supported methods of delivery, e.g. by hand, post, email, collection, etc." DUMP-NAME "gscdm" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscdmtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscdmtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscdmreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscdmrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscdmreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscdmtrigw.p" CRC "?" ADD FIELD "delivery_method_obj" OF "gsc_delivery_method" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Delivery Method Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Delivery method obj" DECIMALS 6 ORDER 10 ADD FIELD "delivery_method_tla" OF "gsc_delivery_method" AS character FORMAT "X(3)" INITIAL "" LABEL "Delivery Method TLA" POSITION 3 SQL-WIDTH 6 VALMSG "s_tla" HELP "Delivery method three letter acronym" ORDER 20 ADD FIELD "delivery_method_short_desc" OF "gsc_delivery_method" AS character FORMAT "X(15)" INITIAL "" LABEL "Delivery Method Short Description" POSITION 4 SQL-WIDTH 30 COLUMN-LABEL "Delivery Method Short Desc" VALMSG "s_short_desc" HELP "Delivery method short description" ORDER 30 ADD FIELD "delivery_method_description" OF "gsc_delivery_method" AS character FORMAT "X(35)" INITIAL "" LABEL "Delivery Method Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Delivery method description" ORDER 40 ADD FIELD "postal_service_method" OF "gsc_delivery_method" AS logical DESCRIPTION "Does this delivery method utilise a postal service requiring postal addresses e.g. post office, DHL, etc. If it is, then the g_address.is_it_a_postal_address must also be set to yes to receive these type of deliveries. If it is set to no, then it is a physical delivery method, e.g. by hand and requires that g_address.is_it_a_delivery_address be set to yes." FORMAT "YES/NO" INITIAL "NO" LABEL "Postal Service Method" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Postal service method" ORDER 50 ADD FIELD "address_label_required" OF "gsc_delivery_method" AS logical DESCRIPTION "Is an address label required for this type of delivery method." FORMAT "YES/NO" INITIAL "NO" LABEL "Address Label Required" POSITION 7 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Address label required" ORDER 60 ADD FIELD "delivery_custom_procedure_obj" OF "gsc_delivery_method" AS decimal DESCRIPTION "This field contains a pointer to a customised procedure to accomodate the actual delivery e.g. a procedure to handle the email process." FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Delivery Custom Procedure Obj" POSITION 8 SQL-WIDTH 21 VALMSG "o_obj" HELP "Delivery custom procedure obj" DECIMALS 6 ORDER 70 ADD INDEX "XPKgsc_delivery_method" ON "gsc_delivery_method" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "delivery_method_obj" ASCENDING ADD INDEX "XAK1gsc_delivery_method" ON "gsc_delivery_method" AREA "Schema Area" UNIQUE INDEX-FIELD "delivery_method_tla" ASCENDING ADD INDEX "XIE1gsc_delivery_method" ON "gsc_delivery_method" AREA "Schema Area" INDEX-FIELD "delivery_method_short_desc" ASCENDING ADD INDEX "XIE2gsc_delivery_method" ON "gsc_delivery_method" AREA "Schema Area" INDEX-FIELD "delivery_method_description" ASCENDING ADD TABLE "gsc_document_type" AREA "Schema Area" DESCRIPTION "The document types supported by the system. Certain document types will be hard coded as they form an integral part of the application, e.g. membership cards, etc. Each document type will have one or more document formats associated with a customised formatting procedure. A document type should be set up for any outgoing documents. We need to know the document_type_tla for system owned document types as this will be used in any print_option_tlas fields to determine where certain data should be printed. " DUMP-NAME "gscdt" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscdttrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscdttrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscdtreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscdtrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscdtreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscdttrigw.p" CRC "?" ADD FIELD "document_type_obj" OF "gsc_document_type" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Document Type Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Document type obj" DECIMALS 6 ORDER 10 ADD FIELD "document_type_short_desc" OF "gsc_document_type" AS character FORMAT "X(15)" INITIAL "" LABEL "Document Type Short Description" POSITION 3 SQL-WIDTH 30 COLUMN-LABEL "Document Type Short Desc" VALMSG "s_short_desc" HELP "Document type short description" ORDER 30 ADD FIELD "document_type_tla" OF "gsc_document_type" AS character DESCRIPTION "A 3 character mnemonic to define the document type. The document_type_tla must be unique as it will be used in print_option_tlas fields to identify on which document types the relevant entity data should be printed. " FORMAT "X(3)" INITIAL "" LABEL "Document Type TLA" POSITION 4 SQL-WIDTH 6 VALMSG "s_tla" HELP "Document type three letter acronym" ORDER 20 ADD FIELD "document_type_description" OF "gsc_document_type" AS character FORMAT "X(35)" INITIAL "" LABEL "Document Type Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Document type description" ORDER 40 ADD FIELD "system_owned" OF "gsc_document_type" AS logical DESCRIPTION "Where a document type is system owned, the document_type_code will contain a hard coded value that will be referenced in program code. It may not be deleted." FORMAT "YES/NO" INITIAL "YES" LABEL "System Owned" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "System owned" ORDER 50 ADD FIELD "default_delivery_method" OF "gsc_document_type" AS decimal DESCRIPTION "The default way this type of document should be delivered, e.g. by hand, email, etc." FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Default Delivery Method" POSITION 7 SQL-WIDTH 21 VALMSG "o_obj" HELP "Default delivery method" DECIMALS 6 ORDER 60 ADD INDEX "XPKgsc_document_type" ON "gsc_document_type" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "document_type_obj" ASCENDING ADD INDEX "XAK1gsc_document_type" ON "gsc_document_type" AREA "Schema Area" UNIQUE INDEX-FIELD "document_type_tla" ASCENDING ADD INDEX "XIE1gsc_document_type" ON "gsc_document_type" AREA "Schema Area" INDEX-FIELD "document_type_description" ASCENDING ADD INDEX "XIE2gsc_document_type" ON "gsc_document_type" AREA "Schema Area" INDEX-FIELD "document_type_short_desc" ASCENDING ADD TABLE "gsm_report_definition" AREA "Schema Area" DESCRIPTION "This table contains control and default information about all the reports produced by the system. Note that all reports will be created by initially extracting a delimited data file which could then be printed using any reporting tool. This table actually defines the report extract procedure and default report options. The extract can the be printed in various formats as defined by the gsm_report_format table. The name of the extract file(s) produced will be hard coded in the extract procedure, but will be derived from the extract procedure name. The extension will be .rpd suffixed with the date and time down to seconds for multi-user support. The actual names used will be recorded in the gst_extract_log." DUMP-NAME "gsmrd" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmrdtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmrdtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmrdreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmrdrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmrdreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmrdtrigw.p" CRC "?" ADD FIELD "report_definition_obj" OF "gsm_report_definition" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Report Definition Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Report definition obj" DECIMALS 6 ORDER 10 ADD FIELD "report_description" OF "gsm_report_definition" AS character FORMAT "X(35)" INITIAL "" LABEL "Report Description" POSITION 3 SQL-WIDTH 70 VALMSG "s_description" HELP "Report description" ORDER 40 ADD FIELD "report_short_desc" OF "gsm_report_definition" AS character FORMAT "X(15)" INITIAL "" LABEL "Report Short Description" POSITION 4 SQL-WIDTH 30 COLUMN-LABEL "Report Short Desc" VALMSG "s_short_desc" HELP "Report short description" ORDER 30 ADD FIELD "next_extract_sequence" OF "gsm_report_definition" AS integer DESCRIPTION "A sequence number to which 1 is added each time the report has been run, unless it has a value of 0 in which case sequencing is not neccessary This should be printed on the report so that it can be recognised that a report is missing. " FORMAT "->>>>>>>9" INITIAL "0" LABEL "Next Extract Sequence" POSITION 5 SQL-WIDTH 4 COLUMN-LABEL "Next Extract Seq." VALMSG "n_sequence" HELP "Next. extract sequence" ORDER 50 ADD FIELD "report_procedure_name" OF "gsm_report_definition" AS character DESCRIPTION "The name of the procedure that does the data extract. This also is a unique identifying field for this table. The procedure name must be an external procedure (.p) that will be physically run to perform the extract. This in turn may call other internal procedures in plips. The procedure must contain no UI so that it can be run on the application server." FORMAT "X(35)" INITIAL "" LABEL "Report Procedure Name" POSITION 6 SQL-WIDTH 70 VALMSG "s_program_name" HELP "Report procedure name" ORDER 20 ADD FIELD "default_destination" OF "gsm_report_definition" AS character DESCRIPTION "If this is left blank, the report will print on the default printer, or in a UNIX environment, on the first printer with the correct stationery that is available. Otherwise this can contain the name of the printer to be used." FORMAT "X(35)" INITIAL "" LABEL "Default Destination" POSITION 7 SQL-WIDTH 70 VALMSG "s_description" HELP "Default destination" ORDER 80 ADD FIELD "default_priority" OF "gsm_report_definition" AS integer DESCRIPTION "The default priority to give the report when adding it to the spool queue (the gst_extract_log)." FORMAT "->>9" INITIAL "0" LABEL "Default Priority" POSITION 8 SQL-WIDTH 4 VALMSG "n_integer_3" HELP "Default priority" ORDER 120 ADD FIELD "default_copies_to_print" OF "gsm_report_definition" AS integer DESCRIPTION "The defaullt number of report copies to print." FORMAT "->>9" INITIAL "0" LABEL "Default Copies to Print" POSITION 9 SQL-WIDTH 4 VALMSG "n_integer_3" HELP "Default copies to print" ORDER 140 ADD FIELD "default_form_type" OF "gsm_report_definition" AS character DESCRIPTION "Default form to load when printing reports from this data." FORMAT "X(10)" INITIAL "" LABEL "Default Form Type" POSITION 10 SQL-WIDTH 20 VALMSG "s_string_10" HELP "Default form type" ORDER 100 ADD FIELD "default_days_to_retain" OF "gsm_report_definition" AS integer DESCRIPTION "The default number of days to retain the extracted data files for an instance of this report, pointed to by the extract log. After these days expire, the extracted data files will be automatically deleted via a daemon." FORMAT "->>9" INITIAL "0" LABEL "Default Days to Retain" POSITION 11 SQL-WIDTH 4 VALMSG "n_integer_3" HELP "Default days to retain" ORDER 150 ADD FIELD "allow_destination_override" OF "gsm_report_definition" AS logical DESCRIPTION "If set to YES, the user will be alllowed to specify the destination of this report at runtime." FORMAT "YES/NO" INITIAL "YES" LABEL "Allow Destination Override" POSITION 12 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Allow destination override" ORDER 90 ADD FIELD "allow_form_type_override" OF "gsm_report_definition" AS logical DESCRIPTION "If set to YES, the user will be alllowed to specify the form type of this report at runtime." FORMAT "YES/NO" INITIAL "YES" LABEL "Allow Form Type Override" POSITION 13 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Allow form type override" ORDER 110 ADD FIELD "allow_priority_override" OF "gsm_report_definition" AS logical DESCRIPTION "If set to YES, the user may override the default priority for this report if required for a specific instance of the report." FORMAT "YES/NO" INITIAL "NO" LABEL "Allow Priority Override" POSITION 14 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Allow priority override" ORDER 130 ADD FIELD "allow_server_printing" OF "gsm_report_definition" AS logical FORMAT "YES/NO" INITIAL "NO" LABEL "Allow Server Printing" POSITION 15 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Allow server printing" ORDER 60 ADD FIELD "allow_client_printing" OF "gsm_report_definition" AS logical FORMAT "YES/NO" INITIAL "YES" LABEL "Allow Client Printing" POSITION 16 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Allow client printing" ORDER 70 ADD FIELD "filter_database_list" OF "gsm_report_definition" AS character DESCRIPTION "Comma seperated list of databases, corresponding to field list for fields used as filters for the report, i.e. fields where a range could be entered to filter the report extract. The results of the filter information will be stored in the generic user parameter file gsc_parameter." FORMAT "X(3000)" INITIAL "" LABEL "Filter Database List" POSITION 17 SQL-WIDTH 6000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL LARGE MAX-CHARS 3000" VALMSG "s_comma_separated_list" HELP "Filter database list" ORDER 160 ADD FIELD "filter_table_list" OF "gsm_report_definition" AS character DESCRIPTION "Comma seperated list of tables, corresponding to field list for fields used as filters for the report, i.e. fields where a range could be entered to filter the report extract. The results of the filter information will be stored in the generic user parameter file gsc_parameter." FORMAT "X(3000)" INITIAL "" LABEL "Filter Table List" POSITION 18 SQL-WIDTH 6000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL LARGE MAX-CHARS 3000" VALMSG "s_comma_separated_list" HELP "Filter table list" ORDER 170 ADD FIELD "filter_field_list" OF "gsm_report_definition" AS character DESCRIPTION "Comma seperated list of fields used as filters for the report, i.e. fields where a range could be entered to filter the report extract. The results of the filter information will be stored in the generic user parameter file gsc_parameter." FORMAT "X(3000)" INITIAL "" LABEL "Filter Field List" POSITION 19 SQL-WIDTH 6000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL LARGE MAX-CHARS 3000" VALMSG "s_comma_separated_list" HELP "Filter field list" ORDER 180 ADD FIELD "filter_label_list" OF "gsm_report_definition" AS character DESCRIPTION "Comma seperated list of field labels, corresponding to field list for fields used as filters for the report, i.e. fields where a range could be entered to filter the report extract. The results of the filter information will be stored in the generic user parameter file gsc_parameter. The labels are the labels to use when prompting for the filter fields. The default will be automatically read from the metaschema." FORMAT "X(3000)" INITIAL "" LABEL "Filter Label List" POSITION 20 SQL-WIDTH 6000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL LARGE MAX-CHARS 3000" VALMSG "s_comma_separated_list" HELP "Filter label list" ORDER 190 ADD FIELD "filter_datatype_list" OF "gsm_report_definition" AS character DESCRIPTION "Comma seperated list of field data types, corresponding to field list for fields used as filters for the report, i.e. fields where a range could be entered to filter the report extract. The results of the filter information will be stored in the generic user parameter file gsc_parameter." FORMAT "X(3000)" INITIAL "" LABEL "Filter Datatype List" POSITION 21 SQL-WIDTH 6000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL LARGE MAX-CHARS 3000" VALMSG "s_comma_separated_list" HELP "Filter datatype list" ORDER 200 ADD FIELD "sort_by_field_list" OF "gsm_report_definition" AS character DESCRIPTION "List of fields (tablename.fieldname) via which to sort report by default." FORMAT "X(3000)" INITIAL "" LABEL "Sort by Field List" POSITION 22 SQL-WIDTH 6000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL LARGE MAX-CHARS 3000" VALMSG "s_comma_separated_list" HELP "Sort by field list" ORDER 210 ADD FIELD "report_distribution_list" OF "gsm_report_definition" AS character DESCRIPTION "A free text description of where the report should be distributed. To be printed on the report footer page." FORMAT "X(500)" INITIAL "" LABEL "Report Distribution List" POSITION 23 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Report distribution list" ORDER 220 ADD FIELD "document_type_obj" OF "gsm_report_definition" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Document Type Obj" POSITION 24 SQL-WIDTH 21 VALMSG "o_obj" HELP "Document type obj" DECIMALS 6 ORDER 230 ADD FIELD "launch_window_name" OF "gsm_report_definition" AS character DESCRIPTION "The name of the window (.w) that launches the extract, allows selection of printer, copies, etc. and requests / stores filter information for the report. The default generic launch window is af/cod/afprtfiltw.w " FORMAT "X(35)" INITIAL "" LABEL "Launch Window Name" POSITION 25 SQL-WIDTH 70 VALMSG "s_program_name" HELP "Launch window name" ORDER 240 ADD FIELD "default_password" OF "gsm_report_definition" AS character DESCRIPTION "This field provides an option for storing an encoded password on extract logs produced for this report definition.The first time the report is printed from the extract log, the password will not be required. Subsequent reprints will not be permitted until the correct password is entered. This prevents the unauthorised reprinting of reports from previously extracted data. " FORMAT "X(35)" INITIAL "" LABEL "Default Password" POSITION 26 SQL-WIDTH 70 VALMSG "s_description" HELP "Default password" ORDER 250 ADD FIELD "password_required" OF "gsm_report_definition" AS logical DESCRIPTION "If set to NO, the entry of an extract log password will not be requested. If set to YES, the entry of an extract log password will be forced." FORMAT "YES/NO" INITIAL "NO" LABEL "Password Required" POSITION 27 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Password required" ORDER 260 ADD FIELD "allow_password_override" OF "gsm_report_definition" AS logical DESCRIPTION "If set to YES, the user will be alllowed to specify a different extract log password at runtime." FORMAT "YES/NO" INITIAL "YES" LABEL "Allow Password Override" POSITION 28 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Allow password override" ORDER 270 ADD FIELD "encrypt_data_file" OF "gsm_report_definition" AS logical DESCRIPTION "If set to YES, the data files containing the xtracted data will be encrypted to prevent unauthorised viewing. The will be decrypted just prior to being passed to the reporting tool, e.g. Crystal Reports, then encrypted again if not being deleted." FORMAT "YES/NO" INITIAL "NO" LABEL "Encrypt Data File" POSITION 29 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Encrypt data file" ORDER 280 ADD FIELD "allow_encrypt_override" OF "gsm_report_definition" AS logical DESCRIPTION "If set to YES, the decision of whether the data files should be encrypted or not may be made at runtime." FORMAT "YES/NO" INITIAL "YES" LABEL "Allow Encrypt Override" POSITION 30 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Allow encrypt override" ORDER 290 ADD FIELD "auto_delete_data_file" OF "gsm_report_definition" AS logical DESCRIPTION "If set to YES, the data files containg the extracted data, together with the extract log record will be deleted immediately the initial print has been completed. This override the retain duration settings and is primarily for secure data that must not be left lying around." FORMAT "YES/NO" INITIAL "NO" LABEL "Auto Delete Data File" POSITION 31 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Auto delete data file" ORDER 300 ADD FIELD "allow_auto_delete_override" OF "gsm_report_definition" AS logical DESCRIPTION "If set to YES, the decision of whether the data files should be automatically deleted or not may be made at runtime." FORMAT "YES/NO" INITIAL "YES" LABEL "Allow Auto Delete Override" POSITION 32 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Allow auto delete override" ORDER 310 ADD FIELD "under_development" OF "gsm_report_definition" AS logical DESCRIPTION "If set to YES, this report is still under development and may not be launched by users who are no developers." FORMAT "YES/NO" INITIAL "NO" LABEL "Under Development" POSITION 33 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Under development" ORDER 320 ADD FIELD "report_definition_reference" OF "gsm_report_definition" AS character DESCRIPTION "A unique and automatically generated reference for a report definition - used to uniquely identify the report rather than the report procedure name - to allow the procedure name to be changed easily without causing problems when releasing system owned data." FORMAT "X(15)" INITIAL "" LABEL "Report Definition Reference" POSITION 34 SQL-WIDTH 30 VALMSG "s_reference" HELP "Report definition reference" ORDER 330 ADD INDEX "XPKgsm_report_definition" ON "gsm_report_definition" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "report_definition_obj" ASCENDING ADD INDEX "XAK1gsm_report_definition" ON "gsm_report_definition" AREA "Schema Area" UNIQUE INDEX-FIELD "report_definition_reference" ASCENDING ADD INDEX "XIE1gsm_report_definition" ON "gsm_report_definition" AREA "Schema Area" INDEX-FIELD "report_short_desc" ASCENDING ADD INDEX "XIE2gsm_report_definition" ON "gsm_report_definition" AREA "Schema Area" INDEX-FIELD "report_description" ASCENDING ADD INDEX "XIE3gsm_report_definition" ON "gsm_report_definition" AREA "Schema Area" INDEX-FIELD "document_type_obj" ASCENDING ADD INDEX "XIE4gsm_report_definition" ON "gsm_report_definition" AREA "Schema Area" INDEX-FIELD "launch_window_name" ASCENDING ADD INDEX "XIE5gsm_report_definition" ON "gsm_report_definition" AREA "Schema Area" INDEX-FIELD "report_procedure_name" ASCENDING ADD TABLE "gsm_reporting_tool" AREA "Schema Area" DESCRIPTION "This table contains information about the reporting tools available to the system. These would be: Progress Results Crystal reports Actuate etc." DUMP-NAME "gsmre" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmretrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmretrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmrereplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmrerepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmrereplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmretrigw.p" CRC "?" ADD FIELD "reporting_tool_obj" OF "gsm_reporting_tool" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Reporting Tool Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Reporting tool obj" DECIMALS 6 ORDER 10 ADD FIELD "reporting_tool_code" OF "gsm_reporting_tool" AS character DESCRIPTION "A code to uniquely identify the reporting tool." FORMAT "X(10)" INITIAL "" LABEL "Reporting Tool Code" POSITION 3 SQL-WIDTH 20 VALMSG "s_code" HELP "Reporting tool code" ORDER 20 ADD FIELD "reporting_tool_description" OF "gsm_reporting_tool" AS character FORMAT "X(35)" INITIAL "" LABEL "Reporting Tool Description" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Reporting tool description" ORDER 30 ADD FIELD "launch_command" OF "gsm_reporting_tool" AS character DESCRIPTION "The command to launch the reporting tool. This would include a set of parameters that would be substituted by the system when the report is initiated and would include: &repformat = Report formatting procedure &datafile = Data file name &copies = Copies to print &formname = Stationery form name &retention = Retention days &priority = Priority &destination = Destination printer etc." FORMAT "X(70)" INITIAL "" LABEL "Launch Command" POSITION 5 SQL-WIDTH 140 VALMSG "s_string_70" HELP "Launch command" ORDER 40 ADD INDEX "XPKgsm_reporting_tool" ON "gsm_reporting_tool" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "reporting_tool_obj" ASCENDING ADD INDEX "XAK1gsm_reporting_tool" ON "gsm_reporting_tool" AREA "Schema Area" UNIQUE INDEX-FIELD "reporting_tool_code" ASCENDING ADD TABLE "gsm_report_format" AREA "Schema Area" DESCRIPTION "Once data for a report has been extracted, it may be printed in different formats using different reporting tools. This table defines the report procedures that may be used to format the extracted data. If printing to Crystal, the report fromat procedure is the name of the Crystal Report definition file. The extract files to send as data to the report will be hard coded in the report extract procedure." DUMP-NAME "gsmrf" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmrftrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmrftrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmrfreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmrfrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmrfreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmrftrigw.p" CRC "?" ADD FIELD "report_definition_obj" OF "gsm_report_format" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Report Definition Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Report definition obj" DECIMALS 6 ORDER 10 ADD FIELD "report_format_obj" OF "gsm_report_format" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Report Format Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Report format obj" DECIMALS 6 ORDER 20 ADD FIELD "report_format_description" OF "gsm_report_format" AS character FORMAT "X(35)" INITIAL "" LABEL "Report Format Description" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Report format description" ORDER 30 ADD FIELD "reporting_tool_obj" OF "gsm_report_format" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Reporting Tool Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Reporting tool obj" DECIMALS 6 ORDER 40 ADD FIELD "report_formatting_procedure" OF "gsm_report_format" AS character DESCRIPTION "The formatting procedure to be passed to the reporting tool. For example: In Crystal reports this would be the report name. In Progress, this would be the print procedure name." FORMAT "X(35)" INITIAL "" LABEL "Report Formatting Procedure" POSITION 6 SQL-WIDTH 70 VALMSG "s_program_procedure" HELP "Report formatting procedure" ORDER 50 ADD FIELD "is_this_the_default" OF "gsm_report_format" AS logical DESCRIPTION "If a report format has not been selected by a user before, this would be the default. " FORMAT "YES/NO" INITIAL "YES" LABEL "is This The Default" POSITION 7 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Is this the default" ORDER 60 ADD FIELD "landscape_report" OF "gsm_report_format" AS logical DESCRIPTION "If set to YES, then this report will default to print in landscape mode at width 132 columns. It will only really make a difference when printing to a laser printer." FORMAT "YES/NO" INITIAL "NO" LABEL "Landscape Report" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Landscape report" ORDER 70 ADD FIELD "laser_report_only" OF "gsm_report_format" AS logical DESCRIPTION "If set to YES, this report can only be printed on a laser printer, due to the fact it contains complex graphics, etc." FORMAT "YES/NO" INITIAL "NO" LABEL "Laser Report Only" POSITION 9 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Laser report only" ORDER 80 ADD FIELD "report_format_reference" OF "gsm_report_format" AS character DESCRIPTION "A unique and automatically generated reference for a menu item - used when releasing menu items to site to be able to update existing menu items, rather than deleting and recreating." FORMAT "X(15)" INITIAL "" LABEL "Report Format Reference" POSITION 10 SQL-WIDTH 30 VALMSG "s_reference" HELP "Report format reference" ORDER 90 ADD FIELD "form_type" OF "gsm_report_format" AS character DESCRIPTION "form to load when printing reports from this data." FORMAT "X(10)" INITIAL "" LABEL "Form Type" POSITION 11 SQL-WIDTH 20 VALMSG "s_string_10" HELP "Form type" ORDER 100 ADD FIELD "page_length" OF "gsm_report_format" AS integer DESCRIPTION "Number of lines on a page for this report, e.g. 72 for A4 printing." FORMAT "->>9" INITIAL "0" LABEL "Page Length" POSITION 12 SQL-WIDTH 4 VALMSG "n_integer_3" HELP "Page length" ORDER 110 ADD FIELD "paper_bin" OF "gsm_report_format" AS character DESCRIPTION "Default bin, e.g. top, bottom, manual, auto" FORMAT "X(15)" INITIAL "" LABEL "Paper Bin" POSITION 13 SQL-WIDTH 30 VALMSG "s_reference" HELP "Paper bin" ORDER 120 ADD FIELD "paper_type" OF "gsm_report_format" AS character DESCRIPTION "Paper type, e.g. A4, Letter, Legal, etc." FORMAT "X(15)" INITIAL "" LABEL "Paper Type" POSITION 14 SQL-WIDTH 30 VALMSG "s_reference" HELP "Paper type" ORDER 130 ADD FIELD "default_font" OF "gsm_report_format" AS character DESCRIPTION "Default font - must be from a standard registry font, e.g. Times New Roman, 10pt" FORMAT "X(35)" INITIAL "" LABEL "Default Font" POSITION 15 SQL-WIDTH 70 VALMSG "s_name" HELP "Default font" ORDER 140 ADD INDEX "XPKgsm_report_format" ON "gsm_report_format" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "report_definition_obj" ASCENDING INDEX-FIELD "report_format_obj" ASCENDING ADD INDEX "XAK1gsm_report_format" ON "gsm_report_format" AREA "Schema Area" UNIQUE INDEX-FIELD "report_format_reference" ASCENDING ADD INDEX "XAK2gsm_report_format" ON "gsm_report_format" AREA "Schema Area" UNIQUE INDEX-FIELD "report_format_obj" ASCENDING ADD INDEX "XIE1gsm_report_format" ON "gsm_report_format" AREA "Schema Area" INDEX-FIELD "report_definition_obj" ASCENDING INDEX-FIELD "report_format_description" ASCENDING ADD INDEX "XIE2gsm_report_format" ON "gsm_report_format" AREA "Schema Area" INDEX-FIELD "report_definition_obj" ASCENDING INDEX-FIELD "is_this_the_default" ASCENDING ADD INDEX "XIE3gsm_report_format" ON "gsm_report_format" AREA "Schema Area" INDEX-FIELD "report_formatting_procedure" ASCENDING ADD TABLE "gsm_default_report_format" AREA "Schema Area" DESCRIPTION "This table provides an override mechanism for default report layouts. For example, specific organisations or people can specify a different default report format for a specific document type. This would typically be used for login company organisations, where for each of the different login companies, a different statement print layout or cheque layout , etc. could be used by default." DUMP-NAME "gsmdr" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmdrtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmdrtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmdrreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmdrrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmdrreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmdrtrigw.p" CRC "?" ADD FIELD "default_report_format_obj" OF "gsm_default_report_format" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Default Report Format Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Default report format obj" DECIMALS 6 ORDER 10 ADD FIELD "owning_entity_mnemonic" OF "gsm_default_report_format" AS character DESCRIPTION "The hard coded entity mnemonics allocated to every table in the application. The hard coded list of entity mnemonics is documented in the ""Key to Entity Mnemonics"" document." FORMAT "X(8)" INITIAL "" LABEL "Owning Entity Mnemonic" POSITION 3 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Owning entity mnemonic" ORDER 30 ADD FIELD "report_definition_obj" OF "gsm_default_report_format" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Report Definition Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Report definition obj" DECIMALS 6 ORDER 20 ADD FIELD "owning_obj" OF "gsm_default_report_format" AS decimal DESCRIPTION "This is the object number of the record in the table refered to by the owning_obj_entity" FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Owning Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Owning obj" DECIMALS 6 ORDER 40 ADD FIELD "document_type_obj" OF "gsm_default_report_format" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Document Type Obj" POSITION 6 SQL-WIDTH 21 VALMSG "o_obj" HELP "Document type obj" DECIMALS 6 ORDER 50 ADD FIELD "report_format_obj" OF "gsm_default_report_format" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Report Format Obj" POSITION 7 SQL-WIDTH 21 VALMSG "o_obj" HELP "Report format obj" DECIMALS 6 ORDER 60 ADD INDEX "XPKgsm_default_report_format" ON "gsm_default_report_format" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "default_report_format_obj" ASCENDING ADD INDEX "XAK1gsm_default_report_format" ON "gsm_default_report_format" AREA "Schema Area" UNIQUE INDEX-FIELD "owning_entity_mnemonic" ASCENDING INDEX-FIELD "owning_obj" ASCENDING INDEX-FIELD "document_type_obj" ASCENDING ADD TABLE "gsc_language" AREA "Schema Area" DESCRIPTION "The languages supported by the system." DUMP-NAME "gsclg" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsclgtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsclgtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsclgreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsclgrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsclgreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsclgtrigw.p" CRC "?" ADD FIELD "language_obj" OF "gsc_language" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Language Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Language obj" DECIMALS 6 ORDER 10 ADD FIELD "language_code" OF "gsc_language" AS character FORMAT "X(10)" INITIAL "" LABEL "Language Code" POSITION 3 SQL-WIDTH 20 VALMSG "s_code" HELP "Language code" ORDER 20 ADD FIELD "language_name" OF "gsc_language" AS character FORMAT "X(35)" INITIAL "" LABEL "Language Name" POSITION 4 SQL-WIDTH 70 VALMSG "s_name" HELP "Language name" ORDER 30 ADD FIELD "person_title1_label" OF "gsc_language" AS character DESCRIPTION "This is the screen label to use when prmpting for the 1st person title in this language." FORMAT "X(28)" INITIAL "" LABEL "Person Title1 Label" POSITION 5 SQL-WIDTH 56 VALMSG "s_label" HELP "Person title1 label" ORDER 40 ADD FIELD "person_title2_label" OF "gsc_language" AS character DESCRIPTION "This is the screen label to use when prmpting for the 2nd person title in this language if applicable." FORMAT "X(28)" INITIAL "" LABEL "Person Title2 Label" POSITION 6 SQL-WIDTH 56 VALMSG "s_label" HELP "Person title2 label" ORDER 50 ADD FIELD "person_title3_label" OF "gsc_language" AS character DESCRIPTION "This is the screen label to use when prmpting for the 3rd person title in this language if applicable." FORMAT "X(28)" INITIAL "" LABEL "Person Title3 Label" POSITION 7 SQL-WIDTH 56 VALMSG "s_label" HELP "Person title3 label" ORDER 60 ADD INDEX "XPKgsc_language" ON "gsc_language" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "language_obj" ASCENDING ADD INDEX "XAK1gsc_language" ON "gsc_language" AREA "Schema Area" UNIQUE INDEX-FIELD "language_code" ASCENDING ADD INDEX "XIE1gsc_language" ON "gsc_language" AREA "Schema Area" INDEX-FIELD "language_name" ASCENDING ADD TABLE "gsm_translation" AREA "Schema Area" DESCRIPTION "This table containes user defined translations for the various languages for widget labels and tooltip text. The setup of every program will first walk the widget tree and change the label / tooltip to the entry in this table according to the language selected by the user - if an entry exists. Translations can be turned off globally using the gsc_security_control.translation_enabled flag. " DUMP-NAME "gsmtl" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmtltrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmtltrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmtlreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmtlrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmtlreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmtltrigw.p" CRC "?" ADD FIELD "translation_obj" OF "gsm_translation" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Translation Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Translation obj" DECIMALS 6 ORDER 10 ADD FIELD "language_obj" OF "gsm_translation" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Language Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Language obj" DECIMALS 6 ORDER 20 ADD FIELD "object_filename" OF "gsm_translation" AS character DESCRIPTION "The filename of the object the widget is contained on. The filename must be specified with an enxtension of .w but no path, as per gsc_object. If the filename is blank, then the entry applies to all objects where the widget appears. " FORMAT "X(35)" INITIAL "" LABEL "Object Filename" POSITION 4 SQL-WIDTH 70 VALMSG "s_program_name" HELP "Object filename" ORDER 30 ADD FIELD "widget_type" OF "gsm_translation" AS character DESCRIPTION "The type of widget. The valid values are: TITLE = window title BROWSE = column name FILL-IN RADIO-SET TEXT BUTTON TOGGLE-BOX COMBO-BOX SLIDER EDITOR " FORMAT "X(35)" INITIAL "" LABEL "Widget Type" POSITION 5 SQL-WIDTH 70 VALMSG "s_name" HELP "Widget type" ORDER 40 ADD FIELD "widget_name" OF "gsm_translation" AS character DESCRIPTION "The actual name of the widget. If it is a database connected widget, then this field will contain table.fieldname otherwise it will just contain the widget name. The exception is ""title"" for a window title. " FORMAT "X(70)" INITIAL "" LABEL "Widget Name" POSITION 6 SQL-WIDTH 140 VALMSG "s_big_name" HELP "Widget name" ORDER 50 ADD FIELD "widget_entry" OF "gsm_translation" AS integer DESCRIPTION "If the widget has multiple values, as is the case with a radio-set, then this is the entry number within the value list for the widget that this translation applies to." FORMAT "->9" INITIAL "0" LABEL "Widget Entry" POSITION 7 SQL-WIDTH 4 VALMSG "n_integer_2" HELP "Widget entry" ORDER 60 ADD FIELD "original_label" OF "gsm_translation" AS character DESCRIPTION "The original label text before modification" FORMAT "X(28)" INITIAL "" LABEL "Original Label" POSITION 8 SQL-WIDTH 56 VALMSG "s_label" HELP "Original label" ORDER 70 ADD FIELD "translation_label" OF "gsm_translation" AS character DESCRIPTION "The new translated label text" FORMAT "X(28)" INITIAL "" LABEL "Translation Label" POSITION 9 SQL-WIDTH 56 VALMSG "s_label" HELP "Translation label" ORDER 80 ADD FIELD "original_tooltip" OF "gsm_translation" AS character DESCRIPTION "The original tooltip as per the schema help." FORMAT "X(70)" INITIAL "" LABEL "Original Tooltip" POSITION 10 SQL-WIDTH 140 VALMSG "s_big_name" HELP "Original tooltip" ORDER 90 ADD FIELD "translation_tooltip" OF "gsm_translation" AS character DESCRIPTION "The translated tooltip." FORMAT "X(70)" INITIAL "" LABEL "Translation Tooltip" POSITION 11 SQL-WIDTH 140 VALMSG "s_big_name" HELP "Translation tooltip" ORDER 100 ADD INDEX "XPKgsm_translation" ON "gsm_translation" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "translation_obj" ASCENDING ADD INDEX "XAK1gsm_translation" ON "gsm_translation" AREA "Schema Area" UNIQUE INDEX-FIELD "object_filename" ASCENDING INDEX-FIELD "widget_type" ASCENDING INDEX-FIELD "widget_name" ASCENDING INDEX-FIELD "widget_entry" ASCENDING INDEX-FIELD "language_obj" ASCENDING ADD INDEX "XAK2gsm_translation" ON "gsm_translation" AREA "Schema Area" UNIQUE INDEX-FIELD "language_obj" ASCENDING INDEX-FIELD "object_filename" ASCENDING INDEX-FIELD "widget_type" ASCENDING INDEX-FIELD "widget_name" ASCENDING INDEX-FIELD "widget_entry" ASCENDING ADD INDEX "XIE1gsm_translation" ON "gsm_translation" AREA "Schema Area" INDEX-FIELD "widget_name" ASCENDING INDEX-FIELD "widget_entry" ASCENDING INDEX-FIELD "object_filename" ASCENDING INDEX-FIELD "language_obj" ASCENDING INDEX-FIELD "widget_type" ASCENDING ADD TABLE "gsc_instance_attribute" AREA "Schema Area" DESCRIPTION "This table contains instance attributes used in the application. Instance attributes change the behaviour of generic objects. For example, a generic object could be developed that behaved differently in a creditors and debtors system. An instance attribute of creditor or debtor could be posted to the program when run to determine its instance specific functionality. The instance attribute will be posted to the program either via the menu option the program was run from, as setup in the menu option, or hard coded in a program if the program was run from a button, etc. For this reason, certain instance attributes will be system owned and cannot be maintained / deleted by users. When security structures e.g. field security are setup, they may be defined globally, for a specific product, product module or down to individual program level. The instance attribute is a level below the program level that permits security settings per instance of a program. Instance attributes will also be used for reporting to allow reports to be printed direct from menu options. The instance attribute code must map to the report_procedure_name in the report_definition table. Whenever a report definition is created, an instance attribute should automatically be created to facilitate this functionality. " DUMP-NAME "gscia" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsciatrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsciatrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsciareplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsciarepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsciareplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsciatrigw.p" CRC "?" ADD FIELD "instance_attribute_obj" OF "gsc_instance_attribute" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Instance Attribute Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Instance attribute obj" DECIMALS 6 ORDER 10 ADD FIELD "attribute_code" OF "gsc_instance_attribute" AS character DESCRIPTION "A unique code to identify this attribute" FORMAT "X(35)" INITIAL "" LABEL "Attribute Code" POSITION 3 SQL-WIDTH 70 VALMSG "s_name" HELP "Attribute code" ORDER 20 ADD FIELD "attribute_description" OF "gsc_instance_attribute" AS character FORMAT "X(500)" INITIAL "" LABEL "Attribute Description" POSITION 4 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Attribute description" ORDER 30 ADD FIELD "disabled" OF "gsc_instance_attribute" AS logical DESCRIPTION "If set to YES, then this attribute will not be checked, and full access will be granted." FORMAT "YES/NO" INITIAL "NO" LABEL "Disabled" POSITION 5 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Disabled" ORDER 40 ADD FIELD "system_owned" OF "gsc_instance_attribute" AS logical DESCRIPTION "The instance attribute will be posted to the program either via the menu option the program was run from, as setup in the menu option, or hard coded in a program if the program was run from a button, etc. For this reason, certain instance attributes will be system owned and cannot be maintained / deleted by users. " FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 50 ADD FIELD "attribute_type" OF "gsc_instance_attribute" AS character DESCRIPTION "The type of attribute, e.g. REP = Report Attribute - see below MEN = Standard Menu Attribute OTH = Other Instance attributes will also be used for reporting to allow reports to be printed direct from menu options. The instance attribute code must map to the report_procedure_name in the report_definition table. Whenever a report definition is created, an instance attribute should automatically be created to facilitate this functionality - with the attribute_type set to REP." FORMAT "X(3)" INITIAL "" LABEL "Attribute Type" POSITION 7 SQL-WIDTH 6 VALMSG "s_type" HELP "Attribute type" ORDER 60 ADD INDEX "XPKgsc_instance_attribute" ON "gsc_instance_attribute" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "instance_attribute_obj" ASCENDING ADD INDEX "XAK1gsc_instance_attribute" ON "gsc_instance_attribute" AREA "Schema Area" UNIQUE INDEX-FIELD "attribute_code" ASCENDING ADD INDEX "XAK2gsc_instance_attribute" ON "gsc_instance_attribute" AREA "Schema Area" UNIQUE INDEX-FIELD "attribute_type" ASCENDING INDEX-FIELD "attribute_code" ASCENDING ADD INDEX "XIE1gsc_instance_attribute" ON "gsc_instance_attribute" AREA "Schema Area" INDEX-FIELD "attribute_description" ASCENDING ADD TABLE "gsm_menu_structure" AREA "Schema Area" DESCRIPTION "This table defines the dynamic menu structues available. A menu structure must belong to a product, and can optionally also be associated with a product module if required - for sorting purposes. The menu structure code will be referenced in source code to build any dynamic menu items associated with the menu structure." DUMP-NAME "gsmms" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmmstrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmmstrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmmsreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmmsrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmmsreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmmstrigw.p" CRC "?" ADD FIELD "menu_structure_obj" OF "gsm_menu_structure" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Menu Structure Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Menu structure obj" DECIMALS 6 ORDER 10 ADD FIELD "product_obj" OF "gsm_menu_structure" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Product Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Product obj" DECIMALS 6 ORDER 20 ADD FIELD "product_module_obj" OF "gsm_menu_structure" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Product Module Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Product module obj" DECIMALS 6 ORDER 30 ADD FIELD "menu_structure_code" OF "gsm_menu_structure" AS character DESCRIPTION "A unique code, within product and product module to identify this menu structure. Making it only unique within product and product module facilitates a single program pulling in different menu options depending on where it is used." FORMAT "X(10)" INITIAL "" LABEL "Menu Structure Code" POSITION 5 SQL-WIDTH 20 VALMSG "s_code" HELP "Menu structure code" ORDER 40 ADD FIELD "menu_structure_description" OF "gsm_menu_structure" AS character FORMAT "X(35)" INITIAL "" LABEL "Menu Structure Description" POSITION 6 SQL-WIDTH 70 VALMSG "s_description" HELP "Menu structure description" ORDER 50 ADD FIELD "disabled" OF "gsm_menu_structure" AS logical DESCRIPTION "I set to YES, the use of this menu structure will be disabled." FORMAT "YES/NO" INITIAL "NO" LABEL "Disabled" POSITION 7 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Disabled" ORDER 60 ADD FIELD "system_owned" OF "gsm_menu_structure" AS logical DESCRIPTION "I a menu structure is system owned, it may not be amended or deleted by users not permitted to maintain system owned data. " FORMAT "YES/NO" INITIAL "YES" LABEL "System Owned" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "System owned" ORDER 70 ADD FIELD "under_development" OF "gsm_menu_structure" AS logical DESCRIPTION "If set to YES, the programs run from this menu structure are still under development. This menu structure will be hidden from users not flagged as developers." FORMAT "YES/NO" INITIAL "NO" LABEL "Under Development" POSITION 9 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Under development" ORDER 80 ADD INDEX "XPKgsm_menu_structure" ON "gsm_menu_structure" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "menu_structure_obj" ASCENDING ADD INDEX "XAK1gsm_menu_structure" ON "gsm_menu_structure" AREA "Schema Area" UNIQUE INDEX-FIELD "product_obj" ASCENDING INDEX-FIELD "product_module_obj" ASCENDING INDEX-FIELD "menu_structure_code" ASCENDING ADD INDEX "XIE1gsm_menu_structure" ON "gsm_menu_structure" AREA "Schema Area" INDEX-FIELD "menu_structure_code" ASCENDING ADD INDEX "XIE2gsm_menu_structure" ON "gsm_menu_structure" AREA "Schema Area" INDEX-FIELD "menu_structure_description" ASCENDING ADD TABLE "gsm_object_menu_structure" AREA "Schema Area" DESCRIPTION "This table defines the dynamic menu structures used by the object - if applicable. Only container objects may have dynamic menu structures. If an instance attribute is specified, then the menu structure will only be dynamically built if the instance attribute is passed in from the previous menu option. This facilitates pulling in different dynamic menu options for a specific object based on its use, e.g. creditors, debtors, etc. having different options. " DUMP-NAME "gsmom" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmomtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmomtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmomreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmomrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmomreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmomtrigw.p" CRC "?" ADD FIELD "object_obj" OF "gsm_object_menu_structure" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object obj" DECIMALS 6 ORDER 10 ADD FIELD "menu_structure_obj" OF "gsm_object_menu_structure" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Menu Structure Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Menu structure obj" DECIMALS 6 ORDER 20 ADD FIELD "object_menu_structure_obj" OF "gsm_object_menu_structure" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Menu Structure Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object menu structure obj" DECIMALS 6 ORDER 40 ADD FIELD "instance_attribute_obj" OF "gsm_object_menu_structure" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Instance Attribute Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Instance attribute obj" DECIMALS 6 ORDER 30 ADD INDEX "XPKgsm_object_menu_structure" ON "gsm_object_menu_structure" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "object_obj" ASCENDING INDEX-FIELD "menu_structure_obj" ASCENDING INDEX-FIELD "instance_attribute_obj" ASCENDING ADD INDEX "XAK1gsm_object_menu_structure" ON "gsm_object_menu_structure" AREA "Schema Area" UNIQUE INDEX-FIELD "menu_structure_obj" ASCENDING INDEX-FIELD "object_obj" ASCENDING INDEX-FIELD "instance_attribute_obj" ASCENDING ADD INDEX "XAK2gsm_object_menu_structure" ON "gsm_object_menu_structure" AREA "Schema Area" UNIQUE INDEX-FIELD "object_menu_structure_obj" ASCENDING ADD INDEX "XIE1gsm_object_menu_structure" ON "gsm_object_menu_structure" AREA "Schema Area" INDEX-FIELD "instance_attribute_obj" ASCENDING ADD TABLE "gsm_menu_item" AREA "Schema Area" DESCRIPTION "This table defines the dynamic menu items that belong to a menu structure, and their hierarchy. Menu items can be sub-menus, rulers, toggle options, or point to an actual program object to run." DUMP-NAME "gsmmi" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmmitrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmmitrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmmireplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmmirepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmmireplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmmitrigw.p" CRC "?" ADD FIELD "menu_item_obj" OF "gsm_menu_item" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Menu Item Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Menu item obj" DECIMALS 6 ORDER 10 ADD FIELD "menu_structure_obj" OF "gsm_menu_item" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Menu Structure Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Menu structure obj" DECIMALS 6 ORDER 20 ADD FIELD "menu_item_label" OF "gsm_menu_item" AS character DESCRIPTION "The label to show on the menu. Do not enter ... as this will be added as necessary. Include an ampersand for the accelerator key where appropriate - the Progress default if not sepcified is to use the 1st character." FORMAT "X(28)" INITIAL "" LABEL "Menu Item Label" POSITION 4 SQL-WIDTH 56 VALMSG "s_label" HELP "Menu item label" ORDER 50 ADD FIELD "menu_item_description" OF "gsm_menu_item" AS character DESCRIPTION "A full description of the menu item" FORMAT "X(35)" INITIAL "" LABEL "Menu Item Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Menu item description" ORDER 60 ADD FIELD "menu_item_sequence" OF "gsm_menu_item" AS integer DESCRIPTION "The sequence within a menu level that the menu item must appear in." FORMAT "->9" INITIAL "0" LABEL "Menu Item Sequence" POSITION 6 SQL-WIDTH 4 COLUMN-LABEL "Menu Item Seq." VALMSG "n_integer_2" HELP "Menu item sequence" ORDER 40 ADD FIELD "sub_menu_item" OF "gsm_menu_item" AS logical DESCRIPTION "If set to YES, this is a sub-menu item and can not have an associated object. Only menu items flagged as sub-menu items can be used as a parent menu item." FORMAT "YES/NO" INITIAL "NO" LABEL "Sub Menu Item" POSITION 7 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Sub menu item" ORDER 70 ADD FIELD "ruler_menu_item" OF "gsm_menu_item" AS logical DESCRIPTION "If set to YES, this menu item is a ruler line." FORMAT "YES/NO" INITIAL "NO" LABEL "Ruler Menu Item" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Ruler menu item" ORDER 80 ADD FIELD "toggle_menu_item" OF "gsm_menu_item" AS logical DESCRIPTION "If set to YES, this menu item is a toggle option that can either be YES or NO." FORMAT "YES/NO" INITIAL "NO" LABEL "Toggle Menu Item" POSITION 9 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Toggle menu item" ORDER 90 ADD FIELD "object_obj" OF "gsm_menu_item" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Obj" POSITION 10 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object obj" DECIMALS 6 ORDER 100 ADD FIELD "toolbar_image_sequence" OF "gsm_menu_item" AS integer DESCRIPTION "The default sequence within this menu structure that dynamic toolbar buttons should be created in. This will be set to 0 if no image is assigned to this menu item." FORMAT "->9" INITIAL "0" LABEL "Toolbar Image Sequence" POSITION 11 SQL-WIDTH 4 COLUMN-LABEL "Toolbar Image Seq." VALMSG "n_integer_2" HELP "Toolbar image sequence" ORDER 110 ADD FIELD "toolbar_image_filename" OF "gsm_menu_item" AS character DESCRIPTION "The filename, including the extension and relative path of the bitmap image to display on a dynamic toolbar when this menu option is used. The filename will be copied from the filename associated with the program. It is here for performace reasons, but may also be changed if required." FORMAT "X(70)" INITIAL "" LABEL "Toolbar Image Filename" POSITION 12 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Toolbar image filename" ORDER 120 ADD FIELD "tooltip_text" OF "gsm_menu_item" AS character DESCRIPTION "The tooltip text to display when this menu item is placed on a dynamic toolbar. This is copied from the object, but may be chaged if required." FORMAT "X(70)" INITIAL "" LABEL "Tooltip Text" POSITION 13 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Tooltip text" ORDER 130 ADD FIELD "shortcut_key" OF "gsm_menu_item" AS character DESCRIPTION "The shortcut key to associate with this menu item, e.g. CTRL-A " FORMAT "X(15)" INITIAL "" LABEL "Shortcut Key" POSITION 14 SQL-WIDTH 30 VALMSG "s_short_name" HELP "Shortcut key" ORDER 140 ADD FIELD "hide_if_disabled" OF "gsm_menu_item" AS logical DESCRIPTION "If this menu option is disabled for security reasons, then with this option set to YES, the menu item will be hidden rather than just greyed out. The default is to grey the option out. " FORMAT "YES/NO" INITIAL "NO" LABEL "Hide if Disabled" POSITION 15 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Hide if disabled" ORDER 150 ADD FIELD "disabled" OF "gsm_menu_item" AS logical DESCRIPTION "I set to YES, this menu item will be disabled. If this is a sub menu item, then all menu items belonging to the sub menu will also therefore be disabled." FORMAT "YES/NO" INITIAL "NO" LABEL "Disabled" POSITION 16 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Disabled" ORDER 160 ADD FIELD "parent_menu_item_obj" OF "gsm_menu_item" AS decimal DESCRIPTION "This should be the sub menu item the menu item belongs to, if any." FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Parent Menu Item Obj" POSITION 17 SQL-WIDTH 21 VALMSG "o_obj" HELP "Parent menu item obj" DECIMALS 6 ORDER 30 ADD FIELD "instance_attribute_obj" OF "gsm_menu_item" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Instance Attribute Obj" POSITION 18 SQL-WIDTH 21 VALMSG "o_obj" HELP "Instance attribute obj" DECIMALS 6 ORDER 170 ADD FIELD "system_owned" OF "gsm_menu_item" AS logical DESCRIPTION "I a menu item is system owned, it may not be amended or deleted by users not permitted to maintain system owned data. " FORMAT "YES/NO" INITIAL "YES" LABEL "System Owned" POSITION 19 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "System owned" ORDER 180 ADD FIELD "under_development" OF "gsm_menu_item" AS logical DESCRIPTION "If set to YES, the program run by this menu option is still under development. This menu option will be hidden from users not flagged as developers." FORMAT "YES/NO" INITIAL "NO" LABEL "Under Development" POSITION 20 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Under development" ORDER 190 ADD FIELD "menu_item_reference" OF "gsm_menu_item" AS character DESCRIPTION "A unique and automatically generated reference for a menu item - used when releasing menu items to site to be able to update existing menu items, rather than deleting and recreating." FORMAT "X(15)" INITIAL "" LABEL "Menu Item Reference" POSITION 21 SQL-WIDTH 30 VALMSG "s_reference" HELP "Menu item reference" ORDER 200 ADD FIELD "publish_link_list" OF "gsm_menu_item" AS character DESCRIPTION "If this menu item needs to publish an event across a link with a specific parameter when it is selected, then this field specifies the link name to use. This could also be a comma seperated list of links across wghich to publish the event." FORMAT "X(70)" INITIAL "" LABEL "Publish Link List" POSITION 22 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Publish link list" ORDER 210 ADD FIELD "publish_event" OF "gsm_menu_item" AS character DESCRIPTION "If this menu item needs to publish an event across a link with a specific parameter when it is selected, then this field specifies the event name to use." FORMAT "X(35)" INITIAL "" LABEL "Publish Event" POSITION 23 SQL-WIDTH 70 VALMSG "s_name" HELP "Publish event" ORDER 220 ADD FIELD "publish_parameter" OF "gsm_menu_item" AS character DESCRIPTION "If this menu item needs to publish an event across a link with a specific parameter when it is selected, then this field specifies the parameter to use. Only a single character parameter is supported. If more parameters are required, then a delimited list could be utilised. " FORMAT "X(70)" INITIAL "" LABEL "Publish Parameter" POSITION 24 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Publish parameter" ORDER 230 ADD FIELD "propagate_links" OF "gsm_menu_item" AS character DESCRIPTION "This contains a comma seperated list of links to propagate. The links must be specified with the -source or -target suffix to indicate the direction of the link being propagated. For this to work, a menu toolbar must exist with an instance attribute of menu. It does not need to be visualised but must exist. The reason is that it would be too dangerous to just propagate links direct from a container. Selecting the menu item will propogate any specified links to/from the menu toolbar through to the program being run, thereby bypassing the menu toolbar. The link could also be further directed by the program to an object in the program if an additional link existed between the container and the object with the same link name. For example, we could have a link from a browserA to a menu toolbar called link1-target. The toolbar runs a new program B. If link1-target is in the list of propogate links, then a link will be created between browserA and programB. If programB has a subsequent link1-target link from its container to another object called viewerC, then the link will actually be routed from browserA to viewerC. This in effect is a generic pass through link mechanism. " FORMAT "X(70)" INITIAL "" LABEL "Propagate Links" POSITION 25 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Propagate links" ORDER 240 ADD INDEX "XPKgsm_menu_item" ON "gsm_menu_item" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "menu_item_obj" ASCENDING ADD INDEX "XAK1gsm_menu_item" ON "gsm_menu_item" AREA "Schema Area" UNIQUE INDEX-FIELD "menu_structure_obj" ASCENDING INDEX-FIELD "parent_menu_item_obj" ASCENDING INDEX-FIELD "menu_item_sequence" ASCENDING ADD INDEX "XAK2gsm_menu_item" ON "gsm_menu_item" AREA "Schema Area" UNIQUE INDEX-FIELD "menu_item_reference" ASCENDING ADD INDEX "XIE2gsm_menu_item" ON "gsm_menu_item" AREA "Schema Area" INDEX-FIELD "menu_structure_obj" ASCENDING INDEX-FIELD "toolbar_image_sequence" ASCENDING INDEX-FIELD "menu_item_sequence" ASCENDING ADD INDEX "XIE3gsm_menu_item" ON "gsm_menu_item" AREA "Schema Area" INDEX-FIELD "menu_structure_obj" ASCENDING INDEX-FIELD "menu_item_label" ASCENDING ADD INDEX "XIE4gsm_menu_item" ON "gsm_menu_item" AREA "Schema Area" INDEX-FIELD "menu_structure_obj" ASCENDING INDEX-FIELD "menu_item_description" ASCENDING ADD INDEX "XIE5gsm_menu_item" ON "gsm_menu_item" AREA "Schema Area" INDEX-FIELD "object_obj" ASCENDING ADD INDEX "XIE6gsm_menu_item" ON "gsm_menu_item" AREA "Schema Area" INDEX-FIELD "instance_attribute_obj" ASCENDING ADD TABLE "gsm_security_structure" AREA "Schema Area" DESCRIPTION "The parts of the application where security restrictions are applicable to. Currently access tokens, fields, and ranges are supported. The owning_obj will refer either to a gsm_token record, a gsm_field record, or a gsm_range record. One table is used rather than a usage table for each of the above as the fields are identical, and if another type is introduced, no major rewrites will be required as this table will automatically support it. The security restriction may be assigned globally, in which case the product module, object and instance attribute will be 0. Alternatively the restriction may be allocated to a product module, a specific program object, or even an insance attribute for a program. A restriction must be assigned to this table for it to be active at all. It is entries in this table that are allocated to users. " DUMP-NAME "gsmss" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmsstrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmsstrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmsstrigw.p" CRC "?" ADD FIELD "security_structure_obj" OF "gsm_security_structure" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Security Structure Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Security structure obj" DECIMALS 6 ORDER 10 ADD FIELD "owning_entity_mnemonic" OF "gsm_security_structure" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Owning Entity Mnemonic" POSITION 3 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Owning entity mnemonic" ORDER 20 ADD FIELD "owning_obj" OF "gsm_security_structure" AS decimal DESCRIPTION "This will either point to a gsm_token.token_obj, a gsm_field.field_obj, or a gsm_range.range_obj depending on the owning_obj_entity field. " FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Owning Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Owning obj" DECIMALS 6 ORDER 30 ADD FIELD "product_module_obj" OF "gsm_security_structure" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Product Module Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Product module obj" DECIMALS 6 ORDER 40 ADD FIELD "object_obj" OF "gsm_security_structure" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Obj" POSITION 6 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object obj" DECIMALS 6 ORDER 50 ADD FIELD "disabled" OF "gsm_security_structure" AS logical DESCRIPTION "If set to YES, then this restriction will not be checked, and full access will be granted." FORMAT "YES/NO" INITIAL "NO" LABEL "Disabled" POSITION 7 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Disabled" ORDER 70 ADD FIELD "instance_attribute_obj" OF "gsm_security_structure" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Instance Attribute Obj" POSITION 8 SQL-WIDTH 21 VALMSG "o_obj" HELP "Instance attribute obj" DECIMALS 6 ORDER 60 ADD INDEX "XPKgsm_security_structure" ON "gsm_security_structure" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "security_structure_obj" ASCENDING ADD INDEX "XAK1gsm_security_structure" ON "gsm_security_structure" AREA "Schema Area" UNIQUE INDEX-FIELD "owning_entity_mnemonic" ASCENDING INDEX-FIELD "owning_obj" ASCENDING INDEX-FIELD "product_module_obj" ASCENDING INDEX-FIELD "object_obj" ASCENDING INDEX-FIELD "instance_attribute_obj" ASCENDING ADD INDEX "XAK2gsm_security_structure" ON "gsm_security_structure" AREA "Schema Area" UNIQUE INDEX-FIELD "product_module_obj" ASCENDING INDEX-FIELD "object_obj" ASCENDING INDEX-FIELD "instance_attribute_obj" ASCENDING INDEX-FIELD "owning_entity_mnemonic" ASCENDING INDEX-FIELD "owning_obj" ASCENDING ADD TABLE "gsm_user_category" AREA "Schema Area" DESCRIPTION "This table defines categories of users. It could be used for job functions, etc. It's primary use is for filtering and reporting." DUMP-NAME "gsmuc" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmuctrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmuctrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmucreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmucrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmucreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmuctrigw.p" CRC "?" ADD FIELD "user_category_obj" OF "gsm_user_category" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "User Category Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "User category obj" DECIMALS 6 ORDER 10 ADD FIELD "user_category_code" OF "gsm_user_category" AS character DESCRIPTION "a unique code to identify the category." FORMAT "X(10)" INITIAL "" LABEL "User Category Code" POSITION 3 SQL-WIDTH 20 VALMSG "s_code" HELP "User category code" ORDER 20 ADD FIELD "user_category_description" OF "gsm_user_category" AS character FORMAT "X(35)" INITIAL "" LABEL "User Category Description" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "User category description" ORDER 30 ADD FIELD "disabled" OF "gsm_user_category" AS logical DESCRIPTION "If set to YES, any users in this category will be prevented access to everything." FORMAT "YES/NO" INITIAL "NO" LABEL "Disabled" POSITION 5 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Disabled" ORDER 40 ADD INDEX "XPKgsm_user_category" ON "gsm_user_category" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "user_category_obj" ASCENDING ADD INDEX "XAK1gsm_user_category" ON "gsm_user_category" AREA "Schema Area" UNIQUE INDEX-FIELD "user_category_code" ASCENDING ADD INDEX "XIE1gsm_user_category" ON "gsm_user_category" AREA "Schema Area" INDEX-FIELD "user_category_description" ASCENDING ADD TABLE "gsm_user" AREA "Schema Area" DESCRIPTION "This table defines the users who may log into the system, i.e. the users of the system. The main user details are contained in an external security system, e.g. openstart pointed at by the external_userid field. This table defines extra user information for this system, and allows a user to be optionally associated with a person to facilitate full name, address, etc. details to be entered for a user as well as comments. There is a logged in flag on this user record to facilitate the identification of user availability (a user is available if they are logged into this application). The existence of this specific user table in our database also facilitates automatic referential integrity. " DUMP-NAME "gsmus" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmustrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmustrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmusreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmusrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmusreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmustrigw.p" CRC "?" ADD FIELD "user_obj" OF "gsm_user" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "User Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "User obj" DECIMALS 6 ORDER 10 ADD FIELD "user_category_obj" OF "gsm_user" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "User Category Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "User category obj" DECIMALS 6 ORDER 20 ADD FIELD "external_userid" OF "gsm_user" AS integer DESCRIPTION "A link to an external security system" FORMAT "->>>>>>>9" INITIAL "0" LABEL "External Userid" POSITION 4 SQL-WIDTH 4 VALMSG "n_userid" HELP "External userid" ORDER 90 ADD FIELD "user_full_name" OF "gsm_user" AS character DESCRIPTION "The full name for the user" FORMAT "X(70)" INITIAL "" LABEL "User Full Name" POSITION 5 SQL-WIDTH 140 VALMSG "s_big_name" HELP "User full name" ORDER 30 ADD FIELD "last_login_date" OF "gsm_user" AS date DESCRIPTION "The date this user last logged into this application." FORMAT "99/99/9999" INITIAL "?" LABEL "Last Login Date" POSITION 6 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Last login date" ORDER 220 ADD FIELD "last_login_time" OF "gsm_user" AS integer FORMAT ">>>>9" INITIAL "0" LABEL "Last Login Time" POSITION 7 SQL-WIDTH 4 VALMSG "n_time" HELP "Last login time" ORDER 230 ADD FIELD "user_login_name" OF "gsm_user" AS character DESCRIPTION "The user login name. This should usually be the same as their login name on the server." FORMAT "X(15)" INITIAL "" LABEL "User Login Name" POSITION 8 SQL-WIDTH 30 VALMSG "s_short_name" HELP "User login name" ORDER 40 ADD FIELD "user_creation_date" OF "gsm_user" AS date FORMAT "99/99/9999" INITIAL "TODAY" LABEL "User Creation Date" POSITION 9 SQL-WIDTH 4 VALMSG "d_date_today" HELP "User creation date" ORDER 50 ADD FIELD "user_creation_time" OF "gsm_user" AS integer FORMAT ">>>>9" INITIAL "0" LABEL "User Creation Time" POSITION 10 SQL-WIDTH 4 VALMSG "n_time" HELP "User creation time" ORDER 60 ADD FIELD "profile_user" OF "gsm_user" AS logical DESCRIPTION "If set to YES, this is a profile user that may be copied. Profile users do not have to be real people, but all other users do." FORMAT "YES/NO" INITIAL "NO" LABEL "Profile User" POSITION 11 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Profile user" ORDER 70 ADD FIELD "created_from_profile_user_obj" OF "gsm_user" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Created From Profile User Obj" POSITION 12 SQL-WIDTH 21 VALMSG "o_obj" HELP "Created from profile user obj" DECIMALS 6 ORDER 80 ADD FIELD "user_password" OF "gsm_user" AS character DESCRIPTION "The current encrypted password. This may need to be unique depending on the setting in the security control table." FORMAT "X(35)" INITIAL "" LABEL "User Password" POSITION 13 SQL-WIDTH 70 VALMSG "s_description" HELP "User password" ORDER 100 ADD FIELD "password_minimum_length" OF "gsm_user" AS integer DESCRIPTION "The minimum length of the user password" FORMAT "->9" INITIAL "0" LABEL "Password Minimum Length" POSITION 14 SQL-WIDTH 4 VALMSG "n_integer_2" HELP "Password minimum length" ORDER 110 ADD FIELD "password_preexpired" OF "gsm_user" AS logical DESCRIPTION "If set to YES, the user must change their password the next time they log in." FORMAT "YES/NO" INITIAL "NO" LABEL "Password Preexpired" POSITION 15 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Password preexpired" ORDER 120 ADD FIELD "password_fail_count" OF "gsm_user" AS integer DESCRIPTION "The number of times the user has got their password wrong since the last sucessful log in." FORMAT "->>9" INITIAL "0" LABEL "Password Fail Count" POSITION 16 SQL-WIDTH 4 VALMSG "n_integer_3" HELP "Password fail count" ORDER 130 ADD FIELD "password_fail_date" OF "gsm_user" AS date DESCRIPTION "The date the user last got their password wrong." FORMAT "99/99/9999" INITIAL "?" LABEL "Password Fail Date" POSITION 17 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Password fail date" ORDER 140 ADD FIELD "password_fail_time" OF "gsm_user" AS integer DESCRIPTION "The time the user last got their password wrong." FORMAT ">>>>9" INITIAL "0" LABEL "Password Fail Time" POSITION 18 SQL-WIDTH 4 VALMSG "n_time" HELP "Password fail time" ORDER 150 ADD FIELD "password_creation_date" OF "gsm_user" AS date FORMAT "99/99/9999" INITIAL "?" LABEL "Password Creation Date" POSITION 19 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Password creation date" ORDER 160 ADD FIELD "password_creation_time" OF "gsm_user" AS integer FORMAT ">>>>9" INITIAL "0" LABEL "Password Creation Time" POSITION 20 SQL-WIDTH 4 VALMSG "n_time" HELP "Password creation time" ORDER 170 ADD FIELD "password_expiry_date" OF "gsm_user" AS date FORMAT "99/99/9999" INITIAL "?" LABEL "Password Expiry Date" POSITION 21 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Password expiry date" ORDER 180 ADD FIELD "password_expiry_time" OF "gsm_user" AS integer FORMAT ">>>>9" INITIAL "0" LABEL "Password Expiry Time" POSITION 22 SQL-WIDTH 4 VALMSG "n_time" HELP "Password expiry time" ORDER 190 ADD FIELD "update_password_history" OF "gsm_user" AS logical DESCRIPTION "If set to YES, a record will be written to the passwor history every time the user changes their password, recording old passwords." FORMAT "YES/NO" INITIAL "NO" LABEL "Update Password History" POSITION 23 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Update password history" ORDER 200 ADD FIELD "check_password_history" OF "gsm_user" AS logical DESCRIPTION "If set to YES, the password history will be checked to ensure the same password is not reused within the specified time period." FORMAT "YES/NO" INITIAL "NO" LABEL "Check Password History" POSITION 24 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Check password history" ORDER 210 ADD FIELD "disabled" OF "gsm_user" AS logical DESCRIPTION "If set to YES, this user account will be disabled and further log ins prevented." FORMAT "YES/NO" INITIAL "NO" LABEL "Disabled" POSITION 25 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Disabled" ORDER 240 ADD FIELD "language_obj" OF "gsm_user" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Language Obj" POSITION 26 SQL-WIDTH 21 VALMSG "o_obj" HELP "Language obj" DECIMALS 6 ORDER 250 ADD FIELD "password_expiry_days" OF "gsm_user" AS integer DESCRIPTION "The number of days to add to the expiry date when a password has expired, to obtain the new expiry date." FORMAT "->>9" INITIAL "0" LABEL "Password Expiry Days" POSITION 27 SQL-WIDTH 4 VALMSG "n_integer_3" HELP "Password expiry days" ORDER 260 ADD FIELD "maintain_system_data" OF "gsm_user" AS logical DESCRIPTION "If set to YES, this user is allowed to maintain system owned data. If set to NO, the user may not add, delete, or modify any system owned data." FORMAT "YES/NO" INITIAL "NO" LABEL "Maintain System Data" POSITION 28 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Maintain system data" ORDER 270 ADD FIELD "default_login_company_obj" OF "gsm_user" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Default Login Company Obj" POSITION 29 SQL-WIDTH 21 VALMSG "o_obj" HELP "Default login company obj" DECIMALS 6 ORDER 280 ADD FIELD "user_email_address" OF "gsm_user" AS character DESCRIPTION "Email address for user - used to automatically send notification messages to user when certain events have finished." FORMAT "X(35)" INITIAL "" LABEL "User Email Address" POSITION 30 SQL-WIDTH 70 VALMSG "s_name" HELP "User email address" ORDER 290 ADD FIELD "development_user" OF "gsm_user" AS logical DESCRIPTION "If set to YES, this user is a system developer and allowed to run menu items / reports that are still under development." FORMAT "YES/NO" INITIAL "NO" LABEL "Development User" POSITION 31 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Development user" ORDER 300 ADD INDEX "XPKgsm_user" ON "gsm_user" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "user_obj" ASCENDING ADD INDEX "XAK2gsm_user" ON "gsm_user" AREA "Schema Area" UNIQUE INDEX-FIELD "user_login_name" ASCENDING ADD INDEX "XIE1gsm_user" ON "gsm_user" AREA "Schema Area" INDEX-FIELD "user_full_name" ASCENDING ADD INDEX "XIE2gsm_user" ON "gsm_user" AREA "Schema Area" INDEX-FIELD "profile_user" ASCENDING INDEX-FIELD "user_full_name" ASCENDING ADD INDEX "XIE3gsm_user" ON "gsm_user" AREA "Schema Area" INDEX-FIELD "external_userid" ASCENDING ADD INDEX "XIE4gsm_user" ON "gsm_user" AREA "Schema Area" INDEX-FIELD "user_password" ASCENDING ADD INDEX "XIE6gsm_user" ON "gsm_user" AREA "Schema Area" INDEX-FIELD "default_login_company_obj" ASCENDING ADD TABLE "gsm_user_allocation" AREA "Schema Area" DESCRIPTION "When a user logs into the system, they log in with a user id, and a select a company (organisation). This table defines the security options for the user when they log into a certian organisation. The user may have different security options when logged into different companies. If the organisation_obj is 0, then the security allocation applies to all companies. Likewise, if the user_obj is 0, then the security allocation applies to all users logged into this company. User security will always override company security. In addition, and owning_obj of 0 always indicates no access to all the data for that entity mnemonic (not supported for security structures, or menus - only really for data). This table generically assigns all security options for the user / company. The standard options that may be specified via the owning_entity_mnemonic and owning_obj are: gsm_security_structure records for security relating to tokens, fields and ranges. gsm_menu_items for securing access to menu items gsm_menu_structure for securing access to menu structures gsm_entity_field_value for securing access to generic entity field values e.g. companies. Additionally, access to any entity data can be secured using this table. For example, to secure access to specific cost centre codes in a general ledger, the owning_entity_mnemonic could be the cost centre table, and the owning_obj used to allocate specific cost centres the user / company has access to. The rules applied to this table for the entity in order are as follows: 0) If security is disabled, then user security is passed. 1) If a specific record exists for the user / company then security is passed 2) If a specific record is found for the user / company with an owning_obj of 0, security is failed 3) If not full access by default, and no entries exist for the user at all, including all users and all companies, security is failed 4) If a record exists for all users or all companies with an owning_obj of 0, then security is failed 5) If a record is found for all users, security is passed 6) If a record is found for all companies, security is passed 7) If full access by default and no records are found at all for the specific user, all users, or all companies, then security is passed. Some allocations require additional data, e.g. allocating a field restriction needs to determine what can be done with the field, e.g. View, Update, Hide, etc. Entries must exist in this table for all security allocations. There is no option for inclusion or exclusion to make querying as fast as possible. The maintenance programs however should allow the specification by inclusion or exclusion for fast data entry - then create / delete all relevant entries in this table. " DUMP-NAME "gsmul" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmultrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmultrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmultrigw.p" CRC "?" ADD FIELD "user_obj" OF "gsm_user_allocation" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "User Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "User obj" DECIMALS 6 ORDER 10 ADD FIELD "owning_entity_mnemonic" OF "gsm_user_allocation" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Owning Entity Mnemonic" POSITION 3 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Owning entity mnemonic" ORDER 30 ADD FIELD "login_organisation_obj" OF "gsm_user_allocation" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Login Organisation Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Login organisation obj" DECIMALS 6 ORDER 20 ADD FIELD "owning_obj" OF "gsm_user_allocation" AS decimal DESCRIPTION "If this is set to 0, it indicates that for the owning_entity_mnemonic, no data access is permitted at all." FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Owning Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Owning obj" DECIMALS 6 ORDER 40 ADD FIELD "user_allocation_obj" OF "gsm_user_allocation" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "User Allocation Obj" POSITION 6 SQL-WIDTH 21 VALMSG "o_obj" HELP "User allocation obj" DECIMALS 6 ORDER 70 ADD FIELD "user_allocation_value1" OF "gsm_user_allocation" AS character DESCRIPTION "The use of this field is dependant on the owning_entity_mnemonic. If this is field security, it will contain the valid field option, e.g. view, update, or hide. If this is range security, it will contain the range from value." FORMAT "X(70)" INITIAL "" LABEL "User Allocation Value1" POSITION 7 SQL-WIDTH 140 VALMSG "s_big_description" HELP "User allocation value1" ORDER 50 ADD FIELD "user_allocation_value2" OF "gsm_user_allocation" AS character DESCRIPTION "The use of this field is dependant on the owning_obj_entity. If this is range security, it will contain the range to value." FORMAT "X(70)" INITIAL "" LABEL "User Allocation Value2" POSITION 8 SQL-WIDTH 140 VALMSG "s_big_description" HELP "User allocation value2" ORDER 60 ADD INDEX "XPKgsm_user_allocation" ON "gsm_user_allocation" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "user_obj" ASCENDING INDEX-FIELD "login_organisation_obj" ASCENDING INDEX-FIELD "owning_entity_mnemonic" ASCENDING INDEX-FIELD "owning_obj" ASCENDING ADD INDEX "XAK1gsm_user_allocation" ON "gsm_user_allocation" AREA "Schema Area" UNIQUE INDEX-FIELD "user_allocation_obj" ASCENDING ADD INDEX "XIE1gsm_user_allocation" ON "gsm_user_allocation" AREA "Schema Area" INDEX-FIELD "login_organisation_obj" ASCENDING INDEX-FIELD "user_obj" ASCENDING INDEX-FIELD "owning_entity_mnemonic" ASCENDING INDEX-FIELD "owning_obj" ASCENDING ADD INDEX "XIE2gsm_user_allocation" ON "gsm_user_allocation" AREA "Schema Area" INDEX-FIELD "owning_entity_mnemonic" ASCENDING INDEX-FIELD "owning_obj" ASCENDING INDEX-FIELD "user_obj" ASCENDING INDEX-FIELD "login_organisation_obj" ASCENDING ADD INDEX "XIE3gsm_user_allocation" ON "gsm_user_allocation" AREA "Schema Area" INDEX-FIELD "owning_entity_mnemonic" ASCENDING INDEX-FIELD "owning_obj" ASCENDING INDEX-FIELD "login_organisation_obj" ASCENDING INDEX-FIELD "user_obj" ASCENDING ADD INDEX "XIE4gsm_user_allocation" ON "gsm_user_allocation" AREA "Schema Area" INDEX-FIELD "owning_obj" ASCENDING ADD TABLE "gsm_entity_field" AREA "Schema Area" DESCRIPTION "This table facilitates securing any application specific or generic data against any entity. For example, if there is a requirement to secure access to specific companies, then the company entity, with the company code field could be set-up in this table. The valid values could then be setup in the entity field values table, and users allocated access to the specific values." DUMP-NAME "gsmef" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmeftrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmeftrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmeftrigw.p" CRC "?" ADD FIELD "entity_field_obj" OF "gsm_entity_field" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Entity Field Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Entity field obj" DECIMALS 6 ORDER 10 ADD FIELD "owning_entity_mnemonic" OF "gsm_entity_field" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Owning Entity Mnemonic" POSITION 3 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Owning entity mnemonic" ORDER 20 ADD FIELD "entity_field_name" OF "gsm_entity_field" AS character DESCRIPTION "The fieldname within the entity that this value is associated with (no tablename prefix required)." FORMAT "X(35)" INITIAL "" LABEL "Entity Field Name" POSITION 4 SQL-WIDTH 70 VALMSG "s_name" HELP "Entity field name" ORDER 30 ADD FIELD "entity_field_description" OF "gsm_entity_field" AS character DESCRIPTION "A description of the fieldname" FORMAT "X(35)" INITIAL "" LABEL "Entity Field Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Entity field description" ORDER 40 ADD INDEX "XPKgsm_entity_field" ON "gsm_entity_field" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "entity_field_obj" ASCENDING ADD INDEX "XAK1gsm_entity_field" ON "gsm_entity_field" AREA "Schema Area" UNIQUE INDEX-FIELD "owning_entity_mnemonic" ASCENDING INDEX-FIELD "entity_field_name" ASCENDING ADD TABLE "gsm_entity_field_value" AREA "Schema Area" DESCRIPTION "The valid values for the entity field, e.g. company codes." DUMP-NAME "gsmev" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmevtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmevtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmevtrigw.p" CRC "?" ADD FIELD "entity_field_value_obj" OF "gsm_entity_field_value" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Entity Field Value Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Entity field value obj" DECIMALS 6 ORDER 10 ADD FIELD "entity_field_obj" OF "gsm_entity_field_value" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Entity Field Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Entity field obj" DECIMALS 6 ORDER 20 ADD FIELD "entity_field_contents" OF "gsm_entity_field_value" AS character DESCRIPTION "The value assigned to the field." FORMAT "X(70)" INITIAL "" LABEL "Entity Field Contents" POSITION 4 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Entity field contents" ORDER 30 ADD INDEX "XPKgsm_entity_field_value" ON "gsm_entity_field_value" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "entity_field_value_obj" ASCENDING ADD INDEX "XIE1gsm_entity_field_value" ON "gsm_entity_field_value" AREA "Schema Area" INDEX-FIELD "entity_field_obj" ASCENDING INDEX-FIELD "entity_field_contents" ASCENDING ADD TABLE "gsm_currency" AREA "Schema Area" DESCRIPTION "This table contains all the currency codes and their symbol references that are available to the system" DUMP-NAME "gsmcr" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmcrtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmcrtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmcrreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmcrrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmcrreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmcrtrigw.p" CRC "?" ADD FIELD "currency_obj" OF "gsm_currency" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Currency Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Currency obj" DECIMALS 6 ORDER 10 ADD FIELD "currency_code" OF "gsm_currency" AS character DESCRIPTION "A unique code that identifies the currency" FORMAT "X(10)" INITIAL "" LABEL "Currency Code" POSITION 3 SQL-WIDTH 20 VALMSG "s_code" HELP "Currency code" ORDER 20 ADD FIELD "currency_description" OF "gsm_currency" AS character FORMAT "X(35)" INITIAL "" LABEL "Currency Description" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Currency description" ORDER 30 ADD FIELD "currency_symbol" OF "gsm_currency" AS character DESCRIPTION "The commonly used symbol to identify this currency code" FORMAT "X(5)" INITIAL "" LABEL "Currency Symbol" POSITION 5 SQL-WIDTH 10 VALMSG "s_string_5" HELP "Currency symbol" ORDER 40 ADD FIELD "symbol_format_mask" OF "gsm_currency" AS character FORMAT "X(35)" INITIAL "" LABEL "Symbol Format Mask" POSITION 6 SQL-WIDTH 70 VALMSG "s_format_string" HELP "Symbol format mask" ORDER 50 ADD FIELD "number_of_decimals" OF "gsm_currency" AS integer DESCRIPTION "The number of decimals to store for the currency, necessary for rounding conversions." FORMAT "->9" INITIAL "0" LABEL "Number of Decimals" POSITION 7 SQL-WIDTH 4 VALMSG "n_integer_2" HELP "Number of decimals" ORDER 60 ADD INDEX "XPKgsm_currency" ON "gsm_currency" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "currency_obj" ASCENDING ADD INDEX "XAK1gsm_currency" ON "gsm_currency" AREA "Schema Area" UNIQUE INDEX-FIELD "currency_code" ASCENDING ADD INDEX "XIE1gsm_currency" ON "gsm_currency" AREA "Schema Area" INDEX-FIELD "currency_description" ASCENDING ADD TABLE "gsc_nationality" AREA "Schema Area" DUMP-NAME "gscna" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscnatrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscnatrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscnareplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscnarepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscnareplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscnatrigw.p" CRC "?" ADD FIELD "nationality_obj" OF "gsc_nationality" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Nationality Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Nationality obj" DECIMALS 6 ORDER 10 ADD FIELD "nationality_code" OF "gsc_nationality" AS character FORMAT "X(10)" INITIAL "" LABEL "Nationality Code" POSITION 3 SQL-WIDTH 20 VALMSG "s_code" HELP "Nationality code" ORDER 20 ADD FIELD "nationality_name" OF "gsc_nationality" AS character FORMAT "X(35)" INITIAL "" LABEL "Nationality Name" POSITION 4 SQL-WIDTH 70 VALMSG "s_name" HELP "Nationality name" ORDER 30 ADD INDEX "XPKgsc_nationality" ON "gsc_nationality" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "nationality_obj" ASCENDING ADD INDEX "XAK1gsc_nationality" ON "gsc_nationality" AREA "Schema Area" UNIQUE INDEX-FIELD "nationality_code" ASCENDING ADD INDEX "XIE1gsc_nationality" ON "gsc_nationality" AREA "Schema Area" INDEX-FIELD "nationality_name" ASCENDING ADD TABLE "gsm_country" AREA "Schema Area" DESCRIPTION "Supported countries, e.g. USA = United States of America, SA = South Africa, UK = United Kingdom" DUMP-NAME "gsmcy" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmcytrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmcytrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmcyreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmcyrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmcyreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmcytrigw.p" CRC "?" ADD FIELD "country_obj" OF "gsm_country" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Country Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Country obj" DECIMALS 6 ORDER 10 ADD FIELD "country_code" OF "gsm_country" AS character DESCRIPTION "The code of the country, as per the ISO3166 standard, e.g. UK = United Kingdom SA = South Africa " FORMAT "X(10)" INITIAL "" LABEL "Country Code" POSITION 3 SQL-WIDTH 20 VALMSG "s_code" HELP "Country code" ORDER 20 ADD FIELD "country_name" OF "gsm_country" AS character DESCRIPTION "The full name for the country" FORMAT "X(35)" INITIAL "" LABEL "Country Name" POSITION 4 SQL-WIDTH 70 VALMSG "s_name" HELP "Country name" ORDER 30 ADD FIELD "min_postcode_lookup_chars" OF "gsm_country" AS integer DESCRIPTION "The minimum number of characters in the postcode field of the address to be matched against the g_postcode file. If this is set to 0, then postcode validation will be turned off. In the UK, this may be set to 4 if only post town and county validation is in effect. In South Africa, it would be set to 4 because that is the full length of the postcode and partial postcodes are not supported." FORMAT "->9" INITIAL "0" LABEL "Min. Postcode Lookup Chars" POSITION 5 SQL-WIDTH 4 VALMSG "n_integer_2" HELP "Min. postcode lookup chars" ORDER 40 ADD FIELD "address_format_procedure_obj" OF "gsm_country" AS decimal DESCRIPTION "This contains an internal procedure name specific to the address / postcode formatting required. All address formatting procedures will exist in a single persistently run program. Refer to the ""Generic Table Usage"" document for a detailed description." FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Address Format Procedure Obj" POSITION 6 SQL-WIDTH 21 VALMSG "o_obj" HELP "Address format procedure obj" DECIMALS 6 ORDER 50 ADD FIELD "properform_address" OF "gsm_country" AS logical DESCRIPTION "Convert the address to proper form true alphanumeric format" FORMAT "YES/NO" INITIAL "YES" LABEL "Properform Address" POSITION 7 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Properform address" ORDER 60 ADD FIELD "upcase_town" OF "gsm_country" AS logical DESCRIPTION "Force the town or suburb into uppercase. It's use is dependant on the type of address." FORMAT "YES/NO" INITIAL "NO" LABEL "Upcase Town" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Upcase town" ORDER 70 ADD FIELD "force_valid_address" OF "gsm_country" AS logical DESCRIPTION "If set to YES, then the entry of valid address lines with a valid postcode will be used, possibly utilising clavis data for the validation." FORMAT "YES/NO" INITIAL "NO" LABEL "Force Valid Address" POSITION 9 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Force valid address" ORDER 80 ADD FIELD "address_line1_label" OF "gsm_country" AS character DESCRIPTION "The screen label to use for the 1st line of the address, e.g. No. / Name" FORMAT "X(28)" INITIAL "" LABEL "Address Line1 Label" POSITION 10 SQL-WIDTH 56 VALMSG "s_label" HELP "Address line1 label" ORDER 90 ADD FIELD "address_line2_label" OF "gsm_country" AS character DESCRIPTION "The screen label to use for the 2nd line of the address, e.g. Street" FORMAT "X(28)" INITIAL "" LABEL "Address Line2 Label" POSITION 11 SQL-WIDTH 56 VALMSG "s_label" HELP "Address line2 label" ORDER 100 ADD FIELD "address_line3_label" OF "gsm_country" AS character DESCRIPTION "The screen label to use for the 3rdline of the address, e.g. City" FORMAT "X(28)" INITIAL "" LABEL "Address Line3 Label" POSITION 12 SQL-WIDTH 56 VALMSG "s_label" HELP "Address line3 label" ORDER 110 ADD FIELD "address_line4_label" OF "gsm_country" AS character DESCRIPTION "The screen label to use for the 4th line of the address, e.g. PO Box" FORMAT "X(28)" INITIAL "" LABEL "Address Line4 Label" POSITION 13 SQL-WIDTH 56 VALMSG "s_label" HELP "Address line4 label" ORDER 120 ADD FIELD "address_line5_label" OF "gsm_country" AS character DESCRIPTION "The screen label to use for the 5th line of the address, e.g. Firm" FORMAT "X(28)" INITIAL "" LABEL "Address Line5 Label" POSITION 14 SQL-WIDTH 56 VALMSG "s_label" HELP "Address line5 label" ORDER 130 ADD FIELD "postcode_label" OF "gsm_country" AS character DESCRIPTION "The screen label for the postcode of an address, e.g. Postcode or ZIP Code." FORMAT "X(28)" INITIAL "" LABEL "Postcode Label" POSITION 15 SQL-WIDTH 56 VALMSG "s_label" HELP "Postcode label" ORDER 140 ADD INDEX "XPKgsm_country" ON "gsm_country" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "country_obj" ASCENDING ADD INDEX "XAK1gsm_country" ON "gsm_country" AREA "Schema Area" UNIQUE INDEX-FIELD "country_code" ASCENDING ADD INDEX "XIE1gsm_country" ON "gsm_country" AREA "Schema Area" INDEX-FIELD "country_name" ASCENDING ADD TABLE "gsc_global_control" AREA "Schema Area" DESCRIPTION "This table defines system wide defaults. It contains a single record within which to hold the current system defaults. " DUMP-NAME "gscgc" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscgctrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscgctrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscgctrigw.p" CRC "?" ADD FIELD "global_control_obj" OF "gsc_global_control" AS decimal DESCRIPTION "A unique object number used to identify this version of the global control information." FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Global Control Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Global control obj" DECIMALS 6 ORDER 10 ADD FIELD "default_country_obj" OF "gsc_global_control" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Default Country Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Default country obj" DECIMALS 6 ORDER 20 ADD FIELD "default_nationality_obj" OF "gsc_global_control" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Default Nationality Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Default nationality obj" DECIMALS 6 ORDER 30 ADD FIELD "default_language_obj" OF "gsc_global_control" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Default Language Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Default language obj" DECIMALS 6 ORDER 40 ADD FIELD "default_currency_obj" OF "gsc_global_control" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Default Currency Obj" POSITION 6 SQL-WIDTH 21 VALMSG "o_obj" HELP "Default currency obj" DECIMALS 6 ORDER 50 ADD FIELD "date_format" OF "gsc_global_control" AS character DESCRIPTION "The session:date-format to use as follows: dmy ymd mdy" FORMAT "X(3)" INITIAL "" LABEL "Date Format" POSITION 7 SQL-WIDTH 6 VALMSG "s_string_3" HELP "Date format" ORDER 60 ADD FIELD "date_format_mask" OF "gsc_global_control" AS character DESCRIPTION "The PROGRESS format mask for date fields. The default is 99/99/9999 " FORMAT "X(35)" INITIAL "" LABEL "Date Format Mask" POSITION 8 SQL-WIDTH 70 VALMSG "s_format_string" HELP "Date format mask" ORDER 70 ADD INDEX "XPKgsc_global_control" ON "gsc_global_control" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "global_control_obj" ASCENDING ADD TABLE "gst_audit" AREA "Schema Area" DESCRIPTION "Global audit file to record modifications to data. The audit can be turned on by defining a category of audit for an entity type. It can be turned off again simply by resetting the active flag on the category. The audit will hold basic details on the action (create, amend, or delete), the user, date & time, the program and procedure used to perform the action, and possibly a record of the data before the update. The audit could easily be used to keep old values of fields by defining more categories, e.g. one for each field or group of fields on an entity." DUMP-NAME "gstad" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gstadtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gstadtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gstadtrigw.p" CRC "?" ADD FIELD "audit_obj" OF "gst_audit" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Audit Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Audit obj" DECIMALS 6 ORDER 10 ADD FIELD "owning_obj" OF "gst_audit" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Owning Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Owning obj" DECIMALS 6 ORDER 30 ADD FIELD "owning_entity_mnemonic" OF "gst_audit" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Owning Entity Mnemonic" POSITION 4 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Owning entity mnemonic" ORDER 20 MANDATORY ADD FIELD "audit_action" OF "gst_audit" AS character DESCRIPTION "The action performed: CRE = create, AME = amend, DEL = delete" FORMAT "X(3)" INITIAL "" LABEL "Audit Action" POSITION 5 SQL-WIDTH 6 VALMSG "s_mnemonic" HELP "Audit action" ORDER 90 ADD FIELD "audit_date" OF "gst_audit" AS date FORMAT "99/99/9999" INITIAL "TODAY" LABEL "Audit Date" POSITION 6 SQL-WIDTH 4 VALMSG "d_date_today" HELP "Audit date" ORDER 40 ADD FIELD "audit_time" OF "gst_audit" AS integer FORMAT ">>>>9" INITIAL "0" LABEL "Audit Time" POSITION 7 SQL-WIDTH 4 VALMSG "n_time" HELP "Audit time" ORDER 50 ADD FIELD "audit_user_obj" OF "gst_audit" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Audit User Obj" POSITION 8 SQL-WIDTH 21 VALMSG "o_obj" HELP "Audit user obj" DECIMALS 6 ORDER 60 ADD FIELD "program_name" OF "gst_audit" AS character DESCRIPTION "The name of the program that was used to perform the action" FORMAT "X(35)" INITIAL "" LABEL "Program Name" POSITION 9 SQL-WIDTH 70 VALMSG "s_program_name" HELP "Program name" ORDER 70 ADD FIELD "program_procedure" OF "gst_audit" AS character DESCRIPTION "The internal procedure within the above program used to perform the action." FORMAT "X(35)" INITIAL "" LABEL "Program Procedure" POSITION 10 SQL-WIDTH 70 VALMSG "s_program_procedure" HELP "Program procedure" ORDER 80 ADD FIELD "old_detail" OF "gst_audit" AS character DESCRIPTION "Possible storage of relevant details in the record before the action took place." FORMAT "X(10000)" INITIAL "" LABEL "Old Detail" POSITION 11 SQL-WIDTH 20000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL LARGE MAX-CHARS 10000" VALMSG "s_buffer" HELP "Old detail" ORDER 100 ADD INDEX "XPKgst_audit" ON "gst_audit" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "audit_obj" ASCENDING ADD INDEX "XIE1gst_audit" ON "gst_audit" AREA "Schema Area" INDEX-FIELD "owning_entity_mnemonic" ASCENDING INDEX-FIELD "owning_obj" ASCENDING INDEX-FIELD "audit_date" ASCENDING INDEX-FIELD "audit_time" ASCENDING ADD INDEX "XIE2gst_audit" ON "gst_audit" AREA "Schema Area" INDEX-FIELD "owning_obj" ASCENDING INDEX-FIELD "audit_date" ASCENDING INDEX-FIELD "audit_time" ASCENDING ADD INDEX "XIE3gst_audit" ON "gst_audit" AREA "Schema Area" INDEX-FIELD "audit_user_obj" ASCENDING INDEX-FIELD "audit_date" ASCENDING INDEX-FIELD "audit_time" ASCENDING ADD TABLE "gsm_profile" AREA "Schema Area" DESCRIPTION "Generic profiles that can be attached to any entity or may stand alone to be used as control information or lookup lists. Profiles could be utilised for user defined fields e.g. smoking and drinking habits of members. For other systems, the modification of a profile and it's related tables must be inhibited where it exists in any s_contribution_type.rule_code_profile_objs with existing s_contribution_rules records." DUMP-NAME "gsmpr" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmprtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmprtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmprtrigw.p" CRC "?" ADD FIELD "profile_obj" OF "gsm_profile" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile obj" DECIMALS 6 ORDER 10 ADD FIELD "category_obj" OF "gsm_profile" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Category Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Category obj" DECIMALS 6 ORDER 20 ADD FIELD "profile_tla" OF "gsm_profile" AS character DESCRIPTION "A unique 3 character profile code within the profile category." FORMAT "X(3)" INITIAL "" LABEL "Profile TLA" POSITION 4 SQL-WIDTH 6 VALMSG "s_tla" HELP "Profile three letter acronym" ORDER 30 ADD FIELD "profile_short_desc" OF "gsm_profile" AS character FORMAT "X(15)" INITIAL "" LABEL "Profile Short Description" POSITION 5 SQL-WIDTH 30 COLUMN-LABEL "Profile Short Desc" VALMSG "s_short_desc" HELP "Profile short description" ORDER 40 ADD FIELD "profile_description" OF "gsm_profile" AS character FORMAT "X(35)" INITIAL "" LABEL "Profile Description" POSITION 6 SQL-WIDTH 70 VALMSG "s_description" HELP "Profile description" ORDER 50 ADD FIELD "data_type" OF "gsm_profile" AS character DESCRIPTION "The PROGRESS data type of this profile code as follows: CHR = CHARACTER INT = INTEGER DEC = DECIMAL DAT = DATE" FORMAT "X(3)" INITIAL "" LABEL "Data Type" POSITION 7 SQL-WIDTH 6 VALMSG "s_type" HELP "Data type" ORDER 60 ADD FIELD "value_is_range" OF "gsm_profile" AS logical DESCRIPTION "Is this profile value a single value, or does it permit the entry of a range of values." FORMAT "YES/NO" INITIAL "NO" LABEL "Value is Range" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Value is range" ORDER 70 ADD FIELD "valid_value_list" OF "gsm_profile" AS logical DESCRIPTION "Is the profile value free input, or must it be selected from a list of valid values" FORMAT "YES/NO" INITIAL "NO" LABEL "Valid Value List" POSITION 9 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Valid value list" ORDER 80 ADD FIELD "retain_profile_history" OF "gsm_profile" AS logical DESCRIPTION "Must we keep a full history of all profile value changes, or just retain the most recent values to use." FORMAT "YES/NO" INITIAL "NO" LABEL "Retain Profile History" POSITION 10 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Retain profile history" ORDER 90 ADD FIELD "profile_mandatory" OF "gsm_profile" AS logical DESCRIPTION "Is entry of this profile value mandatory. If the category is mandatory, then all profile codes within the category must be mandatory. If the category is optional, then this field facilitates making only some of the profile codes within the category mandatory." FORMAT "YES/NO" INITIAL "NO" LABEL "Profile Mandatory" POSITION 11 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Profile mandatory" ORDER 100 ADD FIELD "modifications_allowed" OF "gsm_profile" AS logical DESCRIPTION "If set to no, this profile and its associated entities may not be modified. The default is yes. The management and use of this flag will be controlled within your specific application. For Medstar, in the event that this profile is included in any s_contribution_type.rule_code_profile_objs and s_contribution_rule records exist, this will be set to no. This field is intended to avoid the need to read and check each s_contribution_type before allowing a profile to be modified. The setting / clearing of this status will be managed by the s_contribution_rule schema triggers. " FORMAT "YES/NO" INITIAL "YES" LABEL "Modifications Allowed" POSITION 12 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Modifications allowed" ORDER 110 ADD INDEX "XPKgsm_profile" ON "gsm_profile" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "profile_obj" ASCENDING ADD INDEX "XAK1gsm_profile" ON "gsm_profile" AREA "Schema Area" UNIQUE INDEX-FIELD "category_obj" ASCENDING INDEX-FIELD "profile_tla" ASCENDING ADD INDEX "XIE1gsm_profile" ON "gsm_profile" AREA "Schema Area" INDEX-FIELD "profile_short_desc" ASCENDING ADD INDEX "XIE2gsm_profile" ON "gsm_profile" AREA "Schema Area" INDEX-FIELD "profile_description" ASCENDING ADD TABLE "gsm_profile_date_value" AREA "Schema Area" DESCRIPTION "List of valid dates / date ranges for a profile" DUMP-NAME "gsmpd" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmpdtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmpdtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmpdtrigw.p" CRC "?" ADD FIELD "profile_obj" OF "gsm_profile_date_value" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile obj" DECIMALS 6 ORDER 10 ADD FIELD "profile_sequence" OF "gsm_profile_date_value" AS integer FORMAT "->>9" INITIAL "0" LABEL "Profile Sequence" POSITION 3 SQL-WIDTH 4 COLUMN-LABEL "Profile Seq." VALMSG "n_integer_3" HELP "Profile sequence" ORDER 20 ADD FIELD "description" OF "gsm_profile_date_value" AS character FORMAT "X(35)" INITIAL "" LABEL "Description" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Description" ORDER 30 ADD FIELD "date_value_from" OF "gsm_profile_date_value" AS date DESCRIPTION "This field is only used in the event that the valid value list is a list of ranges rather than single values." FORMAT "99/99/9999" INITIAL "?" LABEL "Date Value From" POSITION 5 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Date value from" ORDER 40 ADD FIELD "date_value_to" OF "gsm_profile_date_value" AS date FORMAT "99/99/9999" INITIAL "?" LABEL "Date Value To" POSITION 6 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Date value to" ORDER 50 ADD FIELD "profile_date_value_obj" OF "gsm_profile_date_value" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Date Value Obj" POSITION 7 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile date value obj" DECIMALS 6 ORDER 60 ADD INDEX "XPKgsm_profile_date_value" ON "gsm_profile_date_value" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "profile_obj" ASCENDING INDEX-FIELD "profile_sequence" ASCENDING ADD INDEX "XAK1gsm_profile_date_value" ON "gsm_profile_date_value" AREA "Schema Area" UNIQUE INDEX-FIELD "profile_obj" ASCENDING INDEX-FIELD "date_value_to" ASCENDING ADD INDEX "XAK2gsm_profile_date_value" ON "gsm_profile_date_value" AREA "Schema Area" UNIQUE INDEX-FIELD "profile_date_value_obj" ASCENDING ADD TABLE "gsm_profile_numeric_value" AREA "Schema Area" DESCRIPTION "List of valid numeric values / ranges for a profile. For other systems, this table is also used for determining contribution rule values e.g. for age or income ranges in conjunction with a hard coded category. The rule value used would be the numeric_value_to. " DUMP-NAME "gsmnv" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmnvtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmnvtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmnvtrigw.p" CRC "?" ADD FIELD "profile_obj" OF "gsm_profile_numeric_value" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile obj" DECIMALS 6 ORDER 10 ADD FIELD "profile_sequence" OF "gsm_profile_numeric_value" AS integer FORMAT "->>9" INITIAL "0" LABEL "Profile Sequence" POSITION 3 SQL-WIDTH 4 COLUMN-LABEL "Profile Seq." VALMSG "n_integer_3" HELP "Profile sequence" ORDER 20 ADD FIELD "description" OF "gsm_profile_numeric_value" AS character FORMAT "X(35)" INITIAL "" LABEL "Description" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Description" ORDER 30 ADD FIELD "numeric_value_from" OF "gsm_profile_numeric_value" AS decimal DESCRIPTION "This field is only used in the event that the valid value list is a list of ranges rather than single values." FORMAT "->>>,>>>,>>>,>>9.999" INITIAL "0" LABEL "Numeric Value From" POSITION 5 SQL-WIDTH 18 VALMSG "n_decimal_3dp_large" HELP "Numeric value from" DECIMALS 3 ORDER 40 ADD FIELD "numeric_value_to" OF "gsm_profile_numeric_value" AS decimal FORMAT "->>>,>>>,>>>,>>9.999" INITIAL "0" LABEL "Numeric Value To" POSITION 6 SQL-WIDTH 18 VALMSG "n_decimal_3dp_large" HELP "Numeric value to" DECIMALS 3 ORDER 50 ADD FIELD "profile_numeric_value_obj" OF "gsm_profile_numeric_value" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Numeric Value Obj" POSITION 7 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile numeric value obj" DECIMALS 6 ORDER 60 ADD INDEX "XPKgsm_profile_numeric_value" ON "gsm_profile_numeric_value" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "profile_obj" ASCENDING INDEX-FIELD "profile_sequence" ASCENDING ADD INDEX "XAK1gsm_profile_numeric_value" ON "gsm_profile_numeric_value" AREA "Schema Area" UNIQUE INDEX-FIELD "profile_obj" ASCENDING INDEX-FIELD "numeric_value_to" ASCENDING ADD INDEX "XAK2gsm_profile_numeric_value" ON "gsm_profile_numeric_value" AREA "Schema Area" UNIQUE INDEX-FIELD "profile_numeric_value_obj" ASCENDING ADD TABLE "gsm_profile_alpha_value" AREA "Schema Area" DESCRIPTION "List of valid values / ranges for an alpha profile" DUMP-NAME "gsmav" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmavtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmavtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmavtrigw.p" CRC "?" ADD FIELD "profile_obj" OF "gsm_profile_alpha_value" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile obj" DECIMALS 6 ORDER 10 ADD FIELD "profile_sequence" OF "gsm_profile_alpha_value" AS integer FORMAT "->>9" INITIAL "0" LABEL "Profile Sequence" POSITION 3 SQL-WIDTH 4 COLUMN-LABEL "Profile Seq." VALMSG "n_integer_3" HELP "Profile sequence" ORDER 20 ADD FIELD "description" OF "gsm_profile_alpha_value" AS character FORMAT "X(35)" INITIAL "" LABEL "Description" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Description" ORDER 30 ADD FIELD "alpha_value_from" OF "gsm_profile_alpha_value" AS character DESCRIPTION "This field is only used in the event that the valid value list is a list of ranges rather than single values." FORMAT "X(15)" INITIAL "" LABEL "Alpha Value From" POSITION 5 SQL-WIDTH 30 VALMSG "s_reference" HELP "Alpha value from" ORDER 40 ADD FIELD "alpha_value_to" OF "gsm_profile_alpha_value" AS character FORMAT "X(15)" INITIAL "" LABEL "Alpha Value To" POSITION 6 SQL-WIDTH 30 VALMSG "s_reference" HELP "Alpha value to" ORDER 50 ADD FIELD "profile_alpha_value_obj" OF "gsm_profile_alpha_value" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Alpha Value Obj" POSITION 7 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile alpha value obj" DECIMALS 6 ORDER 60 ADD INDEX "XPKgsm_profile_alpha_value" ON "gsm_profile_alpha_value" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "profile_obj" ASCENDING INDEX-FIELD "profile_sequence" ASCENDING ADD INDEX "XAK1gsm_profile_alpha_value" ON "gsm_profile_alpha_value" AREA "Schema Area" UNIQUE INDEX-FIELD "profile_obj" ASCENDING INDEX-FIELD "alpha_value_to" ASCENDING ADD INDEX "XAK2gsm_profile_alpha_value" ON "gsm_profile_alpha_value" AREA "Schema Area" UNIQUE INDEX-FIELD "profile_alpha_value_obj" ASCENDING ADD TABLE "gsm_profile_numeric_options" AREA "Schema Area" DESCRIPTION "Numeric specific options for a profile." DUMP-NAME "gsmpn" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmpntrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmpntrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmpntrigw.p" CRC "?" ADD FIELD "profile_obj" OF "gsm_profile_numeric_options" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile obj" DECIMALS 6 ORDER 10 ADD FIELD "decimal_places" OF "gsm_profile_numeric_options" AS integer DESCRIPTION "For a data type of decimal, how many decimal places to use." FORMAT "->9" INITIAL "0" LABEL "Decimal Places" POSITION 3 SQL-WIDTH 4 VALMSG "n_integer_2" HELP "Decimal places" ORDER 20 ADD FIELD "min_value" OF "gsm_profile_numeric_options" AS decimal DESCRIPTION "The minimum permitted value for this profile" FORMAT "->>>,>>>,>>>,>>9.999" INITIAL "0" LABEL "Min. Value" POSITION 4 SQL-WIDTH 18 VALMSG "n_decimal_3dp_large" HELP "Min. value" DECIMALS 3 ORDER 30 ADD FIELD "max_value" OF "gsm_profile_numeric_options" AS decimal DESCRIPTION "The maximum permitted value for this profile" FORMAT "->>>,>>>,>>>,>>9.999" INITIAL "0" LABEL "Max. Value" POSITION 5 SQL-WIDTH 18 VALMSG "n_decimal_3dp_large" HELP "Max. value" DECIMALS 3 ORDER 40 ADD FIELD "field_mask" OF "gsm_profile_numeric_options" AS character DESCRIPTION "The PROGRESS field mask to use when entering or displaying this profile" FORMAT "X(35)" INITIAL "" LABEL "Field Mask" POSITION 6 SQL-WIDTH 70 VALMSG "s_format_string" HELP "Field mask" ORDER 50 ADD FIELD "profile_numeric_options_obj" OF "gsm_profile_numeric_options" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Numeric Options Obj" POSITION 7 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile numeric options obj" DECIMALS 6 ORDER 60 ADD INDEX "XPKgsm_profile_numeric_options" ON "gsm_profile_numeric_options" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "profile_obj" ASCENDING ADD INDEX "XAK1gsm_profile_numeric_option" ON "gsm_profile_numeric_options" AREA "Schema Area" UNIQUE INDEX-FIELD "profile_numeric_options_obj" ASCENDING ADD TABLE "gsm_profile_alpha_options" AREA "Schema Area" DESCRIPTION "Alpha specific details for a profile" DUMP-NAME "gsmpa" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmpatrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmpatrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmpatrigw.p" CRC "?" ADD FIELD "profile_obj" OF "gsm_profile_alpha_options" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile obj" DECIMALS 6 ORDER 10 ADD FIELD "min_characters" OF "gsm_profile_alpha_options" AS integer DESCRIPTION "If any characters are entered, the minimum number of characters that may be entered for this profile, thus enforcing sensible data." FORMAT "->>>>>>>9" INITIAL "0" LABEL "Min. Characters" POSITION 3 SQL-WIDTH 4 VALMSG "n_integer_8" HELP "Min. characters" ORDER 20 ADD FIELD "max_characters" OF "gsm_profile_alpha_options" AS integer DESCRIPTION "The maximum characters to enter for this profile, i.e. the field size" FORMAT "->>>>>>>9" INITIAL "0" LABEL "Max. Characters" POSITION 4 SQL-WIDTH 4 VALMSG "n_integer_8" HELP "Max. characters" ORDER 30 ADD FIELD "force_uppercase" OF "gsm_profile_alpha_options" AS logical DESCRIPTION "Should the value of this profile be forced into uppercase characters." FORMAT "YES/NO" INITIAL "NO" LABEL "Force Uppercase" POSITION 5 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Force uppercase" ORDER 40 ADD FIELD "properform" OF "gsm_profile_alpha_options" AS logical DESCRIPTION "Should the value of this profile be properformed, i.e. automatically tidy up the case of the value into correct upper and lower case." FORMAT "YES/NO" INITIAL "NO" LABEL "Properform" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Properform" ORDER 50 ADD FIELD "profile_alpha_options_obj" OF "gsm_profile_alpha_options" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Alpha Options Obj" POSITION 7 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile alpha options obj" DECIMALS 6 ORDER 60 ADD INDEX "XPKgsm_profile_alpha_options" ON "gsm_profile_alpha_options" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "profile_obj" ASCENDING ADD INDEX "XAK1gsm_profile_alpha_options" ON "gsm_profile_alpha_options" AREA "Schema Area" UNIQUE INDEX-FIELD "profile_alpha_options_obj" ASCENDING ADD TABLE "gsm_profile_history" AREA "Schema Area" DESCRIPTION "History of profiles relating to an object from the effective date onwards. In other systems, in the case where a profile is related to contribution rule value determination, the value fields are not applicable." DUMP-NAME "gsmph" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmphtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmphtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmphtrigw.p" CRC "?" ADD FIELD "profile_obj" OF "gsm_profile_history" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile obj" DECIMALS 6 ORDER 10 ADD FIELD "owning_obj" OF "gsm_profile_history" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Owning Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Owning obj" DECIMALS 6 ORDER 20 ADD FIELD "effective_date" OF "gsm_profile_history" AS date FORMAT "99/99/9999" INITIAL "?" LABEL "Effective Date" POSITION 4 SQL-WIDTH 4 VALMSG "d_start_date" HELP "Effective date" ORDER 30 ADD FIELD "alpha_value" OF "gsm_profile_history" AS character DESCRIPTION "The value for the profile in the case where the profile has a data type of character. This field is also used for logical data types to hold the string of the logical value." FORMAT "X(15)" INITIAL "" LABEL "Alpha Value" POSITION 5 SQL-WIDTH 30 VALMSG "s_reference" HELP "Alpha value" ORDER 40 ADD FIELD "date_value" OF "gsm_profile_history" AS date DESCRIPTION "The value for the profile in the case where the profile has a data type of date." FORMAT "99/99/9999" INITIAL "?" LABEL "Date Value" POSITION 6 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Date value" ORDER 50 ADD FIELD "numeric_value" OF "gsm_profile_history" AS decimal DESCRIPTION "The value for the profile in the case where the profile has a data type of integer or decimal." FORMAT "->>>,>>>,>>>,>>9.999" INITIAL "0" LABEL "Numeric Value" POSITION 7 SQL-WIDTH 18 VALMSG "n_decimal_3dp_large" HELP "Numeric value" DECIMALS 3 ORDER 60 ADD FIELD "alpha_value_to" OF "gsm_profile_history" AS character DESCRIPTION "This field is only used in the event that the profile is a range of values rather than a single value. It is the value to where the profile is a character data type. A logical data type does not support ranges ! " FORMAT "X(15)" INITIAL "" LABEL "Alpha Value To" POSITION 8 SQL-WIDTH 30 VALMSG "s_reference" HELP "Alpha value to" ORDER 70 ADD FIELD "date_value_to" OF "gsm_profile_history" AS date DESCRIPTION "This field is only used in the event that the profile is a range of values rather than a single value. It is the value to where the profile is an date data type. " FORMAT "99/99/9999" INITIAL "?" LABEL "Date Value To" POSITION 9 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Date value to" ORDER 80 ADD FIELD "numeric_value_to" OF "gsm_profile_history" AS decimal DESCRIPTION "This field is only used in the event that the profile is a range of values rather than a single value. It is the value to where the profile is a integer or decimal data type. " FORMAT "->>>,>>>,>>>,>>9.999" INITIAL "0" LABEL "Numeric Value To" POSITION 10 SQL-WIDTH 18 VALMSG "n_decimal_3dp_large" HELP "Numeric value to" DECIMALS 3 ORDER 90 ADD FIELD "profile_history_obj" OF "gsm_profile_history" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile History Obj" POSITION 11 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile history obj" DECIMALS 6 ORDER 100 ADD INDEX "XPKgsm_profile_history" ON "gsm_profile_history" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "profile_obj" ASCENDING INDEX-FIELD "owning_obj" ASCENDING INDEX-FIELD "effective_date" ASCENDING ADD INDEX "XAK1gsm_profile_history" ON "gsm_profile_history" AREA "Schema Area" UNIQUE INDEX-FIELD "profile_history_obj" ASCENDING ADD TABLE "gsm_status" AREA "Schema Area" DESCRIPTION "The actual valid status codes are set-up in the category table. For example: related entity mnemonic = GSMST for gsm_status category type = STS for Status category group = HST for History category subgroup = COD for Code The category subgroup is the actual status in this case. The categories of status will always be system owned and mandatory. The category mandatory flag will be used to indicate whether an object at this status may be modified. At least 1 record must exist in this table for every category subgroup that has a related entity mnemonic of status (GSMST). This record will be system owned, have a sequence of 0 and may not be deleted. It will always be the default status for this category subgroup. This table allows users to modify the narrative of the status, and add extra status's within the same category subgroup to represent their internal business processes. From a business logic point of view, when the status changes within the same category, we do not need to do anything and the user may do this manually via a combo box. The change of status from 1 category to the next within a category group will usually be done via a business logic process. We will always need to join back to the category table to determine what status an object is at from a business logic point of view. The status an object is at effective from a specific date is determined by an entry in the status history table, which means the status does not need to be added to every table it is used for. However, in some cases we have linked objects directly to the status table to show the current status for performance reasons." DUMP-NAME "gsmst" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmsttrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmsttrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmstreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmstrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmstreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmsttrigw.p" CRC "?" ADD FIELD "status_obj" OF "gsm_status" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Status Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Status obj" DECIMALS 6 ORDER 10 ADD FIELD "category_obj" OF "gsm_status" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Category Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Category obj" DECIMALS 6 ORDER 20 ADD FIELD "status_seq" OF "gsm_status" AS integer DESCRIPTION "The order of migration from one status to the next within a category (subgroup). If the system owned flag is set to YES, then the sequence will be 0 and cannot be modified." FORMAT "->>9" INITIAL "0" LABEL "Status Seq." POSITION 4 SQL-WIDTH 4 VALMSG "n_integer_3" HELP "Status seq." ORDER 30 ADD FIELD "status_tla" OF "gsm_status" AS character DESCRIPTION "A 3 character mnemonic e.g. ""UNP"" = Unposted. This may be changed, even if the status is system owned, as the category subgroup identifies the actual status from a business logic perspective. " FORMAT "X(3)" INITIAL "" LABEL "Status TLA" POSITION 5 SQL-WIDTH 6 VALMSG "s_tla" HELP "Status three letter acronym" ORDER 40 ADD FIELD "status_short_desc" OF "gsm_status" AS character FORMAT "X(15)" INITIAL "" LABEL "Status Short Description" POSITION 6 SQL-WIDTH 30 COLUMN-LABEL "Status Short Desc" VALMSG "s_short_desc" HELP "Status short description" ORDER 50 ADD FIELD "status_description" OF "gsm_status" AS character FORMAT "X(35)" INITIAL "" LABEL "Status Description" POSITION 7 SQL-WIDTH 70 VALMSG "s_description" HELP "Status description" ORDER 60 ADD FIELD "system_owned" OF "gsm_status" AS logical DESCRIPTION "System owned status codes cannot be deleted. In addition the status sequence will be 0 and also cannot be modified. 1 system owned status record must exist for every category subgroup related to a status, i.e. related entity mnemonic is GSMST. " FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 80 ADD FIELD "retain_status_history" OF "gsm_status" AS logical DESCRIPTION "Do we want to retain a dated history of status code changes. If not, only the latest status will be kept and previous status's of the same category will be deleted from the gsm_status_history table. " FORMAT "YES/NO" INITIAL "NO" LABEL "Retain Status History" POSITION 9 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Retain status history" ORDER 70 ADD FIELD "auto_display" OF "gsm_status" AS logical DESCRIPTION "Should this status be automatically displayed and acknowledged in an alert dialog box whenever this status is active for an object (no end date if using status history)." FORMAT "YES/NO" INITIAL "NO" LABEL "Auto Display" POSITION 10 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Auto display" ORDER 90 ADD INDEX "XPKgsm_status" ON "gsm_status" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "status_obj" ASCENDING ADD INDEX "XAK1gsm_status" ON "gsm_status" AREA "Schema Area" UNIQUE INDEX-FIELD "category_obj" ASCENDING INDEX-FIELD "status_seq" ASCENDING ADD INDEX "XAK2gsm_status" ON "gsm_status" AREA "Schema Area" UNIQUE INDEX-FIELD "category_obj" ASCENDING INDEX-FIELD "status_tla" ASCENDING ADD INDEX "XIE1gsm_status" ON "gsm_status" AREA "Schema Area" INDEX-FIELD "category_obj" ASCENDING INDEX-FIELD "status_description" ASCENDING ADD INDEX "XIE2gsm_status" ON "gsm_status" AREA "Schema Area" INDEX-FIELD "category_obj" ASCENDING INDEX-FIELD "status_short_desc" ASCENDING ADD TABLE "gsm_status_history" AREA "Schema Area" DESCRIPTION "Actual status of an object as from the effective date" DUMP-NAME "gsmsh" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmshtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmshtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmshtrigw.p" CRC "?" ADD FIELD "owning_obj" OF "gsm_status_history" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Owning Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Owning obj" DECIMALS 6 ORDER 10 ADD FIELD "from_date" OF "gsm_status_history" AS date DESCRIPTION "The date this status became effective for the object." FORMAT "99/99/9999" INITIAL "?" LABEL "From Date" POSITION 3 SQL-WIDTH 4 VALMSG "d_start_date" HELP "From date" ORDER 20 ADD FIELD "status_obj" OF "gsm_status_history" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Status Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Status obj" DECIMALS 6 ORDER 30 ADD FIELD "status_history_obj" OF "gsm_status_history" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Status History Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Status history obj" DECIMALS 6 ORDER 50 ADD FIELD "to_date" OF "gsm_status_history" AS date DESCRIPTION "The date this status was no longer applicable for the object." FORMAT "99/99/9999" INITIAL "?" LABEL "to Date" POSITION 6 SQL-WIDTH 4 VALMSG "d_end_date" HELP "To date" ORDER 40 ADD INDEX "XPKgsm_status_history" ON "gsm_status_history" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "owning_obj" ASCENDING INDEX-FIELD "from_date" ASCENDING INDEX-FIELD "status_obj" ASCENDING ADD INDEX "XAK1gsm_status_history" ON "gsm_status_history" AREA "Schema Area" UNIQUE INDEX-FIELD "status_obj" ASCENDING INDEX-FIELD "owning_obj" ASCENDING INDEX-FIELD "from_date" ASCENDING ADD INDEX "XAK2gsm_status_history" ON "gsm_status_history" AREA "Schema Area" UNIQUE INDEX-FIELD "status_history_obj" ASCENDING ADD INDEX "XIE1gsm_status_history" ON "gsm_status_history" AREA "Schema Area" INDEX-FIELD "owning_obj" ASCENDING INDEX-FIELD "from_date" ASCENDING ADD TABLE "gsm_comment" AREA "Schema Area" DESCRIPTION "Generic comment linked to any entity." DUMP-NAME "gsmcm" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmcmtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmcmtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmcmtrigw.p" CRC "?" ADD FIELD "comment_obj" OF "gsm_comment" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Comment Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Comment obj" DECIMALS 6 ORDER 10 ADD FIELD "owning_obj" OF "gsm_comment" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Owning Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Owning obj" DECIMALS 6 ORDER 30 ADD FIELD "owning_entity_mnemonic" OF "gsm_comment" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Owning Entity Mnemonic" POSITION 4 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Owning entity mnemonic" ORDER 20 ADD FIELD "category_obj" OF "gsm_comment" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Category Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Category obj" DECIMALS 6 ORDER 40 ADD FIELD "comment_text" OF "gsm_comment" AS character FORMAT "X(3000)" INITIAL "" LABEL "Comment Text" POSITION 6 SQL-WIDTH 6000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL LARGE MAX-CHARS 3000" VALMSG "s_big_text_block" HELP "Comment text" ORDER 50 ADD FIELD "auto_display" OF "gsm_comment" AS logical DESCRIPTION "Should this comment be automatically displayed and acknowledged in an alert dialog box whenever the owning_obj is entered." FORMAT "YES/NO" INITIAL "NO" LABEL "Auto Display" POSITION 7 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Auto display" ORDER 60 ADD FIELD "print_option_tlas" OF "gsm_comment" AS character DESCRIPTION "An optional comma separated selection of codes from g_category.valid_print_option_tlas, used to determine on which documents this comment is to be printed. The recognition of these TLA's is hard coded in the appropriate document print programs.." FORMAT "X(70)" INITIAL "" LABEL "Print Option TLAs" POSITION 8 SQL-WIDTH 140 VALMSG "s_tla_list" HELP "Print option three letter acronyms" ORDER 70 ADD FIELD "expiry_date" OF "gsm_comment" AS date DESCRIPTION "The date after which this comment is no longer valid" FORMAT "99/99/9999" INITIAL "?" LABEL "Expiry Date" POSITION 9 SQL-WIDTH 4 VALMSG "d_end_date" HELP "Expiry date" ORDER 80 ADD FIELD "comment_description" OF "gsm_comment" AS character DESCRIPTION "A summary of the comment to display in browsers, etc. where space is limited. A word search could be performed on this field to locate the comment." FORMAT "X(35)" INITIAL "" LABEL "Comment Description" POSITION 10 SQL-WIDTH 70 VALMSG "s_description" HELP "Comment description" ORDER 90 ADD INDEX "XPKgsm_comment" ON "gsm_comment" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "comment_obj" ASCENDING ADD INDEX "XAK1gsm_comment" ON "gsm_comment" AREA "Schema Area" UNIQUE INDEX-FIELD "category_obj" ASCENDING INDEX-FIELD "owning_obj" ASCENDING INDEX-FIELD "comment_obj" ASCENDING INDEX-FIELD "owning_entity_mnemonic" ASCENDING ADD INDEX "XIE1gsm_comment" ON "gsm_comment" AREA "Schema Area" WORD INDEX-FIELD "comment_description" ASCENDING ADD INDEX "XIE2gsm_comment" ON "gsm_comment" AREA "Schema Area" INDEX-FIELD "owning_obj" ASCENDING INDEX-FIELD "auto_display" ASCENDING ADD INDEX "XIE3gsm_comment" ON "gsm_comment" AREA "Schema Area" INDEX-FIELD "owning_entity_mnemonic" ASCENDING INDEX-FIELD "owning_obj" ASCENDING ADD TABLE "gsc_language_text" AREA "Schema Area" DESCRIPTION "Totally generic text file for all supported languages. Text's may be associated with another entity (via owning_obj) or may be simply generic text of a certain type. Numbers enclosed in {} are for parameter substitution. E.g. Scheme option names, transaction narrations, valid people titles, etc." DUMP-NAME "gsclt" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsclttrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsclttrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsclttrigw.p" CRC "?" ADD FIELD "language_text_obj" OF "gsc_language_text" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Language Text Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Language text obj" DECIMALS 6 ORDER 10 ADD FIELD "owning_obj" OF "gsc_language_text" AS decimal DESCRIPTION "This is set only in cases where this language text belongs to another entity, e.g. scheme option names (in each language) belonging to a specific scheme option." FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Owning Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Owning obj" DECIMALS 6 ORDER 20 ADD FIELD "category_obj" OF "gsc_language_text" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Category Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Category obj" DECIMALS 6 ORDER 30 ADD FIELD "language_obj" OF "gsc_language_text" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Language Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Language obj" DECIMALS 6 ORDER 40 ADD FIELD "text_tla" OF "gsc_language_text" AS character DESCRIPTION "This is the identifying TLA of the language text message. The same message in each language will have the same text_tla. In the case of system owned text, the text TLA will be hard coded and referenced within programs. This code can not be amended as it is referenced in other tables within the databases. In the generic database these are currently g_eft_type and g_transaction_type. Additionally in Medstar these are t_claim_note, t_claim_acctran and c_limit." FORMAT "X(3)" INITIAL "" LABEL "Text TLA" POSITION 6 SQL-WIDTH 6 VALMSG "s_tla" HELP "Text three letter acronym" ORDER 50 ADD FIELD "physical_file_name" OF "gsc_language_text" AS character DESCRIPTION "In cases where the text exists in an external file e.g. a Word document, this field would contain the full path, file name and extension. The extension will determine the nature of the file in accordance with Microsoft standards. If this field contains a file name, text_content may show the first portion of the document for identification purposes etc.." FORMAT "X(70)" INITIAL "" LABEL "Physical File Name" POSITION 7 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Physical file name" ORDER 60 ADD FIELD "text_content" OF "gsc_language_text" AS character DESCRIPTION "The actual text in the appropriate language. The text may include codes in brackets, e.g. {1} which will be substituted with appropriate data when used. In cases where a physical file is entered, the physical file content will be used rather than this field value." FORMAT "X(3000)" INITIAL "" LABEL "Text Content" POSITION 8 SQL-WIDTH 6000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL LARGE MAX-CHARS 3000" VALMSG "s_big_text_block" HELP "Text content" ORDER 70 ADD FIELD "system_owned" OF "gsc_language_text" AS logical DESCRIPTION "Is this text system owned ? Certain text will be required and must be system generated. They cannot be deleted. Examples are narrations associated with transaction types, e.g. ""DR Interest""." FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 9 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 80 ADD FIELD "max_length" OF "gsc_language_text" AS integer FORMAT "->>>>>>>9" INITIAL "0" LABEL "Max. Length" POSITION 10 SQL-WIDTH 4 VALMSG "n_integer_8" HELP "Max. length" ORDER 90 ADD FIELD "print_option_tlas" OF "gsc_language_text" AS character DESCRIPTION "An optional selection of TLA's from g_category.valid_print_option_tlas, used to determine on which documents this message is to be printed. The recognition of these TLA's is hard coded in the appropriate document print programs." FORMAT "X(70)" INITIAL "" LABEL "Print Option TLAs" POSITION 11 SQL-WIDTH 140 VALMSG "s_tla_list" HELP "Print option three letter acronyms" ORDER 100 ADD FIELD "search_string" OF "gsc_language_text" AS character DESCRIPTION "A summary of the text content used for searching. This will be automatically populated with the start of the text_content by default." FORMAT "X(70)" INITIAL "" LABEL "Search String" POSITION 12 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Search string" ORDER 110 ADD INDEX "XPKgsc_language_text" ON "gsc_language_text" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "language_text_obj" ASCENDING ADD INDEX "XAK1gsc_language_text" ON "gsc_language_text" AREA "Schema Area" UNIQUE INDEX-FIELD "category_obj" ASCENDING INDEX-FIELD "owning_obj" ASCENDING INDEX-FIELD "language_obj" ASCENDING INDEX-FIELD "text_tla" ASCENDING ADD INDEX "XIE1gsc_language_text" ON "gsc_language_text" AREA "Schema Area" INDEX-FIELD "search_string" ASCENDING ADD TABLE "gsc_custom_procedure" AREA "Schema Area" DESCRIPTION "Due to the complexity and variety of certain business processes, such as calculating contribution amounts, determining limits, etc. parameterisation of these processes becomes impractical. This table contains a list of all the system supported procedures that satisfy these business rules, categorised by entity and procedure type. A number of variations for each process may exist - the procedure to use in each case must be selected from this list. The programs that these procedures exist in will run persistently when required." DUMP-NAME "gsccp" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsccptrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsccptrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsccpreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsccprepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsccpreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsccptrigw.p" CRC "?" ADD FIELD "custom_procedure_obj" OF "gsc_custom_procedure" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Custom Procedure Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Custom procedure obj" DECIMALS 6 ORDER 10 ADD FIELD "category_obj" OF "gsc_custom_procedure" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Category Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Category obj" DECIMALS 6 ORDER 20 ADD FIELD "custom_procedure_short_desc" OF "gsc_custom_procedure" AS character FORMAT "X(15)" INITIAL "" LABEL "Custom Procedure Short Description" POSITION 4 SQL-WIDTH 30 COLUMN-LABEL "Custom Procedure Short Desc" VALMSG "s_short_desc" HELP "Custom procedure short description" ORDER 30 ADD FIELD "custom_procedure_description" OF "gsc_custom_procedure" AS character DESCRIPTION "A description of the customised business process procedure. This will be presented to the user and so should be adequately described." FORMAT "X(70)" INITIAL "" LABEL "Custom Procedure Description" POSITION 5 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Custom procedure description" ORDER 40 ADD FIELD "procedure_name" OF "gsc_custom_procedure" AS character DESCRIPTION "The actual internal procedure name as used in the program." FORMAT "X(35)" INITIAL "" LABEL "Procedure Name" POSITION 6 SQL-WIDTH 70 VALMSG "s_program_procedure" HELP "Procedure name" ORDER 60 ADD FIELD "custom_procedure_notes" OF "gsc_custom_procedure" AS character FORMAT "X(3000)" INITIAL "" LABEL "Custom Procedure Notes" POSITION 7 SQL-WIDTH 6000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL LARGE MAX-CHARS 3000" VALMSG "s_big_text_block" HELP "Custom procedure notes" ORDER 50 ADD FIELD "run_this_procedure" OF "gsc_custom_procedure" AS logical DESCRIPTION "If set to NO, the running of this procedure will be disabled." FORMAT "YES/NO" INITIAL "YES" LABEL "Run This Procedure" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Run this procedure" ORDER 70 ADD INDEX "XPKgsc_custom_procedure" ON "gsc_custom_procedure" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "custom_procedure_obj" ASCENDING ADD INDEX "XAK1gsc_custom_procedure" ON "gsc_custom_procedure" AREA "Schema Area" UNIQUE INDEX-FIELD "procedure_name" ASCENDING ADD INDEX "XIE1gsc_custom_procedure" ON "gsc_custom_procedure" AREA "Schema Area" INDEX-FIELD "category_obj" ASCENDING INDEX-FIELD "custom_procedure_description" ASCENDING ADD INDEX "XIE2gsc_custom_procedure" ON "gsc_custom_procedure" AREA "Schema Area" INDEX-FIELD "category_obj" ASCENDING INDEX-FIELD "custom_procedure_short_desc" ASCENDING ADD TABLE "gsc_sequence" AREA "Schema Area" DESCRIPTION "This is a generic sequence number / format table. All entries in this table will be system owned by their nature. When a sequence number is required to be generated, it will be done at the end of the update as part of the transaction. This table is a potential bottle neck and so locks should be kept to an absolute minimum, i.e. no locks during user interaction. If the sequence number is to be automatically generated, then there can be no holes in the sequence numbers, which is why a Progress sequence will not be used. Example uses for this table would be for the automatic generation of document numbers, transaction references, etc." DUMP-NAME "gscsq" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscsqtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscsqtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscsqreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscsqrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscsqreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscsqtrigw.p" CRC "?" ADD FIELD "owning_entity_mnemonic" OF "gsc_sequence" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Owning Entity Mnemonic" POSITION 2 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Owning entity mnemonic" ORDER 30 ADD FIELD "sequence_tla" OF "gsc_sequence" AS character DESCRIPTION "A 3 character mnemonic to uniquely identify the sequence number in conjunction with the owning_entity_mnemonic. This facilitates more than one sequence per entity. " FORMAT "X(3)" INITIAL "" LABEL "Sequence TLA" POSITION 3 SQL-WIDTH 6 COLUMN-LABEL "Seq. TLA" VALMSG "s_tla" HELP "Sequence three letter acronym" ORDER 40 ADD FIELD "company_organisation_obj" OF "gsc_sequence" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Company Organisation Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Company organisation obj" DECIMALS 6 ORDER 20 ADD FIELD "sequence_short_desc" OF "gsc_sequence" AS character FORMAT "X(15)" INITIAL "" LABEL "Sequence Short Description" POSITION 5 SQL-WIDTH 30 COLUMN-LABEL "Seq. Short Desc" VALMSG "s_short_desc" HELP "Sequence short description" ORDER 50 ADD FIELD "sequence_description" OF "gsc_sequence" AS character FORMAT "X(35)" INITIAL "" LABEL "Sequence Description" POSITION 6 SQL-WIDTH 70 COLUMN-LABEL "Seq. Description" VALMSG "s_description" HELP "Sequence description" ORDER 60 ADD FIELD "min_value" OF "gsc_sequence" AS integer FORMAT "->>>>>>>9" INITIAL "0" LABEL "Min. Value" POSITION 7 SQL-WIDTH 4 VALMSG "n_integer_8" HELP "Min. value" ORDER 70 ADD FIELD "max_value" OF "gsc_sequence" AS integer FORMAT "->>>>>>>9" INITIAL "0" LABEL "Max. Value" POSITION 8 SQL-WIDTH 4 VALMSG "n_integer_8" HELP "Max. value" ORDER 80 ADD FIELD "sequence_format" OF "gsc_sequence" AS character DESCRIPTION "A user defined format mask for the sequence. The format mask must include a numeric format catering for the maximum value and as per the underlying database format rules, e.g. 99999999 = 8 digit number with 0 prefix >>>>>>>9 = 8 digit number with 0 suppression The format may also include hard coded characters, e.g. ""MNU"" for Memu Items or ""RPT"" for Reports The format may additionally include insertion codes to dynamically insert data at runtime as follows: %Y = Insert the last digit of the current year %YY = Insert the current 2 digit year %YYYY = Insert the current 4 digit year %MM = Insert the current 2 digit month %MMM = Insert the current 3 character month %DD = Insert the current day of the month An important point is that sequence formats on site must have a different prefix to any references generated from ICF to ensure we do not overwrite any data generated on site. " FORMAT "X(35)" INITIAL "" LABEL "Sequence Format" POSITION 9 SQL-WIDTH 70 COLUMN-LABEL "Seq. Format" VALMSG "s_format_string" HELP "Sequence format" ORDER 90 ADD FIELD "auto_generate" OF "gsc_sequence" AS logical DESCRIPTION "If set to yes, the sequence will be automatically generated using the next_value. The user is prevented from amending the value of the sequence." FORMAT "YES/NO" INITIAL "YES" LABEL "Auto Generate" POSITION 10 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Auto generate" ORDER 100 ADD FIELD "multi_transaction" OF "gsc_sequence" AS logical DESCRIPTION "If it is possible that a sequence will be used by multiple transactions simultaneously, potential for deadly embrace locks exists. If this field is set to NO, the next_value will be read and updated each time a sequence number is requested, in which case the gsc_sequence record is locked for the duration of the transaction. If this field is set to YES, this table is not locked and the first sequence is used from table gsc_next_sequence." FORMAT "YES/NO" INITIAL "NO" LABEL "Multi Transaction" POSITION 11 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Multi transaction" ORDER 110 ADD FIELD "sequence_obj" OF "gsc_sequence" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Sequence Obj" POSITION 12 SQL-WIDTH 21 COLUMN-LABEL "Seq. Obj" VALMSG "o_obj" HELP "Sequence obj" DECIMALS 6 ORDER 10 ADD FIELD "sequence_active" OF "gsc_sequence" AS logical DESCRIPTION "Is this sequence active. At any time setting this field to NO will disable further use of this sequence, forcing manual entry of the reference field using the sequence. Typically the sequence would be set to not active in a data take-on situation so that imported references are not corrupted." FORMAT "YES/NO" INITIAL "YES" LABEL "Sequence Active" POSITION 13 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" COLUMN-LABEL "Seq. Active" VALMSG "l_yesno" HELP "Sequence active" ORDER 140 ADD FIELD "next_value" OF "gsc_sequence" AS integer DESCRIPTION "The next available value of the sequence, if the sequence is being automatically generated. " FORMAT "->>>>>>>9" INITIAL "0" LABEL "Next Value" POSITION 14 SQL-WIDTH 4 VALMSG "n_integer_8" HELP "Next. value" ORDER 120 ADD FIELD "number_of_sequences" OF "gsc_sequence" AS integer DESCRIPTION "This field is only enabled in multi_transaction is set to YES. It indicates the maximum number of available sequences (that could ever get locked concurrently) contained in gsc_next_sequence table." FORMAT "->>>>>9" INITIAL "0" LABEL "Number of Sequences" POSITION 15 SQL-WIDTH 4 COLUMN-LABEL "Number of Seq.s" VALMSG "n_integer_6" HELP "Number of sequences" ORDER 130 ADD INDEX "XPKgsc_sequence" ON "gsc_sequence" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "sequence_obj" ASCENDING ADD INDEX "XAK1gsc_sequence" ON "gsc_sequence" AREA "Schema Area" UNIQUE INDEX-FIELD "company_organisation_obj" ASCENDING INDEX-FIELD "owning_entity_mnemonic" ASCENDING INDEX-FIELD "sequence_tla" ASCENDING ADD INDEX "XIE1gsc_sequence" ON "gsc_sequence" AREA "Schema Area" INDEX-FIELD "sequence_description" ASCENDING ADD INDEX "XIE2gsc_sequence" ON "gsc_sequence" AREA "Schema Area" INDEX-FIELD "sequence_short_desc" ASCENDING ADD TABLE "gsc_entity_mnemonic_procedure" AREA "Schema Area" DESCRIPTION "This table contains pointers to procedures which may be automatically run by the system before and after table create, write and delete triggers. The procedures would exist under a single category type with 6 category groups: Before create After create Before write After write Before delete After delete." DUMP-NAME "gscep" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsceptrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsceptrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscepreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsceprepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscepreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsceptrigw.p" CRC "?" ADD FIELD "custom_procedure_obj" OF "gsc_entity_mnemonic_procedure" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Custom Procedure Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Custom procedure obj" DECIMALS 6 ORDER 10 ADD FIELD "owning_entity_mnemonic" OF "gsc_entity_mnemonic_procedure" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Owning Entity Mnemonic" POSITION 3 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Owning entity mnemonic" ORDER 20 ADD FIELD "entity_mnemonic_procedure_obj" OF "gsc_entity_mnemonic_procedure" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Entity Mnemonic Procedure Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Entity mnemonic procedure obj" DECIMALS 6 ORDER 30 ADD FIELD "run_this_procedure" OF "gsc_entity_mnemonic_procedure" AS logical DESCRIPTION "If set to NO, this procedure will not be run automatically." FORMAT "YES/NO" INITIAL "YES" LABEL "Run This Procedure" POSITION 5 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Run this procedure" ORDER 40 ADD INDEX "XPKgsc_entity_mnemonic_procedu" ON "gsc_entity_mnemonic_procedure" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "custom_procedure_obj" ASCENDING INDEX-FIELD "owning_entity_mnemonic" ASCENDING ADD TABLE "gsc_default_set" AREA "Schema Area" DESCRIPTION "This table is used to associate a set of parameters / defaults i.e. a set of gsc_default_code records. For example, there could be a general set of defaults applicable to the system in general, and other sets of defaults to be used in certain circumstances e.g. for a specific department. The way these sets are used must be hard coded into the application." DUMP-NAME "gscds" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscdstrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscdstrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscdsreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscdsrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscdsreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscdstrigw.p" CRC "?" ADD FIELD "default_set_code" OF "gsc_default_set" AS character DESCRIPTION "A code to uniquely identify this default set code." FORMAT "X(10)" INITIAL "" LABEL "Default Set Code" POSITION 2 SQL-WIDTH 20 VALMSG "s_code" HELP "Default set code" ORDER 10 ADD FIELD "default_set_description" OF "gsc_default_set" AS character FORMAT "X(35)" INITIAL "" LABEL "Default Set Description" POSITION 3 SQL-WIDTH 70 VALMSG "s_description" HELP "Default set description" ORDER 20 ADD FIELD "default_set_obj" OF "gsc_default_set" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Default Set Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Default set obj" DECIMALS 6 ORDER 30 ADD INDEX "XPKgsc_default_set" ON "gsc_default_set" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "default_set_code" ASCENDING ADD INDEX "XAK1gsc_default_set" ON "gsc_default_set" AREA "Schema Area" UNIQUE INDEX-FIELD "default_set_obj" ASCENDING ADD INDEX "XIE1gsc_default_set" ON "gsc_default_set" AREA "Schema Area" INDEX-FIELD "default_set_description" ASCENDING ADD TABLE "gsc_default_set_usage" AREA "Schema Area" DESCRIPTION "This table associates default sets with objects in the application. For example, in property administration, a default set could be for a specific administration company. In medical aid, a default set could be for a specific scheme option, employer group etc." DUMP-NAME "gscdu" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscdutrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscdutrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscdutrigw.p" CRC "?" ADD FIELD "default_set_code" OF "gsc_default_set_usage" AS character DESCRIPTION "A code to uniquely identify this default set code." FORMAT "X(10)" INITIAL "" LABEL "Default Set Code" POSITION 2 SQL-WIDTH 20 VALMSG "s_code" HELP "Default set code" ORDER 10 ADD FIELD "owning_entity_mnemonic" OF "gsc_default_set_usage" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Owning Entity Mnemonic" POSITION 3 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Owning entity mnemonic" ORDER 20 ADD FIELD "owning_obj" OF "gsc_default_set_usage" AS decimal DESCRIPTION "." FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Owning Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Owning obj" DECIMALS 6 ORDER 30 ADD FIELD "default_set_usage_obj" OF "gsc_default_set_usage" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Default Set Usage Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Default set usage obj" DECIMALS 6 ORDER 40 ADD INDEX "XPKgsc_default_set_usage" ON "gsc_default_set_usage" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "default_set_code" ASCENDING INDEX-FIELD "owning_entity_mnemonic" ASCENDING INDEX-FIELD "owning_obj" ASCENDING ADD TABLE "gsc_default_code" AREA "Schema Area" DESCRIPTION "This table makes provision for any number of parameters or system defaults that need be specified to the system, without neccessitating structural database changes. How these parameters / defaults are used needs to be hard coded into the application. These records can be grouped into sets under gsc_default_set, to facilitate different parameter / defaults sets. Again, the selection of a default set would be coded into the application. An example would be different parameter sets for warehouse control, different controls per administration group etc." DUMP-NAME "gscdc" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscdctrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscdctrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscdcreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscdcrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscdcreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscdctrigw.p" CRC "?" ADD FIELD "default_set_code" OF "gsc_default_code" AS character DESCRIPTION "A code to uniquely identify this default set code." FORMAT "X(10)" INITIAL "" LABEL "Default Set Code" POSITION 2 SQL-WIDTH 20 VALMSG "s_code" HELP "Default set code" ORDER 10 ADD FIELD "owning_entity_mnemonic" OF "gsc_default_code" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Owning Entity Mnemonic" POSITION 3 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Owning entity mnemonic" ORDER 20 ADD FIELD "field_name" OF "gsc_default_code" AS character DESCRIPTION "The field name used to uniquely identify the default code within the default set." FORMAT "X(70)" INITIAL "" LABEL "Field Name" POSITION 4 SQL-WIDTH 140 VALMSG "s_big_name" HELP "Field name" ORDER 30 ADD FIELD "effective_date" OF "gsc_default_code" AS date DESCRIPTION "The date this default code became effective. This rate is effective until a new effective date is entered." FORMAT "99/99/9999" INITIAL "?" LABEL "Effective Date" POSITION 5 SQL-WIDTH 4 VALMSG "d_start_date" HELP "Effective date" ORDER 40 ADD FIELD "data_type" OF "gsc_default_code" AS character DESCRIPTION "The PROGRESS data type of this profile code as follows: CHR = CHARACTER INT = INTEGER DEC = DECIMAL DAT = DATE" FORMAT "X(10)" INITIAL "" LABEL "Data Type" POSITION 6 SQL-WIDTH 20 VALMSG "s_data_type" HELP "Data type" ORDER 50 ADD FIELD "field_value" OF "gsc_default_code" AS character DESCRIPTION "The value for the default, always in character format. Where this is not character, it would need to be converted to the appropriate data_type before being used by the application. The update program should set this value using a field type of the data_type to force a level of input validation, and then convert this to character to store in this field." FORMAT "X(70)" INITIAL "" LABEL "Field Value" POSITION 7 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Field value" ORDER 60 ADD FIELD "default_code_obj" OF "gsc_default_code" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Default Code Obj" POSITION 8 SQL-WIDTH 21 VALMSG "o_obj" HELP "Default code obj" DECIMALS 6 ORDER 70 ADD INDEX "XPKgsc_default_code" ON "gsc_default_code" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "default_set_code" ASCENDING INDEX-FIELD "owning_entity_mnemonic" ASCENDING INDEX-FIELD "field_name" ASCENDING INDEX-FIELD "effective_date" ASCENDING ADD INDEX "XAK1gsc_default_code" ON "gsc_default_code" AREA "Schema Area" UNIQUE INDEX-FIELD "default_code_obj" ASCENDING ADD TABLE "gsm_token" AREA "Schema Area" DESCRIPTION "Tokens are used in the application to control access to functions the user may perform within a program via tab folder page names and button names. Tokens may be created for any tab page names or button labels, being careful to ignore any shortcut characters and ... suffixes. The tokens must then be added to the security structure table to become active. The security structure table facilitates the token being restricted for a specific object instance, specific object, specific product module, or generically for everything. The software will only check security providing a valid enabled token exists for the button label or tab folder page. If a user has no tokens allocated at all, then it is assumed they have full access (providing security contol is set to full access by default). Once a user is allocated tokens, then security comes into force and the user will only be granted access for folder pages and buttons they have been granted access to (an that have restricted access set up). Example tokens would be add, delete, modify, view, copy, page 1, page 2, etc. " DUMP-NAME "gsmto" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmtotrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmtotrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmtotrigw.p" CRC "?" ADD FIELD "token_obj" OF "gsm_token" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Token Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Token obj" DECIMALS 6 ORDER 10 ADD FIELD "token_code" OF "gsm_token" AS character DESCRIPTION "The unique code allocated to this token." FORMAT "X(35)" INITIAL "" LABEL "Token Code" POSITION 3 SQL-WIDTH 70 VALMSG "s_name" HELP "Token code" ORDER 20 ADD FIELD "token_description" OF "gsm_token" AS character DESCRIPTION "A full description of the token purpose." FORMAT "X(35)" INITIAL "" LABEL "Token Description" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Token description" ORDER 30 ADD FIELD "disabled" OF "gsm_token" AS logical DESCRIPTION "If set to YES, then this token will not be checked, and full access will be granted." FORMAT "YES/NO" INITIAL "NO" LABEL "Disabled" POSITION 5 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Disabled" ORDER 40 ADD FIELD "system_owned" OF "gsm_token" AS logical DESCRIPTION "If set to YES, this token is required for the system to operate and cannot be amended or deleted by users." FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 50 ADD INDEX "XPKgsm_token" ON "gsm_token" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "token_obj" ASCENDING ADD INDEX "XAK1gsm_token" ON "gsm_token" AREA "Schema Area" UNIQUE INDEX-FIELD "token_code" ASCENDING ADD INDEX "XIE1gsm_token" ON "gsm_token" AREA "Schema Area" INDEX-FIELD "token_description" ASCENDING ADD TABLE "gsm_field" AREA "Schema Area" DESCRIPTION "Fields that require secured access in the software. Not many fields required security, but those that do should be defined in this table. Users can only be given restricted access to fields specified in this table. If a user is given restricted access to a field specified in this table, then the access granted to the user may be view only, hidden, or update. For field security to be activated, entries must be created in the security structure table, as it is this table that is allocated to users, and allows the field security to be restricted or different in various parts of the application. Usually developers will create appropriate fields, and users may then assign them to certain parts of the application via the security structure table. " DUMP-NAME "gsmff" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmfftrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmfftrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmfftrigw.p" CRC "?" ADD FIELD "field_obj" OF "gsm_field" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Field Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Field obj" DECIMALS 6 ORDER 10 ADD FIELD "field_name" OF "gsm_field" AS character DESCRIPTION "The actual schema fieldname, specified as tablename.fieldname." FORMAT "X(70)" INITIAL "" LABEL "Field Name" POSITION 3 SQL-WIDTH 140 VALMSG "s_big_name" HELP "Field name" ORDER 20 ADD FIELD "field_description" OF "gsm_field" AS character DESCRIPTION "A description of the field." FORMAT "X(35)" INITIAL "" LABEL "Field Description" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Field description" ORDER 30 ADD FIELD "disabled" OF "gsm_field" AS logical DESCRIPTION "If set to YES, then this field will not be checked, and full access will be granted." FORMAT "YES/NO" INITIAL "NO" LABEL "Disabled" POSITION 5 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Disabled" ORDER 40 ADD FIELD "system_owned" OF "gsm_field" AS logical DESCRIPTION "If set to YES, this field is required for the system to operate and cannot be amended or deleted by users." FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 50 ADD INDEX "XPKgsm_field" ON "gsm_field" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "field_obj" ASCENDING ADD INDEX "XAK1gsm_field" ON "gsm_field" AREA "Schema Area" UNIQUE INDEX-FIELD "field_name" ASCENDING ADD INDEX "XIE1gsm_field" ON "gsm_field" AREA "Schema Area" INDEX-FIELD "field_description" ASCENDING ADD TABLE "gsm_range" AREA "Schema Area" DESCRIPTION "These are range structures that control what data a user may view. When allocated to a user, the ranges of permitted data will be specified. Sample range structures could include ""Nominal Codes"", ""Cost Centres"", or ""Member Codes"", etc. The appropriate data will be hidden from the user. For range security to be activated, entries must be created in the security structure table, as it is this table that is allocated to users, and allows the range security to be restricted or different in various parts of the application. Usually developers will create appropriate ranges, and users may then assign them to certain parts of the application via the security structure table. " DUMP-NAME "gsmra" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmratrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmratrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmratrigw.p" CRC "?" ADD FIELD "range_obj" OF "gsm_range" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Range Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Range obj" DECIMALS 6 ORDER 10 ADD FIELD "range_code" OF "gsm_range" AS character DESCRIPTION "The unique code allocated to this range." FORMAT "X(10)" INITIAL "" LABEL "Range Code" POSITION 3 SQL-WIDTH 20 VALMSG "s_code" HELP "Range code" ORDER 20 ADD FIELD "range_description" OF "gsm_range" AS character DESCRIPTION "A full description of the purpose of the range." FORMAT "X(35)" INITIAL "" LABEL "Range Description" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Range description" ORDER 30 ADD FIELD "disabled" OF "gsm_range" AS logical DESCRIPTION "If set to YES, then this range will not be checked, and full access will be granted." FORMAT "YES/NO" INITIAL "NO" LABEL "Disabled" POSITION 5 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Disabled" ORDER 40 ADD FIELD "system_owned" OF "gsm_range" AS logical DESCRIPTION "If set to YES, this range is required for the system to operate and cannot be amended or deleted by users." FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 50 ADD INDEX "XPKgsm_range" ON "gsm_range" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "range_obj" ASCENDING ADD INDEX "XAK1gsm_range" ON "gsm_range" AREA "Schema Area" UNIQUE INDEX-FIELD "range_code" ASCENDING ADD INDEX "XIE1gsm_range" ON "gsm_range" AREA "Schema Area" INDEX-FIELD "range_description" ASCENDING ADD TABLE "gsm_help" AREA "Schema Area" DESCRIPTION "This table defines help contexts for containers, objects on containers, and fields on obejcts if required. When context sensitive help is requested, the context and help file will be retrieved from this file if available. Help may be specified in multiple languages if required. An entry in this table for a specific language but no container, object or field specified will override the standard help file used systemwide for the specified language from gsc_security_control." DUMP-NAME "gsmhe" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmhetrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmhetrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gsmhereplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gsmherepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gsmhereplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmhetrigw.p" CRC "?" ADD FIELD "help_obj" OF "gsm_help" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Help Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Help obj" DECIMALS 6 ORDER 10 ADD FIELD "help_filename" OF "gsm_help" AS character DESCRIPTION "If specified, this will override the default help file used by the system for this specific help context. If empty, the default will be used as per the system control record. " FORMAT "X(70)" INITIAL "" LABEL "Help Filename" POSITION 3 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Help filename" ORDER 20 ADD FIELD "help_container_filename" OF "gsm_help" AS character DESCRIPTION "The container filename this help context is for. Specify an extension e.g. .w, but do not specify a path" FORMAT "X(70)" INITIAL "" LABEL "Help Container Filename" POSITION 4 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Help container filename" ORDER 30 ADD FIELD "help_object_filename" OF "gsm_help" AS character DESCRIPTION "The optional object filename this help context is for. Specify an extension e.g. .w, but do not specify a path" FORMAT "X(70)" INITIAL "" LABEL "Help Object Filename" POSITION 5 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Help object filename" ORDER 40 ADD FIELD "help_fieldname" OF "gsm_help" AS character DESCRIPTION "The optional fieldname this help context is for. If specified, the fieldname must be entered as tablename.fieldname. " FORMAT "X(70)" INITIAL "" LABEL "Help Fieldname" POSITION 6 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Help fieldname" ORDER 50 ADD FIELD "help_context" OF "gsm_help" AS character DESCRIPTION "The help context which is the index into the specified help file. If text is specified, then this is used as a partial-key, else it is assumed to be a context number." FORMAT "X(70)" INITIAL "" LABEL "Help Context" POSITION 7 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Help context" ORDER 70 ADD FIELD "language_obj" OF "gsm_help" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Language Obj" POSITION 8 SQL-WIDTH 21 VALMSG "o_obj" HELP "Language obj" DECIMALS 6 ORDER 60 ADD INDEX "XPKgsm_help" ON "gsm_help" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "help_obj" ASCENDING ADD INDEX "XAK1gsm_help" ON "gsm_help" AREA "Schema Area" UNIQUE INDEX-FIELD "help_container_filename" ASCENDING INDEX-FIELD "help_object_filename" ASCENDING INDEX-FIELD "help_fieldname" ASCENDING INDEX-FIELD "language_obj" ASCENDING ADD INDEX "XIE1gsm_help" ON "gsm_help" AREA "Schema Area" INDEX-FIELD "language_obj" ASCENDING INDEX-FIELD "help_container_filename" ASCENDING INDEX-FIELD "help_object_filename" ASCENDING INDEX-FIELD "help_fieldname" ASCENDING ADD INDEX "XIE2gsm_help" ON "gsm_help" AREA "Schema Area" INDEX-FIELD "help_context" ASCENDING ADD TABLE "gsc_error" AREA "Schema Area" DESCRIPTION "This table defines all the application errors that can occur, together with summary and full descriptions. The summary description will be shown first, with an option to display a fuller description if available. The use of error codes from this table facilitates the customisation of error messages. This table now supports any kind of message to the user. No messages should be hard coded in the application at all, every message to the user should be channelled through here. Supported message types are: MES = Message INF = Information ERR = Error WAR = Warning QUE = Question The default is ERR for Error if nothing is set-up. Errors in multiple langages are also supported if required. " DUMP-NAME "gscer" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscertrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscertrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscerreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscerrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscerreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscertrigw.p" CRC "?" ADD FIELD "error_obj" OF "gsc_error" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Error Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Error obj" DECIMALS 6 ORDER 60 ADD FIELD "error_group" OF "gsc_error" AS character DESCRIPTION "A group code for this error. A sample use of this could be to group errors by application, e.g. ""ICF"" for ICF Framework error, ""RV"" for ICF Repository Version errors, etc." FORMAT "X(3)" INITIAL "" LABEL "Error Group" POSITION 3 SQL-WIDTH 6 VALMSG "s_mnemonic" HELP "Error group" ORDER 10 ADD FIELD "error_number" OF "gsc_error" AS integer DESCRIPTION "A unique number within error group to identify the error." FORMAT "->>>>>>>9" INITIAL "0" LABEL "Error Number" POSITION 4 SQL-WIDTH 4 VALMSG "n_integer_8" HELP "Error number" ORDER 20 ADD FIELD "language_obj" OF "gsc_error" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Language Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Language obj" DECIMALS 6 ORDER 30 ADD FIELD "error_summary_description" OF "gsc_error" AS character DESCRIPTION "A brief description of the error." FORMAT "X(70)" INITIAL "" LABEL "Error Summary Description" POSITION 6 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Error summary description" ORDER 40 ADD FIELD "error_full_description" OF "gsc_error" AS character DESCRIPTION "A full description of the error." FORMAT "X(3000)" INITIAL "" LABEL "Error Full Description" POSITION 7 SQL-WIDTH 6000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL LARGE MAX-CHARS 3000" VALMSG "s_big_text_block" HELP "Error full description" ORDER 50 ADD FIELD "update_error_log" OF "gsc_error" AS logical DESCRIPTION "If set to YES, then whenever this error occurs, it will always be written to the error log. In business logic run on the server, errors will be written to the error log regardless of this setting. The setting is only used for client side on-line processing." FORMAT "YES/NO" INITIAL "NO" LABEL "Update Error Log" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Update error log" ORDER 70 ADD FIELD "error_type" OF "gsc_error" AS character DESCRIPTION "This indicates the type of error and how to display the error to the user. Supported message types are: MES = Message INF = Information ERR = Error WAR = Warning QUE = Question The default is ERR for Error if nothing is set-up." FORMAT "X(3)" INITIAL "" LABEL "Error Type" POSITION 9 SQL-WIDTH 6 VALMSG "s_tla" HELP "Error type" ORDER 80 ADD INDEX "XPKgsc_error" ON "gsc_error" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "error_group" ASCENDING INDEX-FIELD "error_number" ASCENDING INDEX-FIELD "language_obj" ASCENDING ADD INDEX "XAK1gsc_error" ON "gsc_error" AREA "Schema Area" UNIQUE INDEX-FIELD "error_obj" ASCENDING ADD INDEX "XIE1gsc_error" ON "gsc_error" AREA "Schema Area" INDEX-FIELD "error_group" ASCENDING INDEX-FIELD "error_summary_description" ASCENDING ADD INDEX "XIE2gsc_error" ON "gsc_error" AREA "Schema Area" INDEX-FIELD "language_obj" ASCENDING INDEX-FIELD "error_group" ASCENDING INDEX-FIELD "error_number" ASCENDING ADD INDEX "XIE3gsc_error" ON "gsc_error" AREA "Schema Area" INDEX-FIELD "error_type" ASCENDING INDEX-FIELD "error_group" ASCENDING INDEX-FIELD "error_number" ASCENDING ADD INDEX "XIE4gsc_error" ON "gsc_error" AREA "Schema Area" INDEX-FIELD "language_obj" ASCENDING INDEX-FIELD "error_type" ASCENDING INDEX-FIELD "error_group" ASCENDING INDEX-FIELD "error_number" ASCENDING ADD TABLE "gsc_security_control" AREA "Schema Area" DESCRIPTION "Extra control information pertinent to security settings. This table will actually only contain a single record." DUMP-NAME "gscsc" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscsctrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscsctrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscsctrigw.p" CRC "?" ADD FIELD "security_control_obj" OF "gsc_security_control" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Security Control Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Security control obj" DECIMALS 6 ORDER 10 ADD FIELD "password_max_retries" OF "gsc_security_control" AS integer DESCRIPTION "The maximum number of times the user can get their password wrong before their account is disabled." FORMAT "->>9" INITIAL "0" LABEL "Password Max. Retries" POSITION 3 SQL-WIDTH 4 VALMSG "n_integer_3" HELP "Password max. retries" ORDER 20 ADD FIELD "password_history_life_time" OF "gsc_security_control" AS integer DESCRIPTION "the number of days to keep and check the password history, default would be 365 for a full year. This would prevent users from using the same password in the same year." FORMAT "->>>>>9" INITIAL "0" LABEL "Password History Life Time" POSITION 4 SQL-WIDTH 4 VALMSG "n_integer_6" HELP "Password history life time" ORDER 30 ADD FIELD "full_access_by_default" OF "gsc_security_control" AS logical DESCRIPTION "If set to YES, the user is granted access to everything by default, and only revoked access specifically. If set to NO, the user has access to nothing except what is specifically allocated to them." FORMAT "YES/NO" INITIAL "YES" LABEL "Full Access by Default" POSITION 5 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Full access by default" ORDER 40 ADD FIELD "security_enabled" OF "gsc_security_control" AS logical DESCRIPTION "If set to NO, all security checks will be turned off." FORMAT "YES/NO" INITIAL "YES" LABEL "Security Enabled" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Security enabled" ORDER 50 ADD FIELD "help_writer_enabled" OF "gsc_security_control" AS logical DESCRIPTION "If set to YES, then assistance with context help writing will be activated." FORMAT "YES/NO" INITIAL "NO" LABEL "Help Writer Enabled" POSITION 7 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Help writer enabled" ORDER 60 ADD FIELD "build_top_menus_only" OF "gsc_security_control" AS logical DESCRIPTION "I set to YES, only top level menus will be built initially, and sub-menus built on menudrop events." FORMAT "YES/NO" INITIAL "YES" LABEL "Build Top Menus Only" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Build top menus only" ORDER 70 ADD FIELD "default_help_filename" OF "gsc_security_control" AS character DESCRIPTION "The name of the default help file for the system" FORMAT "X(70)" INITIAL "" LABEL "Default Help Filename" POSITION 9 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Default help filename" ORDER 80 ADD FIELD "error_log_filename" OF "gsc_security_control" AS character FORMAT "X(70)" INITIAL "" LABEL "Error Log Filename" POSITION 10 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Error log filename" ORDER 90 ADD FIELD "translation_enabled" OF "gsc_security_control" AS logical DESCRIPTION "If set to YES, widget label language translation is turned on. Translations are defined in the table gsm_translation" FORMAT "YES/NO" INITIAL "NO" LABEL "Translation Enabled" POSITION 11 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Translation enabled" ORDER 100 ADD FIELD "login_filename" OF "gsc_security_control" AS character DESCRIPTION "The name of the login program to run" FORMAT "X(70)" INITIAL "" LABEL "Login Filename" POSITION 12 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Login filename" ORDER 110 ADD FIELD "multi_user_check" OF "gsc_security_control" AS logical DESCRIPTION "If set to YES, turns on functionality that checks if a user is already logged in via share lock on gst_lock table." FORMAT "YES/NO" INITIAL "YES" LABEL "Multi User Check" POSITION 13 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Multi user check" ORDER 120 ADD FIELD "program_access_check" OF "gsc_security_control" AS logical DESCRIPTION "If set to YES, turns on functionality that checks if a user is already running a program via share lock on gst_lock table." FORMAT "YES/NO" INITIAL "YES" LABEL "Program Access Check" POSITION 14 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Program access check" ORDER 130 ADD FIELD "minimise_siblings" OF "gsc_security_control" AS logical DESCRIPTION "If set to YES, turns on functionality that also minimises all child windows of an object controller or menu controller window. " FORMAT "YES/NO" INITIAL "YES" LABEL "Minimise Siblings" POSITION 15 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Minimise siblings" ORDER 140 ADD FIELD "enable_window_positioning" OF "gsc_security_control" AS logical DESCRIPTION "If set to YES, turns on functionality that enables the saving of window positions by user." FORMAT "YES/NO" INITIAL "YES" LABEL "Enable Window Positioning" POSITION 16 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Enable window positioning" ORDER 150 ADD FIELD "force_unique_password" OF "gsc_security_control" AS logical DESCRIPTION "If set to YES, passwords allocated to users must be unique. This will allow the entry of a password to locate the user record the password belongs to, avoiding having to ensure a user name and a password." FORMAT "YES/NO" INITIAL "NO" LABEL "Force Unique Password" POSITION 17 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Force unique password" ORDER 160 ADD FIELD "company_logo_filename" OF "gsc_security_control" AS character DESCRIPTION "The filename and relative path of the company logo to display on the help about window, etc." FORMAT "X(70)" INITIAL "" LABEL "Company Logo Filename" POSITION 18 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Company logo filename" ORDER 170 ADD FIELD "system_icon_filename" OF "gsc_security_control" AS character DESCRIPTION "The filename and relative path of the system icon to load for all windows." FORMAT "X(70)" INITIAL "" LABEL "System Icon Filename" POSITION 19 SQL-WIDTH 140 VALMSG "s_file_name" HELP "System icon filename" ORDER 180 ADD FIELD "small_icon_filename" OF "gsc_security_control" AS character DESCRIPTION "The filename and relative path of the small system icon to load for all windows." FORMAT "X(70)" INITIAL "" LABEL "Small Icon Filename" POSITION 20 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Small icon filename" ORDER 190 ADD FIELD "product_logo_filename" OF "gsc_security_control" AS character DESCRIPTION "The filename and relative path of the product logo to display on the help about window, etc." FORMAT "X(70)" INITIAL "" LABEL "Product Logo Filename" POSITION 21 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Product logo filename" ORDER 200 ADD FIELD "scm_checks_on" OF "gsc_security_control" AS logical DESCRIPTION "If set to yes, this field indicates that all the SCM checks built into the framework are active. If set to no, the SCM checks are ignored." FORMAT "YES/NO" INITIAL "YES" LABEL "Scm Checks On" POSITION 22 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Scm checks on" ORDER 210 ADD FIELD "scm_tool_code" OF "gsc_security_control" AS character DESCRIPTION "The name of the SCM tool in use if any, e.g. RTB for Roundtable." FORMAT "X(35)" INITIAL "" LABEL "Scm Tool Code" POSITION 23 SQL-WIDTH 70 VALMSG "s_name" HELP "Scm tool code" ORDER 220 ADD INDEX "XPKgsc_security_control" ON "gsc_security_control" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "security_control_obj" ASCENDING ADD TABLE "gst_password_history" AREA "Schema Area" DESCRIPTION "This table keeps a history of previous passwords used by users. It is used for audit purposes, and preventing users using the same password within a given time period, e.g. 1 year." DUMP-NAME "gstph" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gstphtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gstphtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gstphtrigw.p" CRC "?" ADD FIELD "password_history_obj" OF "gst_password_history" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Password History Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Password history obj" DECIMALS 6 ORDER 10 ADD FIELD "user_obj" OF "gst_password_history" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "User Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "User obj" DECIMALS 6 ORDER 20 ADD FIELD "old_password" OF "gst_password_history" AS character DESCRIPTION "The old password prior to the change - encrypted." FORMAT "X(35)" INITIAL "" LABEL "Old Password" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Old password" ORDER 30 ADD FIELD "password_change_date" OF "gst_password_history" AS date FORMAT "99/99/9999" INITIAL "TODAY" LABEL "Password Change Date" POSITION 5 SQL-WIDTH 4 VALMSG "d_date_today" HELP "Password change date" ORDER 40 ADD FIELD "password_change_time" OF "gst_password_history" AS integer FORMAT ">>>>9" INITIAL "0" LABEL "Password Change Time" POSITION 6 SQL-WIDTH 4 VALMSG "n_time" HELP "Password change time" ORDER 50 ADD FIELD "changed_by_user_obj" OF "gst_password_history" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Changed by User Obj" POSITION 7 SQL-WIDTH 21 VALMSG "o_obj" HELP "Changed by user obj" DECIMALS 6 ORDER 60 ADD INDEX "XPKgst_password_history" ON "gst_password_history" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "password_history_obj" ASCENDING ADD INDEX "XAK1gst_password_history" ON "gst_password_history" AREA "Schema Area" UNIQUE INDEX-FIELD "user_obj" ASCENDING INDEX-FIELD "old_password" ASCENDING INDEX-FIELD "password_change_date" ASCENDING INDEX-FIELD "password_change_time" ASCENDING ADD INDEX "XIE1gst_password_history" ON "gst_password_history" AREA "Schema Area" INDEX-FIELD "user_obj" ASCENDING INDEX-FIELD "password_change_date" ASCENDING INDEX-FIELD "password_change_time" ASCENDING ADD TABLE "gst_batch_job" AREA "Schema Area" DESCRIPTION "A job can be run immediately or at a user selected time in which case it is stored as a batch job. A daemon will monitor this table and initiate the jobs at the selected time. The batch_job_procedure_name may be the same as a report_procedure_name, or it may be for a separate procedure that initiates a number of separate procedures. These may or may not be report_procedure_name's. Parameters for the batch job will be stored as per those for the report definition." DUMP-NAME "gstbt" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gstbttrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gstbttrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gstbttrigw.p" CRC "?" ADD FIELD "batch_job_obj" OF "gst_batch_job" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Batch Job Obj" POSITION 2 SQL-WIDTH 15 VALMSG "o_obj" HELP "Batch job obj" ORDER 10 ADD FIELD "job_description" OF "gst_batch_job" AS character DESCRIPTION "A full description of the batch job" FORMAT "X(35)" INITIAL "" LABEL "Job Description" POSITION 3 SQL-WIDTH 70 VALMSG "s_description" HELP "Job description" ORDER 20 ADD FIELD "status_obj" OF "gst_batch_job" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Status Obj" POSITION 4 SQL-WIDTH 15 VALMSG "o_obj" HELP "Status obj" ORDER 30 ADD FIELD "batch_job_procedure_name" OF "gst_batch_job" AS character DESCRIPTION "The batch_job_procedure_name may be the same as a report_procedure_name, or it may be for a separate procedure that initiates a number of separate procedures. These may or may not be report_procedure_name's. The procedure name must be an external procedure (.p) " FORMAT "X(35)" INITIAL "" LABEL "Batch Job Procedure Name" POSITION 5 SQL-WIDTH 70 VALMSG "s_program_procedure" HELP "Batch job procedure name" ORDER 40 ADD FIELD "priority" OF "gst_batch_job" AS integer DESCRIPTION "The priority of the batch job" FORMAT "->>9" INITIAL "0" LABEL "Priority" POSITION 6 SQL-WIDTH 4 VALMSG "n_integer_3" HELP "Priority" ORDER 50 ADD FIELD "date_to_start" OF "gst_batch_job" AS date DESCRIPTION "The date the batch job is due to start." FORMAT "99/99/9999" INITIAL "?" LABEL "Date to Start" POSITION 7 SQL-WIDTH 4 VALMSG "d_start_date" HELP "Date to start" ORDER 60 ADD FIELD "time_to_start" OF "gst_batch_job" AS integer DESCRIPTION "The time the batch job is due to start." FORMAT ">>>>9" INITIAL "0" LABEL "Time to Start" POSITION 8 SQL-WIDTH 4 VALMSG "n_time" HELP "Time to start" ORDER 70 ADD FIELD "date_started" OF "gst_batch_job" AS date DESCRIPTION "The date the batch job started" FORMAT "99/99/9999" INITIAL "?" LABEL "Date Started" POSITION 9 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Date started" ORDER 80 ADD FIELD "time_started" OF "gst_batch_job" AS integer DESCRIPTION "The time the batch job started" FORMAT ">>>>9" INITIAL "0" LABEL "Time Started" POSITION 10 SQL-WIDTH 4 VALMSG "n_time" HELP "Time started" ORDER 90 ADD FIELD "date_completed" OF "gst_batch_job" AS date DESCRIPTION "The date the batch job completed" FORMAT "99/99/9999" INITIAL "?" LABEL "Date Completed" POSITION 11 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Date completed" ORDER 100 ADD FIELD "time_completed" OF "gst_batch_job" AS integer DESCRIPTION "The time the batch job completed" FORMAT ">>>>9" INITIAL "0" LABEL "Time Completed" POSITION 12 SQL-WIDTH 4 VALMSG "n_time" HELP "Time completed" ORDER 110 ADD FIELD "days_to_retain" OF "gst_batch_job" AS integer DESCRIPTION "The default days to retain extract log data in this batch" FORMAT "->>9" INITIAL "0" LABEL "Days to Retain" POSITION 13 SQL-WIDTH 4 VALMSG "n_integer_3" HELP "Days to retain" ORDER 120 ADD FIELD "user_obj" OF "gst_batch_job" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "User Obj" POSITION 14 SQL-WIDTH 15 VALMSG "o_obj" HELP "User obj" ORDER 130 ADD INDEX "XPKgst_batch_job" ON "gst_batch_job" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "batch_job_obj" ASCENDING ADD INDEX "XIE1gst_batch_job" ON "gst_batch_job" AREA "Schema Area" INDEX-FIELD "date_started" ASCENDING INDEX-FIELD "time_started" ASCENDING INDEX-FIELD "date_to_start" ASCENDING INDEX-FIELD "time_to_start" ASCENDING ADD TABLE "gst_extract_log" AREA "Schema Area" DESCRIPTION "Each time a data extract report is run, an entry is created in this file. The main intention is to track the completion of extract procedures so that report formatting procedures can be initiated where required. In the event that an extract log record is deleted, then any document produced records associated with the extract should be cascade deleted, providing that the print date has not been set - in order to tidy up the data." DUMP-NAME "gstel" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsteltrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsteltrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsteltrigw.p" CRC "?" ADD FIELD "extract_log_obj" OF "gst_extract_log" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Extract Log Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Extract log obj" DECIMALS 6 ORDER 10 ADD FIELD "data_file_name" OF "gst_extract_log" AS character DESCRIPTION "The name of the data file created. This will be created using date and time information, and will reside in a user defined spool directory defined in the gsc_global_default table. Some reports require multiple data files, in which case this will be a comma separated list of data file names." FORMAT "X(500)" INITIAL "" LABEL "Data File Name" POSITION 3 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Data file name" ORDER 20 ADD FIELD "destination" OF "gst_extract_log" AS character DESCRIPTION "The printer destination. If blank will go to the default printer." FORMAT "X(35)" INITIAL "" LABEL "Destination" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Destination" ORDER 40 ADD FIELD "extract_sequence" OF "gst_extract_log" AS integer DESCRIPTION "This should be printed on the report so that it can be recognised that a report is missing. It is taken from the next_extract_sequence on the report definition table " FORMAT "->>>>>>>9" INITIAL "0" LABEL "Extract Sequence" POSITION 5 SQL-WIDTH 4 COLUMN-LABEL "Extract Seq." VALMSG "n_sequence" HELP "Extract sequence" ORDER 30 ADD FIELD "form_type" OF "gst_extract_log" AS character DESCRIPTION "The form type if required and different to the default." FORMAT "X(10)" INITIAL "" LABEL "Form Type" POSITION 6 SQL-WIDTH 20 VALMSG "s_string_10" HELP "Form type" ORDER 50 ADD FIELD "priority" OF "gst_extract_log" AS integer DESCRIPTION "The priority of the job" FORMAT "->>9" INITIAL "0" LABEL "Priority" POSITION 7 SQL-WIDTH 4 VALMSG "n_integer_3" HELP "Priority" ORDER 60 ADD FIELD "copies_to_print" OF "gst_extract_log" AS integer DESCRIPTION "The number of copies to print this time, defaulted from the report definition" FORMAT "->>9" INITIAL "0" LABEL "Copies to Print" POSITION 8 SQL-WIDTH 4 VALMSG "n_integer_3" HELP "Copies to print" ORDER 70 ADD FIELD "print_automatically" OF "gst_extract_log" AS logical DESCRIPTION "Should the print procedure be initiated automatically when the extract completes." FORMAT "YES/NO" INITIAL "YES" LABEL "Print Automatically" POSITION 9 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Print automatically" ORDER 80 ADD FIELD "created_on_date" OF "gst_extract_log" AS date DESCRIPTION "The date the extract was run." FORMAT "99/99/9999" INITIAL "TODAY" LABEL "Created On Date" POSITION 10 SQL-WIDTH 4 VALMSG "d_date_today" HELP "Created on date" ORDER 90 ADD FIELD "printed_date" OF "gst_extract_log" AS date DESCRIPTION "The date the report was first printed." FORMAT "99/99/9999" INITIAL "?" LABEL "Printed Date" POSITION 11 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Printed date" ORDER 110 ADD FIELD "created_at_time" OF "gst_extract_log" AS integer DESCRIPTION "The timethe extract was run." FORMAT ">>>>9" INITIAL "0" LABEL "Created at Time" POSITION 12 SQL-WIDTH 4 VALMSG "n_time" HELP "Created at time" ORDER 100 ADD FIELD "delete_on_date" OF "gst_extract_log" AS date DESCRIPTION "The date after which this report data should be deleted by an automatc archive program. This will be set automatically based on the creation date and the days to retain as set-up on the report definition table." FORMAT "99/99/9999" INITIAL "?" LABEL "Delete On Date" POSITION 13 SQL-WIDTH 4 VALMSG "d_end_date" HELP "Delete on date" ORDER 150 ADD FIELD "printed_time" OF "gst_extract_log" AS integer DESCRIPTION "The time the report was first printed." FORMAT ">>>>9" INITIAL "0" LABEL "Printed Time" POSITION 14 SQL-WIDTH 4 VALMSG "n_time" HELP "Printed time" ORDER 120 ADD FIELD "last_printed_date" OF "gst_extract_log" AS date DESCRIPTION "The date the report was last printed from this extracted data. If different to the printed date then it is a reprint." FORMAT "99/99/9999" INITIAL "?" LABEL "Last Printed Date" POSITION 15 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Last printed date" ORDER 130 ADD FIELD "report_definition_obj" OF "gst_extract_log" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Report Definition Obj" POSITION 16 SQL-WIDTH 15 VALMSG "o_obj" HELP "Report definition obj" ORDER 160 ADD FIELD "user_obj" OF "gst_extract_log" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "User Obj" POSITION 17 SQL-WIDTH 15 VALMSG "o_obj" HELP "User obj" ORDER 170 ADD FIELD "last_printed_time" OF "gst_extract_log" AS integer DESCRIPTION "The time the report was last printed from this extracted data. If different to the printed time then it is a reprint." FORMAT ">>>>9" INITIAL "0" LABEL "Last Printed Time" POSITION 18 SQL-WIDTH 4 VALMSG "n_time" HELP "Last printed time" ORDER 140 ADD FIELD "batch_job_obj" OF "gst_extract_log" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Batch Job Obj" POSITION 19 SQL-WIDTH 15 VALMSG "o_obj" HELP "Batch job obj" ORDER 180 ADD FIELD "extract_log_password" OF "gst_extract_log" AS character DESCRIPTION "The use of an extract log password is optional dependant on the report definition settings. If an extract log password is specified, then the encoded value will be stored in this field. The first time the report is printed from this extract log, the password will not be required. Subsequent reprints will not be permitted until the correct password is entered. This prevents the unauthorised reprinting of reports from previously extracted data." FORMAT "X(35)" INITIAL "" LABEL "Extract Log Password" POSITION 20 SQL-WIDTH 70 VALMSG "s_description" HELP "Extract log password" ORDER 190 ADD FIELD "data_file_encrypted" OF "gst_extract_log" AS logical DESCRIPTION "If set to YES, then the text files containing the extracted data have been encrypted, and must be decrypted before being passed to the report tool, e.g. Crystal Reports. The report definition settings determine whether the data files need to be encrypted. " FORMAT "YES/NO" INITIAL "NO" LABEL "Data File Encrypted" POSITION 21 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Data file encrypted" ORDER 200 ADD FIELD "auto_delete_extract" OF "gst_extract_log" AS logical DESCRIPTION "If set to YES, then this extract log and associated data files will be deleted after initial printing. The setting of this flag is dependnat on report definition options." FORMAT "YES/NO" INITIAL "NO" LABEL "Auto Delete Extract" POSITION 22 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Auto delete extract" ORDER 210 ADD FIELD "extract_log_description" OF "gst_extract_log" AS character DESCRIPTION "This is a free text narration for the extract log to help explain what the extracted data is. It will default to the report description but may be overridden. This field will help identify an extract to reprint." FORMAT "X(35)" INITIAL "" LABEL "Extract Log Description" POSITION 23 SQL-WIDTH 70 VALMSG "s_description" HELP "Extract log description" ORDER 220 ADD INDEX "XPKgst_extract_log" ON "gst_extract_log" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "extract_log_obj" ASCENDING ADD INDEX "XIE1gst_extract_log" ON "gst_extract_log" AREA "Schema Area" INDEX-FIELD "report_definition_obj" ASCENDING INDEX-FIELD "created_on_date" ASCENDING INDEX-FIELD "created_at_time" ASCENDING ADD INDEX "XIE2gst_extract_log" ON "gst_extract_log" AREA "Schema Area" INDEX-FIELD "report_definition_obj" ASCENDING INDEX-FIELD "printed_date" ASCENDING INDEX-FIELD "printed_time" ASCENDING ADD INDEX "XIE3gst_extract_log" ON "gst_extract_log" AREA "Schema Area" INDEX-FIELD "batch_job_obj" ASCENDING INDEX-FIELD "created_on_date" ASCENDING INDEX-FIELD "created_at_time" ASCENDING ADD INDEX "XIE4gst_extract_log" ON "gst_extract_log" AREA "Schema Area" INDEX-FIELD "user_obj" ASCENDING INDEX-FIELD "created_on_date" ASCENDING INDEX-FIELD "created_at_time" ASCENDING ADD INDEX "XIE5gst_extract_log" ON "gst_extract_log" AREA "Schema Area" INDEX-FIELD "delete_on_date" ASCENDING ADD TABLE "gst_error_log" AREA "Schema Area" DESCRIPTION "This table holds a list of errors generated either from business logic or user interface code. The table will be periodically archived to ensure it does not get too huge. The data in the table will be fed direct from the user interface, and periodically fed by the business logic error file which will be a flat file due to the fact that we cannot write direct to this table as the write would form part of the transaction being undone.." DUMP-NAME "gster" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gstertrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gstertrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gstertrigw.p" CRC "?" ADD FIELD "error_log_obj" OF "gst_error_log" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Error Log Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Error log obj" DECIMALS 6 ORDER 10 ADD FIELD "business_logic_error" OF "gst_error_log" AS logical DESCRIPTION "If set to YES, this error was created by a business logic routine. If set to NO, the error originated from a user interface routine." FORMAT "YES/NO" INITIAL "NO" LABEL "Business Logic Error" POSITION 3 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Business logic error" ORDER 20 ADD FIELD "error_group" OF "gst_error_log" AS character DESCRIPTION "A group code for this error, e.g. the application could be used e.g. RV for ICF Repository Version" FORMAT "X(3)" INITIAL "" LABEL "Error Group" POSITION 4 SQL-WIDTH 6 VALMSG "s_mnemonic" HELP "Error group" ORDER 30 ADD FIELD "error_number" OF "gst_error_log" AS integer DESCRIPTION "A unique number within error group to identify the error." FORMAT "->>>>>>>9" INITIAL "0" LABEL "Error Number" POSITION 5 SQL-WIDTH 4 VALMSG "n_integer_8" HELP "Error number" ORDER 40 ADD FIELD "error_message" OF "gst_error_log" AS character DESCRIPTION "The actual text of the error message, complete with insertion codes expanded." FORMAT "X(70)" INITIAL "" LABEL "Error Message" POSITION 6 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Error message" ORDER 50 ADD FIELD "user_obj" OF "gst_error_log" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "User Obj" POSITION 7 SQL-WIDTH 21 VALMSG "o_obj" HELP "User obj" DECIMALS 6 ORDER 60 ADD FIELD "error_date" OF "gst_error_log" AS date FORMAT "99/99/9999" INITIAL "TODAY" LABEL "Error Date" POSITION 8 SQL-WIDTH 4 VALMSG "d_date_today" HELP "Error date" ORDER 70 ADD FIELD "error_time" OF "gst_error_log" AS integer FORMAT ">>>>9" INITIAL "0" LABEL "Error Time" POSITION 9 SQL-WIDTH 4 VALMSG "n_time" HELP "Error time" ORDER 80 ADD FIELD "error_in_program" OF "gst_error_log" AS character DESCRIPTION "The program name the error occurred in / was raised in." FORMAT "X(70)" INITIAL "" LABEL "Error in Program" POSITION 10 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Error in program" ORDER 90 ADD FIELD "owning_entity_mnemonic" OF "gst_error_log" AS character DESCRIPTION "The entity mnemonic of the entity that generated this error log record. This could either point at the audit table, or the actual table that is in error." FORMAT "X(8)" INITIAL "" LABEL "Owning Entity Mnemonic" POSITION 11 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Owning entity mnemonic" ORDER 100 ADD FIELD "owning_obj" OF "gst_error_log" AS decimal DESCRIPTION "The object number of the entity that generated this error log record. This could either point at the audit table record, or the actual table record that is in error." FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Owning Obj" POSITION 12 SQL-WIDTH 21 VALMSG "o_obj" HELP "Owning obj" DECIMALS 6 ORDER 110 ADD INDEX "XPKgst_error_log" ON "gst_error_log" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "error_log_obj" ASCENDING ADD INDEX "XAK1gst_error_log" ON "gst_error_log" AREA "Schema Area" UNIQUE INDEX-FIELD "error_group" ASCENDING INDEX-FIELD "error_number" ASCENDING INDEX-FIELD "error_log_obj" ASCENDING ADD INDEX "XIE1gst_error_log" ON "gst_error_log" AREA "Schema Area" INDEX-FIELD "error_date" ASCENDING INDEX-FIELD "error_time" ASCENDING ADD INDEX "XIE2gst_error_log" ON "gst_error_log" AREA "Schema Area" INDEX-FIELD "error_in_program" ASCENDING INDEX-FIELD "error_date" ASCENDING INDEX-FIELD "error_time" ASCENDING ADD TABLE "gsc_global_default" AREA "Schema Area" DESCRIPTION "This table contains global default values across the entire application. It differes from the parameter file in that the parameter file is specific to a user, whereas entries in this table are system wide. Standard entries exist in the gsc_global_control table. This table facilitates the generic addition of other defaults without the need for database change. The entries in this table will be system owned by ther nature, and the only fields that may change are the owning_obj and the default_value. The changing of any of these values will create a new record for the owning_entity_mnemonic and default_type, efffective as of the new date with the new values. Entries may not therefore be deleted from this table, other than by a system administrator." DUMP-NAME "gscgd" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscgdtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscgdtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscgdtrigw.p" CRC "?" ADD FIELD "global_default_obj" OF "gsc_global_default" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Global Default Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Global default obj" DECIMALS 6 ORDER 10 ADD FIELD "owning_entity_mnemonic" OF "gsc_global_default" AS character DESCRIPTION "The hard coded entity mnemonic this global default is for, i.e. the table the default relates to. For example, if this was a default gsc_custom_procedure, then this would be gsccp and the owing_obj would be a cutom_procedure_obj" FORMAT "X(8)" INITIAL "" LABEL "Owning Entity Mnemonic" POSITION 3 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Owning entity mnemonic" ORDER 20 ADD FIELD "default_type" OF "gsc_global_default" AS character DESCRIPTION "A hard coded TLA to allow multiple defaults for a single table. For example, to allow many default custom procedures of different types, e.g. eft custom procedures, interest custom procedures, etc." FORMAT "X(3)" INITIAL "" LABEL "Default Type" POSITION 4 SQL-WIDTH 6 VALMSG "s_type" HELP "Default type" ORDER 30 ADD FIELD "effective_date" OF "gsc_global_default" AS date DESCRIPTION "Any alterations to this record will necessitate the creation of a new record in order to retain a history of the global control information. This field contains the date from which this data is effective." FORMAT "99/99/9999" INITIAL "?" LABEL "Effective Date" POSITION 5 SQL-WIDTH 4 VALMSG "d_start_date" HELP "Effective date" ORDER 40 ADD FIELD "owning_obj" OF "gsc_global_default" AS decimal DESCRIPTION "This is the object number the default is for, and will depend on the value of the owning_entity_mnemonic. For example, if the owning_enity_mnemonic is gsccp, then the owning_obj will point to a custom_procedure_obj.." FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Owning Obj" POSITION 6 SQL-WIDTH 21 VALMSG "o_obj" HELP "Owning obj" DECIMALS 6 ORDER 50 ADD FIELD "default_value" OF "gsc_global_default" AS character DESCRIPTION "If the default is simply a value, rather than pointing at a specific record with an object number, then this field will contain the default value. If multiple values are to be used, then these will be in a comma delimited list. The use of the default value will be hard coded dependant on the owning_entity_mnemonic and the default_type." FORMAT "X(70)" INITIAL "" LABEL "Default Value" POSITION 7 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Default value" ORDER 60 ADD INDEX "XPKgsc_global_default" ON "gsc_global_default" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "global_default_obj" ASCENDING ADD INDEX "XAK1gsc_global_default" ON "gsc_global_default" AREA "Schema Area" UNIQUE INDEX-FIELD "owning_entity_mnemonic" ASCENDING INDEX-FIELD "owning_obj" ASCENDING INDEX-FIELD "default_type" ASCENDING INDEX-FIELD "effective_date" ASCENDING ADD TABLE "gsm_external_xref" AREA "Schema Area" DESCRIPTION "This table defines generic cross reference information to details in external tables. For example, an organisation whose accounts are held in this database, may have other account codes in an external database where these account codes originated from. This table could be used to define which internal accounts point to which external accounts for xref and reporting purposes. In this example, the fields would be setup as follows: related entity = The gsm_organisation table in this database related object = Specific organisations Internal entity = The gsm_account table in this database internal object = specific account codes If an external table is available, then the external entity and object can be defined, otherwise the external details can be keyed directly into this table. " DUMP-NAME "gsmex" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmextrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmextrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmextrigw.p" CRC "?" ADD FIELD "related_entity_mnemonic" OF "gsm_external_xref" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Related Entity Mnemonic" POSITION 2 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Related entity mnemonic" ORDER 10 ADD FIELD "related_owning_obj" OF "gsm_external_xref" AS decimal DESCRIPTION "The entity this xref is for. This will probably be an organisation or a person." FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Related Owning Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Related owning obj" DECIMALS 6 ORDER 20 ADD FIELD "internal_entity_mnemonic" OF "gsm_external_xref" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Internal Entity Mnemonic" POSITION 4 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Internal entity mnemonic" ORDER 30 ADD FIELD "internal_owning_obj" OF "gsm_external_xref" AS decimal DESCRIPTION "The interal entity the xref is for, e.g. an account" FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Internal Owning Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Internal owning obj" DECIMALS 6 ORDER 40 ADD FIELD "external_entity_mnemonic" OF "gsm_external_xref" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "External Entity Mnemonic" POSITION 6 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "External entity mnemonic" ORDER 60 ADD FIELD "external_owning_obj" OF "gsm_external_xref" AS decimal DESCRIPTION "The external entity the xref is for, e.g. an account in another database. This is optional as the external details can be keyed directly into this table." FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "External Owning Obj" POSITION 7 SQL-WIDTH 21 VALMSG "o_obj" HELP "External owning obj" DECIMALS 6 ORDER 70 ADD FIELD "external_code" OF "gsm_external_xref" AS character DESCRIPTION "The external reference from the external table that relates to the internal details pointed at by the internal owning obj." FORMAT "X(20)" INITIAL "" LABEL "External Code" POSITION 8 SQL-WIDTH 40 VALMSG "s_string_20" HELP "External code" ORDER 80 ADD FIELD "external_description" OF "gsm_external_xref" AS character DESCRIPTION "The external description from the external table that relates to the internal details pointed at by the internal owning obj." FORMAT "X(35)" INITIAL "" LABEL "External Description" POSITION 9 SQL-WIDTH 70 VALMSG "s_description" HELP "External description" ORDER 90 ADD FIELD "external_details" OF "gsm_external_xref" AS character DESCRIPTION "Other external details from the external table that relates to the internal details pointed at by the internal owning obj. This is an additional field for application specific purposes. It could contain a delimited list of many other field values if required." FORMAT "X(500)" INITIAL "" LABEL "External Details" POSITION 10 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "External details" ORDER 100 ADD FIELD "external_xref_obj" OF "gsm_external_xref" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "External Xref Obj" POSITION 11 SQL-WIDTH 21 VALMSG "o_obj" HELP "External xref obj" DECIMALS 6 ORDER 50 ADD INDEX "XPKgsm_external_xref" ON "gsm_external_xref" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "related_entity_mnemonic" ASCENDING INDEX-FIELD "related_owning_obj" ASCENDING INDEX-FIELD "internal_entity_mnemonic" ASCENDING INDEX-FIELD "internal_owning_obj" ASCENDING INDEX-FIELD "external_xref_obj" ASCENDING ADD INDEX "XIE1gsm_external_xref" ON "gsm_external_xref" AREA "Schema Area" INDEX-FIELD "related_entity_mnemonic" ASCENDING INDEX-FIELD "related_owning_obj" ASCENDING INDEX-FIELD "internal_entity_mnemonic" ASCENDING INDEX-FIELD "external_owning_obj" ASCENDING ADD INDEX "XIE2gsm_external_xref" ON "gsm_external_xref" AREA "Schema Area" INDEX-FIELD "related_entity_mnemonic" ASCENDING INDEX-FIELD "related_owning_obj" ASCENDING INDEX-FIELD "internal_entity_mnemonic" ASCENDING INDEX-FIELD "external_code" ASCENDING ADD INDEX "XIE3gsm_external_xref" ON "gsm_external_xref" AREA "Schema Area" INDEX-FIELD "related_entity_mnemonic" ASCENDING INDEX-FIELD "related_owning_obj" ASCENDING INDEX-FIELD "internal_entity_mnemonic" ASCENDING INDEX-FIELD "external_description" ASCENDING ADD INDEX "XIE4gsm_external_xref" ON "gsm_external_xref" AREA "Schema Area" INDEX-FIELD "related_entity_mnemonic" ASCENDING INDEX-FIELD "related_owning_obj" ASCENDING INDEX-FIELD "internal_entity_mnemonic" ASCENDING INDEX-FIELD "external_details" ASCENDING ADD INDEX "XIE5gsm_external_xref" ON "gsm_external_xref" AREA "Schema Area" INDEX-FIELD "external_entity_mnemonic" ASCENDING INDEX-FIELD "external_owning_obj" ASCENDING ADD INDEX "XIE6gsm_external_xref" ON "gsm_external_xref" AREA "Schema Area" INDEX-FIELD "external_code" ASCENDING ADD TABLE "gsm_control_code" AREA "Schema Area" DESCRIPTION "This is a generic table for holding device control codes. The category is used to define what the code is for, and the owning_obj is optionally to define the device the code relates to. If the owning_obj is left as 0, then it applies to all devices. An example use is in a point of sale system where codes must be sent to a pole for various reasons, e.g. to reset the poll, to make the message scroll, etc. Different categories would be defined for each action. The owning_entity_mnemonic on the category would determine which table the owning_obj related to. This will usually be some sort of application specific device table. " DUMP-NAME "gsmcl" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmcltrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmcltrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmcltrigw.p" CRC "?" ADD FIELD "category_obj" OF "gsm_control_code" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Category Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Category obj" DECIMALS 6 ORDER 10 ADD FIELD "owning_obj" OF "gsm_control_code" AS decimal DESCRIPTION "The owning_obj is optionally to define the device the code relates to. If the owning_obj is left as 0, then it applies to all devices. An example use is in a point of sale system where codes must be sent to a pole for various reasons, e.g. to reset the poll, to make the message scroll, etc. Different categories would be defined for each action. The owning_entity_mnemonic on the category would determine which table the owning_obj related to. This will usually be some sort of application specific device table. " FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Owning Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Owning obj" DECIMALS 6 ORDER 20 ADD FIELD "control_data" OF "gsm_control_code" AS character DESCRIPTION "The actual data to send to the device for the specified action (category)." FORMAT "X(70)" INITIAL "" LABEL "Control Data" POSITION 4 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Control data" ORDER 30 ADD FIELD "control_short_description" OF "gsm_control_code" AS character DESCRIPTION "A summary free text description of the control code data" FORMAT "X(15)" INITIAL "" LABEL "Control Short Descriptionription" POSITION 5 SQL-WIDTH 30 COLUMN-LABEL "Control Short Description" VALMSG "s_short_desc" HELP "Control short descriptionription" ORDER 40 ADD FIELD "control_description" OF "gsm_control_code" AS character DESCRIPTION "A free text explanation of the control code data." FORMAT "X(35)" INITIAL "" LABEL "Control Description" POSITION 6 SQL-WIDTH 70 VALMSG "s_description" HELP "Control description" ORDER 50 ADD FIELD "control_code_obj" OF "gsm_control_code" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Control Code Obj" POSITION 7 SQL-WIDTH 21 VALMSG "o_obj" HELP "Control code obj" DECIMALS 6 ORDER 60 ADD INDEX "XPKgsm_control_code" ON "gsm_control_code" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "category_obj" ASCENDING INDEX-FIELD "owning_obj" ASCENDING ADD INDEX "XAK1gsm_control_code" ON "gsm_control_code" AREA "Schema Area" UNIQUE INDEX-FIELD "control_code_obj" ASCENDING ADD INDEX "XIE1gsm_control_code" ON "gsm_control_code" AREA "Schema Area" INDEX-FIELD "control_description" ASCENDING ADD INDEX "XIE2gsm_control_code" ON "gsm_control_code" AREA "Schema Area" INDEX-FIELD "control_short_description" ASCENDING ADD INDEX "XIE3gsm_control_code" ON "gsm_control_code" AREA "Schema Area" INDEX-FIELD "control_data" ASCENDING ADD TABLE "gsm_site_specific" AREA "Schema Area" DESCRIPTION "This table defines data that is specific to a site or location where ICF is running, e.g. ICF, POSSE, PCS, etc. Additionally the data may be specific to a product or product module. Its use is to make certain data specific to a particular site, e.g. menu items, menu structures, report definitions, report formats, etc. specific to ICF. The data being filtered is identified by the owning entity mnemonic, and the specific reference identifies the actual item of data being filtered. It is possible to make an item of data available to many sites. If the item of data does not exist in the table, then it will be assumed the data is applicable to all sites. This table is also used to allocate which sites a specific user is associated with. In this case the entity mnemonic would be GSMUS and the specific reference would be the user login name. Examples of data that may be specific to site codes are menu items, menu structures, report definitions and report formats. For any supported tables, e.g. menu items when building menus, a check will need to be made in the site specific data table for the appropriate entity mnemonic and unique reference (e.g. menu item reference). If any records exist at all, then the site codes allocated to the user must be checked to see that the user has a matching site code. If not, the data should be skipped over as it is not relevant. This site table is in RVDB because it is not specific to any product or workspace. This table is in ICFDB because it relates to the specific product and workspace data, allowing different workspaces to support different configurations of site specific data. A standard folder with a 2 selection list viewer must be developed to allow the generic allocation of site codes for a specific item of data by passing in an instance attribute for the entity mnemonic. Also a standard api should be developed to check for the existence of data in this table and whether the user has a matching site code. To avoid checking the user site codes all the time, they should be placed into the extra user login value variables." DUMP-NAME "gsmsp" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmsptrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmsptrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmsptrigw.p" CRC "?" ADD FIELD "entity_mnemonic" OF "gsm_site_specific" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Entity Mnemonic" POSITION 2 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Entity mnemonic" ORDER 10 ADD FIELD "specific_reference" OF "gsm_site_specific" AS character DESCRIPTION "The unique reference field for the data identified by the entity mnemonic, e.g. user login name, menu structure code, menu item reference, report definition reference, report format reference, etc." FORMAT "X(15)" INITIAL "" LABEL "Specific Reference" POSITION 3 SQL-WIDTH 30 VALMSG "s_reference" HELP "Specific reference" ORDER 20 ADD FIELD "site_code" OF "gsm_site_specific" AS character DESCRIPTION "A unique code to indentify the site / location." FORMAT "X(10)" INITIAL "" LABEL "Site Code" POSITION 4 SQL-WIDTH 20 VALMSG "s_code" HELP "Site code" ORDER 30 ADD FIELD "site_specific_obj" OF "gsm_site_specific" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Site Specific Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Site specific obj" DECIMALS 6 ORDER 60 ADD FIELD "product_code" OF "gsm_site_specific" AS character DESCRIPTION "If this item of data is specific to a product this field optionally identifies a specific product code that the data belongs to. If the field is left blank, it is assumed not to be specific to a product. " FORMAT "X(10)" INITIAL "" LABEL "Product Code" POSITION 6 SQL-WIDTH 20 VALMSG "s_code" HELP "Product code" ORDER 40 ADD FIELD "product_module_code" OF "gsm_site_specific" AS character DESCRIPTION "If this item of data is specific to a product module this field optionally identifies a specific product module code that the data belongs to. If the field is left blank, it is assumed not to be specific to a product module. " FORMAT "X(10)" INITIAL "" LABEL "Product Module Code" POSITION 7 SQL-WIDTH 20 VALMSG "s_code" HELP "Product module code" ORDER 50 ADD INDEX "XPKgsm_site_specific" ON "gsm_site_specific" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "entity_mnemonic" ASCENDING INDEX-FIELD "specific_reference" ASCENDING INDEX-FIELD "site_code" ASCENDING INDEX-FIELD "product_code" ASCENDING INDEX-FIELD "product_module_code" ASCENDING ADD INDEX "XAK1gsm_site_specific" ON "gsm_site_specific" AREA "Schema Area" UNIQUE INDEX-FIELD "entity_mnemonic" ASCENDING INDEX-FIELD "site_code" ASCENDING INDEX-FIELD "specific_reference" ASCENDING ADD INDEX "XAK2gsm_site_specific" ON "gsm_site_specific" AREA "Schema Area" UNIQUE INDEX-FIELD "site_specific_obj" ASCENDING ADD INDEX "XIE1gsm_site_specific" ON "gsm_site_specific" AREA "Schema Area" INDEX-FIELD "product_code" ASCENDING ADD INDEX "XIE2gsm_site_specific" ON "gsm_site_specific" AREA "Schema Area" INDEX-FIELD "product_module_code" ASCENDING ADD TABLE "gsc_next_sequence" AREA "Schema Area" DESCRIPTION "This table is used to allocate sequence numbers where it is possible that multiple sequence numbers may be requested by multiple transactions simultaneously - it is intended to avoid deadly embrace record locks. When a gsc_sequence is created / updated with multi_transaction set to YES, number_of_sequences records are created in this table starting from gsc-sequence.next_value. When a sequence number is requested, the first record in this table for the gsc_sequence is found, saved and deleted. At the same time, a new gsc_next_sequence record is tagged on the end i.e. with the sequence number just found plus number_of_sequences." DUMP-NAME "gscsn" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscsntrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscsntrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscsntrigw.p" CRC "?" ADD FIELD "sequence_obj" OF "gsc_next_sequence" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Sequence Obj" POSITION 2 SQL-WIDTH 21 COLUMN-LABEL "Seq. Obj" VALMSG "o_obj" HELP "Sequence obj" DECIMALS 6 ORDER 10 ADD FIELD "next_sequence_obj" OF "gsc_next_sequence" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Next Sequence Obj" POSITION 3 SQL-WIDTH 21 COLUMN-LABEL "Next Seq. Obj" VALMSG "o_obj" HELP "Next. sequence obj" DECIMALS 6 ORDER 30 ADD FIELD "next_sequence_value" OF "gsc_next_sequence" AS integer DESCRIPTION "The value of the sequence. " FORMAT "->>>>>>>9" INITIAL "0" LABEL "Next Sequence Value" POSITION 4 SQL-WIDTH 4 COLUMN-LABEL "Next Seq. Value" VALMSG "n_integer_8" HELP "Next. sequence value" ORDER 20 ADD INDEX "XPKgsc_next_sequence" ON "gsc_next_sequence" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "sequence_obj" ASCENDING INDEX-FIELD "next_sequence_value" ASCENDING ADD TABLE "gsm_server_context" AREA "Schema Area" DESCRIPTION "This table is a generic table to stored context information between stateless appserver connections. The type of information that is required includes user information, security information, possibly SCM workspace and task information, etc. " DUMP-NAME "gsmsc" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmsctrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmsctrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmsctrigw.p" CRC "?" ADD FIELD "server_context_obj" OF "gsm_server_context" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Server ConText Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Server context obj" DECIMALS 6 ORDER 10 ADD FIELD "context_id" OF "gsm_server_context" AS character DESCRIPTION "A unique id to identify the session." FORMAT "X(28)" INITIAL "" LABEL "ConText Id" POSITION 3 SQL-WIDTH 56 VALMSG "s_string_28" HELP "Context id" ORDER 20 ADD FIELD "context_id_date" OF "gsm_server_context" AS date DESCRIPTION "The date the session was created." FORMAT "99/99/9999" INITIAL "TODAY" LABEL "ConText Id Date" POSITION 4 SQL-WIDTH 4 VALMSG "d_date_today" HELP "Context id date" ORDER 30 ADD FIELD "context_id_time" OF "gsm_server_context" AS integer DESCRIPTION "The time the session was created." FORMAT ">>>>9" INITIAL "0" LABEL "ConText Id Time" POSITION 5 SQL-WIDTH 4 VALMSG "n_time" HELP "Context id time" ORDER 40 ADD FIELD "context_name" OF "gsm_server_context" AS character DESCRIPTION "the name of the data required, e.g. username." FORMAT "X(35)" INITIAL "" LABEL "ConText Name" POSITION 6 SQL-WIDTH 70 VALMSG "s_name" HELP "Context name" ORDER 50 ADD FIELD "context_value" OF "gsm_server_context" AS character DESCRIPTION "the value of the data, e.g. Fred Bloggs." FORMAT "X(70)" INITIAL "" LABEL "ConText Value" POSITION 7 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Context value" ORDER 60 ADD INDEX "XPKgsm_server_context" ON "gsm_server_context" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "server_context_obj" ASCENDING ADD INDEX "XAK1gsm_server_context" ON "gsm_server_context" AREA "Schema Area" UNIQUE INDEX-FIELD "context_id" ASCENDING INDEX-FIELD "context_name" ASCENDING ADD INDEX "XIE1gsm_server_context" ON "gsm_server_context" AREA "Schema Area" INDEX-FIELD "context_id_date" ASCENDING INDEX-FIELD "context_id_time" ASCENDING INDEX-FIELD "context_id" ASCENDING ADD INDEX "XIE2gsm_server_context" ON "gsm_server_context" AREA "Schema Area" INDEX-FIELD "context_name" ASCENDING INDEX-FIELD "context_id_date" ASCENDING INDEX-FIELD "context_id_time" ASCENDING ADD TABLE "gsc_profile_type" AREA "Schema Area" DESCRIPTION "This table defines the types of profile codes supported for allocation to users. Records will exist for any type of profile information stored against a user between sessions. Examples include browser filter settings, report filter settings, Toolbar cusomisation settings, window positions and sizes, system wide settings such as tooltips on/off, etc. " DUMP-NAME "gscpf" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscpftrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscpftrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscpfreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscpfrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscpfreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscpftrigw.p" CRC "?" ADD FIELD "profile_type_obj" OF "gsc_profile_type" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Type Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile type obj" DECIMALS 6 ORDER 10 ADD FIELD "profile_type_code" OF "gsc_profile_type" AS character DESCRIPTION "A unique code to identify the profile type." FORMAT "X(10)" INITIAL "" LABEL "Profile Type Code" POSITION 3 SQL-WIDTH 20 VALMSG "s_code" HELP "Profile type code" ORDER 20 ADD FIELD "profile_type_description" OF "gsc_profile_type" AS character DESCRIPTION "A description of the profile type." FORMAT "X(35)" INITIAL "" LABEL "Profile Type Description" POSITION 4 SQL-WIDTH 70 VALMSG "s_description" HELP "Profile type description" ORDER 30 ADD FIELD "client_profile_type" OF "gsc_profile_type" AS logical DESCRIPTION "If set to YES, profile codes for this type are relevant in the client session. If the server profile type is also YES, then changes to the code value must also be replicated into the server session." FORMAT "YES/NO" INITIAL "YES" LABEL "Client Profile Type" POSITION 5 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Client profile type" ORDER 40 ADD FIELD "server_profile_type" OF "gsc_profile_type" AS logical DESCRIPTION "If set to YES, profile codes for this type are relevant in the server session. It is not posible to have server profile types only. IF this falg is set to YES, then the client flag mist also be set to YES. This flag indicates that changes to the profile values must also be replicated to the server session." FORMAT "YES/NO" INITIAL "YES" LABEL "Server Profile Type" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Server profile type" ORDER 50 ADD FIELD "profile_type_active" OF "gsc_profile_type" AS logical DESCRIPTION "IF set to NO, then use of the values against this profile will be disabled. Profiles could be turned off for performance reasons. " FORMAT "YES/NO" INITIAL "YES" LABEL "Profile Type Active" POSITION 7 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Profile type active" ORDER 60 ADD INDEX "XPKgsc_profile_type" ON "gsc_profile_type" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "profile_type_obj" ASCENDING ADD INDEX "XAK1gsc_profile_type" ON "gsc_profile_type" AREA "Schema Area" UNIQUE INDEX-FIELD "profile_type_code" ASCENDING ADD INDEX "XIE1gsc_profile_type" ON "gsc_profile_type" AREA "Schema Area" INDEX-FIELD "profile_type_description" ASCENDING ADD TABLE "gsc_profile_code" AREA "Schema Area" DESCRIPTION "This table defines the codes that exist for each profile type, and the structure of the key / data value fields when this code is allocated against a user in the gsm_profile_data table. An example profile type would be filter settings, and example profile codes for filter settings would be filter from values, filter to values, filtering enabled, filter field names, etc." DUMP-NAME "gscpc" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gscpctrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gscpctrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/gscpcreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/gscpcrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/gscpcreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gscpctrigw.p" CRC "?" ADD FIELD "profile_type_obj" OF "gsc_profile_code" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Type Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile type obj" DECIMALS 6 ORDER 10 ADD FIELD "profile_code_obj" OF "gsc_profile_code" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Code Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile code obj" DECIMALS 6 ORDER 20 ADD FIELD "profile_code" OF "gsc_profile_code" AS character DESCRIPTION "A unique code within profile type to identify the profile code." FORMAT "X(10)" INITIAL "" LABEL "Profile Code" POSITION 4 SQL-WIDTH 20 VALMSG "s_code" HELP "Profile code" ORDER 30 ADD FIELD "profile_description" OF "gsc_profile_code" AS character DESCRIPTION "A decsription of the profile code." FORMAT "X(35)" INITIAL "" LABEL "Profile Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Profile description" ORDER 40 ADD FIELD "profile_narrative" OF "gsc_profile_code" AS character DESCRIPTION "An explanation for the profile code including details of what information is stored in the data key and data value fields when the profile code is allocated to a user." FORMAT "X(500)" INITIAL "" LABEL "Profile Narrative" POSITION 6 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Profile narrative" ORDER 50 ADD INDEX "XPKgsc_profile_code" ON "gsc_profile_code" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "profile_type_obj" ASCENDING INDEX-FIELD "profile_code_obj" ASCENDING ADD INDEX "XAK1gsc_profile_code" ON "gsc_profile_code" AREA "Schema Area" UNIQUE INDEX-FIELD "profile_type_obj" ASCENDING INDEX-FIELD "profile_code" ASCENDING ADD INDEX "XAK2gsc_profile_code" ON "gsc_profile_code" AREA "Schema Area" UNIQUE INDEX-FIELD "profile_code_obj" ASCENDING ADD INDEX "XIE1gsc_profile_code" ON "gsc_profile_code" AREA "Schema Area" INDEX-FIELD "profile_type_obj" ASCENDING INDEX-FIELD "profile_description" ASCENDING ADD TABLE "gsm_profile_data" AREA "Schema Area" DESCRIPTION "This table is used to store profile information for specific users, e.g. browser filter settings, window positions and sizes, report filtter settings, etc. The nature of the data key and data value fields is determined by the profile type and code. Data can be stored permannently, or only for the current session, depending on the context_id field." DUMP-NAME "gsmpf" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gsmpftrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gsmpftrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gsmpftrigw.p" CRC "?" ADD FIELD "user_obj" OF "gsm_profile_data" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "User Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "User obj" DECIMALS 6 ORDER 10 ADD FIELD "profile_type_obj" OF "gsm_profile_data" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Type Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile type obj" DECIMALS 6 ORDER 20 ADD FIELD "profile_code_obj" OF "gsm_profile_data" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Code Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile code obj" DECIMALS 6 ORDER 30 ADD FIELD "profile_data_key" OF "gsm_profile_data" AS character DESCRIPTION "This is the key to identify the profile data for the user for this profile type and code. The structure of the key is dependant on the profile code. For example, if the profile code was relating to browser filter from settings, then the key would indicate.the container and browser that these filter settings were for." FORMAT "X(70)" INITIAL "" LABEL "Profile Data Key" POSITION 5 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Profile data key" ORDER 40 ADD FIELD "context_id" OF "gsm_profile_data" AS character DESCRIPTION "A unique id to identify the session. If on the server, this would be the session connection id and if on the client will be allocated from a session progress sequence that wraps. This is used so that profile data can be stored for the current session only. If this field is blank, then the profile data is stored permanently. Session specific profile data will be deleted from the file when the session ends. This field is part of the primary key to facilitate a single user having multiple concurrent sessions with different temporary profile data. " FORMAT "X(28)" INITIAL "" LABEL "ConText Id" POSITION 6 SQL-WIDTH 56 VALMSG "s_string_28" HELP "Context id" ORDER 50 ADD FIELD "profile_data_value" OF "gsm_profile_data" AS character DESCRIPTION "This is the actual value of the profile for the user / profile type / profile code / profile key value. The structure of the value is dependant on the profile code. For example, if the profile code was relating to browser filter from settings, then the key would indicate.the container and browser that these filter settings were for, and the value would indicate the actual filter from values for each of the filtered fields. " FORMAT "X(500)" INITIAL "" LABEL "Profile Data Value" POSITION 7 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Profile data value" ORDER 60 ADD FIELD "profile_data_obj" OF "gsm_profile_data" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Profile Data Obj" POSITION 8 SQL-WIDTH 21 VALMSG "o_obj" HELP "Profile data obj" DECIMALS 6 ORDER 70 ADD INDEX "XPKgsm_profile_data" ON "gsm_profile_data" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "user_obj" ASCENDING INDEX-FIELD "profile_type_obj" ASCENDING INDEX-FIELD "profile_code_obj" ASCENDING INDEX-FIELD "profile_data_key" ASCENDING INDEX-FIELD "context_id" ASCENDING ADD INDEX "XAK1gsm_profile_data" ON "gsm_profile_data" AREA "Schema Area" UNIQUE INDEX-FIELD "profile_type_obj" ASCENDING INDEX-FIELD "profile_code_obj" ASCENDING INDEX-FIELD "profile_data_key" ASCENDING INDEX-FIELD "context_id" ASCENDING INDEX-FIELD "user_obj" ASCENDING ADD INDEX "XAK2gsm_profile_data" ON "gsm_profile_data" AREA "Schema Area" UNIQUE INDEX-FIELD "profile_data_obj" ASCENDING ADD INDEX "XIE1gsm_profile_data" ON "gsm_profile_data" AREA "Schema Area" INDEX-FIELD "context_id" ASCENDING ADD TABLE "gst_record_version" AREA "Schema Area" DESCRIPTION "This table provides the means for identifying when static data is changed and needs to be deployed. When an item of data on a record changes, the replication trigger on the table will check if the version_data flag on the gsc_entity_mnemonic table is switched on. If the flag is on, either a record is written to this table or an existing record in the table is updated to indicate that the data has changed by incrementing the version_number_seq and resetting date, time and user. This table is checked every time the deployment data is written to ensure that all data that matches the deployment criteria is written out. If no record exists for a record that is supposed to be deployed, it is assumed that this data already exists in the remote database because it would have been created from a baseline or initial installation." DUMP-NAME "gstrv" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/gstrvtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/gstrvtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/gstrvtrigw.p" CRC "?" ADD FIELD "record_version_obj" OF "gst_record_version" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Record Version Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Record version obj" DECIMALS 6 ORDER 10 ADD FIELD "entity_mnemonic" OF "gst_record_version" AS character DESCRIPTION "The code allocated to every table in the database that uniquely identifies the database table. This code is used when generically joining to tables, as the basis for naming conventions (e.g. a prefix to all objects that maintain this table), etc. This code is usually stored in the dump name of the table. " FORMAT "X(8)" INITIAL "" LABEL "Entity Mnemonic" POSITION 3 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Entity mnemonic" ORDER 20 ADD FIELD "key_field_value" OF "gst_record_version" AS character DESCRIPTION "This is the key field value of the record in the table identified by the entity mnemonic and dbname. The contents of this field are defined by the gsc_entity_mnemonic table and will contain the object field if specified otherwise the key field. In either case it will be a unique single field used to find the current record." FORMAT "X(70)" INITIAL "" LABEL "Key Field Value" POSITION 4 SQL-WIDTH 140 VALMSG "s_big_name" HELP "Key field value" ORDER 30 ADD FIELD "version_number_seq" OF "gst_record_version" AS decimal DESCRIPTION "Every time the data related to the record specified in the key_field_value field changes, this number is incremented. " FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Version Number Seq." POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Version number seq." DECIMALS 6 ORDER 40 ADD FIELD "version_date" OF "gst_record_version" AS date DESCRIPTION "This field contains the date that this data was updated." FORMAT "99/99/9999" INITIAL "TODAY" LABEL "Version Date" POSITION 6 SQL-WIDTH 4 VALMSG "d_date_today" HELP "Version date" ORDER 50 ADD FIELD "version_time" OF "gst_record_version" AS integer DESCRIPTION "This field contains the time that this data was updated." FORMAT ">>>>9" INITIAL "0" LABEL "Version Time" POSITION 7 SQL-WIDTH 4 VALMSG "n_time" HELP "Version time" ORDER 60 ADD FIELD "version_user" OF "gst_record_version" AS character DESCRIPTION "This field indicates which user created this version of the data if known." FORMAT "X(20)" INITIAL "" LABEL "Version User" POSITION 8 SQL-WIDTH 40 VALMSG "s_string_20" HELP "Version user" ORDER 70 ADD FIELD "deletion_flag" OF "gst_record_version" AS logical DESCRIPTION "If set to yes, this field indicates that the last action against the record resulted in a deletion." FORMAT "YES/NO" INITIAL "NO" LABEL "Deletion Flag" POSITION 9 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Deletion flag" ORDER 80 ADD INDEX "XPKgst_record_version" ON "gst_record_version" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "record_version_obj" ASCENDING ADD INDEX "XAK1gst_record_version" ON "gst_record_version" AREA "Schema Area" UNIQUE INDEX-FIELD "entity_mnemonic" ASCENDING INDEX-FIELD "key_field_value" ASCENDING ADD INDEX "XIE1gst_record_version" ON "gst_record_version" AREA "Schema Area" INDEX-FIELD "key_field_value" ASCENDING ADD INDEX "XIE2gst_record_version" ON "gst_record_version" AREA "Schema Area" INDEX-FIELD "version_date" ASCENDING INDEX-FIELD "version_time" ASCENDING ADD INDEX "XIE3gst_record_version" ON "gst_record_version" AREA "Schema Area" INDEX-FIELD "entity_mnemonic" ASCENDING INDEX-FIELD "version_date" ASCENDING INDEX-FIELD "version_time" ASCENDING ADD TABLE "ryc_attribute_type" AREA "Schema Area" DESCRIPTION "This table defines the types of attributes supported. Attribute types then define the structure of values associated with attributes of this type. Example attribute types could be: CHR = Character COL = Collection IMG = Image (so we can search/preview) FIL = File (so we can search) " DUMP-NAME "rycay" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycaytrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycaytrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/rycayreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/rycayrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/rycayreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycaytrigw.p" CRC "?" ADD FIELD "attribute_type_tla" OF "ryc_attribute_type" AS character DESCRIPTION "This is a unique 3 letter acronym to define the attribute type, e.g. CHR = Character COL = Collection IMG = Image (so we can search/preview) FIL = File (so we can search) " FORMAT "X(3)" INITIAL "" LABEL "Attribute Type TLA" POSITION 2 SQL-WIDTH 6 VALMSG "s_tla" HELP "Attribute type three letter acronym" ORDER 10 ADD FIELD "attribute_type_description" OF "ryc_attribute_type" AS character DESCRIPTION "A description of the attribute type" FORMAT "X(35)" INITIAL "" LABEL "Attribute Type Description" POSITION 3 SQL-WIDTH 70 VALMSG "s_description" HELP "Attribute type description" ORDER 20 ADD FIELD "collection_attribute" OF "ryc_attribute_type" AS logical FORMAT "YES/NO" INITIAL "NO" LABEL "Collection Attribute" POSITION 4 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Collection attribute" ORDER 30 ADD FIELD "edit_program" OF "ryc_attribute_type" AS character DESCRIPTION "This facilitates the launch of a program to edit the value of the attribute, e.g. launch a program to search for a filename. The program should support 3 character parameters as follows: input attribute name input attribute type tla input-output attribute value " FORMAT "X(70)" INITIAL "" LABEL "Edit Program" POSITION 5 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Edit program" ORDER 40 ADD FIELD "attribute_type_obj" OF "ryc_attribute_type" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Attribute Type Obj" POSITION 6 SQL-WIDTH 21 VALMSG "o_obj" HELP "Attribute type obj" DECIMALS 6 ORDER 50 ADD INDEX "XPKryc_attribute_type" ON "ryc_attribute_type" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "attribute_type_tla" ASCENDING ADD INDEX "XAK1ryc_attribute_type" ON "ryc_attribute_type" AREA "Schema Area" UNIQUE INDEX-FIELD "attribute_type_obj" ASCENDING ADD INDEX "XIE1ryc_attribute_type" ON "ryc_attribute_type" AREA "Schema Area" INDEX-FIELD "attribute_type_description" ASCENDING ADD TABLE "ryc_layout" AREA "Schema Area" DESCRIPTION "This table defines the available page layouts for pages on smartfolder windows, e.g. 1 browser with 1 toolbar underneath, n viewers above each other, 2 side by side viewers, 2 side by side browsers, etc. It also defines the available frame layouts for objects on a frame, e.g. 1 column, 2 columns, etc. The purpose of this table is to specify the program which is responsible for the layout when the window / frame is construted or resized. " DUMP-NAME "rycla" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/ryclatrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/ryclatrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/ryclareplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/ryclarepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/ryclareplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/ryclatrigw.p" CRC "?" ADD FIELD "layout_obj" OF "ryc_layout" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Layout Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Layout obj" DECIMALS 6 ORDER 10 ADD FIELD "layout_name" OF "ryc_layout" AS character DESCRIPTION "A unique name to identify the layout" FORMAT "X(28)" INITIAL "" LABEL "Layout Name" POSITION 3 SQL-WIDTH 56 VALMSG "s_label" HELP "Layout name" ORDER 20 ADD FIELD "layout_type" OF "ryc_layout" AS character DESCRIPTION "This is a 3 character code to identify the tupe of layout, e.g. PAG = Page Layout FRA = Frame Object Layout BTH = Both " FORMAT "X(3)" INITIAL "" LABEL "Layout Type" POSITION 4 SQL-WIDTH 6 VALMSG "s_type" HELP "Layout type" ORDER 30 ADD FIELD "layout_narrative" OF "ryc_layout" AS character DESCRIPTION "A full description of the layout" FORMAT "X(500)" INITIAL "" LABEL "Layout Narrative" POSITION 5 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Layout narrative" ORDER 40 ADD FIELD "layout_filename" OF "ryc_layout" AS character DESCRIPTION "The filename to run, including relative path, in order to actual perform the laying out of the objects on the page / frame during initial construction and resize." FORMAT "X(70)" INITIAL "" LABEL "Layout Filename" POSITION 6 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Layout filename" ORDER 50 ADD FIELD "sample_image_filename" OF "ryc_layout" AS character DESCRIPTION "If available, the name and relative path of an image file that can be displayed illustrating the page / frame layout." FORMAT "X(70)" INITIAL "" LABEL "Sample Image Filename" POSITION 7 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Sample image filename" ORDER 60 ADD FIELD "system_owned" OF "ryc_layout" AS logical DESCRIPTION "If set to YES, this record may only be modified by users with a system owned flag. " FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 70 ADD FIELD "layout_code" OF "ryc_layout" AS character DESCRIPTION "This is a suffix to add to internal procedures in the layout manager plip to identify the specific layout manager, e.g. 01 would run the procedure version resize01 for this layout." FORMAT "X(10)" INITIAL "" LABEL "Layout Code" POSITION 9 SQL-WIDTH 20 VALMSG "s_code" HELP "Layout code" ORDER 80 ADD INDEX "XPKryc_layout" ON "ryc_layout" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "layout_obj" ASCENDING ADD INDEX "XAK1ryc_layout" ON "ryc_layout" AREA "Schema Area" UNIQUE INDEX-FIELD "layout_name" ASCENDING ADD INDEX "XAK2ryc_layout" ON "ryc_layout" AREA "Schema Area" UNIQUE INDEX-FIELD "layout_type" ASCENDING INDEX-FIELD "layout_name" ASCENDING ADD TABLE "ryc_smartobject" AREA "Schema Area" DESCRIPTION "This entity represents every smartobject known to the repository, whether static or dynamic. Relationships exist to various child tables; however the existence of data in these child tables corresponding to this particular smartobject is dictated by the smartobject type - e.g. only Toolbar smartobjects may have toolbar group data. Some smartobjects are visualisations of data provided by a smartdataobject. This is represented by the cyclic relationship ""provides data for"". NOTE: Every ICF object will be automatically created in this table to make it easy to use a mixture of static and dynamic objects onto static or dynamic containers. The creation of these records should therefore be done by the appropriate wizards, etc. NOTE2: We have turned off the delete trigger RI to prevent an object being deleted if it is on a container somewhere - to allow our imports and assignments of the data in the versioning system to work. Therefore, this RI must be manually coded wherever it is possible to delete a smartobject, to ensure smartobjects that exist on containers are not inadvertantly deleted. NOTE3: We turned off the automatic delete cascade of smartobject attributes as it was also deleting attributes for instances of the smartobject when we did not want it to. Added a specific delete trigger customisation that rather joined on the primary_smartobject_obj in the attribute table when deleting attributes, to ensure only attributes for the smartobject were deleted, not also instance attributes." DUMP-NAME "rycso" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycsotrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycsotrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/rycsoreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/rycsorepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/rycsoreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycsotrigw.p" CRC "?" ADD FIELD "smartobject_obj" OF "ryc_smartobject" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "SmartObject Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "SmartObject obj" DECIMALS 6 ORDER 10 ADD FIELD "layout_obj" OF "ryc_smartobject" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Layout Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Layout obj" DECIMALS 6 ORDER 20 ADD FIELD "object_type_obj" OF "ryc_smartobject" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Type Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object type obj" DECIMALS 6 ORDER 30 ADD FIELD "object_obj" OF "ryc_smartobject" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object obj" DECIMALS 6 ORDER 40 ADD FIELD "static_object" OF "ryc_smartobject" AS logical DESCRIPTION "Indicates whether this object is static or dynamic. Static objects exist in the repository only so that they can be used as instances wihin smart containers. Dynamic objects exist in the repository so that they can be constructed at runtime. Static smartdataobjects are described in sigificant detail within the repository so that they can be used in the subsequent description of data visualisation objects (smartviewers, smartbrowsers, webforms etc)." FORMAT "YES/NO" INITIAL "NO" LABEL "Static Object" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Static object" ORDER 70 ADD FIELD "object_filename" OF "ryc_smartobject" AS character DESCRIPTION "This is the actual filename of the object, carried from gsc_object for performance reasons. The filename does not contain any path details, but does contain an extension if it is a physical smartobject (as apposed to a dynamic object). " FORMAT "X(70)" INITIAL "" LABEL "Object Filename" POSITION 7 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Object filename" ORDER 50 ADD FIELD "product_module_obj" OF "ryc_smartobject" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Product Module Obj" POSITION 8 SQL-WIDTH 21 VALMSG "o_obj" HELP "Product module obj" DECIMALS 6 ORDER 60 ADD FIELD "custom_super_procedure" OF "ryc_smartobject" AS character DESCRIPTION "This attribute is the optional name of a procedure which will be instantiated as a super-procedure of the smartobject. Super procedures provide code-level services (e.g. functions and internal procedures) to smartobjects in addition to those inherent in the smartobject itself." FORMAT "X(70)" INITIAL "" LABEL "Custom Super Procedure" POSITION 9 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Custom super procedure" ORDER 80 ADD FIELD "system_owned" OF "ryc_smartobject" AS logical DESCRIPTION "If set to YES, this record may only be modified by users with a system owned flag. " FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 10 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 90 ADD FIELD "shutdown_message_text" OF "ryc_smartobject" AS character DESCRIPTION "This message text will be displayed to the user should they attempt to close down this object whilst it contains unsaved changes." FORMAT "X(70)" INITIAL "" LABEL "Shutdown Message Text" POSITION 11 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Shutdown message text" ORDER 100 ADD FIELD "sdo_smartobject_obj" OF "ryc_smartobject" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Sdo SmartObject Obj" POSITION 12 SQL-WIDTH 21 VALMSG "o_obj" HELP "Sdo SmartObject obj" DECIMALS 6 ORDER 110 ADD FIELD "template_smartobject" OF "ryc_smartobject" AS logical DESCRIPTION "If set to YES, then this smartobject may be used as a template for creating other similar smartobjects. This makes it easy to define standard containers, such as an object controller with a standard toolbar, a standard browser, a standard layout, etc. and to create new objects based on this template - via some sort of copy operation with bits likely to change prompted for. " FORMAT "YES/NO" INITIAL "NO" LABEL "Template SmartObject" POSITION 13 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Template SmartObject" ORDER 120 ADD INDEX "XPKryc_smartobject" ON "ryc_smartobject" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "smartobject_obj" ASCENDING ADD INDEX "XAK1ryc_smartobject" ON "ryc_smartobject" AREA "Schema Area" UNIQUE INDEX-FIELD "object_filename" ASCENDING ADD INDEX "XAK2ryc_smartobject" ON "ryc_smartobject" AREA "Schema Area" UNIQUE INDEX-FIELD "object_type_obj" ASCENDING INDEX-FIELD "object_obj" ASCENDING ADD INDEX "XAK3ryc_smartobject" ON "ryc_smartobject" AREA "Schema Area" UNIQUE INDEX-FIELD "product_module_obj" ASCENDING INDEX-FIELD "object_filename" ASCENDING ADD INDEX "XIE1ryc_smartobject" ON "ryc_smartobject" AREA "Schema Area" INDEX-FIELD "sdo_smartobject_obj" ASCENDING ADD INDEX "XIE2ryc_smartobject" ON "ryc_smartobject" AREA "Schema Area" INDEX-FIELD "layout_obj" ASCENDING INDEX-FIELD "object_type_obj" ASCENDING ADD TABLE "ryc_widget_type" AREA "Schema Area" DESCRIPTION "This table defines the supported widget types, e.g. frame, button, fill-in, editor, radio-set, menu-item, etc." DUMP-NAME "rycwt" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycwttrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycwttrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycwttrigw.p" CRC "?" ADD FIELD "widget_type_obj" OF "ryc_widget_type" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Widget Type Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Widget type obj" DECIMALS 6 ORDER 10 ADD FIELD "widget_type_name" OF "ryc_widget_type" AS character DESCRIPTION "A unique name to identify the widget, i.e. button, frame, etc." FORMAT "X(28)" INITIAL "" LABEL "Widget Type Name" POSITION 3 SQL-WIDTH 56 VALMSG "s_label" HELP "Widget type name" ORDER 20 ADD FIELD "widget_type_narrative" OF "ryc_widget_type" AS character DESCRIPTION "A full description of the widget." FORMAT "X(500)" INITIAL "" LABEL "Widget Type Narrative" POSITION 4 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Widget type narrative" ORDER 30 ADD INDEX "XPKryc_widget_type" ON "ryc_widget_type" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "widget_type_obj" ASCENDING ADD INDEX "XAK1ryc_widget_type" ON "ryc_widget_type" AREA "Schema Area" UNIQUE INDEX-FIELD "widget_type_name" ASCENDING ADD TABLE "ryc_smartobject_field" AREA "Schema Area" DESCRIPTION "This table contains field infromation for smartdataobjects (sdo's), smartviewers, smartbrowsers, webbrower's, webforms, etc. Certain information is specific to certain types of objects, but is contained in a central table for performance and simplicity reasons, and to reduce the number of tables required by the repository. The table defines the fields for a smartdataobject which are all the fields available to any objects using the smartdataobject. When the fields are related to anything other than a smartdataobject, certain of the values only need to be specified if they differ from the default values defined in the smartdataobject fields, thereby facilitating the override of default values per instance. Holding this information in the repository removes the dependany on the Progress system tables (underscore tables) and also allows us to add extra information required by the repository. We provide import tables to automatically create a lot of this information directly from existing objects, and wizards on the smartdataobject to populate the data for new objects. " DUMP-NAME "rycsf" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycsftrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycsftrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/rycsfreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/rycsfrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/rycsfreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycsftrigw.p" CRC "?" ADD FIELD "smartobject_field_obj" OF "ryc_smartobject_field" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "SmartObject Field Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "SmartObject field obj" DECIMALS 6 ORDER 10 ADD FIELD "smartobject_obj" OF "ryc_smartobject_field" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "SmartObject Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "SmartObject obj" DECIMALS 6 ORDER 20 ADD FIELD "field_sequence" OF "ryc_smartobject_field" AS integer DESCRIPTION "This is the order of the fields in the rowobject table for an sdo, or the order of the fields displayed on a browser, viewer, etc." FORMAT "->>9" INITIAL "0" LABEL "Field Sequence" POSITION 4 SQL-WIDTH 4 COLUMN-LABEL "Field Seq." VALMSG "n_integer_3" HELP "Field sequence" ORDER 30 ADD FIELD "field_name" OF "ryc_smartobject_field" AS character DESCRIPTION "This is the actual SDO fieldname, without any table prefix." FORMAT "X(35)" INITIAL "" LABEL "Field Name" POSITION 5 SQL-WIDTH 70 VALMSG "s_name" HELP "Field name" ORDER 40 ADD FIELD "database_table" OF "ryc_smartobject_field" AS character DESCRIPTION "This is the name of the database table the field belongs to. This will be blank for calculated fields." FORMAT "X(35)" INITIAL "" LABEL "Database Table" POSITION 6 SQL-WIDTH 70 VALMSG "s_name" HELP "Database table" ORDER 50 ADD FIELD "database_field" OF "ryc_smartobject_field" AS character DESCRIPTION "This is the name of the database field. It will be blank for a calculated field, and normally the same as the sdo field name for non calculated fields. The only time this will differ from the sdo fieldname is in the event of duplicate fieldnames from multiple tables." FORMAT "X(35)" INITIAL "" LABEL "Database Field" POSITION 7 SQL-WIDTH 70 VALMSG "s_name" HELP "Database field" ORDER 60 ADD FIELD "field_datatype" OF "ryc_smartobject_field" AS character DESCRIPTION "The Progress datatype, i.e. character decimal integer logical date raw " FORMAT "X(15)" INITIAL "" LABEL "Field Datatype" POSITION 8 SQL-WIDTH 30 VALMSG "s_short_name" HELP "Field datatype" ORDER 70 ADD FIELD "widget_type_obj" OF "ryc_smartobject_field" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Widget Type Obj" POSITION 9 SQL-WIDTH 21 VALMSG "o_obj" HELP "Widget type obj" DECIMALS 6 ORDER 80 ADD FIELD "field_format" OF "ryc_smartobject_field" AS character DESCRIPTION "The Progress format of the field." FORMAT "X(28)" INITIAL "" LABEL "Field Format" POSITION 10 SQL-WIDTH 56 VALMSG "s_label" HELP "Field format" ORDER 90 ADD FIELD "field_label" OF "ryc_smartobject_field" AS character DESCRIPTION "The side label for the field" FORMAT "X(28)" INITIAL "" LABEL "Field Label" POSITION 11 SQL-WIDTH 56 VALMSG "s_label" HELP "Field label" ORDER 100 ADD FIELD "field_column_label" OF "ryc_smartobject_field" AS character DESCRIPTION "The default column label for the field" FORMAT "X(28)" INITIAL "" LABEL "Field Column Label" POSITION 12 SQL-WIDTH 56 VALMSG "s_label" HELP "Field column label" ORDER 110 ADD FIELD "field_enabled" OF "ryc_smartobject_field" AS logical DESCRIPTION "If set to YES, this field may be updated by a viewer or browser. If this is set to NO, the SDO will never save these changes. Fields from joined tables will usually be set to NO. The viewer or browser may override this setting from NO to YES if required when defining the browser or viewer fields." FORMAT "YES/NO" INITIAL "YES" LABEL "Field Enabled" POSITION 13 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Field enabled" ORDER 120 ADD FIELD "field_view_as" OF "ryc_smartobject_field" AS character DESCRIPTION "The view-as phrase for the field to determine its default visualisation." FORMAT "X(70)" INITIAL "" LABEL "Field View As" POSITION 14 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Field view as" ORDER 130 ADD FIELD "field_tooltip" OF "ryc_smartobject_field" AS character DESCRIPTION "The tooltip forthe field. This is copied from the field help text if none is specified." FORMAT "X(70)" INITIAL "" LABEL "Field Tooltip" POSITION 15 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Field tooltip" ORDER 140 ADD FIELD "field_default" OF "ryc_smartobject_field" AS character DESCRIPTION "This is the default value for the field when in an add situation." FORMAT "X(70)" INITIAL "" LABEL "Field Default" POSITION 16 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Field default" ORDER 150 ADD FIELD "use_as_title_field" OF "ryc_smartobject_field" AS logical DESCRIPTION "If set to YES, this field could be used in a window title to identify the data in the window." FORMAT "YES/NO" INITIAL "NO" LABEL "Use as Title Field" POSITION 17 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Use as title field" ORDER 160 ADD FIELD "use_as_object_field" OF "ryc_smartobject_field" AS logical DESCRIPTION "If set to YES, this is the identifying object field (_obj) used to uniquely identify the record." FORMAT "YES/NO" INITIAL "NO" LABEL "Use as Object Field" POSITION 18 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Use as object field" ORDER 170 ADD FIELD "use_as_description_field" OF "ryc_smartobject_field" AS logical DESCRIPTION "If set to YES, this field could be used to describe the data, i.e. when building generic objects." FORMAT "YES/NO" INITIAL "NO" LABEL "Use as Description Field" POSITION 19 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Use as description field" ORDER 180 ADD FIELD "index_list" OF "ryc_smartobject_field" AS character DESCRIPTION "This is a comma delimited list of indexes and positions that this field belongs to, e.g. 1.2, 3.2, 4.1 Would indicate that it is the 2nd field of the 1st index, the 2nd field of the 3rd index, etc. This information is useful when filtering the data to indicate which fields will result in an efficient search result set." FORMAT "X(35)" INITIAL "" LABEL "Index List" POSITION 20 SQL-WIDTH 70 VALMSG "s_description" HELP "Index list" ORDER 190 ADD FIELD "enable_on_create" OF "ryc_smartobject_field" AS logical DESCRIPTION "If set to YES, this field will be enabled during an add operation." FORMAT "YES/NO" INITIAL "YES" LABEL "Enable On Create" POSITION 21 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Enable on create" ORDER 200 ADD FIELD "enable_on_modify" OF "ryc_smartobject_field" AS logical DESCRIPTION "If set to YES, this field will be enabled during a modify situation." FORMAT "YES/NO" INITIAL "YES" LABEL "Enable On Modify" POSITION 22 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Enable on modify" ORDER 210 ADD FIELD "initial_focus_field" OF "ryc_smartobject_field" AS logical DESCRIPTION "If set to YES, this is the first field that will receive focus when tabbing into the viewer." FORMAT "YES/NO" INITIAL "NO" LABEL "Initial Focus Field" POSITION 23 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Initial focus field" ORDER 220 ADD FIELD "smartfield_filename" OF "ryc_smartobject_field" AS character DESCRIPTION "This is the filename of a smartdatafield in the event that the field needs to support complex behaviour, e.g. lookups, combo's, etc." FORMAT "X(70)" INITIAL "" LABEL "Smartfield Filename" POSITION 24 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Smartfield filename" ORDER 230 ADD FIELD "find_field" OF "ryc_smartobject_field" AS logical DESCRIPTION "If set to YES, this field may be used in generic find functionality to allow records to be located using this field as criteria. Usually this functionality will be restricted to indexed fields." FORMAT "YES/NO" INITIAL "YES" LABEL "Find Field" POSITION 25 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Find field" ORDER 240 ADD FIELD "filter_field" OF "ryc_smartobject_field" AS logical DESCRIPTION "If set to YES, this field may be used in generic filter functionality to allow records to be filtered using this field as criteria. Usually this functionality will be restricted to indexed fields." FORMAT "YES/NO" INITIAL "YES" LABEL "Filter Field" POSITION 26 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Filter field" ORDER 250 ADD FIELD "sort_field" OF "ryc_smartobject_field" AS logical DESCRIPTION "If set to YES, this field may be used in generic sort functionality to allow records to be sorted using this field as criteria. Usually this functionality will be restricted to indexed fields." FORMAT "YES/NO" INITIAL "YES" LABEL "Sort Field" POSITION 27 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Sort field" ORDER 260 ADD FIELD "sort_descending" OF "ryc_smartobject_field" AS logical DESCRIPTION "If set to YES, then the initial sort of the column will be descending. Pressing a toolbar column will toggle this option." FORMAT "YES/NO" INITIAL "NO" LABEL "Sort Descending" POSITION 28 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Sort descending" ORDER 270 ADD INDEX "XPKryc_smartobject_field" ON "ryc_smartobject_field" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "smartobject_field_obj" ASCENDING ADD INDEX "XAK1ryc_smartobject_field" ON "ryc_smartobject_field" AREA "Schema Area" UNIQUE INDEX-FIELD "smartobject_obj" ASCENDING INDEX-FIELD "field_sequence" ASCENDING ADD INDEX "XAK2ryc_smartobject_field" ON "ryc_smartobject_field" AREA "Schema Area" UNIQUE INDEX-FIELD "smartobject_obj" ASCENDING INDEX-FIELD "field_name" ASCENDING ADD INDEX "XIE1ryc_smartobject_field" ON "ryc_smartobject_field" AREA "Schema Area" INDEX-FIELD "widget_type_obj" ASCENDING ADD INDEX "XIE2ryc_smartobject_field" ON "ryc_smartobject_field" AREA "Schema Area" INDEX-FIELD "database_table" ASCENDING INDEX-FIELD "database_field" ASCENDING ADD INDEX "XIE3ryc_smartobject_field" ON "ryc_smartobject_field" AREA "Schema Area" INDEX-FIELD "smartfield_filename" ASCENDING ADD TABLE "ryc_smartlink_type" AREA "Schema Area" DESCRIPTION "This table defines the supported smart links available for linking objects on containers for object communication purposes. Example links include page, container, update, commit, tableio, etc. The main purpose of this table is to provide a valid list of smart links to choose from when building generic containers. Additional user defined smart links may be implemented by defining a user defined link. The actual link name will be cascaded down onto the smartlink table where this is not a user defined link. The supported link table will be used to highlight which are the expected links between any two smartobjects. " DUMP-NAME "rycst" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycsttrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycsttrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/rycstreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/rycstrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/rycstreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycsttrigw.p" CRC "?" ADD FIELD "smartlink_type_obj" OF "ryc_smartlink_type" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Smartlink Type Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Smartlink type obj" DECIMALS 6 ORDER 10 ADD FIELD "link_name" OF "ryc_smartlink_type" AS character DESCRIPTION "This is the actual link name (excluding the source or target suffix). This name will always be cascaded down to the smartlink table when the user defined link flag is set to NO, therefore avoiding having to always read this table to get the actual link name." FORMAT "X(28)" INITIAL "" LABEL "Link Name" POSITION 3 SQL-WIDTH 56 VALMSG "s_label" HELP "Link name" ORDER 20 ADD FIELD "used_defined_link" OF "ryc_smartlink_type" AS logical DESCRIPTION "If set to YES, this is a user defined link and the link name specified here is for information purposes only, i.e. custom link. If this is set to NO, then this is a system link and the link name specified will be cascaded down onto the smartlink table for performance reasons. This must be done in both add and modify situations. " FORMAT "YES/NO" INITIAL "NO" LABEL "Used Defined Link" POSITION 4 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Used defined link" ORDER 30 ADD FIELD "system_owned" OF "ryc_smartlink_type" AS logical DESCRIPTION "If set to YES, this record may only be modified by users with a system owned flag. " FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 5 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 40 ADD INDEX "XPKryc_smartlink_type" ON "ryc_smartlink_type" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "smartlink_type_obj" ASCENDING ADD INDEX "XAK1ryc_smartlink_type" ON "ryc_smartlink_type" AREA "Schema Area" UNIQUE INDEX-FIELD "link_name" ASCENDING ADD TABLE "ryc_supported_link" AREA "Schema Area" DESCRIPTION "This table defines the supported smartlinks for the various type of smartobjects, and whether the link can be a source, target, or both. User defined links should not be set-up in this table. This table is purely to ensure that when linking objects on containers, only valid system links are used, plus user defined links. It is merely a developer aid. Not all types of smartobjects support links, in which case there will be no entries in this table for them." DUMP-NAME "rycsl" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycsltrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycsltrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycsltrigw.p" CRC "?" ADD FIELD "supported_link_obj" OF "ryc_supported_link" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Supported Link Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Supported link obj" DECIMALS 6 ORDER 10 ADD FIELD "object_type_obj" OF "ryc_supported_link" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Type Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object type obj" DECIMALS 6 ORDER 20 ADD FIELD "smartlink_type_obj" OF "ryc_supported_link" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Smartlink Type Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Smartlink type obj" DECIMALS 6 ORDER 30 ADD FIELD "link_source" OF "ryc_supported_link" AS logical DESCRIPTION "If set to YES, objects of this smart type are capable of acting as the source for the specified link." FORMAT "YES/NO" INITIAL "YES" LABEL "Link Source" POSITION 5 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Link source" ORDER 40 ADD FIELD "link_target" OF "ryc_supported_link" AS logical DESCRIPTION "If set to YES, objects of this smart type are capable of acting as the target for the specified link." FORMAT "YES/NO" INITIAL "YES" LABEL "Link Target" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Link target" ORDER 50 ADD FIELD "deactivated_link_on_hide" OF "ryc_supported_link" AS logical DESCRIPTION "If set to YES, this link for this type of smartobject will be automatically deactivated when the object is hidden, and activated again when the object is viewed." FORMAT "YES/NO" INITIAL "NO" LABEL "Deactivated Link On Hide" POSITION 7 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Deactivated link on hide" ORDER 60 ADD INDEX "XPKryc_supported_link" ON "ryc_supported_link" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "supported_link_obj" ASCENDING ADD INDEX "XAK1ryc_supported_link" ON "ryc_supported_link" AREA "Schema Area" UNIQUE INDEX-FIELD "object_type_obj" ASCENDING INDEX-FIELD "smartlink_type_obj" ASCENDING ADD INDEX "XAK2ryc_supported_link" ON "ryc_supported_link" AREA "Schema Area" UNIQUE INDEX-FIELD "smartlink_type_obj" ASCENDING INDEX-FIELD "object_type_obj" ASCENDING ADD TABLE "ryc_subscribe" AREA "Schema Area" DESCRIPTION "This is a generic table that facilitates any object subscribing to events across links and running internal procedures to perform some action as a result of the event. Its primary use would be to subscribe frames or containers to system events." DUMP-NAME "rycsu" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycsutrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycsutrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/rycsureplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/rycsurepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/rycsureplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycsutrigw.p" CRC "?" ADD FIELD "subscribe_obj" OF "ryc_subscribe" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Subscribe Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Subscribe obj" DECIMALS 6 ORDER 10 ADD FIELD "owning_entity_mnemonic" OF "ryc_subscribe" AS character DESCRIPTION "This is the FLA of the table that this subscribed event relates to, e.g. the FLA of the container table in order to subscribe containers to generic events." FORMAT "X(8)" INITIAL "" LABEL "Owning Entity Mnemonic" POSITION 3 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Owning entity mnemonic" ORDER 20 ADD FIELD "owning_obj" OF "ryc_subscribe" AS decimal DESCRIPTION "This is the object number of the record from the table identified by the owning entity mnemonic, e.g. the object number of a container that subscribes to the generic event." FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Owning Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Owning obj" DECIMALS 6 ORDER 30 ADD FIELD "subscribe_to_event" OF "ryc_subscribe" AS character DESCRIPTION "This is the actual name of the event being subscribed to." FORMAT "X(28)" INITIAL "" LABEL "Subscribe to Event" POSITION 5 SQL-WIDTH 56 VALMSG "s_label" HELP "Subscribe to event" ORDER 40 ADD FIELD "subscribe_in_link" OF "ryc_subscribe" AS character DESCRIPTION "This is a comma delimited list of links the event should be subscribed across." FORMAT "X(70)" INITIAL "" LABEL "Subscribe in Link" POSITION 6 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Subscribe in link" ORDER 50 ADD FIELD "run_local_procedure" OF "ryc_subscribe" AS character DESCRIPTION "In the event that a different procedure should be run than that of the event name, this specfies the new procedure to run." FORMAT "X(70)" INITIAL "" LABEL "Run Local Procedure" POSITION 7 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Run local procedure" ORDER 60 ADD FIELD "system_owned" OF "ryc_subscribe" AS logical DESCRIPTION "If set to YES, this record may only be modified by users with a system owned flag. " FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 70 ADD INDEX "XPKryc_subscribe" ON "ryc_subscribe" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "subscribe_obj" ASCENDING ADD INDEX "XAK1ryc_subscribe" ON "ryc_subscribe" AREA "Schema Area" UNIQUE INDEX-FIELD "owning_entity_mnemonic" ASCENDING INDEX-FIELD "owning_obj" ASCENDING INDEX-FIELD "subscribe_to_event" ASCENDING INDEX-FIELD "subscribe_in_link" ASCENDING ADD TABLE "ryc_ui_trigger" AREA "Schema Area" DESCRIPTION "The supported Progress UI events, e.g. choose, value-changed, etc." DUMP-NAME "rycut" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycuttrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycuttrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycuttrigw.p" CRC "?" ADD FIELD "ui_trigger_obj" OF "ryc_ui_trigger" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "UI Trigger Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "User interface trigger obj" DECIMALS 6 ORDER 10 ADD FIELD "ui_trigger_name" OF "ryc_ui_trigger" AS character DESCRIPTION "A unique name to identify the UI trigger, e.g. choose, value-changed, etc." FORMAT "X(28)" INITIAL "" LABEL "UI Trigger Name" POSITION 3 SQL-WIDTH 56 VALMSG "s_label" HELP "User interface trigger name" ORDER 20 ADD FIELD "ui_trigger_narrative" OF "ryc_ui_trigger" AS character DESCRIPTION "A full description of the trigger." FORMAT "X(500)" INITIAL "" LABEL "UI Trigger Narrative" POSITION 4 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "User interface trigger narrative" ORDER 30 ADD INDEX "XPKryc_ui_trigger" ON "ryc_ui_trigger" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "ui_trigger_obj" ASCENDING ADD INDEX "XAK1ryc_ui_trigger" ON "ryc_ui_trigger" AREA "Schema Area" UNIQUE INDEX-FIELD "ui_trigger_name" ASCENDING ADD TABLE "ryc_custom_ui_trigger" AREA "Schema Area" DESCRIPTION "This table facilitates the generic allocation of UI triggers to individual fields and frames directly from the repository. For example, we could define an event to publish or a procedure to run when a specific button is pressed on a specific viewer. The actual code would have to already exist or reside in a super procedure." DUMP-NAME "rycct" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/ryccttrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/ryccttrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/rycctreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/rycctrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/rycctreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/ryccttrigw.p" CRC "?" ADD FIELD "custom_ui_trigger_obj" OF "ryc_custom_ui_trigger" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Custom UI Trigger Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Custom user interface trigger obj" DECIMALS 6 ORDER 10 ADD FIELD "smartobject_obj" OF "ryc_custom_ui_trigger" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "SmartObject Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "SmartObject obj" DECIMALS 6 ORDER 20 ADD FIELD "smartobject_field_obj" OF "ryc_custom_ui_trigger" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "SmartObject Field Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "SmartObject field obj" DECIMALS 6 ORDER 30 ADD FIELD "ui_trigger_obj" OF "ryc_custom_ui_trigger" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "UI Trigger Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "User interface trigger obj" DECIMALS 6 ORDER 40 ADD FIELD "publish_event" OF "ryc_custom_ui_trigger" AS character DESCRIPTION "The event to publish when the UI trigger is fired for the specified object. This could be used instead of specifying a procedure to run." FORMAT "X(28)" INITIAL "" LABEL "Publish Event" POSITION 6 SQL-WIDTH 56 VALMSG "s_label" HELP "Publish event" ORDER 50 ADD FIELD "trigger_parameter" OF "ryc_custom_ui_trigger" AS character DESCRIPTION "The parameter to pass to the procedue run by the published event," FORMAT "X(70)" INITIAL "" LABEL "Trigger Parameter" POSITION 7 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Trigger parameter" ORDER 60 ADD FIELD "run_procedure_name" OF "ryc_custom_ui_trigger" AS character DESCRIPTION "This is an alternative to publshing an event when the UI trigger is fired. If specified, the procedure will be run passing in the trigger parameter." FORMAT "X(70)" INITIAL "" LABEL "Run Procedure Name" POSITION 8 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Run procedure name" ORDER 70 ADD FIELD "system_owned" OF "ryc_custom_ui_trigger" AS logical DESCRIPTION "If set to YES, this record may only be modified by users with a system owned flag. " FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 9 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 80 ADD INDEX "XPKryc_custom_ui_trigger" ON "ryc_custom_ui_trigger" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "custom_ui_trigger_obj" ASCENDING ADD INDEX "XIE1ryc_custom_ui_trigger" ON "ryc_custom_ui_trigger" AREA "Schema Area" INDEX-FIELD "ui_trigger_obj" ASCENDING ADD INDEX "XIE2ryc_custom_ui_trigger" ON "ryc_custom_ui_trigger" AREA "Schema Area" INDEX-FIELD "smartobject_obj" ASCENDING INDEX-FIELD "ui_trigger_obj" ASCENDING ADD INDEX "XIE3ryc_custom_ui_trigger" ON "ryc_custom_ui_trigger" AREA "Schema Area" INDEX-FIELD "smartobject_field_obj" ASCENDING INDEX-FIELD "ui_trigger_obj" ASCENDING ADD TABLE "ryc_valid_ui_trigger" AREA "Schema Area" DESCRIPTION "This table defines the valid triggers supported for each widget type, e.g. a button may have a choose UI trigger. This is used to filter down the available UI triggers when defining custom UI triggers - therefore avoiding runtime errors." DUMP-NAME "rycvt" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycvttrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycvttrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycvttrigw.p" CRC "?" ADD FIELD "valid_ui_trigger_obj" OF "ryc_valid_ui_trigger" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Valid UI Trigger Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Valid user interface trigger obj" DECIMALS 6 ORDER 10 ADD FIELD "widget_type_obj" OF "ryc_valid_ui_trigger" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Widget Type Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Widget type obj" DECIMALS 6 ORDER 20 ADD FIELD "ui_trigger_obj" OF "ryc_valid_ui_trigger" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "UI Trigger Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "User interface trigger obj" DECIMALS 6 ORDER 30 ADD INDEX "XPKryc_valid_ui_trigger" ON "ryc_valid_ui_trigger" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "valid_ui_trigger_obj" ASCENDING ADD INDEX "XAK1ryc_valid_ui_trigger" ON "ryc_valid_ui_trigger" AREA "Schema Area" UNIQUE INDEX-FIELD "widget_type_obj" ASCENDING INDEX-FIELD "ui_trigger_obj" ASCENDING ADD INDEX "XAK2ryc_valid_ui_trigger" ON "ryc_valid_ui_trigger" AREA "Schema Area" UNIQUE INDEX-FIELD "ui_trigger_obj" ASCENDING INDEX-FIELD "widget_type_obj" ASCENDING ADD TABLE "ryc_attribute_group" AREA "Schema Area" DESCRIPTION "This table facilitates the logical grouping of attributes to simplify their use, e.g. geometry, statusbar, etc. The primary use of this table is make the presentation of the attributes to the user more effective and usable. It is likely we could use a tree view, with attribute groups as a node and pressing plus on the group, showing all attributes within that group." DUMP-NAME "rycap" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycaptrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycaptrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/rycapreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/rycaprepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/rycapreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycaptrigw.p" CRC "?" ADD FIELD "attribute_group_obj" OF "ryc_attribute_group" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Attribute Group Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Attribute group obj" DECIMALS 6 ORDER 10 ADD FIELD "attribute_group_name" OF "ryc_attribute_group" AS character DESCRIPTION "This is a name to uniquely identify the group of attributes, e.g. geometry, statusbar, etc." FORMAT "X(28)" INITIAL "" LABEL "Attribute Group Name" POSITION 3 SQL-WIDTH 56 VALMSG "s_label" HELP "Attribute group name" ORDER 20 ADD FIELD "attribute_group_narrative" OF "ryc_attribute_group" AS character DESCRIPTION "A full description of the attribute group explaining the purpose of its contents." FORMAT "X(500)" INITIAL "" LABEL "Attribute Group Narrative" POSITION 4 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Attribute group narrative" ORDER 30 ADD INDEX "XPKryc_attribute_group" ON "ryc_attribute_group" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "attribute_group_obj" ASCENDING ADD INDEX "XAK1ryc_attribute_group" ON "ryc_attribute_group" AREA "Schema Area" UNIQUE INDEX-FIELD "attribute_group_name" ASCENDING ADD TABLE "ryc_object_instance" AREA "Schema Area" DESCRIPTION "This is a running instance of an object on a container. This facilitates the allocation of specific attributes, links, and page numbers, etc. for the specific instance of an object. The reason that the container_obj is included in the primary key is to ensure that we can only create links between objects in a single container, and to stop us creating links between objects in different containers at design time. The object_instance_obj however is uniqe in its own right, therefor avoiding having to specify a rolename for the container when propogating the key onto the smartlink table." DUMP-NAME "rycoi" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycoitrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycoitrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/rycoireplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/rycoirepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/rycoireplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycoitrigw.p" CRC "?" ADD FIELD "container_smartobject_obj" OF "ryc_object_instance" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Container SmartObject Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Container SmartObject obj" DECIMALS 6 ORDER 10 ADD FIELD "object_instance_obj" OF "ryc_object_instance" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Instance Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object instance obj" DECIMALS 6 ORDER 20 ADD FIELD "smartobject_obj" OF "ryc_object_instance" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "SmartObject Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "SmartObject obj" DECIMALS 6 ORDER 30 ADD FIELD "system_owned" OF "ryc_object_instance" AS logical DESCRIPTION "If set to YES, this record may only be modified by users with a system owned flag. " FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 5 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 90 ADD FIELD "instance_x" OF "ryc_object_instance" AS integer DESCRIPTION "This is the object instances x coordinate in pixels, relative to its container default frame. This attribute will likely become obselete when the layout manager is fully implemented." FORMAT "->>>>>9" INITIAL "0" LABEL "Instance X" POSITION 6 SQL-WIDTH 4 VALMSG "n_integer_6" HELP "Instance x" ORDER 40 ADD FIELD "instance_y" OF "ryc_object_instance" AS integer DESCRIPTION "This is the object instances y coordinate in pixels, relative to its container default frame. This attribute will likely become obselete when the layout manager is fully implemented." FORMAT "->>>>>9" INITIAL "0" LABEL "Instance Y" POSITION 7 SQL-WIDTH 4 VALMSG "n_integer_6" HELP "Instance y" ORDER 50 ADD FIELD "instance_width" OF "ryc_object_instance" AS integer DESCRIPTION "This is the object instances width in pixels. This attribute will likely become obselete when the layout manager is fully implemented." FORMAT "->>>>>9" INITIAL "0" LABEL "Instance Width" POSITION 8 SQL-WIDTH 4 VALMSG "n_integer_6" HELP "Instance width" ORDER 60 ADD FIELD "instance_height" OF "ryc_object_instance" AS integer DESCRIPTION "This is the object instances height in pixels. This attribute will likely become obselete when the layout manager is fully implemented." FORMAT "->>>>>9" INITIAL "0" LABEL "Instance Height" POSITION 9 SQL-WIDTH 4 VALMSG "n_integer_6" HELP "Instance height" ORDER 70 ADD FIELD "attribute_list" OF "ryc_object_instance" AS character DESCRIPTION "This is the value pair list of all attribute values for this object instance. This field is maintained automatically whenever new attribute values are asociated with the object instance. It is here to speed up access to an objects properties. The delimiter between the attribute name and its value will be CHR(4) and the delimiter between attribute value pairs will be CHR(3). So the list will contain name + chr(4) + value + chr(3) + name + chr(4) + value + chr(3) etc. " FORMAT "X(500)" INITIAL "" LABEL "Attribute List" POSITION 10 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Attribute list" ORDER 80 ADD FIELD "layout_position" OF "ryc_object_instance" AS character DESCRIPTION "A code indicating where in the layout the object belongs. This is then used by the layout managers to automatically position objects, e.g. top, centre, bottom, etc. Where an object appears on a container multiple times, it must always have a seperate layout position. If it needs to be in the same position on multiple pages as a seperate instance, then we will append the page number to the layout position as comma page number, e.g. ""top,1"" to ensure uniqueness. " FORMAT "X(15)" INITIAL "" LABEL "Layout Position" POSITION 11 SQL-WIDTH 30 VALMSG "s_reference" HELP "Layout position" ORDER 100 ADD INDEX "XPKryc_object_instance" ON "ryc_object_instance" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "container_smartobject_obj" ASCENDING INDEX-FIELD "object_instance_obj" ASCENDING ADD INDEX "XIE1ryc_object_instance" ON "ryc_object_instance" AREA "Schema Area" INDEX-FIELD "smartobject_obj" ASCENDING ADD INDEX "XIE2ryc_object_instance" ON "ryc_object_instance" AREA "Schema Area" INDEX-FIELD "container_smartobject_obj" ASCENDING ADD INDEX "XIE3ryc_object_instance" ON "ryc_object_instance" AREA "Schema Area" INDEX-FIELD "container_smartobject_obj" ASCENDING INDEX-FIELD "smartobject_obj" ASCENDING INDEX-FIELD "layout_position" ASCENDING ADD INDEX "XIE4ryc_object_instance" ON "ryc_object_instance" AREA "Schema Area" INDEX-FIELD "object_instance_obj" ASCENDING ADD TABLE "ryc_attribute" AREA "Schema Area" DESCRIPTION "This table defines the attributes that may be allocated to smartobjects, e.g. size, position, window title, query, where clause, etc. They are used to defined the properties of dynamic objects, plus to dynamically alter the behaviour of static objects. Certain attributes are required for the application to function correctly and these will be set to system owned to prevent accidental deletion. Only users that are classified as able to maintain system owned information may manipulate this data. In many cases, the actual attribute label will need to match to a valid Progress supported attribute. Default attributes may be defined for the various smartobject types in the type attribute table, plus additional attributes allocated for each instance of a smartobject, thus the types define default bahaviour that may be overriden and extended for each instance. Due to the powerful feature of allowing attributes to be defined at various levels, most dynamic data about smartobjects will utilise attributes. Example areas that we will utilise attributes for include browser query, sort order and where clauses, container window titles, which window to run based on various button actions in a browser, e.g. add, modify, view, etc., status bar configuration, page enabling and disabling, field enabling and disabling by object instance, whether toolbar items are included in the menu, etc. " DUMP-NAME "rycat" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycattrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycattrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/rycatreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/rycatrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/rycatreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycattrigw.p" CRC "?" ADD FIELD "attribute_group_obj" OF "ryc_attribute" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Attribute Group Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Attribute group obj" DECIMALS 6 ORDER 10 ADD FIELD "attribute_type_tla" OF "ryc_attribute" AS character DESCRIPTION "This is a unique 3 letter acronym to define the attribute type, e.g. CHR = Character COL = Collection IMG = Image (so we can search/preview) FIL = File (so we can search) " FORMAT "X(3)" INITIAL "" LABEL "Attribute Type TLA" POSITION 3 SQL-WIDTH 6 VALMSG "s_tla" HELP "Attribute type three letter acronym" ORDER 30 ADD FIELD "attribute_label" OF "ryc_attribute" AS character DESCRIPTION "This is the name of the attribute. In many cases this will reflect the actual Progress name for the attribute." FORMAT "X(35)" INITIAL "" LABEL "Attribute Label" POSITION 4 SQL-WIDTH 70 VALMSG "s_name" HELP "Attribute label" ORDER 20 ADD FIELD "attribute_narrative" OF "ryc_attribute" AS character DESCRIPTION "This is a full description of the purpose and use of the attribute." FORMAT "X(500)" INITIAL "" LABEL "Attribute Narrative" POSITION 5 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Attribute narrative" ORDER 40 ADD FIELD "system_owned" OF "ryc_attribute" AS logical DESCRIPTION "If set to YES, this attribute may only be modified by users with a system owned flag. Certain attributes are required for the application to function correctly and these will be set to system owned to prevent accidental deletion. Only users that are classified as able to maintain system owned information may manipulate this data. In many cases, the actual attribute label will need to match to a valid Progress supported attribute." FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 50 ADD FIELD "attribute_obj" OF "ryc_attribute" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Attribute Obj" POSITION 7 SQL-WIDTH 21 VALMSG "o_obj" HELP "Attribute obj" DECIMALS 6 ORDER 60 ADD INDEX "XPKryc_attribute" ON "ryc_attribute" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "attribute_group_obj" ASCENDING INDEX-FIELD "attribute_label" ASCENDING INDEX-FIELD "attribute_type_tla" ASCENDING ADD INDEX "XAK2ryc_attribute" ON "ryc_attribute" AREA "Schema Area" UNIQUE INDEX-FIELD "attribute_label" ASCENDING ADD INDEX "XIE1ryc_attribute" ON "ryc_attribute" AREA "Schema Area" INDEX-FIELD "attribute_type_tla" ASCENDING ADD INDEX "XIE2ryc_attribute" ON "ryc_attribute" AREA "Schema Area" INDEX-FIELD "attribute_obj" ASCENDING ADD TABLE "ryc_attribute_value" AREA "Schema Area" DESCRIPTION "This entity associated attributes with object types, smartobjects, and smartobject instances, and specifies the value of the attribute. Where the attribute is associated with an object type or a smartobject, then the attribute value will reflect a default value. where the attribute is associated with an instance of a smartobject, then the value will reflect an actual value. When creating entries in this table for attributes associated with an object type, then the smart object and instance will be 0. When creating entries in the table for a smartobject, we will also populate the object type field to avoid having 0 in the key. Likewise when creating attributes for an object instance, we will populate the object type and the smartobject. This ensures effective use of the alternate keys. Note: We must be careful when looking for attributes associated with an object type to ensure we look for the specific object type and 0 values for the smartobject and instance fields. Where an attribute is defined as a collection, then attribute values can be linked together. The ""attribute_value"" field of the collection attribute_value record will be the number of elements in the collection, and this will then parent each of the attribute value records in the collection by collection sequence. Where attribute values are defined for object types and smartobjects, these values will be cascaded down to actual smartobject instances for performance reasons. Any future modifications of these values will also be cascaded down to all instances where the inherrited_value is set to YES, therefore ensuring we do not overwrite manual changes made at an instance level. " DUMP-NAME "rycav" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycavtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycavtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/rycavreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/rycavrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/rycavreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycavtrigw.p" CRC "?" ADD FIELD "attribute_value_obj" OF "ryc_attribute_value" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Attribute Value Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Attribute value obj" DECIMALS 6 ORDER 10 ADD FIELD "object_type_obj" OF "ryc_attribute_value" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Type Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object type obj" DECIMALS 6 ORDER 20 ADD FIELD "container_smartobject_obj" OF "ryc_attribute_value" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Container SmartObject Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Container SmartObject obj" DECIMALS 6 ORDER 30 ADD FIELD "smartobject_obj" OF "ryc_attribute_value" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "SmartObject Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "SmartObject obj" DECIMALS 6 ORDER 40 ADD FIELD "object_instance_obj" OF "ryc_attribute_value" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Instance Obj" POSITION 6 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object instance obj" DECIMALS 6 ORDER 50 ADD FIELD "collect_attribute_value_obj" OF "ryc_attribute_value" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Collect Attribute Value Obj" POSITION 7 SQL-WIDTH 21 VALMSG "o_obj" HELP "Collect attribute value obj" DECIMALS 6 ORDER 60 ADD FIELD "collection_sequence" OF "ryc_attribute_value" AS integer DESCRIPTION "If this attribute belings to a collection, then this is the sequence of the collection." FORMAT "->>>>>9" INITIAL "0" LABEL "Collection Sequence" POSITION 8 SQL-WIDTH 4 COLUMN-LABEL "Collection Seq." VALMSG "n_integer_6" HELP "Collection sequence" ORDER 70 ADD FIELD "inheritted_value" OF "ryc_attribute_value" AS logical DESCRIPTION "If set to YES, then the attribute value was inherited from its super class and has not been modified. Super class attribute values are cascaded to their subclasses for performance reasons. If the specific attribute value is modified then this flag will automatically be set to NO. If this flag is manually changed from NO to YES, then the attribute value will be automatically changed to the value from its super class. " FORMAT "YES/NO" INITIAL "YES" LABEL "Inheritted Value" POSITION 9 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Inheritted value" ORDER 80 ADD FIELD "constant_value" OF "ryc_attribute_value" AS logical DESCRIPTION "If set to YES, this value cannot be modified in any subclass. It is final (Rob says this is the java term for constant). " FORMAT "YES/NO" INITIAL "NO" LABEL "Constant Value" POSITION 10 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Constant value" ORDER 90 ADD FIELD "attribute_group_obj" OF "ryc_attribute_value" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Attribute Group Obj" POSITION 11 SQL-WIDTH 21 VALMSG "o_obj" HELP "Attribute group obj" DECIMALS 6 ORDER 100 ADD FIELD "attribute_type_tla" OF "ryc_attribute_value" AS character DESCRIPTION "This is a unique 3 letter acronym to define the attribute type, e.g. CHR = Character COL = Collection IMG = Image (so we can search/preview) FIL = File (so we can search) " FORMAT "X(3)" INITIAL "" LABEL "Attribute Type TLA" POSITION 12 SQL-WIDTH 6 VALMSG "s_tla" HELP "Attribute type three letter acronym" ORDER 110 ADD FIELD "attribute_label" OF "ryc_attribute_value" AS character DESCRIPTION "This is the name of the attribute. In many cases this will reflect the actual Progress name for the attribute." FORMAT "X(35)" INITIAL "" LABEL "Attribute Label" POSITION 13 SQL-WIDTH 70 VALMSG "s_name" HELP "Attribute label" ORDER 120 ADD FIELD "attribute_value" OF "ryc_attribute_value" AS character DESCRIPTION "Where this value is associated with an object type, this is the default value of the attribute for objects of this type. Likewise, where the value is associated with a smartobject, this is the default value of the attribute for the smartobject. Where the value is associated with a smartobject instance, this is the actual value of the attribute for the smartobject instance. It is possible that this could contain a delimited list of values, however we do support attribute collections. If this attribute is a collection, then the value will be the number of elements in the collection. Modification of the attribute value will automatically set the inherited flag to NO. If the constant value is set to YES and the inherited value is also set to YES, then this value cannot be modified. " FORMAT "X(70)" INITIAL "" LABEL "Attribute Value" POSITION 14 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Attribute value" ORDER 130 ADD FIELD "primary_smartobject_obj" OF "ryc_attribute_value" AS decimal DESCRIPTION "Attributes may be associated with object types, smartobjects and smartobject instances. If associated with an object type, the container smartobject and the smartobject will be 0. If assoiated with a smartobject, the container smartobject will be 0. If associated with an instance, the container smartobject will have a value. This field will contain the value of the container smartobject if not 0, otherwise the smartobject if that is not 0, otherwise 0. It is used as the replication key field when writing replication triggers to cascade changes to the version database, as the replication triggers could not handle the use of alternative fields (e.g. container smartobject_obj or smartobject_obj). The update of this field will be done in the write trigger. " FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Primary SmartObject Obj" POSITION 15 SQL-WIDTH 21 VALMSG "o_obj" HELP "Primary SmartObject obj" DECIMALS 6 ORDER 140 ADD INDEX "XPKryc_attribute_value" ON "ryc_attribute_value" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "attribute_value_obj" ASCENDING ADD INDEX "XAK1ryc_attribute_value" ON "ryc_attribute_value" AREA "Schema Area" UNIQUE INDEX-FIELD "object_type_obj" ASCENDING INDEX-FIELD "smartobject_obj" ASCENDING INDEX-FIELD "object_instance_obj" ASCENDING INDEX-FIELD "attribute_label" ASCENDING INDEX-FIELD "collect_attribute_value_obj" ASCENDING INDEX-FIELD "collection_sequence" ASCENDING INDEX-FIELD "container_smartobject_obj" ASCENDING ADD INDEX "XAK2ryc_attribute_value" ON "ryc_attribute_value" AREA "Schema Area" UNIQUE INDEX-FIELD "collect_attribute_value_obj" ASCENDING INDEX-FIELD "collection_sequence" ASCENDING INDEX-FIELD "attribute_label" ASCENDING ADD INDEX "XIE1ryc_attribute_value" ON "ryc_attribute_value" AREA "Schema Area" INDEX-FIELD "attribute_group_obj" ASCENDING INDEX-FIELD "attribute_type_tla" ASCENDING INDEX-FIELD "attribute_label" ASCENDING INDEX-FIELD "object_type_obj" ASCENDING ADD INDEX "XIE2ryc_attribute_value" ON "ryc_attribute_value" AREA "Schema Area" INDEX-FIELD "primary_smartobject_obj" ASCENDING INDEX-FIELD "attribute_group_obj" ASCENDING INDEX-FIELD "attribute_type_tla" ASCENDING INDEX-FIELD "attribute_label" ASCENDING ADD TABLE "ryc_action" AREA "Schema Area" DESCRIPTION "This table defines the actions available to place on a toolbar. Actions are organised into bands and whole bands are always allocated to toolbars rather than individual actions. An action however may be included in many bands. Example toolbar actions would include navigation - first, next, previous, last, tableio - add, delete, modify, view, copy, etc. etc. All actions in this table are standard actions available to all applications using the repository. " DUMP-NAME "rycac" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycactrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycactrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/rycacreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/rycacrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/rycacreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycactrigw.p" CRC "?" ADD FIELD "action_obj" OF "ryc_action" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Action Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Action obj" DECIMALS 6 ORDER 10 ADD FIELD "action_reference" OF "ryc_action" AS character DESCRIPTION "This is a unique reference field to identify the action. It could be automatically generated using ICF sequences, or if allocated manually could default to be the same as the action label. " FORMAT "X(15)" INITIAL "" LABEL "Action Reference" POSITION 3 SQL-WIDTH 30 VALMSG "s_reference" HELP "Action reference" ORDER 20 ADD FIELD "action_menu_label" OF "ryc_action" AS character DESCRIPTION "This is a potentially longer label for the button that would appear in a dynamic menu containing all buttons in an action group. It should contain ampersand (&) to act as the shortcut character. If left blank, this will default to the action label field. When translating the label, the ampersand will be removed." FORMAT "X(28)" INITIAL "" LABEL "Action Menu Label" POSITION 4 SQL-WIDTH 56 VALMSG "s_label" HELP "Action menu label" ORDER 40 ADD FIELD "action_label" OF "ryc_action" AS character DESCRIPTION "This is a short label for the button that would appear on the button as the button label in the event that the button has no image. It should contain ampersand (&) to act as the shortcut character. When translating the label, the ampersand will be removed. " FORMAT "X(28)" INITIAL "" LABEL "Action Label" POSITION 5 SQL-WIDTH 56 VALMSG "s_label" HELP "Action label" ORDER 30 ADD FIELD "security_token" OF "ryc_action" AS character DESCRIPTION "This will default to the action label, without the ampersand (&) but may be different if required. The security token is used to automatically enable and disable toolbar action according to user security permissions (via tokens). " FORMAT "X(28)" INITIAL "" LABEL "Security Token" POSITION 6 SQL-WIDTH 56 VALMSG "s_label" HELP "Security token" ORDER 60 ADD FIELD "action_accelerator" OF "ryc_action" AS character DESCRIPTION "Specifies a keyboard accelerator for this menu item. A keyboard accelerator is a key sometimes modified by SHIFT, CONTROL, or ALT that chooses a menu item even if the menu is not displayed. The value keylabel must be character-string expression that evaluates to a valid key label recognized by Progress, such as a, F1, or ALT-SHIFT-F1. If multiple toolbars are on a container and this action is included in multiple submenus, then this may not work. " FORMAT "X(10)" INITIAL "" LABEL "Action Accelerator" POSITION 7 SQL-WIDTH 20 VALMSG "s_code" HELP "Action accelerator" ORDER 50 ADD FIELD "image1_up_filename" OF "ryc_action" AS character DESCRIPTION "The filename of the normal image to display when the button is sensitive and not depressed. For flat buttons this is usally the only state that is required." FORMAT "X(70)" INITIAL "" LABEL "Image1 Up Filename" POSITION 8 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Image1 up filename" ORDER 110 ADD FIELD "image1_down_filename" OF "ryc_action" AS character DESCRIPTION "The filename of the normal image to display when the button is sensitive and pressed." FORMAT "X(70)" INITIAL "" LABEL "Image1 Down Filename" POSITION 9 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Image1 down filename" ORDER 120 ADD FIELD "image1_insensitive_filename" OF "ryc_action" AS character DESCRIPTION "The filename of the normal image to display when the button is insensitive (greyed out)." FORMAT "X(70)" INITIAL "" LABEL "Image1 Insensitive Filename" POSITION 10 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Image1 insensitive filename" ORDER 130 ADD FIELD "action_narration" OF "ryc_action" AS character DESCRIPTION "This is a free text field to describe exactly what the action does, where it may be used, how it works, etc." FORMAT "X(500)" INITIAL "" LABEL "Action Narration" POSITION 11 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Action narration" ORDER 80 ADD FIELD "image2_up_filename" OF "ryc_action" AS character DESCRIPTION "The filename of the secondary image to display when the button is sensitive and not depressed. For flat buttons this is usally the only state that is required. A secondary image is useful when the button has 2 main states, i.e. for a filter button it may be ticked if a filter is active, or have no tick when there is no active filter." FORMAT "X(70)" INITIAL "" LABEL "Image2 Up Filename" POSITION 12 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Image2 up filename" ORDER 140 ADD FIELD "image2_down_filename" OF "ryc_action" AS character DESCRIPTION "The filename of the secondary image to display when the button is sensitive and pressed. A secondary image is useful when the button has 2 main states, i.e. for a filter button it may be ticked if a filter is active, or have no tick when there is no active filter." FORMAT "X(70)" INITIAL "" LABEL "Image2 Down Filename" POSITION 13 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Image2 down filename" ORDER 150 ADD FIELD "image2_insensitive_filename" OF "ryc_action" AS character DESCRIPTION "The filename of the secondary image to display when the button is insensitive (greyed out). A secondary image is useful when the button has 2 main states, i.e. for a filter button it may be ticked if a filter is active, or have no tick when there is no active filter." FORMAT "X(70)" INITIAL "" LABEL "Image2 Insensitive Filename" POSITION 14 SQL-WIDTH 140 VALMSG "s_file_name" HELP "Image2 insensitive filename" ORDER 160 ADD FIELD "action_tooltip" OF "ryc_action" AS character DESCRIPTION "The tooltip to display for this toolbar button." FORMAT "X(70)" INITIAL "" LABEL "Action Tooltip" POSITION 15 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Action tooltip" ORDER 70 ADD FIELD "action_disabled" OF "ryc_action" AS logical DESCRIPTION "If set to YES, this button will be made insensitive." FORMAT "YES/NO" INITIAL "NO" LABEL "Action Disabled" POSITION 16 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Action disabled" ORDER 300 ADD FIELD "place_action_on_toolbar" OF "ryc_action" AS logical DESCRIPTION "If set to YES, this action will be placed on the toolbar, providing appropriate image files / labels are specified. If set to NO, this action will be excluded from the toolbar." FORMAT "YES/NO" INITIAL "YES" LABEL "Place Action On Toolbar" POSITION 17 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Place action on toolbar" ORDER 90 ADD FIELD "place_action_on_menu" OF "ryc_action" AS logical DESCRIPTION "If set to YES, this action will be placed on the toolbar menu using the action label. If set to NO, this action will not be included in the toolbar menu." FORMAT "YES/NO" INITIAL "YES" LABEL "Place Action On Menu" POSITION 18 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Place action on menu" ORDER 100 ADD FIELD "action_link" OF "ryc_action" AS character DESCRIPTION "This is the link across which to perform the specified on choose action for the action type. If the action type is RUN or PROPERTY then the procedure or property function is executed IN the handle of the object at the other end of the link. If the action type is PUBLISH then the event is published IN the handle of the object at the other end of the link. If no link is specified, the container is assumed. An example link may be tableio-target - note the full link name must be specified. If multiple links are required, then they will be comma delimited. " FORMAT "X(70)" INITIAL "" LABEL "Action Link" POSITION 19 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Action link" ORDER 190 ADD FIELD "action_type_code" OF "ryc_action" AS character DESCRIPTION "This is the type of action and determines the behaviour when the action is selected. The type can have a value of PUBLISH, RUN, PROPERTY, LAUNCH or nothing. PUBLISH means that a named event should be published when the item is selected. The event name is specified in the on_choose_action field. RUN means that an internal procedure should be run when the item is selected. The procedure name is specified in the on_choose_action field. PROPERTY means that the action should be realized as a state button and a menu item toggle, representing an ADM property of datatype logical. The name of the is stored in the on_choose_action field. Get and Set functions for the property will be used to display and modify its value. LAUNCH means launch the object (container) specified in the object_obj foreign key field and pass in the optional instance attribute if specified." FORMAT "X(10)" INITIAL "" LABEL "Action Type Code" POSITION 20 SQL-WIDTH 20 VALMSG "s_code" HELP "Action type code" ORDER 170 ADD FIELD "on_choose_action" OF "ryc_action" AS character DESCRIPTION "If the action_type_code is PUBLISH, then this is the event name to publish on choose of the action. If the action_type_code is RUN, then this is the internal procedure name to run on choose of the action. If the action_type_code is PROPERTY, then this is the property name to set (toggle) on choose of the action. If the action_type_code is LAUNCH then this is not reelvant as the program to launch is specified by the object_obj foreign key. " FORMAT "X(35)" INITIAL "" LABEL "On Choose Action" POSITION 21 SQL-WIDTH 70 VALMSG "s_name" HELP "On choose action" ORDER 180 ADD FIELD "action_parameter" OF "ryc_action" AS character DESCRIPTION "This is an optional parameter to pass to the procedure that subscribes to the event being published, or the internal procedure being run, depending on the action type. For PROPERTY action types this is not relevant. " FORMAT "X(70)" INITIAL "" LABEL "Action Parameter" POSITION 22 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Action parameter" ORDER 200 ADD FIELD "object_obj" OF "ryc_action" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Obj" POSITION 23 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object obj" DECIMALS 6 ORDER 230 ADD FIELD "instance_attribute_obj" OF "ryc_action" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Instance Attribute Obj" POSITION 24 SQL-WIDTH 21 VALMSG "o_obj" HELP "Instance attribute obj" DECIMALS 6 ORDER 240 ADD FIELD "initial_code" OF "ryc_action" AS character DESCRIPTION "This field defines a function that is called on menu drop of the action." FORMAT "X(70)" INITIAL "" LABEL "Initial Code" POSITION 25 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Initial code" ORDER 210 ADD FIELD "on_create_publish_event" OF "ryc_action" AS character DESCRIPTION "This attribute allows the developer to postpone the definition of certain actions until runtime. If specified, when this action is first defined the event name specified will be published in either the container or link specified. The event procedure used must take a single input parameter which will be passed in as the band name and action name, seperated by a comma. An example would be an action that would run an event during initialisation of the container that should build dynamic menus for any menu items linked to the container - meaning that each instance of a toolbar has its own specific dynamic menu items built when the toolbar is initialised. It can get information at runtime about the target-procedure and behave differently according to the instance of its use. The on choose action could be defined at this level, or defined individually when cretaing the dynamic menu options if required (by the procedure run). " FORMAT "X(35)" INITIAL "" LABEL "On Create Publish Event" POSITION 26 SQL-WIDTH 70 VALMSG "s_name" HELP "On create publish event" ORDER 220 ADD FIELD "propagate_links" OF "ryc_action" AS character DESCRIPTION "This contains a comma seperated list of links to propagate. The links must be specified with the -source or -target suffix to indicate the direction of the link being propagated. Selecting the action will propagate any specified links to/from the toolbar through to the program being run, thereby bypassing the toolbar. The link could also be further directed by the program to an object in the program if an additional link existed between the container and the object with the same link name. For example, we could have a link from a browserA to a toolbar called link1-target. The toolbar runs a new program B. If link1-target is in the list of propogate links, then a link will be created between browserA and programB. If programB has a subsequent link1-target link from its container to another object called viewerC, then the link will actually be routed from browserA to viewerC. This in effect is a generic pass through link mechanism. " FORMAT "X(70)" INITIAL "" LABEL "Propagate Links" POSITION 27 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Propagate links" ORDER 250 ADD FIELD "enable_state_list" OF "ryc_action" AS character DESCRIPTION "This is a comma delimited list of states under which this button should be specifically enabled. If this list is empty, the button will be enabled by default, otherwise it will be disabled by default and only enabled when the appropriate state is set." FORMAT "X(70)" INITIAL "" LABEL "Enable State List" POSITION 28 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Enable state list" ORDER 260 ADD FIELD "disable_state_list" OF "ryc_action" AS character DESCRIPTION "This is a comma delimited list of states under which this button should be specifically disabled. " FORMAT "X(70)" INITIAL "" LABEL "Disable State List" POSITION 29 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Disable state list" ORDER 270 ADD FIELD "view_state_list" OF "ryc_action" AS character DESCRIPTION "This is a comma delimited list of states under which this button should be specifically viewed. If this list is empty, the button will be viewed by default, otherwise it will only be hidden by default and only viewed when the appropriate state is set. This is used where a band contains buttons that should only be viewed in certain circumstances, e.g. an action panel with buttons ok, cancel, exit, apply, create, help. In a view mode the only buttons should be exit, help. In modify mode the buttons would be ok,cancel,apply,help. In create mode the buttons would be ok,cancel,create,help. " FORMAT "X(70)" INITIAL "" LABEL "View State List" POSITION 30 SQL-WIDTH 140 VALMSG "s_big_description" HELP "View state list" ORDER 280 ADD FIELD "system_owned" OF "ryc_action" AS logical DESCRIPTION "If set to YES, this action may only be modified by users with a system owned flag. Certain actions are required for the application to function and therefore may not be deleted by standard users. " FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 31 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 310 ADD FIELD "hide_state_list" OF "ryc_action" AS character DESCRIPTION "This is a comma delimited list of states under which this button should be specifically hidden. This is used where a band contains buttons that should only be viewed in certain circumstances, e.g. an action panel with buttons ok, cancel, exit, apply, create, help. In a view mode the only buttons should be exit, help. In modify mode the buttons would be ok,cancel,apply,help. In create mode the buttons would be ok,cancel,create,help. " FORMAT "X(70)" INITIAL "" LABEL "Hide State List" POSITION 32 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Hide state list" ORDER 290 ADD INDEX "XPKryc_action" ON "ryc_action" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "action_obj" ASCENDING ADD INDEX "XAK1ryc_action" ON "ryc_action" AREA "Schema Area" UNIQUE INDEX-FIELD "action_reference" ASCENDING ADD INDEX "XIE1ryc_action" ON "ryc_action" AREA "Schema Area" INDEX-FIELD "action_label" ASCENDING ADD INDEX "XIE2ryc_action" ON "ryc_action" AREA "Schema Area" INDEX-FIELD "action_menu_label" ASCENDING ADD INDEX "XIE3ryc_action" ON "ryc_action" AREA "Schema Area" INDEX-FIELD "security_token" ASCENDING ADD INDEX "XIE4ryc_action" ON "ryc_action" AREA "Schema Area" INDEX-FIELD "object_obj" ASCENDING ADD INDEX "XIE5ryc_action" ON "ryc_action" AREA "Schema Area" INDEX-FIELD "instance_attribute_obj" ASCENDING ADD TABLE "ryc_band" AREA "Schema Area" DESCRIPTION "This table provides a grouping mechanism for related toolbar actions, e.g. navigation, update, browse, desktop, system, etc. They equate to toolbar bands and each band will likely be demarkated with seperators for clarity. Bands are allocated to the dynamic toolbar using instance attributes." DUMP-NAME "rycbd" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycbdtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycbdtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/rycbdreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/rycbdrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/rycbdreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycbdtrigw.p" CRC "?" ADD FIELD "band_obj" OF "ryc_band" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Band Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Band obj" DECIMALS 6 ORDER 10 ADD FIELD "band_name" OF "ryc_band" AS character DESCRIPTION "This is a unique name to identify the band, e.g. navigation." FORMAT "X(28)" INITIAL "" LABEL "Band Name" POSITION 3 SQL-WIDTH 56 VALMSG "s_label" HELP "Band name" ORDER 20 ADD FIELD "band_narrative" OF "ryc_band" AS character DESCRIPTION "This is a full description of the aband describing its contents." FORMAT "X(500)" INITIAL "" LABEL "Band Narrative" POSITION 4 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Band narrative" ORDER 40 ADD FIELD "band_sequence" OF "ryc_band" AS integer DESCRIPTION "The sequence that the bands should appear within a toolbar. This facilitates the navigation band always coming first for example." FORMAT "->>9" INITIAL "0" LABEL "Band Sequence" POSITION 5 SQL-WIDTH 4 COLUMN-LABEL "Band Seq." VALMSG "n_integer_3" HELP "Band sequence" ORDER 30 ADD FIELD "band_disabled" OF "ryc_band" AS logical DESCRIPTION "If set to YES, buttons for this band will be disabled." FORMAT "YES/NO" INITIAL "NO" LABEL "Band Disabled" POSITION 6 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Band disabled" ORDER 50 ADD FIELD "band_submenu_label" OF "ryc_band" AS character DESCRIPTION "If the actions for a band must be replicated into the containers menu, then a band submenu label must be specified to indicate which submenu to add the actions to. If the submenu does not exist, it will be created and given the name specified here. If no submenu is specified for the band, the band actions will not be placed into the menus. The menu label specified should include an ampersand to specify the shortcut key. The ampersand will be removed from the label before translation. Multiple entries may be specified in the sybmenu label to create multiple levels of submenu, e.g. File,Navigation to create submenu called navigation under a submenu called file. A special case is to specify the submenu label as RULE indicating that this bands actions should simply be added to an existing submenu, seperated by a rule line. The submenu to use will be decided as follows: a) If the toolbar parent menu is a real submenu rather than the menubar then this submenu will be used. b) If the toolbar parent menu is the menubar, then we will use the first submenu on the menubar. If no submenus yet exist at all, then we will create one called FILE by default. When adding submenus for a toolbar, we need to determine where we should parent this toolbar submenus to, i.e which submenu to hook onto if any. We do this by looking for an attribute in the toolbar called ToolbarParentMenu which may indicate a secific submenu, e.g. customers. If this is empty, then the submenus will simply be added to the menubar." FORMAT "X(28)" INITIAL "" LABEL "Band Submenu Label" POSITION 7 SQL-WIDTH 56 VALMSG "s_label" HELP "Band submenu label" ORDER 60 ADD FIELD "system_owned" OF "ryc_band" AS logical DESCRIPTION "If set to YES, this band may only be modified by users with a system owned flag. Certain bands are required for the application to function and therefore may not be deleted by standard users. " FORMAT "YES/NO" INITIAL "NO" LABEL "System Owned" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "System owned" ORDER 110 ADD FIELD "band_alignment" OF "ryc_band" AS character DESCRIPTION "When the band appears on a toolbar, this is the alignment option to use as follows: LEF = Left justified (the default) RIG = Right justified CEN = Centred " FORMAT "X(3)" INITIAL "" LABEL "Band Alignment" POSITION 9 SQL-WIDTH 6 VALMSG "s_tla" HELP "Band alignment" ORDER 70 ADD FIELD "band_link" OF "ryc_band" AS character DESCRIPTION "If a link is specified for the band, then when the band is included in a toolbar, the link indicates that other objects in the container could use the link and dynamically modified the objects supported links accordingly. For example if the link is specified as tableio-target, then the toolbar will expect there to be a tableio-target in the container, so the toolbar itself is defined as a tableio-source. This is used in the Appbuilder for the link advisors to work." FORMAT "X(35)" INITIAL "" LABEL "Band Link" POSITION 10 SQL-WIDTH 70 VALMSG "s_name" HELP "Band link" ORDER 80 ADD FIELD "inherit_menu_icons" OF "ryc_band" AS logical DESCRIPTION "If set to YES, this band will inherit buttons from dynamic menu items added at runtime, i.e. any dynamic menu items that have an associated button will be added as actions to this band. Usually if this is set to YES, the band would be centered and contain no other actions. " FORMAT "YES/NO" INITIAL "NO" LABEL "Inherit Menu Icons" POSITION 11 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Inherit menu icons" ORDER 90 ADD FIELD "initial_state" OF "ryc_band" AS character DESCRIPTION "An initial state to be used when constructing the menu/toolbar for this band. For example, an action panel band may send an initial state of view to ensure the correct buttons are initially displayed. The appropriate enable,disable,hide and view state lists will then be actioned for the band. This may be overrriden by the toolbar initiial state set with the instance properties." FORMAT "X(35)" INITIAL "" LABEL "Initial State" POSITION 12 SQL-WIDTH 70 VALMSG "s_name" HELP "Initial state" ORDER 100 ADD INDEX "XPKryc_band" ON "ryc_band" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "band_obj" ASCENDING ADD INDEX "XAK1ryc_band" ON "ryc_band" AREA "Schema Area" UNIQUE INDEX-FIELD "band_name" ASCENDING ADD INDEX "XIE1ryc_band" ON "ryc_band" AREA "Schema Area" INDEX-FIELD "band_submenu_label" ASCENDING ADD INDEX "XIE2ryc_band" ON "ryc_band" AREA "Schema Area" INDEX-FIELD "band_sequence" ASCENDING ADD TABLE "ryc_smartlink" AREA "Schema Area" DESCRIPTION "This table defines the actual smartlinks between objects on a container, to facilitate object communication. The link name may be user defined, or automatically copied from the smartlink type for system supported links. If the source object instance is not specified, then the source s assumed to be the container. Likewise if the target object instance is not specified, then the target is assumed to be the container. Example links would be a tableio link between a smartbrowser and a smarttoolbar, a record link between a smartbrowser and a smartviewer, etc." DUMP-NAME "rycsm" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycsmtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycsmtrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/rycsmreplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/rycsmrepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/rycsmreplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycsmtrigw.p" CRC "?" ADD FIELD "smartlink_obj" OF "ryc_smartlink" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Smartlink Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Smartlink obj" DECIMALS 6 ORDER 10 ADD FIELD "container_smartobject_obj" OF "ryc_smartlink" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Container SmartObject Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Container SmartObject obj" DECIMALS 6 ORDER 20 ADD FIELD "smartlink_type_obj" OF "ryc_smartlink" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Smartlink Type Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Smartlink type obj" DECIMALS 6 ORDER 30 ADD FIELD "link_name" OF "ryc_smartlink" AS character DESCRIPTION "This is the actual link name. The link name may be user defined, or automatically copied from the smartlink type for system supported links. " FORMAT "X(28)" INITIAL "" LABEL "Link Name" POSITION 5 SQL-WIDTH 56 VALMSG "s_label" HELP "Link name" ORDER 40 ADD FIELD "source_object_instance_obj" OF "ryc_smartlink" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Source Object Instance Obj" POSITION 6 SQL-WIDTH 21 VALMSG "o_obj" HELP "Source object instance obj" DECIMALS 6 ORDER 50 ADD FIELD "target_object_instance_obj" OF "ryc_smartlink" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Target Object Instance Obj" POSITION 7 SQL-WIDTH 21 VALMSG "o_obj" HELP "Target object instance obj" DECIMALS 6 ORDER 60 ADD INDEX "XPKryc_smartlink" ON "ryc_smartlink" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "smartlink_obj" ASCENDING ADD INDEX "XAK1ryc_smartlink" ON "ryc_smartlink" AREA "Schema Area" UNIQUE INDEX-FIELD "container_smartobject_obj" ASCENDING INDEX-FIELD "source_object_instance_obj" ASCENDING INDEX-FIELD "link_name" ASCENDING INDEX-FIELD "target_object_instance_obj" ASCENDING ADD INDEX "XIE1ryc_smartlink" ON "ryc_smartlink" AREA "Schema Area" INDEX-FIELD "link_name" ASCENDING INDEX-FIELD "container_smartobject_obj" ASCENDING ADD INDEX "XIE2ryc_smartlink" ON "ryc_smartlink" AREA "Schema Area" INDEX-FIELD "smartlink_type_obj" ASCENDING INDEX-FIELD "container_smartobject_obj" ASCENDING ADD INDEX "XIE3ryc_smartlink" ON "ryc_smartlink" AREA "Schema Area" INDEX-FIELD "source_object_instance_obj" ASCENDING INDEX-FIELD "container_smartobject_obj" ASCENDING ADD INDEX "XIE4ryc_smartlink" ON "ryc_smartlink" AREA "Schema Area" INDEX-FIELD "target_object_instance_obj" ASCENDING INDEX-FIELD "container_smartobject_obj" ASCENDING ADD TABLE "ryc_page" AREA "Schema Area" DESCRIPTION "This table defines the actual pages in a container. All containers must at least have one page, which is page 0 and is always displayed. All objects on page 0 are always displayed. If there are no other pages, then no tab folder is visualised. Example pages could be Page 1, Page 2, Customer Details, etc." DUMP-NAME "rycpa" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycpatrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycpatrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/rycpareplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/rycparepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/rycpareplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycpatrigw.p" CRC "?" ADD FIELD "container_smartobject_obj" OF "ryc_page" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Container SmartObject Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Container SmartObject obj" DECIMALS 6 ORDER 10 ADD FIELD "page_obj" OF "ryc_page" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Page Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Page obj" DECIMALS 6 ORDER 20 ADD FIELD "layout_obj" OF "ryc_page" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Layout Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Layout obj" DECIMALS 6 ORDER 30 ADD FIELD "page_sequence" OF "ryc_page" AS integer DESCRIPTION "This is the actual page number and determines the sequence the pages are displayed. There must always be a page 0 and any objects on page 0 are always displayed. Page 0 does not appear on a tab folder. If there are no other pages, then no tab folder will be visualised. " FORMAT "->9" INITIAL "0" LABEL "Page Sequence" POSITION 5 SQL-WIDTH 4 COLUMN-LABEL "Page Seq." VALMSG "n_integer_2" HELP "Page sequence" ORDER 40 ADD FIELD "page_label" OF "ryc_page" AS character DESCRIPTION "This is the actual label to display on the tab folder detailing the contents of the page. Te label must be entered with an & denoting the shortcut key to select the page, e.g. &Details would facilitate pressing ALT-D to select the page. " FORMAT "X(28)" INITIAL "" LABEL "Page Label" POSITION 6 SQL-WIDTH 56 VALMSG "s_label" HELP "Page label" ORDER 50 ADD FIELD "security_token" OF "ryc_page" AS character DESCRIPTION "This will default to the page label, without the ampersand (&) but may be different if required. The security token is used to automatically enable and disable folder pages according to user security permissions (via tokens). " FORMAT "X(28)" INITIAL "" LABEL "Security Token" POSITION 7 SQL-WIDTH 56 VALMSG "s_label" HELP "Security token" ORDER 60 ADD FIELD "enable_on_create" OF "ryc_page" AS logical DESCRIPTION "If set to YES, this folder page will be enabled during an add operation. If set to NO, then this folder page will be disabled during an add operation. This will only affect the sensitivity of the page, not the objects contained on the page." FORMAT "YES/NO" INITIAL "YES" LABEL "Enable On Create" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Enable on create" ORDER 70 ADD FIELD "enable_on_modify" OF "ryc_page" AS logical DESCRIPTION "If set to YES, this folder page will be enabled during a modify operation. If set to NO, then this folder page will be disabled during a modify operation. This will only affect the sensitivity of the page, not the objects contained on the page." FORMAT "YES/NO" INITIAL "YES" LABEL "Enable On Modify" POSITION 9 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Enable on modify" ORDER 80 ADD FIELD "enable_on_view" OF "ryc_page" AS logical DESCRIPTION "If set to YES, this folder page will be enabled during an view operation. If set to NO, then this folder page will be disabled during an view operation. This will only affect the sensitivity of the page, not the objects contained on the page." FORMAT "YES/NO" INITIAL "YES" LABEL "Enable On View" POSITION 10 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Enable on view" ORDER 90 ADD INDEX "XPKryc_page" ON "ryc_page" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "container_smartobject_obj" ASCENDING INDEX-FIELD "page_obj" ASCENDING ADD INDEX "XAK1ryc_page" ON "ryc_page" AREA "Schema Area" UNIQUE INDEX-FIELD "container_smartobject_obj" ASCENDING INDEX-FIELD "page_sequence" ASCENDING ADD INDEX "XIE1ryc_page" ON "ryc_page" AREA "Schema Area" INDEX-FIELD "layout_obj" ASCENDING INDEX-FIELD "container_smartobject_obj" ASCENDING ADD INDEX "XIE2ryc_page" ON "ryc_page" AREA "Schema Area" INDEX-FIELD "page_obj" ASCENDING ADD TABLE "ryc_page_object" AREA "Schema Area" DESCRIPTION "This table defines the object instances that appear on a page of a container and in what sequence they should be created by the layout manager. How these objects communicate on the container is defined by the supported links table." DUMP-NAME "rycpo" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycpotrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycpotrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/rycporeplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/rycporepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/rycporeplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycpotrigw.p" CRC "?" ADD FIELD "page_object_obj" OF "ryc_page_object" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Page Object Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Page object obj" DECIMALS 6 ORDER 10 ADD FIELD "container_smartobject_obj" OF "ryc_page_object" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Container SmartObject Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Container SmartObject obj" DECIMALS 6 ORDER 20 ADD FIELD "page_obj" OF "ryc_page_object" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Page Obj" POSITION 4 SQL-WIDTH 21 VALMSG "o_obj" HELP "Page obj" DECIMALS 6 ORDER 30 ADD FIELD "page_object_sequence" OF "ryc_page_object" AS integer DESCRIPTION "This is the sequence in which to create the object instances on a page." FORMAT "->>9" INITIAL "0" LABEL "Page Object Sequence" POSITION 5 SQL-WIDTH 4 COLUMN-LABEL "Page Object Seq." VALMSG "n_integer_3" HELP "Page object sequence" ORDER 40 ADD FIELD "object_instance_obj" OF "ryc_page_object" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Object Instance Obj" POSITION 6 SQL-WIDTH 21 VALMSG "o_obj" HELP "Object instance obj" DECIMALS 6 ORDER 50 ADD INDEX "XPKryc_page_object" ON "ryc_page_object" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "page_object_obj" ASCENDING ADD INDEX "XAK1ryc_page_object" ON "ryc_page_object" AREA "Schema Area" UNIQUE INDEX-FIELD "container_smartobject_obj" ASCENDING INDEX-FIELD "page_obj" ASCENDING INDEX-FIELD "page_object_sequence" ASCENDING ADD INDEX "XIE1ryc_page_object" ON "ryc_page_object" AREA "Schema Area" INDEX-FIELD "container_smartobject_obj" ASCENDING INDEX-FIELD "object_instance_obj" ASCENDING INDEX-FIELD "page_obj" ASCENDING ADD TABLE "rym_data_version" AREA "Schema Area" DESCRIPTION "This table facilitates the generic storage of data version numbers without having to add a specific version number field to any tables that require version control. This will definitely be used in the context of versioning smartobjects, but may also be used to record a version number for any data, e.g. menu items, help, etc. The update of this table will be automated by the version control procedures if they are being used to control maintenance of the data. This information must be made available generically to a help about window in the context of smartobject versioning. The version number is the version number as at the time written by the versioning procedures. The data may have been subsequently changed by the user outside of the version control procedures, which is a situation we cannot generically hande. " DUMP-NAME "rymdv" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rymdvtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rymdvtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rymdvtrigw.p" CRC "?" ADD FIELD "data_version_obj" OF "rym_data_version" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Data Version Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Data version obj" DECIMALS 6 ORDER 10 ADD FIELD "related_entity_mnemonic" OF "rym_data_version" AS character DESCRIPTION "This is the FLA of the table containing the data record being version stamped." FORMAT "X(8)" INITIAL "" LABEL "Related Entity Mnemonic" POSITION 3 SQL-WIDTH 16 VALMSG "s_entity_mnemonic" HELP "Related entity mnemonic" ORDER 20 ADD FIELD "related_entity_key" OF "rym_data_version" AS character DESCRIPTION "This is the SCM object name from the table identified by the FLA. " FORMAT "X(70)" INITIAL "" LABEL "Related Entity Key" POSITION 4 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Related entity key" ORDER 30 ADD FIELD "data_version_number" OF "rym_data_version" AS integer DESCRIPTION "This is the current version number of this item of data as written by the versioning procedures." FORMAT "->>>>>9" INITIAL "0" LABEL "Data Version Number" POSITION 5 SQL-WIDTH 4 VALMSG "n_integer_6" HELP "Data version number" ORDER 40 ADD INDEX "XPKrym_data_version" ON "rym_data_version" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "data_version_obj" ASCENDING ADD INDEX "XAK1rym_data_version" ON "rym_data_version" AREA "Schema Area" UNIQUE INDEX-FIELD "related_entity_mnemonic" ASCENDING INDEX-FIELD "related_entity_key" ASCENDING ADD TABLE "ryc_band_action" AREA "Schema Area" DESCRIPTION "This table defines the actions allocated to bands. an action may be allocated to many bands, and a band may include many actions. This table facilitates the re-use of actions in many bands. If multiple bands are included on a toolbar, and duplicate actions occur then this will be ignored and the user must re-organise the band actions accordingly." DUMP-NAME "rycba" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rycbatrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rycbatrigd.p" CRC "?" TABLE-TRIGGER "REPLICATION-CREATE" OVERRIDE PROCEDURE "icf/trg/rycbareplc.p" CRC "?" TABLE-TRIGGER "REPLICATION-DELETE" OVERRIDE PROCEDURE "icf/trg/rycbarepld.p" CRC "?" TABLE-TRIGGER "REPLICATION-WRITE" OVERRIDE PROCEDURE "icf/trg/rycbareplw.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rycbatrigw.p" CRC "?" ADD FIELD "band_action_obj" OF "ryc_band_action" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Band Action Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Band action obj" DECIMALS 6 ORDER 10 ADD FIELD "band_obj" OF "ryc_band_action" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Band Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Band obj" DECIMALS 6 ORDER 20 ADD FIELD "band_action_sequence" OF "ryc_band_action" AS integer DESCRIPTION "The sequence that the buttons appear within an band." FORMAT "->>9" INITIAL "0" LABEL "Band Action Sequence" POSITION 4 SQL-WIDTH 4 COLUMN-LABEL "Band Action Seq." VALMSG "n_integer_3" HELP "Band action sequence" ORDER 30 ADD FIELD "action_obj" OF "ryc_band_action" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Action Obj" POSITION 5 SQL-WIDTH 21 VALMSG "o_obj" HELP "Action obj" DECIMALS 6 ORDER 40 ADD INDEX "XPKryc_band_action" ON "ryc_band_action" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "band_action_obj" ASCENDING ADD INDEX "XAK1ryc_band_action" ON "ryc_band_action" AREA "Schema Area" UNIQUE INDEX-FIELD "action_obj" ASCENDING INDEX-FIELD "band_obj" ASCENDING ADD INDEX "XIE1ryc_band_action" ON "ryc_band_action" AREA "Schema Area" INDEX-FIELD "band_obj" ASCENDING INDEX-FIELD "band_action_sequence" ASCENDING ADD TABLE "rym_wizard_menc" AREA "Schema Area" DESCRIPTION "This table captures wizard responses for the creation / modification of a standard ICF Dynamic Menu Controller object. It is used to forward engineer the object into the full Repository, generating all appropriate smartobject instances and attributes. Many assumptions are made regarding the look and feel of a standard ICF Menu Controller which significantly simplifies the data that must be captured. More complex specific modifications to an object may be made using the standard Repository Maintenance options. This table also facilitates generation of the object into different UI's, e.g. Java. " DUMP-NAME "rymwm" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rymwmtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rymwmtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rymwmtrigw.p" CRC "?" ADD FIELD "wizard_menc_obj" OF "rym_wizard_menc" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Wizard Menc Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Wizard menc obj" DECIMALS 6 ORDER 10 ADD FIELD "object_name" OF "rym_wizard_menc" AS character DESCRIPTION "The name of the logical object with no path or extension (as logical objects do not have these). The object does not have to exist anywhere at time of capture." FORMAT "X(35)" INITIAL "" LABEL "Object Name" POSITION 3 SQL-WIDTH 70 VALMSG "s_name" HELP "Object name" ORDER 40 ADD FIELD "product_code" OF "rym_wizard_menc" AS character DESCRIPTION "A unique code to identify the product this dynamic object belongs to. This code should correspond to a code that exists in gsc_product in the ICFDB database. This code is used when forward engineering the object into the full Repository, at which time it must exist or optionally be created in the gsc_product table." FORMAT "X(10)" INITIAL "" LABEL "Product Code" POSITION 4 SQL-WIDTH 20 VALMSG "s_code" HELP "Product code" ORDER 20 ADD FIELD "object_description" OF "rym_wizard_menc" AS character DESCRIPTION "A description of the object" FORMAT "X(35)" INITIAL "" LABEL "Object Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Object description" ORDER 50 ADD FIELD "product_module_code" OF "rym_wizard_menc" AS character DESCRIPTION "A unique code to identify the product module this dynamic object belongs to. This code should correspond to a code that exists in gsc_product_module in the ICFDB database, plus should be a product module that exists in the SCM tool. This code is used when forward engineering the object into the full Repository, at which time it must exist or optionally be created in the gsc_product_module table." FORMAT "X(10)" INITIAL "" LABEL "Product Module Code" POSITION 6 SQL-WIDTH 20 VALMSG "s_code" HELP "Product module code" ORDER 30 ADD FIELD "window_title" OF "rym_wizard_menc" AS character DESCRIPTION "The window title for the container." FORMAT "X(35)" INITIAL "" LABEL "Window Title" POSITION 7 SQL-WIDTH 70 VALMSG "s_description" HELP "Window title" ORDER 60 ADD FIELD "generated_date" OF "rym_wizard_menc" AS date DESCRIPTION "The date this object was last generated." FORMAT "99/99/9999" INITIAL "?" LABEL "Generated Date" POSITION 8 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Generated date" ORDER 70 ADD FIELD "generated_time" OF "rym_wizard_menc" AS integer DESCRIPTION "The time this object was last generated." FORMAT ">>>>9" INITIAL "0" LABEL "Generated Time" POSITION 9 SQL-WIDTH 4 VALMSG "n_time" HELP "Generated time" ORDER 80 ADD INDEX "XPKrym_wizard_menc" ON "rym_wizard_menc" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "wizard_menc_obj" ASCENDING ADD INDEX "XAK1rym_wizard_menc" ON "rym_wizard_menc" AREA "Schema Area" UNIQUE INDEX-FIELD "object_name" ASCENDING ADD INDEX "XAK2rym_wizard_menc" ON "rym_wizard_menc" AREA "Schema Area" UNIQUE INDEX-FIELD "product_code" ASCENDING INDEX-FIELD "product_module_code" ASCENDING INDEX-FIELD "object_name" ASCENDING ADD INDEX "XIE1rym_wizard_menc" ON "rym_wizard_menc" AREA "Schema Area" INDEX-FIELD "object_description" ASCENDING ADD TABLE "rym_wizard_objc" AREA "Schema Area" DESCRIPTION "This table captures wizard responses for the creation / modification of a standard ICF Dynamic Object Controller object. It is used to forward engineer the object into the full Repository, generating all appropriate smartobject instances and attributes. Many assumptions are made regarding the look and feel of a standard ICF Object Controller which significantly simplifies the data that must be captured. More complex specific modifications to an object may be made using the standard Repository Maintenance options. This table also facilitates generation of the object into different UI's, e.g. Java. " DUMP-NAME "rymwo" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rymwotrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rymwotrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rymwotrigw.p" CRC "?" ADD FIELD "wizard_objc_obj" OF "rym_wizard_objc" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Wizard Objc Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Wizard objc obj" DECIMALS 6 ORDER 10 ADD FIELD "object_name" OF "rym_wizard_objc" AS character DESCRIPTION "The name of the logical object with no path or extension (as logical objects do not have these). The object does not have to exist anywhere at time of capture." FORMAT "X(35)" INITIAL "" LABEL "Object Name" POSITION 3 SQL-WIDTH 70 VALMSG "s_name" HELP "Object name" ORDER 40 ADD FIELD "product_code" OF "rym_wizard_objc" AS character DESCRIPTION "A unique code to identify the product this dynamic object belongs to. This code should correspond to a code that exists in gsc_product in the ICFDB database. This code is used when forward engineering the object into the full Repository, at which time it must exist or optionally be created in the gsc_product table." FORMAT "X(10)" INITIAL "" LABEL "Product Code" POSITION 4 SQL-WIDTH 20 VALMSG "s_code" HELP "Product code" ORDER 20 ADD FIELD "object_description" OF "rym_wizard_objc" AS character DESCRIPTION "A description of the object" FORMAT "X(35)" INITIAL "" LABEL "Object Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Object description" ORDER 50 ADD FIELD "product_module_code" OF "rym_wizard_objc" AS character DESCRIPTION "A unique code to identify the product module this dynamic object belongs to. This code should correspond to a code that exists in gsc_product_module in the ICFDB database, plus should be a product module that exists in the SCM tool. This code is used when forward engineering the object into the full Repository, at which time it must exist or optionally be created in the gsc_product_module table." FORMAT "X(10)" INITIAL "" LABEL "Product Module Code" POSITION 6 SQL-WIDTH 20 VALMSG "s_code" HELP "Product module code" ORDER 30 ADD FIELD "window_title" OF "rym_wizard_objc" AS character DESCRIPTION "The window title for the container." FORMAT "X(35)" INITIAL "" LABEL "Window Title" POSITION 7 SQL-WIDTH 70 VALMSG "s_description" HELP "Window title" ORDER 60 ADD FIELD "generated_date" OF "rym_wizard_objc" AS date DESCRIPTION "The date this object was last generated." FORMAT "99/99/9999" INITIAL "?" LABEL "Generated Date" POSITION 8 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Generated date" ORDER 170 ADD FIELD "generated_time" OF "rym_wizard_objc" AS integer DESCRIPTION "The time this object was last generated." FORMAT ">>>>9" INITIAL "0" LABEL "Generated Time" POSITION 9 SQL-WIDTH 4 VALMSG "n_time" HELP "Generated time" ORDER 180 ADD FIELD "sdo_foreign_fields" OF "rym_wizard_objc" AS character DESCRIPTION "If the sdo_name is the child of some other data object and relies on parent key information from the parent data object to resolve its query, then the fields to map between the data objects should be specified in this property. This is a comma-separated paired list of database field names in the Data-Target and RowObject Temp-Table fields in the Data-Source that should be used for opening the Data-Target's database query using one or more key values from the Data-Source. A good example is joining a customer sdo with an order sdo and the foreign fields would be set to order.cust-num,cust-num. For SBOs, the temp-table is not refered to as rowobject, but rather as the SDO name within the SBO. In this case, the 2nd part of each foreign field pair would be qualified with the sdo name. Note that for each Foreign Field pair, the first entry is the name of the field in the database query for the Data-Target (the child or detail SDO in the parent-child or master-detail relationship), which is Order.CustNum in our example. This first entry is expressed as the database field name (optionally with the table qualifier) because that fieldname will actually be inserted into a where clause used to open the database query for the Data-Target, resulting in FOR EACH Order WHERE Order.CustNum = . The second entry in the pair is the name of the key field in the Data-Source SDO which is to be compared to the database field in the Target, or CustNum in our case. This must be the name of the field as it occurs in the Data-Source SDO column list (no DB table qualification unless SBO where we need an SDO qualification) because the Source SDO is providing that value from the SDO's temp-table, not straight out of the database. Each time the dataAvailable event is published by the Data-Source, indicating that its query on Customers has been re-positioned, the Data-Target (Order) SDO will request the value of the CustNum field from the Customer SDO and plug that into the Order query where clause as indicated above. " FORMAT "X(70)" INITIAL "" LABEL "Sdo Foreign Fields" POSITION 10 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Sdo foreign fields" ORDER 80 ADD FIELD "viewer_name" OF "rym_wizard_objc" AS character DESCRIPTION "The optional name of a viewer that will be displayed above the browser, maybe for specific filtering of the browser. This should be specified without a path and extension. At capture time it does not have to exist, but in order to forward engineer the folder window, the viewer must exist as a valid object in gsc_object in ICFDB. A static or dynamic viewer may be used. " FORMAT "X(35)" INITIAL "" LABEL "Viewer Name" POSITION 11 SQL-WIDTH 70 VALMSG "s_name" HELP "Viewer name" ORDER 90 ADD FIELD "sdo_name" OF "rym_wizard_objc" AS character DESCRIPTION "This is the data object the browser is linked to. It could be an SDO or an SBO. If this is an SBO, then the query_sdo_name field must contain the name of the SDO within the SBO to use for the browser query. This should be specified without a path and extension. At capture time it does not have to exist, but in order to forward engineer the object controller, the data object must exist as a valid object in gsc_object in ICFDB. " FORMAT "X(35)" INITIAL "" LABEL "Sdo Name" POSITION 12 SQL-WIDTH 70 VALMSG "s_name" HELP "Sdo name" ORDER 70 ADD FIELD "query_sdo_name" OF "rym_wizard_objc" AS character DESCRIPTION "In the event that the sdo_name is an SBO, then this field identifies the name of the SDO within the SBO to use as the query for the browser. If the sdo_name is not an SBO, then this field will be left blank. " FORMAT "X(35)" INITIAL "" LABEL "Query Sdo Name" POSITION 13 SQL-WIDTH 70 VALMSG "s_name" HELP "Query sdo name" ORDER 110 ADD FIELD "custom_super_procedure" OF "rym_wizard_objc" AS character DESCRIPTION "The name of a custom super procedure to attach to the browser when the browser is instantiated onto the container. A relative path and file extension must be specified for the super procedure. This facilitates the coding of specific business logic for a dynamic object. Your super procedure could include an initializeObject procedure that does a RUN SUPER, and after that subscribes to events in the containers toolbar. User defined menu items can then be attached to the conrtainer that publish the event to action the specific business logic." FORMAT "X(35)" INITIAL "" LABEL "Custom Super Procedure" POSITION 14 SQL-WIDTH 70 VALMSG "s_name" HELP "Custom super procedure" ORDER 120 ADD FIELD "browser_toolbar_parent_menu" OF "rym_wizard_objc" AS character DESCRIPTION "The parent submenu to use for the browsers toolbar, e.g. ""Attribute Group"". All menu options for the browsers toolbar options will be placed under this submenu if specified." FORMAT "X(28)" INITIAL "" LABEL "Browser Toolbar Parent Menu" POSITION 15 SQL-WIDTH 56 VALMSG "s_label" HELP "Browser toolbar parent menu" ORDER 130 ADD FIELD "browser_name" OF "rym_wizard_objc" AS character DESCRIPTION "The name of the browser that will be displayed on the object controller. This should be specified without a path and extension. At capture time it does not have to exist, but in order to forward engineer the object controller, the browser must exist as a valid object in gsc_object in ICFDB. A static or dynamic browser may be used. " FORMAT "X(35)" INITIAL "" LABEL "Browser Name" POSITION 16 SQL-WIDTH 70 VALMSG "s_name" HELP "Browser name" ORDER 100 ADD FIELD "window_title_field" OF "rym_wizard_objc" AS character DESCRIPTION "This is the field name whose value should be appended to the window title. The fieldname without a table prefix must be specified and should match a field in the SDO serving as the data source within the window." FORMAT "X(35)" INITIAL "" LABEL "Window Title Field" POSITION 17 SQL-WIDTH 70 VALMSG "s_name" HELP "Window title field" ORDER 150 ADD FIELD "page_layout" OF "rym_wizard_objc" AS character DESCRIPTION "The layout code for the page, the default is Top/Center/Bottom if not specified. This is used by the layout manager when resizing the window. " FORMAT "X(35)" INITIAL "" LABEL "Page Layout" POSITION 18 SQL-WIDTH 70 VALMSG "s_name" HELP "Page layout" ORDER 160 ADD FIELD "launch_container" OF "rym_wizard_objc" AS character DESCRIPTION "The object name of the container to launch when an action is taken on the selected record in the browser. This should be specified without a path and extension and should relate to a record in gsc_object in ICFDB. A dynamic or static container may be specified. The validity of the container to launch will not be checked until runtime. This will supersede the launch container specified for the browser. " FORMAT "X(35)" INITIAL "" LABEL "Launch Container" POSITION 19 SQL-WIDTH 70 VALMSG "s_description" HELP "Launch container" ORDER 140 ADD INDEX "XPKrym_wizard_objc" ON "rym_wizard_objc" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "wizard_objc_obj" ASCENDING ADD INDEX "XAK1rym_wizard_objc" ON "rym_wizard_objc" AREA "Schema Area" UNIQUE INDEX-FIELD "object_name" ASCENDING ADD INDEX "XAK2rym_wizard_objc" ON "rym_wizard_objc" AREA "Schema Area" UNIQUE INDEX-FIELD "product_code" ASCENDING INDEX-FIELD "product_module_code" ASCENDING INDEX-FIELD "object_name" ASCENDING ADD INDEX "XIE1rym_wizard_objc" ON "rym_wizard_objc" AREA "Schema Area" INDEX-FIELD "object_description" ASCENDING ADD INDEX "XIE2rym_wizard_objc" ON "rym_wizard_objc" AREA "Schema Area" INDEX-FIELD "sdo_name" ASCENDING ADD INDEX "XIE3rym_wizard_objc" ON "rym_wizard_objc" AREA "Schema Area" INDEX-FIELD "browser_name" ASCENDING ADD INDEX "XIE4rym_wizard_objc" ON "rym_wizard_objc" AREA "Schema Area" INDEX-FIELD "launch_container" ASCENDING ADD INDEX "XIE5rym_wizard_objc" ON "rym_wizard_objc" AREA "Schema Area" INDEX-FIELD "viewer_name" ASCENDING ADD TABLE "rym_wizard_fold" AREA "Schema Area" DESCRIPTION "This table captures wizard responses for the creation / modification of a standard ICF Dynamic Folder Window object. It is used to forward engineer the object into the full Repository, generating all appropriate smartobject instances and attributes. Many assumptions are made regarding the look and feel of a standard ICF Folder Window which significantly simplifies the data that must be captured. More complex specific modifications to an object may be made using the standard Repository Maintenance options. This table also facilitates generation of the object into different UI's, e.g. Java. " DUMP-NAME "rymwf" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rymwftrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rymwftrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rymwftrigw.p" CRC "?" ADD FIELD "wizard_fold_obj" OF "rym_wizard_fold" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Wizard Fold Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Wizard fold obj" DECIMALS 6 ORDER 10 ADD FIELD "object_name" OF "rym_wizard_fold" AS character DESCRIPTION "The name of the logical object with no path or extension (as logical objects do not have these). The object does not have to exist anywhere at time of capture." FORMAT "X(35)" INITIAL "" LABEL "Object Name" POSITION 3 SQL-WIDTH 70 VALMSG "s_name" HELP "Object name" ORDER 40 ADD FIELD "product_code" OF "rym_wizard_fold" AS character DESCRIPTION "A unique code to identify the product this dynamic object belongs to. This code should correspond to a code that exists in gsc_product in the ICFDB database. This code is used when forward engineering the object into the full Repository, at which time it must exist or optionally be created in the gsc_product table." FORMAT "X(10)" INITIAL "" LABEL "Product Code" POSITION 4 SQL-WIDTH 20 VALMSG "s_code" HELP "Product code" ORDER 20 ADD FIELD "object_description" OF "rym_wizard_fold" AS character DESCRIPTION "A description of the object" FORMAT "X(35)" INITIAL "" LABEL "Object Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Object description" ORDER 50 ADD FIELD "product_module_code" OF "rym_wizard_fold" AS character DESCRIPTION "A unique code to identify the product module this dynamic object belongs to. This code should correspond to a code that exists in gsc_product_module in the ICFDB database, plus should be a product module that exists in the SCM tool. This code is used when forward engineering the object into the full Repository, at which time it must exist or optionally be created in the gsc_product_module table." FORMAT "X(10)" INITIAL "" LABEL "Product Module Code" POSITION 6 SQL-WIDTH 20 VALMSG "s_code" HELP "Product module code" ORDER 30 ADD FIELD "window_title" OF "rym_wizard_fold" AS character DESCRIPTION "The window title for the container." FORMAT "X(35)" INITIAL "" LABEL "Window Title" POSITION 7 SQL-WIDTH 70 VALMSG "s_description" HELP "Window title" ORDER 60 ADD FIELD "generated_date" OF "rym_wizard_fold" AS date DESCRIPTION "The date this object was last generated." FORMAT "99/99/9999" INITIAL "?" LABEL "Generated Date" POSITION 8 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Generated date" ORDER 110 ADD FIELD "generated_time" OF "rym_wizard_fold" AS integer DESCRIPTION "The time this object was last generated." FORMAT ">>>>9" INITIAL "0" LABEL "Generated Time" POSITION 9 SQL-WIDTH 4 VALMSG "n_time" HELP "Generated time" ORDER 120 ADD FIELD "no_sdo" OF "rym_wizard_fold" AS logical DESCRIPTION "If set to YES, this folder window does not require an SDO/SBO and all updates will be done manually from the viewers. No data links will be created for this container and the container toolbar will have its bands set to: TxtAction,AstraWindow,AstraHelp,AstraAbout,AstraMenuExit,AstraFile As apposed to the standard band set of: Adm2Navigation,txttableio,Foldertableio,folderfunction,AstraFile,AstraHelp,AstraWindow,AstraAbout,AstraMenuExit The viewers on the container must then manually subscribe to toolbar events in the containers toolbar so that they can action an OK or CANCEL being pressed in the toolbar. They also subscribe the container toolbar to update states in the viewer so they can change the state of the toolbar into update mode when something is changed on the viewer. See the dynamic preferences or tranlation windows in ICF for examples (rydynprf1v.w, rydynprf2v.w, rydyntranv.w) " FORMAT "YES/NO" INITIAL "NO" LABEL "No Sdo" POSITION 10 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "No sdo" ORDER 80 ADD FIELD "default_mode" OF "rym_wizard_fold" AS character DESCRIPTION "The default mode for the container, e.g. add, modify, view. This will usually be inherited from the browser the folder was launched from, but may be useful when running direct from a menu. " FORMAT "X(28)" INITIAL "" LABEL "Default Mode" POSITION 11 SQL-WIDTH 56 VALMSG "s_label" HELP "Default mode" ORDER 70 ADD FIELD "viewer_link_name" OF "rym_wizard_fold" AS character DESCRIPTION "This is a manual user link to create from the primary viewer to all other viewers with the same (or no) sdo specified. " FORMAT "X(28)" INITIAL "" LABEL "Viewer Link Name" POSITION 12 SQL-WIDTH 56 VALMSG "s_label" HELP "Viewer link name" ORDER 90 ADD FIELD "page_layout" OF "rym_wizard_fold" AS character DESCRIPTION "The default layout code for each page, the default is Top/Center/Bottom if not specified. This is used by the layout manager when resizing the window. " FORMAT "X(35)" INITIAL "" LABEL "Page Layout" POSITION 13 SQL-WIDTH 70 VALMSG "s_name" HELP "Page layout" ORDER 100 ADD INDEX "XPKrym_wizard_fold" ON "rym_wizard_fold" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "wizard_fold_obj" ASCENDING ADD INDEX "XAK1rym_wizard_fold" ON "rym_wizard_fold" AREA "Schema Area" UNIQUE INDEX-FIELD "object_name" ASCENDING ADD INDEX "XAK2rym_wizard_fold" ON "rym_wizard_fold" AREA "Schema Area" UNIQUE INDEX-FIELD "product_code" ASCENDING INDEX-FIELD "product_module_code" ASCENDING INDEX-FIELD "object_name" ASCENDING ADD INDEX "XIE1rym_wizard_fold" ON "rym_wizard_fold" AREA "Schema Area" INDEX-FIELD "object_description" ASCENDING ADD TABLE "rym_wizard_fold_page" AREA "Schema Area" DESCRIPTION "This table defines the pages of the folder window, the objects that should appear on the page and attributes about the page itself. How the objects are linked and organised on the page will be defaulted according to rules for a standard dynamic folder window." DUMP-NAME "rymfp" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rymfptrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rymfptrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rymfptrigw.p" CRC "?" ADD FIELD "wizard_fold_obj" OF "rym_wizard_fold_page" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Wizard Fold Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Wizard fold obj" DECIMALS 6 ORDER 10 ADD FIELD "wizard_fold_page_obj" OF "rym_wizard_fold_page" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Wizard Fold Page Obj" POSITION 3 SQL-WIDTH 21 VALMSG "o_obj" HELP "Wizard fold page obj" DECIMALS 6 ORDER 20 ADD FIELD "page_number" OF "rym_wizard_fold_page" AS integer DESCRIPTION "This is the sequence number for the pages, starting at 1." FORMAT "->>9" INITIAL "0" LABEL "Page Number" POSITION 4 SQL-WIDTH 4 VALMSG "n_integer_3" HELP "Page number" ORDER 30 ADD FIELD "page_label" OF "rym_wizard_fold_page" AS character DESCRIPTION "This is the screen label for the page. It should contain an ampersand (&) if a shortcut is required for the page." FORMAT "X(28)" INITIAL "" LABEL "Page Label" POSITION 5 SQL-WIDTH 56 VALMSG "s_label" HELP "Page label" ORDER 40 ADD FIELD "viewer_object_name" OF "rym_wizard_fold_page" AS character DESCRIPTION "The name of the viewer that will be displayed on the folder page. If a viewer and browser are specified on a folder page, then the viewer will always be placed above the browser. This should be specified without a path and extension. At capture time it does not have to exist, but in order to forward engineer the folder window, the viewer must exist as a valid object in gsc_object in ICFDB. A static or dynamic viewer may be used. " FORMAT "X(35)" INITIAL "" LABEL "Viewer Object Name" POSITION 6 SQL-WIDTH 70 VALMSG "s_name" HELP "Viewer object name" ORDER 60 ADD FIELD "page_layout" OF "rym_wizard_fold_page" AS character DESCRIPTION "The default layout code for each page, the default is Top/Center/Bottom if this page contains a browser or Everything Centred if it contains a viewer. This is used by the layout manager when resizing the window. " FORMAT "X(35)" INITIAL "" LABEL "Page Layout" POSITION 7 SQL-WIDTH 70 VALMSG "s_name" HELP "Page layout" ORDER 50 ADD FIELD "primary_viewer" OF "rym_wizard_fold_page" AS logical DESCRIPTION "If a viewer is specified for the page, this flag indicates whether this is the primary viewer for the folder window. Only one viewer should be specified as the primary viewer on a folder window per SDO. All other viewers on the folder with the same SDO will be linked to the primary viewer with a group assign link." FORMAT "YES/NO" INITIAL "NO" LABEL "Primary Viewer" POSITION 8 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Primary viewer" ORDER 70 ADD FIELD "browser_object_name" OF "rym_wizard_fold_page" AS character DESCRIPTION "The name of the browser that will be displayed on the folder page. If a browser is specified, then an SDO/SBO must also be specified. If the browser is linked to an SBO, then the query_object_name must also be specified to identify the SDO within the SBO to use for the browser query. If a viewer and browser are specified on a folder page, then the viewer will always be placed above the browser. This should be specified without a path and extension. At capture time it does not have to exist, but in order to forward engineer the folder window, the browser must exist as a valid object in gsc_object in ICFDB. A static or dynamic browser may be used. " FORMAT "X(35)" INITIAL "" LABEL "Browser Object Name" POSITION 9 SQL-WIDTH 70 VALMSG "s_name" HELP "Browser object name" ORDER 100 ADD FIELD "viewer_toolbar_parent_menu" OF "rym_wizard_fold_page" AS character DESCRIPTION "The parent submenu to use for the viewers toolbar if any. The viewer will have a toolbar above it if it is a primary viewer and is linked to an sdo on the folder window itself. The submenu should reflect the data in the viewer, e.g. Attribute Group. All menu options for the viewers toolbar options will be placed under this submenu if specified. " FORMAT "X(28)" INITIAL "" LABEL "Viewer Toolbar Parent Menu" POSITION 10 SQL-WIDTH 56 VALMSG "s_label" HELP "Viewer toolbar parent menu" ORDER 80 ADD FIELD "sdo_object_name" OF "rym_wizard_fold_page" AS character DESCRIPTION "If a browser is specified on the page, then the SDO/SBO object name must also be specified for the data source of the browser. If a viewer is specified on the page, then this should be the SDO/SBO that this viewer is linked to, or blank to link the viewer to the external sdo through the container. If the sdo_object_name is an SBO and a browser exists on the page, then the query_object_name must also be specified. If a viewer is on the page, then the viewer_data_source_name and the viewer_update_target_names must also be specified. All viewers with the same SDO/SBO will be group-assigned together. Explain further for SBO functionality.... This should be specified without a path and extension. At capture time it does not have to exist, but in order to forward engineer the folder, the sdo must exist as a valid object in gsc_object in ICFDB. " FORMAT "X(35)" INITIAL "" LABEL "Sdo Object Name" POSITION 11 SQL-WIDTH 70 VALMSG "s_name" HELP "Sdo object name" ORDER 120 ADD FIELD "link_viewer_to_sdo" OF "rym_wizard_fold_page" AS logical DESCRIPTION "If the page contains a viewer, this flag indicates whether the viewer is linked to the SDO /SBO specified on the page. Normally this would be true, unless the viewer is simply a non db-field viewer used to filter the browser that is also on the page. Even if the SDO/SBO name is blank indicating an external SDO/SBO, if this viewer requires data from an SDO/SBO, this flag should be set to YES." FORMAT "YES/NO" INITIAL "YES" LABEL "Link Viewer to Sdo" POSITION 12 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_yesno" HELP "Link viewer to sdo" ORDER 90 ADD FIELD "browser_toolbar_parent_menu" OF "rym_wizard_fold_page" AS character DESCRIPTION "The parent submenu to use for the browsers toolbar, e.g. ""Attribute Group"". All menu options for the browsers toolbar options will be placed under this submenu if specified. This is only relevant if the page contains a browser." FORMAT "X(28)" INITIAL "" LABEL "Browser Toolbar Parent Menu" POSITION 13 SQL-WIDTH 56 VALMSG "s_label" HELP "Browser toolbar parent menu" ORDER 110 ADD FIELD "static_object" OF "rym_wizard_fold_page" AS logical DESCRIPTION "field not used currently" FORMAT "YES/NO" INITIAL "NO" LABEL "Static Object" POSITION 14 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Static object" ORDER 200 ADD FIELD "sdo_foreign_fields" OF "rym_wizard_fold_page" AS character DESCRIPTION "If the sdo_object_name is the child of some other data object and relies on parent key information from the parent data object to resolve its query, then the fields to map between the data objects should be specified in this property. This is a comma-separated paired list of database field names in the Data-Target and RowObject Temp-Table fields in the Data-Source that should be used for opening the Data-Target's database query using one or more key values from the Data-Source. A good example is joining a customer sdo with an order sdo and the foreign fields would be set to order.cust-num,cust-num. For SBOs, the temp-table is not refered to as rowobject, but rather as the SDO name within the SBO. In this case, the 2nd part of each foreign field pair would be qualified with the sdo name. Note that for each Foreign Field pair, the first entry is the name of the field in the database query for the Data-Target (the child or detail SDO in the parent-child or master-detail relationship), which is Order.CustNum in our example. This first entry is expressed as the database field name (optionally with the table qualifier) because that fieldname will actually be inserted into a where clause used to open the database query for the Data-Target, resulting in FOR EACH Order WHERE Order.CustNum = . The second entry in the pair is the name of the key field in the Data-Source SDO which is to be compared to the database field in the Target, or CustNum in our case. This must be the name of the field as it occurs in the Data-Source SDO column list (no DB table qualification unless SBO where we need an SDO qualification) because the Source SDO is providing that value from the SDO's temp-table, not straight out of the database. Each time the dataAvailable event is published by the Data-Source, indicating that its query on Customers has been re-positioned, the Data-Target (Order) SDO will request the value of the CustNum field from the Customer SDO and plug that into the Order query where clause as indicated above. " FORMAT "X(70)" INITIAL "" LABEL "Sdo Foreign Fields" POSITION 15 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Sdo foreign fields" ORDER 140 ADD FIELD "parent_sdo_object_name" OF "rym_wizard_fold_page" AS character DESCRIPTION "If the page contains an sdo/sbo, then this field optionally specifies the sdo/sbo on another page that this sdo/sbo is the child of. If this field is specified then the foreign fields must also be specified. If this field is left blank and foreign fields are specified, then pass through links will be added from the container for an external sdo. This should be specified without a path and extension. At capture time it does not have to exist, but in order to forward engineer the folder, the sdo must exist as a valid object in gsc_object in ICFDB. " FORMAT "X(35)" INITIAL "" LABEL "Parent Sdo Object Name" POSITION 16 SQL-WIDTH 70 VALMSG "s_name" HELP "Parent sdo object name" ORDER 130 ADD FIELD "query_sdo_name" OF "rym_wizard_fold_page" AS character DESCRIPTION "In the event that the sdo_object_name is an SBO, then this field identifies the name of the SDO within the SBO to use as the query for the browser. If the sdo_object_name is not an SBO, then this field will be left blank. " FORMAT "X(35)" INITIAL "" LABEL "Query Sdo Name" POSITION 17 SQL-WIDTH 70 VALMSG "s_name" HELP "Query sdo name" ORDER 150 ADD FIELD "window_title_field" OF "rym_wizard_fold_page" AS character DESCRIPTION "This is the field name whose value should be appended to the window title. The fieldname without a table prefix must be specified and should match a field in the SDO serving as the data source within the window." FORMAT "X(35)" INITIAL "" LABEL "Window Title Field" POSITION 18 SQL-WIDTH 70 VALMSG "s_name" HELP "Window title field" ORDER 180 ADD FIELD "viewer_data_source_names" OF "rym_wizard_fold_page" AS character DESCRIPTION "In the event that the sdo_object_name is an SBO and there is a viewer on the page, then this field identifies a comma delimited list of SDO's that are referenced by fields on the viewer. " FORMAT "X(500)" INITIAL "" LABEL "Viewer Data Source Names" POSITION 19 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Viewer data source names" ORDER 160 ADD FIELD "viewer_update_target_names" OF "rym_wizard_fold_page" AS character DESCRIPTION "In the event that the sdo_object_name is an SBO and there is a viewer on the page, then this field identifies a comma delimited list of SDO's that are updated by fields on the viewer. In the majority of cases, this is a single SDO. The only case where this is more than one is for one to one relationships inside an SBO. " FORMAT "X(500)" INITIAL "" LABEL "Viewer Update Target Names" POSITION 20 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Viewer update target names" ORDER 170 ADD FIELD "custom_super_procedure" OF "rym_wizard_fold_page" AS character DESCRIPTION "The name of a custom super procedure to attach to the browser or viewer when it is instantiated onto the container. A relative path and file extension must be specified for the super procedure. This facilitates the coding of specific business logic for a dynamic object. Your super procedure could include an initializeObject procedure that does a RUN SUPER, and after that subscribes to events in the containers toolbar. User defined menu items can then be attached to the conrtainer that publish the event to action the specific business logic." FORMAT "X(35)" INITIAL "" LABEL "Custom Super Procedure" POSITION 21 SQL-WIDTH 70 VALMSG "s_name" HELP "Custom super procedure" ORDER 190 ADD INDEX "XPKrym_wizard_fold_page" ON "rym_wizard_fold_page" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "wizard_fold_obj" ASCENDING INDEX-FIELD "wizard_fold_page_obj" ASCENDING ADD INDEX "XAK1rym_wizard_fold_page" ON "rym_wizard_fold_page" AREA "Schema Area" UNIQUE INDEX-FIELD "wizard_fold_obj" ASCENDING INDEX-FIELD "page_number" ASCENDING ADD INDEX "XIE1rym_wizard_fold_page" ON "rym_wizard_fold_page" AREA "Schema Area" INDEX-FIELD "viewer_object_name" ASCENDING ADD INDEX "XIE2rym_wizard_fold_page" ON "rym_wizard_fold_page" AREA "Schema Area" INDEX-FIELD "browser_object_name" ASCENDING ADD INDEX "XIE3rym_wizard_fold_page" ON "rym_wizard_fold_page" AREA "Schema Area" INDEX-FIELD "sdo_object_name" ASCENDING ADD INDEX "XIE4rym_wizard_fold_page" ON "rym_wizard_fold_page" AREA "Schema Area" INDEX-FIELD "wizard_fold_obj" ASCENDING INDEX-FIELD "sdo_object_name" ASCENDING INDEX-FIELD "primary_viewer" ASCENDING ADD INDEX "XIE5rym_wizard_fold_page" ON "rym_wizard_fold_page" AREA "Schema Area" INDEX-FIELD "wizard_fold_page_obj" ASCENDING ADD TABLE "rym_wizard_view" AREA "Schema Area" DESCRIPTION "This table captures wizard responses for the creation / modification of a standard ICF Dynamic Viewer object. It is used to forward engineer the object into the full Repository, generating all appropriate smartobject instances and attributes. Many assumptions are made regarding the look and feel of a standard ICF Viewer which significantly simplifies the data that must be captured. More complex specific modifications to an object may be made using the standard Repository Maintenance options. This table also facilitates generation of the object into different UI's, e.g. Java. " DUMP-NAME "rymwv" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rymwvtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rymwvtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rymwvtrigw.p" CRC "?" ADD FIELD "wizard_view_obj" OF "rym_wizard_view" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Wizard View Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Wizard view obj" DECIMALS 6 ORDER 10 ADD FIELD "object_name" OF "rym_wizard_view" AS character DESCRIPTION "The name of the logical object with no path or extension (as logical objects do not have these). The object does not have to exist anywhere at time of capture." FORMAT "X(35)" INITIAL "" LABEL "Object Name" POSITION 3 SQL-WIDTH 70 VALMSG "s_name" HELP "Object name" ORDER 40 ADD FIELD "product_code" OF "rym_wizard_view" AS character DESCRIPTION "A unique code to identify the product this dynamic object belongs to. This code should correspond to a code that exists in gsc_product in the ICFDB database. This code is used when forward engineering the object into the full Repository, at which time it must exist or optionally be created in the gsc_product table." FORMAT "X(10)" INITIAL "" LABEL "Product Code" POSITION 4 SQL-WIDTH 20 VALMSG "s_code" HELP "Product code" ORDER 20 ADD FIELD "object_description" OF "rym_wizard_view" AS character DESCRIPTION "A description of the object" FORMAT "X(35)" INITIAL "" LABEL "Object Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Object description" ORDER 50 ADD FIELD "product_module_code" OF "rym_wizard_view" AS character DESCRIPTION "A unique code to identify the product module this dynamic object belongs to. This code should correspond to a code that exists in gsc_product_module in the ICFDB database, plus should be a product module that exists in the SCM tool. This code is used when forward engineering the object into the full Repository, at which time it must exist or optionally be created in the gsc_product_module table." FORMAT "X(10)" INITIAL "" LABEL "Product Module Code" POSITION 6 SQL-WIDTH 20 VALMSG "s_code" HELP "Product module code" ORDER 30 ADD FIELD "generated_date" OF "rym_wizard_view" AS date DESCRIPTION "The date this object was last generated." FORMAT "99/99/9999" INITIAL "?" LABEL "Generated Date" POSITION 7 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Generated date" ORDER 120 ADD FIELD "generated_time" OF "rym_wizard_view" AS integer DESCRIPTION "The time this object was last generated." FORMAT ">>>>9" INITIAL "0" LABEL "Generated Time" POSITION 8 SQL-WIDTH 4 VALMSG "n_time" HELP "Generated time" ORDER 130 ADD FIELD "viewer_data_source_names" OF "rym_wizard_view" AS character DESCRIPTION "In the event that the sdo_name is an SBO, then this field identifies a comma delimited list of SDO's that are referenced by fields on the viewer. " FORMAT "X(500)" INITIAL "" LABEL "Viewer Data Source Names" POSITION 9 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Viewer data source names" ORDER 70 ADD FIELD "viewer_update_target_names" OF "rym_wizard_view" AS character DESCRIPTION "In the event that the sdo_name is an SBO, then this field identifies a comma delimited list of SDO's that are updated by fields on the viewer. In the majority of cases, this is a single SDO. The only case where this is more than one is for one to one relationships inside an SBO. " FORMAT "X(500)" INITIAL "" LABEL "Viewer Update Target Names" POSITION 10 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Viewer update target names" ORDER 80 ADD FIELD "window_title_field" OF "rym_wizard_view" AS character DESCRIPTION "This is the field name whose value should be appended to the window title. The fieldname without a table prefix must be specified and should match a field in the SDO serving as the data source within the window." FORMAT "X(35)" INITIAL "" LABEL "Window Title Field" POSITION 11 SQL-WIDTH 70 VALMSG "s_name" HELP "Window title field" ORDER 90 ADD FIELD "custom_super_procedure" OF "rym_wizard_view" AS character DESCRIPTION "The name of a custom super procedure to attach to the viewer when the viewer is instantiated onto a container. A relative path and file extension must be specified for the super procedure. This facilitates the coding of specific business logic for a dynamic object. Your super procedure could include an initializeObject procedure that does a RUN SUPER, and after that subscribes to events in the containers toolbar. User defined menu items can then be attached to the conrtainer that publish the event to action the specific business logic." FORMAT "X(35)" INITIAL "" LABEL "Custom Super Procedure" POSITION 12 SQL-WIDTH 70 VALMSG "s_name" HELP "Custom super procedure" ORDER 100 ADD FIELD "selected_fields" OF "rym_wizard_view" AS character DESCRIPTION "A list of selected fields chr(4) delimited. within each entry, the following entries exist chr(3) delimited: field number field name field enabled " FORMAT "X(3000)" INITIAL "" LABEL "Selected Fields" POSITION 13 SQL-WIDTH 6000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL LARGE MAX-CHARS 3000" VALMSG "s_big_text_block" HELP "Selected fields" ORDER 110 ADD FIELD "sdo_name" OF "rym_wizard_view" AS character DESCRIPTION "The name of the SDO/SBO that will be used as the data source for the viewer. This is only required in order to select fields for the viewer. The actual SDO/SBO linked to the viewer at runtime may be different. A valid existing SDO/SBO must be specified, with a relative path and extension to enable the SDO/SBO to be located on the operating system. If a SBO is specified, then the viewer_data_source_names and the viewer_update_target_names must also be specified." FORMAT "X(35)" INITIAL "" LABEL "Sdo Name" POSITION 14 SQL-WIDTH 70 VALMSG "s_name" HELP "Sdo name" ORDER 60 ADD INDEX "XPKrym_wizard_view" ON "rym_wizard_view" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "wizard_view_obj" ASCENDING ADD INDEX "XAK1rym_wizard_view" ON "rym_wizard_view" AREA "Schema Area" UNIQUE INDEX-FIELD "object_name" ASCENDING ADD INDEX "XAK2rym_wizard_view" ON "rym_wizard_view" AREA "Schema Area" UNIQUE INDEX-FIELD "product_code" ASCENDING INDEX-FIELD "product_module_code" ASCENDING INDEX-FIELD "object_name" ASCENDING ADD INDEX "XIE1rym_wizard_view" ON "rym_wizard_view" AREA "Schema Area" INDEX-FIELD "object_description" ASCENDING ADD INDEX "XIE2rym_wizard_view" ON "rym_wizard_view" AREA "Schema Area" INDEX-FIELD "sdo_name" ASCENDING ADD TABLE "rym_wizard_brow" AREA "Schema Area" DESCRIPTION "This table captures wizard responses for the creation / modification of a standard ICF Dynamic Browser object. It is used to forward engineer the object into the full Repository, generating all appropriate smartobject instances and attributes. Many assumptions are made regarding the look and feel of a standard ICF Browser which significantly simplifies the data that must be captured. More complex specific modifications to an object may be made using the standard Repository Maintenance options. This table also facilitates generation of the object into different UI's, e.g. Java. " DUMP-NAME "rymwb" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rymwbtrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rymwbtrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rymwbtrigw.p" CRC "?" ADD FIELD "wizard_brow_obj" OF "rym_wizard_brow" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Wizard Brow Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Wizard brow obj" DECIMALS 6 ORDER 10 ADD FIELD "object_name" OF "rym_wizard_brow" AS character DESCRIPTION "The name of the logical object with no path or extension (as logical objects do not have these). The object does not have to exist anywhere at time of capture." FORMAT "X(35)" INITIAL "" LABEL "Object Name" POSITION 3 SQL-WIDTH 70 VALMSG "s_name" HELP "Object name" ORDER 40 ADD FIELD "product_code" OF "rym_wizard_brow" AS character DESCRIPTION "A unique code to identify the product this dynamic object belongs to. This code should correspond to a code that exists in gsc_product in the ICFDB database. This code is used when forward engineering the object into the full Repository, at which time it must exist or optionally be created in the gsc_product table." FORMAT "X(10)" INITIAL "" LABEL "Product Code" POSITION 4 SQL-WIDTH 20 VALMSG "s_code" HELP "Product code" ORDER 20 ADD FIELD "object_description" OF "rym_wizard_brow" AS character DESCRIPTION "A description of the object" FORMAT "X(35)" INITIAL "" LABEL "Object Description" POSITION 5 SQL-WIDTH 70 VALMSG "s_description" HELP "Object description" ORDER 50 ADD FIELD "product_module_code" OF "rym_wizard_brow" AS character DESCRIPTION "A unique code to identify the product module this dynamic object belongs to. This code should correspond to a code that exists in gsc_product_module in the ICFDB database, plus should be a product module that exists in the SCM tool. This code is used when forward engineering the object into the full Repository, at which time it must exist or optionally be created in the gsc_product_module table." FORMAT "X(10)" INITIAL "" LABEL "Product Module Code" POSITION 6 SQL-WIDTH 20 VALMSG "s_code" HELP "Product module code" ORDER 30 ADD FIELD "generated_date" OF "rym_wizard_brow" AS date DESCRIPTION "The date this object was last generated." FORMAT "99/99/9999" INITIAL "?" LABEL "Generated Date" POSITION 7 SQL-WIDTH 4 VALMSG "d_date_empty" HELP "Generated date" ORDER 120 ADD FIELD "generated_time" OF "rym_wizard_brow" AS integer DESCRIPTION "The time this object was last generated." FORMAT ">>>>9" INITIAL "0" LABEL "Generated Time" POSITION 8 SQL-WIDTH 4 VALMSG "n_time" HELP "Generated time" ORDER 130 ADD FIELD "sdo_foreign_fields" OF "rym_wizard_brow" AS character DESCRIPTION "If the SDO is the child of some other SDO and relies on parent key information from the parent SDO to resolve its query, then the fields to map between the SDOs should be specified in this property. This is a comma-separated paired list of database field names in the Data-Target and RowObject Temp-Table fields in the Data-Source that should be used for opening the Data-Target's database query using one or more key values from the Data-Source. A good example is joining a customer sdo with an order sdo and the foreign fields would be set to order.cust-num,cust-num. Note that for each Foreign Field pair, the first entry is the name of the field in the database query for the Data-Target (the child or detail SDO in the parent-child or master-detail relationship), which is Order.CustNum in our example. This first entry is expressed as the database field name (optionally with the table qualifier) because that fieldname will actually be inserted into a where clause used to open the database query for the Data-Target, resulting in FOR EACH Order WHERE Order.CustNum = . The second entry in the pair is the name of the key field in the Data-Source SDO which is to be compared to the database field in the Target, or CustNum in our case. This must be the name of the field as it occurs in the Data-Source SDO column list (no DB table qualification) because the Source SDO is providing that value from the SDO's temp-table, not straight out of the database. Each time the dataAvailable event is published by the Data-Source, indicating that its query on Customers has been re-positioned, the Data-Target (Order) SDO will request the value of the CustNum field from the Customer SDO and plug that into the Order query where clause as indicated above. " FORMAT "X(70)" INITIAL "" LABEL "Sdo Foreign Fields" POSITION 9 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Sdo foreign fields" ORDER 70 ADD FIELD "sdo_name" OF "rym_wizard_brow" AS character DESCRIPTION "The name of the SDO that will be used as the data source for the browser. This is only required in order to select fields for the browser. The actual SDO linked to the browser at runtime may be different. A valid existing SDO must be specified, with a relative path and extension to enable the SDO to be located on the operating system. " FORMAT "X(35)" INITIAL "" LABEL "Sdo Name" POSITION 10 SQL-WIDTH 70 VALMSG "s_name" HELP "Sdo name" ORDER 60 ADD FIELD "window_title_field" OF "rym_wizard_brow" AS character DESCRIPTION "This is the field name whose value should be appended to the window title. The fieldname without a table prefix must be specified and should match a field in the SDO serving as the data source within the window." FORMAT "X(35)" INITIAL "" LABEL "Window Title Field" POSITION 11 SQL-WIDTH 70 VALMSG "s_name" HELP "Window title field" ORDER 90 ADD FIELD "custom_super_procedure" OF "rym_wizard_brow" AS character DESCRIPTION "The name of a custom super procedure to attach to the browser when the browser is instantiated onto a container. A relative path and file extension must be specified for the super procedure. This facilitates the coding of specific business logic for a dynamic object. Your super procedure could include an initializeObject procedure that does a RUN SUPER, and after that subscribes to events in the containers toolbar. User defined menu items can then be attached to the conrtainer that publish the event to action the specific business logic." FORMAT "X(35)" INITIAL "" LABEL "Custom Super Procedure" POSITION 12 SQL-WIDTH 70 VALMSG "s_name" HELP "Custom super procedure" ORDER 100 ADD FIELD "selected_fields" OF "rym_wizard_brow" AS character DESCRIPTION "A list of selected fields chr(4) delimited. within each entry, the following entries exist chr(3) delimited: field number field name field enabled " FORMAT "X(3000)" INITIAL "" LABEL "Selected Fields" POSITION 13 SQL-WIDTH 6000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL LARGE MAX-CHARS 3000" VALMSG "s_big_text_block" HELP "Selected fields" ORDER 110 ADD FIELD "launch_container" OF "rym_wizard_brow" AS character DESCRIPTION "The object name of the container to launch when an action is taken on the selected record in the browser. This should be specified without a path and extension and should relate to a record in gsc_object in ICFDB. A dynamic or static container may be specified. The validity of the container to launch will not be checked until runtime. This may be superseded by a specific launch container specified for a specific object controller. " FORMAT "X(35)" INITIAL "" LABEL "Launch Container" POSITION 14 SQL-WIDTH 70 VALMSG "s_description" HELP "Launch container" ORDER 80 ADD INDEX "XPKrym_wizard_brow" ON "rym_wizard_brow" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "wizard_brow_obj" ASCENDING ADD INDEX "XAK1rym_wizard_brow" ON "rym_wizard_brow" AREA "Schema Area" UNIQUE INDEX-FIELD "object_name" ASCENDING ADD INDEX "XAK2rym_wizard_brow" ON "rym_wizard_brow" AREA "Schema Area" UNIQUE INDEX-FIELD "product_code" ASCENDING INDEX-FIELD "product_module_code" ASCENDING INDEX-FIELD "object_name" ASCENDING ADD INDEX "XIE1rym_wizard_brow" ON "rym_wizard_brow" AREA "Schema Area" INDEX-FIELD "object_description" ASCENDING ADD INDEX "XIE2rym_wizard_brow" ON "rym_wizard_brow" AREA "Schema Area" INDEX-FIELD "sdo_name" ASCENDING ADD INDEX "XIE3rym_wizard_brow" ON "rym_wizard_brow" AREA "Schema Area" INDEX-FIELD "launch_container" ASCENDING ADD TABLE "rym_lookup_field" AREA "Schema Area" DESCRIPTION "This table defines fields that have smartdatafields linked to them. If the smartdatafield is the special case of a dynamic lookup, then the majority of the fields define the instance attributes for the dynamic lookup. The lookup can be specific to an object, or whereever a specific field occurs in any object. This table is used by dynamic viewers to apply smartdatafields. " DUMP-NAME "rymlf" TABLE-TRIGGER "CREATE" OVERRIDE PROCEDURE "icf/trg/rymlftrigc.p" CRC "?" TABLE-TRIGGER "DELETE" OVERRIDE PROCEDURE "icf/trg/rymlftrigd.p" CRC "?" TABLE-TRIGGER "WRITE" OVERRIDE PROCEDURE "icf/trg/rymlftrigw.p" CRC "?" ADD FIELD "lookup_field_obj" OF "rym_lookup_field" AS decimal FORMAT ">>>>>>>>>>>>>>>>>9.999999" INITIAL "0" LABEL "Lookup Field Obj" POSITION 2 SQL-WIDTH 21 VALMSG "o_obj" HELP "Lookup field obj" DECIMALS 6 ORDER 10 ADD FIELD "lookup_field_name" OF "rym_lookup_field" AS character DESCRIPTION "This is the name of the field requiring lookup functionality. Wherever this fieldname is found on a dynamic viewer, the specified lookup functionality will be provided. The fieldname specified should not contain a table prefix, as it will be a rowobject field from the SDO. The field to be stored in the database should be specified, usually the object number field. If a specific object name is specified, then the lookup will only function this way for the specific object, otherwise the lookup will be available system wide. " FORMAT "X(35)" INITIAL "" LABEL "Lookup Field Name" POSITION 3 SQL-WIDTH 70 VALMSG "s_name" HELP "Lookup field name" ORDER 20 ADD FIELD "specific_object_name" OF "rym_lookup_field" AS character DESCRIPTION "If the lookup is specific to an object, e.g. a specific dynamic viewer, then the object name should be specified here (without a path and no extension if a logical object). If this field is left blank, then the lookup will be available systemwide. " FORMAT "X(35)" INITIAL "" LABEL "Specific Object Name" POSITION 4 SQL-WIDTH 70 VALMSG "s_name" HELP "Specific object name" ORDER 30 ADD FIELD "sdf_filename" OF "rym_lookup_field" AS character DESCRIPTION "If the lookup should use a specific smartdatafield, such as a combo smartdatafield, then the filename including relative path and extension of the smartdatafield should be specified here. For lookups this field should be lset to the dynamic lookup window rydynlookw " FORMAT "X(35)" INITIAL "" LABEL "Sdf Filename" POSITION 5 SQL-WIDTH 70 VALMSG "s_name" HELP "Sdf filename" ORDER 40 ADD FIELD "base_query_string" OF "rym_lookup_field" AS character DESCRIPTION "Lookup specific attribute: The first property you must specify is the query to be used for the lookup. The query must start with FOR EACH and must not end in a full stop or colon and must not include the END statement. The query may join to as many tables as you wish. The tables may be in any order and may contain any where clause you require. The query may also contain a BY clause if necessary. You should include in the query any tables whose field values you wish to display in the lookup browser, or whose field values you wish to return to the viewer on completion of the lookup. Table names should not contain a database prefix. When you have finished typing in the query, simply press the REFRESH button to populate the rest of the property window information. HINT: The easiest way to enter the query and test its efficiency, etc. is to key it into the procedure editor and run it. When you are happy, simply cut and paste it into the property window and press the REFRESH button. " FORMAT "X(3000)" INITIAL "" LABEL "Base Query String" POSITION 6 SQL-WIDTH 6000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL LARGE MAX-CHARS 3000" VALMSG "s_big_text_block" HELP "Base query string" ORDER 50 ADD FIELD "query_tables" OF "rym_lookup_field" AS character DESCRIPTION "This property is calculated automatically in the maintenance program and contains a comma delimited list of table names in the query. " FORMAT "X(70)" INITIAL "" LABEL "Query Tables" POSITION 7 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Query tables" ORDER 60 ADD FIELD "rows_to_batch" OF "rym_lookup_field" AS integer DESCRIPTION "This is the initial number of records to retrieve at a time for displaying in the lookup browser. The value may be manipulated at runtime after retrieval of the first batch of records. This is to ensure that lookups on a large dataset do not take too long. The default is 200. As the user scrolls through the dataset, extra batches will be retrieved (via the Appserver) until all records have been read. The setting of this property to a reasonably low figure will improve performance and give the user the opportunity to filter the result set in order to target a more defined set of records. Be careful not to set this too low however as this will increase the number of hits on the Appserver to retrieve the full dataset." FORMAT "->>>>>9" INITIAL "0" LABEL "Rows to Batch" POSITION 8 SQL-WIDTH 4 VALMSG "n_integer_6" HELP "Rows to batch" ORDER 70 ADD FIELD "key_field_name" OF "rym_lookup_field" AS character DESCRIPTION "This is the field whose value should be assigned to the external field on completion of the lookup. Any of the fields from any of the buffers in the specified query may be used, but the field selected should have the same data type as the lookup field name." FORMAT "X(70)" INITIAL "" LABEL "Key Field Name" POSITION 9 SQL-WIDTH 140 VALMSG "s_big_name" HELP "Key field name" ORDER 80 ADD FIELD "key_field_format" OF "rym_lookup_field" AS character DESCRIPTION "The format of the key field" FORMAT "X(15)" INITIAL "" LABEL "Key Field Format" POSITION 10 SQL-WIDTH 30 VALMSG "s_short_name" HELP "Key field format" ORDER 90 ADD FIELD "key_field_datatype" OF "rym_lookup_field" AS character DESCRIPTION "The datatype of the key field" FORMAT "X(15)" INITIAL "" LABEL "Key Field Datatype" POSITION 11 SQL-WIDTH 30 VALMSG "s_short_name" HELP "Key field datatype" ORDER 100 ADD FIELD "displayed_field_name" OF "rym_lookup_field" AS character DESCRIPTION "This is the field whose value should be displayed on the viewer in place of the key field value. This may be the same as the key field but may also be different. For example the key field may be the customer code but the displayed field could be the customer name. Note that the lookup supports entry of the displayed field for resolution of the lookup without calling up the browser, and so a sensible indexed field should be used if possible." FORMAT "X(70)" INITIAL "" LABEL "Displayed Field Name" POSITION 12 SQL-WIDTH 140 VALMSG "s_big_name" HELP "Displayed field name" ORDER 110 ADD FIELD "displayed_field_format" OF "rym_lookup_field" AS character DESCRIPTION "The format of the displayed field" FORMAT "X(15)" INITIAL "" LABEL "Displayed Field Format" POSITION 13 SQL-WIDTH 30 VALMSG "s_short_name" HELP "Displayed field format" ORDER 120 ADD FIELD "displayed_field_datatype" OF "rym_lookup_field" AS character DESCRIPTION "The datatype of the displayed field" FORMAT "X(15)" INITIAL "" LABEL "Displayed Field Datatype" POSITION 14 SQL-WIDTH 30 VALMSG "s_short_name" HELP "Displayed field datatype" ORDER 130 ADD FIELD "field_label" OF "rym_lookup_field" AS character DESCRIPTION "This is the label of the displayed field to display on the viewer. It will usually reflect a sensible label for the external field." FORMAT "X(28)" INITIAL "" LABEL "Field Label" POSITION 15 SQL-WIDTH 56 VALMSG "s_label" HELP "Field label" ORDER 140 ADD FIELD "field_tooltip" OF "rym_lookup_field" AS character DESCRIPTION "This is the tooltip to use for entry of the displayed field on the viewer. If nothing else it should at least say Press F4 for Lookup." FORMAT "X(70)" INITIAL "" LABEL "Field Tooltip" POSITION 16 SQL-WIDTH 140 VALMSG "s_big_description" HELP "Field tooltip" ORDER 150 ADD FIELD "browse_title" OF "rym_lookup_field" AS character DESCRIPTION "This is the title to displayed on the lookup browser and should reflect the data that is being looked up, e.g. Lookup Customers." FORMAT "X(35)" INITIAL "" LABEL "Browse Title" POSITION 17 SQL-WIDTH 70 VALMSG "s_description" HELP "Browse title" ORDER 160 ADD FIELD "browse_field_list" OF "rym_lookup_field" AS character DESCRIPTION "A comma delimited list of fields to include in the lookup browser, in the correct sequence that they should appear." FORMAT "X(500)" INITIAL "" LABEL "Browse Field List" POSITION 18 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Browse field list" ORDER 170 ADD FIELD "browse_field_datatypes" OF "rym_lookup_field" AS character DESCRIPTION "The data types corresponding to the browse fields, also comma delimited" FORMAT "X(500)" INITIAL "" LABEL "Browse Field Datatypes" POSITION 19 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Browse field datatypes" ORDER 180 ADD FIELD "browse_field_formats" OF "rym_lookup_field" AS character DESCRIPTION "The formats corresponding to the browse fields, also comma delimited" FORMAT "X(500)" INITIAL "" LABEL "Browse Field Formats" POSITION 20 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Browse field formats" ORDER 190 ADD FIELD "linked_field_list" OF "rym_lookup_field" AS character DESCRIPTION "A comma delimited list of linked field names whose data you wish to retrieve as part of the lookup query. This is so that you can use the data in the standard hooks such as the lookupComplete hook for specific code in your viewer. It can also be used to automatically populate related field information for example to display the customer code and name field on return from the lookup. " FORMAT "X(500)" INITIAL "" LABEL "Linked Field List" POSITION 21 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Linked field list" ORDER 200 ADD FIELD "linked_field_datatypes" OF "rym_lookup_field" AS character DESCRIPTION "The data types corresponding to the linked fields, also comma delimited" FORMAT "X(500)" INITIAL "" LABEL "Linked Field Datatypes" POSITION 22 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Linked field datatypes" ORDER 210 ADD FIELD "linked_field_formats" OF "rym_lookup_field" AS character DESCRIPTION "The formats corresponding to the linked fields, also comma delimited" FORMAT "X(500)" INITIAL "" LABEL "Linked Field Formats" POSITION 23 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Linked field formats" ORDER 220 ADD FIELD "linked_widget_list" OF "rym_lookup_field" AS character DESCRIPTION "Comma delimited list of linked widgets. For any of the linked fields you may specify a widget name to update with the linked field value on return from the lookup. The widget must be a valid widget as displayed on your viewer but may be a database field or a local fill-in. If you specify a widget name, this widgets screen value will be automatically updated with the data in the associated linked field. NOTE: You can have linked fields without a widget specified and can simply hard code what you do with the returned values into your viewer via the standard lookup hooks explained below. " FORMAT "X(500)" INITIAL "" LABEL "Linked Widget List" POSITION 24 SQL-WIDTH 1000 VIEW-AS "VIEW-AS EDITOR SIZE 70 BY 8 SCROLLBAR-VERTICAL MAX-CHARS 500" VALMSG "s_small_text_block" HELP "Linked widget list" ORDER 230 ADD FIELD "disable_lookup" OF "rym_lookup_field" AS logical DESCRIPTION "If set to YES, this lookup will be temporarily disabled." FORMAT "YES/NO" INITIAL "NO" LABEL "Disable Lookup" POSITION 25 SQL-WIDTH 1 VIEW-AS "VIEW-AS TOGGLE-BOX" VALMSG "l_noyes" HELP "Disable lookup" ORDER 240 ADD INDEX "XPKrym_lookup_field" ON "rym_lookup_field" AREA "Schema Area" UNIQUE PRIMARY INDEX-FIELD "lookup_field_obj" ASCENDING ADD INDEX "XAK1rym_lookup_field" ON "rym_lookup_field" AREA "Schema Area" UNIQUE INDEX-FIELD "lookup_field_name" ASCENDING INDEX-FIELD "specific_object_name" ASCENDING ADD INDEX "XIE1rym_lookup_field" ON "rym_lookup_field" AREA "Schema Area" INDEX-FIELD "specific_object_name" ASCENDING ADD INDEX "XIE2rym_lookup_field" ON "rym_lookup_field" AREA "Schema Area" INDEX-FIELD "sdf_filename" ASCENDING . PSC cpstream=UTF-8 . 0000590182