REM This file updates the Meta Data tables for 6i 4.6

DECLARE

BEGIN

        DELETE FROM sdd_reserved_names
        WHERE  rn_res_name in ( SELECT ci_name 
                                FROM   ck_installed_objects 
                                WHERE  ci_stage like 'CKROB%');

	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_GPH_PK','CONSTRAINT','CONSTRAINT','N','N','N','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('HIM_PK','CONSTRAINT','CONSTRAINT','N','N','N','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_HND_PK','CONSTRAINT','CONSTRAINT','N','N','N','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_HTT_HIM_FK','CONSTRAINT','CONSTRAINT','N','N','N','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_HTT_PK','CONSTRAINT','CONSTRAINT','N','N','N','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_HST_GPH_FK','CONSTRAINT','CONSTRAINT','N','N','N','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_PRF_PK','CONSTRAINT','CONSTRAINT','N','N','N','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_ELT_PK','CONSTRAINT','CONSTRAINT','N','N','N','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_ELT_UK1','CONSTRAINT','CONSTRAINT','N','N','N','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_ELT_UK2','CONSTRAINT','CONSTRAINT','N','N','N','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_ELT_UK3','CONSTRAINT','CONSTRAINT','N','N','N','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_CHK_EVENT','FUNCTION','FUNCTION','N','N','N','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_CHK_FUN_IS_BUSINESS_RULE','FUNCTION','FUNCTION','N','N','N','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_CHK_PLM_IS_BRDD','FUNCTION','FUNCTION','N','N','N','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CHK_STATIC_BR_NO_ETG','FUNCTION','FUNCTION','N','N','N','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_REL','FUNCTION','FUNCTION','N','N','N','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWPBASE','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_BR','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_BRD','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_DIA','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_DOM','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_ENT','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_FIL','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_FUN','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_MCO','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_MDE','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_PLM','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_PRC','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_TBL','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_TER','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_TXT','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('CDWP_VW','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('HTMLTREE','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('HWS','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('HWSF','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('HWSP','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('JR_ROLE','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWABROW','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWACHCK','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWACHKI','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWACTXT','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWADBUG','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWADEPS','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWAGRPH','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWAHELP','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWAINFO','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWALPAD','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWAPRED','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWAPREF','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWAPRIV','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWAPROP','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWAROBS','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWARPRT','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWASLIB','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWASPOT','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWASRCH','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWATREE','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWAUPLD','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWAVRSN','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWAXIST','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_APP','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_FOL','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_MGT','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_QCK','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_STC','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_WSF','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('PARSE4DEPS','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ROB_MSG','PACKAGE','PACKAGE','N','N','Y','N','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_DETAILS','TABLE','TABLE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_GRAPHICS','TABLE','TABLE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_GRPH_CATEGORIES','TABLE','TABLE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_HELP_ITEMS','TABLE','TABLE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_HELP_NODES','TABLE','TABLE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_HELP_TEXT','TABLE','TABLE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_HOTSPOTS','TABLE','TABLE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_HTML','TABLE','TABLE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_PREFERENCES','TABLE','TABLE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_PROVIDED','TABLE','TABLE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_QUALITY_CHECKS','TABLE','TABLE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_SESSIONS','TABLE','TABLE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_VHV_BRANCHES','TABLE','TABLE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('PIE_ELEMENT_TYPES','TABLE','TABLE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_GRPH_CAT_SEQ','SEQUENCE','SEQUENCE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_HIM_SEQ','SEQUENCE','SEQUENCE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_HND_SEQ','SEQUENCE','SEQUENCE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_HOTSPOT_SEQ','SEQUENCE','SEQUENCE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_HTML_SEQ1','SEQUENCE','SEQUENCE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_SESSION_SEQ','SEQUENCE','SEQUENCE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_VHV_BRANCHES_SEQ','SEQUENCE','SEQUENCE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_QUERY_LIBRARY','TABLE','TABLE','N','N','Y','Y','N',NULL,NULL)
	;
	INSERT INTO sdd_reserved_names
	(RN_RES_NAME,RN_TYPE,RN_COMMENT,RN_GLOBAL,RN_TEMPORARY,RN_ENABLED,RN_USR_ACCESS,RN_CDAPI,RN_OBJECT_IRID,RN_OBJECT_IVID)
	VALUES
	('ODWA_QLB_SEQ','SEQUENCE','SEQUENCE','N','N','Y','Y','N',NULL,NULL)
	;




	-- Remove any data from the help tables.
	DELETE FROM odwa_help_items;
	DELETE FROM odwa_help_nodes;
	DELETE FROM odwa_help_text;


	--
	-- Populate ODWA_HELP_ITEMS Table
	-- This Table Consists of all the Help topics in ROB's Online Help along with the Keywords used for search
	--
	INSERT INTO odwa_help_items VALUES
	(100, 
	'Uploading Files', 
	'', 
	'upload,create,new file,automatic check out');

	INSERT INTO odwa_help_items VALUES
	(110, 
	'Check In (and Upload Existing Files)', 
	'', 
	'check in notes,checkin notes,branch');

	INSERT INTO odwa_help_items VALUES
	(120, 
	'Check Out (and Download a File)', 
	'', 
	'check out, download, context workarea');

	INSERT INTO odwa_help_items VALUES
	(111, 
	'Check In with immediate Check Out', 
	'', 
	'check in, check out, lock');

	INSERT INTO odwa_help_items VALUES
	(130, 
	'Undo Check Out', 
	'', 
	'undo check out, undo checkout');

	INSERT INTO odwa_help_items VALUES
	(140, 
	'Reconciling', 
	'', 
	'role,reconcile,privileges');

	INSERT INTO odwa_help_items VALUES
	(150, 
	'On Line Help System', 
	'', 
	'help,help on help,documentation;100;200;;;;0');

	INSERT INTO odwa_help_items VALUES
	(170, 
	'Getting Started with the Repository Object Browser', 
	'', 
	'Start');

	INSERT INTO odwa_help_items VALUES
	(180, 
	'Getting Started - End Users', 
	'', 
	'End Users, Start');

	INSERT INTO odwa_help_items VALUES
	(190, 
	'Getting Started - Developers', 
	'', 
	'Developer, Start, ');

	INSERT INTO odwa_help_items VALUES
	(200, 
	'Getting Started - Repository Managers', 
	'', 
	'Start, Manager, Repository');

	INSERT INTO odwa_help_items VALUES
	(220, 
	'Granting Privileges', 
	'', 
	'Roles,users, Access, Privileges, granting');

	INSERT INTO odwa_help_items VALUES
	(230, 
	'Granting Roles to Users or other Roles', 
	'', 
	'Role, Grant, User');

	INSERT INTO odwa_help_items VALUES
	(240, 
	'Including Graphics in Help Items', 
	'', 
	'help,helpitem,graphic,gif');

	INSERT INTO odwa_help_items VALUES
	(250, 
	'Include Repository Object References in help items', 
	'', 
	'object reference,help,help item');

	INSERT INTO odwa_help_items VALUES
	(403, 
	'Repository Reports', 
	'', 
	'repository reports, workarea, configuration, element type, cdm fast track, cdm fasttrack, cdm classic');

	INSERT INTO odwa_help_items VALUES
	(270, 
	'Including Graphics in Reports', 
	'', 
	'mlt,text,graphics,hotspots,reference,report,image');

	INSERT INTO odwa_help_items VALUES
	(280, 
	'Include Repository Object References in Reports', 
	'', 
	'reference,report,object,link,association,navigate');

	INSERT INTO odwa_help_items VALUES
	(290, 
	'Repository - File System Synchronization (technical notes)', 
	'', 
	'crc,files,synchronization,filesystem,mapping,CRC');

	INSERT INTO odwa_help_items VALUES
	(400, 
	'Repository Navigator', 
	'', 
	'repository navigator, workareas, configurations, all containers, wastebasket, check out, check in, file download, file upload, undo check out');

	INSERT INTO odwa_help_items VALUES
	(1000, 
	'ROB On Line Help', 
	'', 
	'help,splash,start');

	INSERT INTO odwa_help_items VALUES
	(1550, 
	'Management Facility', 
	'', 
	'');

	INSERT INTO odwa_help_items VALUES
	(1020, 
	'ROB Operations', 
	'', 
	'Operations, New User');

	INSERT INTO odwa_help_items VALUES
	(1030, 
	'CRC Corrector Utility', 
	'', 
	'crc,file,synchronization');

	INSERT INTO odwa_help_items VALUES
	(406, 
	'Graphics Manager', 
	'', 
	'graphic,hotspot,diagram,clickable,gif,image,jpg');

	INSERT INTO odwa_help_items VALUES
	(1050, 
	'Overlapping Hotspots (e.g.Super and Sub type Entities)', 
	'', 
	'supertype,subtype,super');

	INSERT INTO odwa_help_items VALUES
	(1250, 
	'3. Connect the diagram gif to the diagram element', 
	'', 
	'diagram, reports, diagram element,');

	INSERT INTO odwa_help_items VALUES
	(1260, 
	'Support for CDM RuleFrame in Reports', 
	'', 
	'cdm ruleframe,cdm rule frame,repository reports,business rules, business rule design definitions, brdd''s, brdds');

	INSERT INTO odwa_help_items VALUES
	(402, 
	'Repository Search', 
	'', 
	'search');

	INSERT INTO odwa_help_items VALUES
	(1090, 
	'Basic Search Options', 
	'', 
	'basic,search,');

	INSERT INTO odwa_help_items VALUES
	(1100, 
	'Advanced Search Options', 
	'', 
	'advanced,search');

	INSERT INTO odwa_help_items VALUES
	(1110, 
	'Version Search Options', 
	'', 
	'version,search');

	INSERT INTO odwa_help_items VALUES
	(1120, 
	'Audit Search Options', 
	'', 
	'audit,search,changed,log,track,timestamp');

	INSERT INTO odwa_help_items VALUES
	(1130, 
	'1. Create Graphic for an Oracle Designer Diagram', 
	'', 
	'erd,fhd,bpm,dd,diagram,click,image');

	INSERT INTO odwa_help_items VALUES
	(1150, 
	'Create Diagram Image using Netscape Composer', 
	'', 
	'netscape,composer,diagram,gif,image,jpg');

	INSERT INTO odwa_help_items VALUES
	(408, 
	'Version History Viewer', 
	'', 
	'Version, History, Branch, Merge');

	INSERT INTO odwa_help_items VALUES
	(1170, 
	'1. Create or Select a Graphic Category', 
	'', 
	'Graphic, image, diagram');

	INSERT INTO odwa_help_items VALUES
	(1180, 
	'2. Add a Graphic to ROB', 
	'', 
	'Graphic, Diagram, Image');

	INSERT INTO odwa_help_items VALUES
	(409, 
	'3. Create hotspots in a Graphic using the Hotspot Editor', 
	'', 
	'hotspot editor, graphic');

	INSERT INTO odwa_help_items VALUES
	(1200, 
	'4. Designer Diagrams and Hotspots', 
	'', 
	'hotspot, wizard, diagrams, ERD, FHD, DHD, Process Flows');

	INSERT INTO odwa_help_items VALUES
	(1210, 
	'2. Use the Hotspot Wizard.', 
	'', 
	'');

	INSERT INTO odwa_help_items VALUES
	(1220, 
	'Troubleshooting', 
	'', 
	'problems, know issues, workarounds,UE,user extensibility');

	INSERT INTO odwa_help_items VALUES
	(401, 
	'Repository Object Browser', 
	'', 
	'browser, object, repository, properties, associations');

	INSERT INTO odwa_help_items VALUES
	(1240, 
	'Add a New ROB User', 
	'', 
	'New user');

	INSERT INTO odwa_help_items VALUES
	(405, 
	'Repository Security Manager', 
	'', 
	'role,user,privilege, reconcile, manage');

	INSERT INTO odwa_help_items VALUES
	(1300, 
	'Finding Reports by Element Type', 
	'', 
	'');

	INSERT INTO odwa_help_items VALUES
	(1280, 
	'Change how ROB recognizes Business Rules', 
	'', 
	'cdm ruleframe,business rules,cdwp_chk_fun_is_business_rule');

	INSERT INTO odwa_help_items VALUES
	(1290, 
	'Change how ROB recognizes Data Event Types', 
	'', 
	'cdm ruleframe,data events,cdwp_chk_event');

	INSERT INTO odwa_help_items VALUES
	(1310, 
	'The Contents of Repository Reports', 
	'', 
	'repository reports,access,references,');

	INSERT INTO odwa_help_items VALUES
	(1320, 
	'Enhancing the Repository Reports', 
	'', 
	'graphics, hotspots, repository reports, object references');

	INSERT INTO odwa_help_items VALUES
	(1330, 
	'Finding Reports by CDM Deliverable', 
	'', 
	'cdm deliverable, repository reports, cdm fast track, cdm fasttrack, cdm classic');

	INSERT INTO odwa_help_items VALUES
	(1340, 
	'Check In Branch', 
	'', 
	'check in branch');

	INSERT INTO odwa_help_items VALUES
	(1350, 
	'Version Label', 
	'', 
	'check in version label');

	INSERT INTO odwa_help_items VALUES
	(1360, 
	'Check In Notes', 
	'', 
	'check in notes, checkin notes');

	INSERT INTO odwa_help_items VALUES
	(1370, 
	'Check Out Notes', 
	'', 
	'check out notes,checkout notes');

	INSERT INTO odwa_help_items VALUES
	(1380, 
	'Known Restrictions of the File Upload functionality', 
	'', 
	'upload known restrictions');

	INSERT INTO odwa_help_items VALUES
	(1390, 
	'Automatic check out of folder / application system', 
	'', 
	'auto check out');

	INSERT INTO odwa_help_items VALUES
	(1400, 
	'Downloading Files', 
	'', 
	'downloading files,compressed');

	INSERT INTO odwa_help_items VALUES
	(1410, 
	'Granting Workareas', 
	'', 
	'grants,workareas,roles, users');

	INSERT INTO odwa_help_items VALUES
	(1420, 
	'Granting Configurations', 
	'', 
	'grants, configurations, roles, users, privileges, access rights');

	INSERT INTO odwa_help_items VALUES
	(1430, 
	'Granting Folders', 
	'', 
	'grants,root folders, roles, users,access privileges');

	INSERT INTO odwa_help_items VALUES
	(1440, 
	'Reconciling Users', 
	'', 
	'reconciliation,repository users');

	INSERT INTO odwa_help_items VALUES
	(1450, 
	'Reconciling Roles', 
	'', 
	'reconciliation, recursive, cascade, sub roles, subroles');

	INSERT INTO odwa_help_items VALUES
	(1460, 
	'Revoking Roles', 
	'', 
	'');

	INSERT INTO odwa_help_items VALUES
	(1470, 
	'Revoking Privileges From Roles', 
	'', 
	'');

	INSERT INTO odwa_help_items VALUES
	(1480, 
	'Deleting roles', 
	'', 
	'delete repository roles');

	INSERT INTO odwa_help_items VALUES
	(1490, 
	'Revoking Privileges', 
	'', 
	'roles, users, access rights');

	INSERT INTO odwa_help_items VALUES
	(1500, 
	'Revoking Privileges From Roles', 
	'', 
	'');

	INSERT INTO odwa_help_items VALUES
	(1520, 
	'Hide insignificant versions', 
	'', 
	'version history viewer');

	INSERT INTO odwa_help_items VALUES
	(1530, 
	'Representation of Merges', 
	'', 
	'');

	INSERT INTO odwa_help_items VALUES
	(1540, 
	'Upload and Check In a New File', 
	'', 
	'upload, check in');

	INSERT INTO odwa_help_items VALUES
	(1560, 
	'Purge Session Data', 
	'', 
	'purge');

	INSERT INTO odwa_help_items VALUES
	(1570, 
	'Check Newer Versions for Workarea', 
	'', 
	'Workarea, Object Browser');

	INSERT INTO odwa_help_items VALUES
	(1580, 
	'Repository Object Selector', 
	'', 
	'Object Selector');

	INSERT INTO odwa_help_items VALUES
	(1590, 
	'Search and Repository Access Privileges', 
	'', 
	'search,access,global,privileges');

	INSERT INTO odwa_help_items VALUES
	(1600, 
	'Create Folder', 
	'', 
	'folder,root folder,create folder, add folder');

	INSERT INTO odwa_help_items VALUES
	(1610, 
	'Dependency Data', 
	'', 
	'dependencies,uses,used by,parse,impact analysis');

	INSERT INTO odwa_help_items VALUES
	(1620, 
	'Download Folder Contents (zip-file)', 
	'', 
	'download,folder,zipfile,multi,file');

	INSERT INTO odwa_help_items VALUES
	(1630, 
	'Download Zipfile for Folder Tree (with contents)', 
	'', 
	'download,zipfile,tree,folderstructure,multiple, files');

	INSERT INTO odwa_help_items VALUES
	(1640, 
	'Parsing Repository Objects for Dependencies', 
	'', 
	'parse,dependencies,structured,analysis,user defined dependencies');

	INSERT INTO odwa_help_items VALUES
	(1650, 
	'Search Library', 
	'', 
	'save, query,library,search,publish,reuse,archive');

	INSERT INTO odwa_help_items VALUES
	(1700, 
	'Manage ROB Preferences', 
	'', 
	'Preferences,image_path,use_cdm,CDM,Global search user,enable file upload,servlets,servlet_urlbase');

	INSERT INTO odwa_help_items VALUES
	(1710, 
	'What is CDM ?', 
	'', 
	'preferences,use_cdm,CDM, Business Rules, headstart, Oracle consulting');



	--
	-- Populate ODWA_HELP_NODES Table
	-- This Table Consists of the Node details of all the Help topics in ROB's Online Help 
	--
	INSERT INTO odwa_help_nodes VALUES
	(1, 
	0, 
	2, 
	1, 
	'Repository Navigator', 
	400 );

	INSERT INTO odwa_help_nodes VALUES
	(132, 
	76, 
	3, 
	4, 
	'3. Connect the diagram gif to the diagram element', 
	1250 );

	INSERT INTO odwa_help_nodes VALUES
	(3, 
	0, 
	5, 
	1, 
	'Repository Object Browser', 
	401 );

	INSERT INTO odwa_help_nodes VALUES
	(4, 
	5, 
	1, 
	2, 
	'Repository Security Manager', 
	405 );

	INSERT INTO odwa_help_nodes VALUES
	(5, 
	0, 
	6, 
	1, 
	'Management Facility', 
	0 );

	INSERT INTO odwa_help_nodes VALUES
	(6, 
	0, 
	15, 
	1, 
	'On Line Help System', 
	150 );

	INSERT INTO odwa_help_nodes VALUES
	(7, 
	0, 
	1, 
	1, 
	'Getting Started with the Repository Object Browser', 
	170 );

	INSERT INTO odwa_help_nodes VALUES
	(8, 
	0, 
	3, 
	1, 
	'Repository Reports', 
	403 );

	INSERT INTO odwa_help_nodes VALUES
	(133, 
	8, 
	4, 
	2, 
	'Support for CDM RuleFrame in Reports', 
	1260 );

	INSERT INTO odwa_help_nodes VALUES
	(10, 
	1, 
	4, 
	2, 
	'Check In (and Upload Existing Files)', 
	110 );

	INSERT INTO odwa_help_nodes VALUES
	(11, 
	1, 
	2, 
	2, 
	'Check Out (and Download a File)', 
	120 );

	INSERT INTO odwa_help_nodes VALUES
	(12, 
	1, 
	3, 
	2, 
	'Undo Check Out', 
	130 );

	INSERT INTO odwa_help_nodes VALUES
	(13, 
	1, 
	6, 
	2, 
	'Uploading Files', 
	100 );

	INSERT INTO odwa_help_nodes VALUES
	(14, 
	4, 
	3, 
	3, 
	'Granting Roles to Users or other Roles', 
	230 );

	INSERT INTO odwa_help_nodes VALUES
	(15, 
	4, 
	2, 
	3, 
	'Granting Privileges', 
	220 );

	INSERT INTO odwa_help_nodes VALUES
	(16, 
	4, 
	4, 
	3, 
	'Reconciling', 
	140 );

	INSERT INTO odwa_help_nodes VALUES
	(18, 
	6, 
	1, 
	2, 
	'Include Repository Object References in help items', 
	250 );

	INSERT INTO odwa_help_nodes VALUES
	(19, 
	6, 
	2, 
	2, 
	'Including Graphics in Help Items', 
	240 );

	INSERT INTO odwa_help_nodes VALUES
	(21, 
	7, 
	3, 
	2, 
	'Getting Started - End Users', 
	180 );

	INSERT INTO odwa_help_nodes VALUES
	(22, 
	7, 
	4, 
	2, 
	'Getting Started - Developers', 
	190 );

	INSERT INTO odwa_help_nodes VALUES
	(23, 
	7, 
	5, 
	2, 
	'Getting Started - Repository Managers', 
	200 );

	INSERT INTO odwa_help_nodes VALUES
	(24, 
	137, 
	5, 
	3, 
	'Include Repository Object References in Reports', 
	280 );

	INSERT INTO odwa_help_nodes VALUES
	(25, 
	137, 
	6, 
	3, 
	'Including Graphics in Reports', 
	270 );

	INSERT INTO odwa_help_nodes VALUES
	(26, 
	10, 
	1, 
	3, 
	'Check In with immediate Check Out', 
	111 );

	INSERT INTO odwa_help_nodes VALUES
	(27, 
	193, 
	2, 
	4, 
	'Repository - File System Synchronization (technical notes)', 
	290 );

	INSERT INTO odwa_help_nodes VALUES
	(134, 
	133, 
	1, 
	3, 
	'Change how ROB recognizes Business Rules', 
	1280 );

	INSERT INTO odwa_help_nodes VALUES
	(43, 
	0, 
	12, 
	1, 
	'ROB Operations', 
	1020 );

	INSERT INTO odwa_help_nodes VALUES
	(44, 
	193, 
	3, 
	4, 
	'CRC Corrector Utility', 
	1030 );

	INSERT INTO odwa_help_nodes VALUES
	(45, 
	5, 
	2, 
	2, 
	'Graphics Manager', 
	406 );

	INSERT INTO odwa_help_nodes VALUES
	(46, 
	77, 
	2, 
	5, 
	'Overlapping Hotspots (e.g.Super and Sub type Entities)', 
	1050 );

	INSERT INTO odwa_help_nodes VALUES
	(47, 
	0, 
	4, 
	1, 
	'Repository Search', 
	402 );

	INSERT INTO odwa_help_nodes VALUES
	(48, 
	47, 
	1, 
	2, 
	'Basic Search Options', 
	1090 );

	INSERT INTO odwa_help_nodes VALUES
	(49, 
	47, 
	2, 
	2, 
	'Advanced Search Options', 
	1100 );

	INSERT INTO odwa_help_nodes VALUES
	(50, 
	47, 
	3, 
	2, 
	'Version Search Options', 
	1110 );

	INSERT INTO odwa_help_nodes VALUES
	(51, 
	47, 
	4, 
	2, 
	'Audit Search Options', 
	1120 );

	INSERT INTO odwa_help_nodes VALUES
	(52, 
	76, 
	1, 
	4, 
	'1. Create Graphic for an Oracle Designer Diagram', 
	1130 );

	INSERT INTO odwa_help_nodes VALUES
	(54, 
	52, 
	1, 
	5, 
	'Create Diagram Image using Netscape Composer', 
	1150 );

	INSERT INTO odwa_help_nodes VALUES
	(72, 
	0, 
	7, 
	1, 
	'Version History Viewer', 
	408 );

	INSERT INTO odwa_help_nodes VALUES
	(73, 
	45, 
	1, 
	3, 
	'1. Create or Select a Graphic Category', 
	1170 );

	INSERT INTO odwa_help_nodes VALUES
	(74, 
	45, 
	2, 
	3, 
	'2. Add a Graphic to ROB', 
	1180 );

	INSERT INTO odwa_help_nodes VALUES
	(75, 
	45, 
	3, 
	3, 
	'3. Create hotspots in a Graphic using the Hotspot Editor', 
	409 );

	INSERT INTO odwa_help_nodes VALUES
	(76, 
	45, 
	5, 
	3, 
	'4. Designer Diagrams and Hotspots', 
	1200 );

	INSERT INTO odwa_help_nodes VALUES
	(77, 
	76, 
	2, 
	4, 
	'2. Use the Hotspot Wizard.', 
	1210 );

	INSERT INTO odwa_help_nodes VALUES
	(92, 
	0, 
	10, 
	1, 
	'Troubleshooting', 
	1220 );

	INSERT INTO odwa_help_nodes VALUES
	(135, 
	133, 
	2, 
	3, 
	'Change how ROB recognizes Data Event Types', 
	1290 );

	INSERT INTO odwa_help_nodes VALUES
	(136, 
	8, 
	1, 
	2, 
	'Finding Reports by Element Type', 
	1300 );

	INSERT INTO odwa_help_nodes VALUES
	(137, 
	8, 
	5, 
	2, 
	'Enhancing the Repository Reports', 
	1320 );

	INSERT INTO odwa_help_nodes VALUES
	(138, 
	8, 
	3, 
	2, 
	'The Contents of Repository Reports', 
	1310 );

	INSERT INTO odwa_help_nodes VALUES
	(153, 
	8, 
	2, 
	2, 
	'Finding Reports by CDM Deliverable', 
	1330 );

	INSERT INTO odwa_help_nodes VALUES
	(154, 
	10, 
	2, 
	3, 
	'Check In Branch', 
	1340 );

	INSERT INTO odwa_help_nodes VALUES
	(155, 
	10, 
	3, 
	3, 
	'Version Label', 
	1350 );

	INSERT INTO odwa_help_nodes VALUES
	(156, 
	10, 
	4, 
	3, 
	'Check In Notes', 
	1360 );

	INSERT INTO odwa_help_nodes VALUES
	(173, 
	11, 
	1, 
	3, 
	'Check Out Notes', 
	1370 );

	INSERT INTO odwa_help_nodes VALUES
	(193, 
	293, 
	2, 
	3, 
	'Known Restrictions of the File Upload functionality', 
	1380 );

	INSERT INTO odwa_help_nodes VALUES
	(194, 
	293, 
	1, 
	3, 
	'Automatic check out of folder / application system', 
	1390 );

	INSERT INTO odwa_help_nodes VALUES
	(195, 
	1, 
	5, 
	2, 
	'Downloading Files', 
	1400 );

	INSERT INTO odwa_help_nodes VALUES
	(213, 
	15, 
	1, 
	4, 
	'Granting Workareas', 
	1410 );

	INSERT INTO odwa_help_nodes VALUES
	(214, 
	15, 
	2, 
	4, 
	'Granting Configurations', 
	1420 );

	INSERT INTO odwa_help_nodes VALUES
	(215, 
	15, 
	3, 
	4, 
	'Granting Folders', 
	1430 );

	INSERT INTO odwa_help_nodes VALUES
	(216, 
	16, 
	2, 
	4, 
	'Reconciling Users', 
	1440 );

	INSERT INTO odwa_help_nodes VALUES
	(217, 
	16, 
	1, 
	4, 
	'Reconciling Roles', 
	1450 );

	INSERT INTO odwa_help_nodes VALUES
	(218, 
	4, 
	5, 
	3, 
	'Revoking Roles', 
	1460 );

	INSERT INTO odwa_help_nodes VALUES
	(233, 
	4, 
	6, 
	3, 
	'Revoking Privileges', 
	1490 );

	INSERT INTO odwa_help_nodes VALUES
	(234, 
	4, 
	7, 
	3, 
	'Deleting roles', 
	1480 );

	INSERT INTO odwa_help_nodes VALUES
	(273, 
	72, 
	2, 
	2, 
	'Hide insignificant versions', 
	1520 );

	INSERT INTO odwa_help_nodes VALUES
	(274, 
	72, 
	1, 
	2, 
	'Representation of Merges', 
	1530 );

	INSERT INTO odwa_help_nodes VALUES
	(293, 
	1, 
	1, 
	2, 
	'Upload and Check In a New File', 
	1540 );

	INSERT INTO odwa_help_nodes VALUES
	(313, 
	5, 
	3, 
	2, 
	'Purge Session Data', 
	1560 );

	INSERT INTO odwa_help_nodes VALUES
	(333, 
	1, 
	7, 
	2, 
	'Check Newer Versions for Workarea', 
	1570 );

	INSERT INTO odwa_help_nodes VALUES
	(334, 
	0, 
	8, 
	1, 
	'Repository Object Selector', 
	1580 );

	INSERT INTO odwa_help_nodes VALUES
	(354, 
	47, 
	5, 
	2, 
	'Search and Repository Access Privileges', 
	1590 );

	INSERT INTO odwa_help_nodes VALUES
	(374, 
	1, 
	8, 
	2, 
	'Create Folder', 
	1600 );

	INSERT INTO odwa_help_nodes VALUES
	(394, 
	3, 
	1, 
	2, 
	'Dependency Data', 
	1610 );

	INSERT INTO odwa_help_nodes VALUES
	(2, 
	1, 
	9, 
	2, 
	'Download Folder Contents (zip-file)', 
	1620 );

	INSERT INTO odwa_help_nodes VALUES
	(2001, 
	1, 
	10, 
	2, 
	'Download Zipfile for Folder Tree (with contents)', 
	1630 );

	INSERT INTO odwa_help_nodes VALUES
	(2002, 
	394, 
	1, 
	3, 
	'Parsing Repository Objects for Dependencies', 
	1640 );

	INSERT INTO odwa_help_nodes VALUES
	(2003, 
	47, 
	6, 
	2, 
	'Search Library', 
	1650 );

	INSERT INTO odwa_help_nodes VALUES
	(2004, 
	5, 
	4, 
	2, 
	'Manage ROB Preferences', 
	1700 );

	INSERT INTO odwa_help_nodes VALUES
	(2005, 
	8, 
	5, 
	2, 
	'What is CDM ?', 
	1710 );



	--
	-- Populate ODWA_HELP_TEXT Table
	-- This Table Consists of The Help text for all the ROB's Online Help
	--
	-- TITLE: Granting Roles to Users or other Roles
	-- NODE : Granting Roles to Users or other Roles
	INSERT INTO odwa_help_text VALUES
	(230, 
	5, 
	'
	 From the Repository Security manager you can grant the role to the Oracle Repository Users. <BR>You are allowed to grant
	 a role if you are the Repository Owner, the Role Owner, or you have the Grant privilege
	 on the role.Be aware that after you have granted the role to users, this does not
	 mean the user immediately has the access rights. You still need to perform a reconcile,
	 see <A href="javascript:parent.showHelp(140)">Reconciling</A>.<BR><BR><B>Starting
	 at the role</b><BR><Br>After navigating to the right role:<ol><li>Click on the Grant
	 Role icon {db_user_rolegr.gif, ALT="Grant Role"}. You will only see the Grant Role icon if you have the right privileges.</li><li>Select
	 the Grantees (you can use shift- and ctrl-click). A grantee can either be a role
	 or an Oracle Repository User.</li><li>Select the privileges.</li><li>Decide if you
	 immediately want to reconcile the role (see <A href="javascript:parent.showHelp(140)">Reconciling</A>).</li><li>Press
	 save.</li></ol><B>Starting at the user</b><BR><Br>After navigating to the right
	 user:<ol><li>Click on the Grant Role icon {db_user_rolegr.gif, ALT="Grant Role"}.<BR></li><li>Select
	 the Roles you want to grant to this user (you can use shift- and ctrl-click).</li><li>Select
	 the privileges.</li><li>Decide if you immediately want to reconcile the user (see
	 <A href="javascript:parent.showHelp(140)">Reconciling</A>).</li><li>Press save.</li></ol>
	' );

	-- TITLE: Reconciling Roles
	-- NODE : Reconciling Roles
	INSERT INTO odwa_help_text VALUES
	(1450, 
	5, 
	'
	 Reconciling a role means granting the privileges of the role to every user that 
	 has been granted this role. To reconcile a role you need to have the Reconcile privilege
	 on the role.<ol><li>Select the role in the left pane.</li><li>Click on the Reconcile
	 icon in the menu bar {reconcilegr.gif, ALT="Reconcile"}.</li><li>Decide if you want to do this recursively,
	 in other words: do you want to reconcile the sub roles of this role as well?</li><li>Press
	 Reconcile.</li></ol>Now all the Repository Users that have this role granted to
	 them have the access privileges as specified by this role. Alternative method: check
	 the Reconcile checkbox when granting a Folder, Workarea or Configuration to a role.<BR><BR>Methods
	 for reconciling a role for one particular user:<ul><li>Check the Reconcile checkbox
	 when granting a role to a user.</li><li>Navigate to a user and then to one of its
	 roles, and click on the Reconcile icon {reconcilegr.gif, ALT="Reconcile"} (can also be done recursively).</li><li>Navigate
	 to a role and then to one of its Granted To users, and click on the Reconcile icon
	 {reconcilegr.gif, ALT="Reconcile"} (can also be done recursively).</li></ul>
	' );

	-- TITLE: Reconciling Users
	-- NODE : Reconciling Users
	INSERT INTO odwa_help_text VALUES
	(1440, 
	5, 
	'
	 Reconciling a user means making sure the user gets all the privileges of the roles 
	 that have been granted to him. To reconcile a user you need to have the ''Management
	 of Users'' privilege, which can be assigned in the Repository Administration Utility
	 (RAU) of Oracle Repository.<BR><BR>1. Select the user in the left pane.<BR>2. Click
	 on the Reconcile icon in the right hand menu bar {reconcilegr.gif, ALT="Reconcile"}.<BR>3. Decide
	 if you want to revoke all privileges that are not granted through roles. <b>Warning:
	 if you check this box, you revoke all direct access privileges given to the user
	 that are not also granted via a role!</b><BR>4. Press Reconcile<BR><BR>Now the Repository
	 User has all privileges that have been granted to it through roles.
	' );

	-- TITLE: Getting Started with the Repository Object Browser
	-- NODE : Getting Started with the Repository Object Browser
	INSERT INTO odwa_help_text VALUES
	(170, 
	5, 
	'
	Repository Object Browser caters for three different groups.<BR>- <A href="javascript:parent.showHelp(180)">End 
	 Users</A><BR>- <A href="javascript:parent.showHelp(190)">Developers</A><BR>- <A
	 href="javascript:parent.showHelp(200)">Repository/ROB Managers</A><BR>
	' );

	-- TITLE: Revoking Privileges From Roles
	INSERT INTO odwa_help_text VALUES
	(1470, 
	5, 
	'
	To revoke a folder, workarea or configuration privilege from a role, either navigate 
	 to the role and then to one of its folders / workareas / configurations, or navigate
	 to the folder / workarea / configuration and then to its ''granted to'' roles.<ol><li>Click
	 on the Revoke icon {deletiongr.gif, ALT="Revoke"}.</li><li>You will be asked if you are sure you
	 want to do this.</li><li>Press ok.</li></ol>Remember that the users that have this
	 role will still have the privileges, until you do a reconcile (see <A href="javascript:parent.showHelp(140)">Reconciling</A>).
	' );

	-- TITLE: Deleting roles
	-- NODE : Deleting roles
	INSERT INTO odwa_help_text VALUES
	(1480, 
	5, 
	'
	For deleting a role, you need to have both the Grant and the Delete option on the 
	 role.<BR><BR>Navigate to the role you want to delete.<ol><li>Click on the Delete
	 Role icon {deletiongr.gif, ALT="Revoke"}.</li><li>You will be asked if you are sure you want to
	 do this.</li><li>Press ok.</li></ol>Remember that users that used to have this role
	 will still have the priviliges of the role, until you do a reconcile (see <A href="javascript:parent.showHelp(140)">Reconciling</A>).
	' );

	-- TITLE: Version History Viewer
	-- NODE : Version History Viewer
	INSERT INTO odwa_help_text VALUES
	(408, 
	5, 
	'
	The Version History Viewer gives you a graphical overview of the history of an object. 
	 It demonstrates the version of an object, the branches off the object and when an
	 object is merged. You can view it whenever you see the {vhv.gif, ALT="Version History Viewer"} symbol behind an
	 object (for example from the Repository Navigator, the Repository Reports, or the
	 Repository Search).<BR><BR> On the right hand side you get useful information about
	 the version like, who has checked out the particular object version, when that was,
	 the notes and in which workareas and configuration the object version is included.
	 For files you have the possibility to download them. If you click on another version
	 in the version history tree this information will be refreshed for that version.
	 <BR><BR>You can also start the version event viewer {vevgr.gif, ALT="Version Event Viewer"} to get a listing
	 of all previous versions of the object version that you selected. You will also
	 be able to see when branches and merges have taken place. <BR>
	' );

	-- TITLE: Revoking Privileges
	-- NODE : Revoking Privileges
	INSERT INTO odwa_help_text VALUES
	(1490, 
	5, 
	'
	There are two ways to revoke folder / workarea / configuration privileges from a 
	 role or user:<ol><li>through the Grant Access Privileges dialog in the Repository
	 Object Navigator (RON) of Oracle Repository</li><li>through the Security Manager
	 of Repository Object Browser</li></ol>In both cases you need the Admin privilege
	 on the Folder, Workarea or Configuration. In the second case there is an extra requirement
	 when revoking privileges directly from users: you have to have granted the privilege
	 yourself, to be allowed to revoke it again (this is enforced by the Repository API).<BR><BR>Here
	 we will describe the second method: using the Security Manager. Either navigate
	 to the role/user and then to one of its folders, workareas or configurations, or
	 navigate to the folder/workarea/configuration and then to one of its Granted To
	 roles/users.<ol><li>Click on the Revoke icon {deletiongr.gif, ALT="Revoke"}.</li><li>You will
	 be asked if you are sure you want to do this.</li><li>Press ok.</li></ol>Remember
	 that if you revoke privileges from a role, users with this role still have these
	 priviliges until you do a reconcile (see <A href="javascript:parent.showHelp(140)">Reconciling</A>).
	' );

	-- TITLE: Representation of Merges
	-- NODE : Representation of Merges
	INSERT INTO odwa_help_text VALUES
	(1530, 
	5, 
	'
	<BR>Be aware that merge is depicted differently than in the Version History Viewer 
	 in the RON. A green arrow that points to the right {mergeout.gif, ALT="Green arrow pointing to the right"} means that this
	 object version is merged into another version. If you hover over the arrow you
	 can see to which object version the merge has taken place. A green arrow that points
	 to the left {mergein.gif, ALT="Green arrow pointing to the left"} means that another object version is merged into this
	 object version. If you hover over the arrow you will see which object version is
	 merged in.<BR>
	' );

	-- TITLE: Hide insignificant versions
	-- NODE : Hide insignificant versions
	INSERT INTO odwa_help_text VALUES
	(1520, 
	5, 
	'
	In the upper left corner of the Version History Viewer you can see the icon {prop_zoomout.gif, ALT="Hide or show insignificant versions"}. 
	 If you click on this icon the Version History Viewer will only show the significant
	 versions.<BR><BR>Significant versions are: <ul><li>current version</li><li>root</li><LI>tip
	 on any Branch</li><li>point of Branch or Merge</li><li>versions with a label starting
	 with a different character than the previous version (1.x => 2.0) and versions with
	 the strings MAJOR or SIGNIFICANT in their Check In Notes</li></ul>If you click on
	 {prop_zoomout.gif, ALT="Hide or show insignificant versions"} again, you will see all versions again.
	' );

	-- TITLE: Getting Started - Developers
	-- NODE : Getting Started - Developers
	INSERT INTO odwa_help_text VALUES
	(190, 
	5, 
	'
	As a Developer you will normally start in the Repository Navigator{ssnav.gif, ALT="Repository navigator"}. The 
	 Repository Navigator allows you to:<BR>- Select and view all elements of the Oracle
	 Designer Repository that you have access to<BR>- Start up Reports of elements that
	 have pre-defined Reports<BR>- Start up the Object Browser for elements that do not
	 have pre-defined Reports<BR>- Get more information on the element or file by clicking
	 on the information icon<BR>- Start up the Version History Viewer for a certain element<BR>-
	 Upload files and Check In elements, files and folder into the Oracle Repository
	 if you have the right privileges<BR>- Download files and Check out elements, files
	 and folders out of the Oracle Repository if you have the right privileges.<BR><BR>Go
	 the Repository Navigator Help for more information on how the Navigator works.<BR><BR>As
	 a Developer you may also want to use the Repository Search functionality if you
	 look for a specific element or do not know the folder of an element.<BR> If you
	 want to include graphics in the system documentation you may want to start up the
	 Graphics Manager.<BR>
	' );

	-- TITLE: Including Graphics in Help Items
	-- NODE : Including Graphics in Help Items
	INSERT INTO odwa_help_text VALUES
	(240, 
	5, 
	'
	Help Items can be illustrated with Graphics, in the same way any piece of Multi 
	 Line Text stored in the Repository can also include graphics. There are three way
	 of creating a reference to a graphic:<BR><BR>1) Include the name of a gif-file stored
	 in the /rob_images/ directory between curly brackets; e.g.: ^{help.gif^} {help.gif, ALT="Help"}
	 <BR>2) Include the name of an ODWA_GRAPHIC in the help item as follows: ^{GRAPHIC=graphicCode^}<BR>3)
	 Include the ivid of a file (type gif/jpg) containing a graphic you want to display,
	 stored somewhere in the Repository, in the following way: ^{REPFILE=ivid^}<BR><BR>ROB
	 will try to interpret the reference between the curly bracket and will replace the
	 brackets with the actual image you refer to.<BR><BR>You can show curly brackets
	 by using ^ as an escape character. Alternatively, any string between curly brackets
	 that does not contain either a period, the tag GRAPHIC= or the tag REP_FILE= is
	 not considered a valid graphic reference and is therefore shown as a literal string.
	 For example: {string between curly brackets} is shown, since it does not appear to
	 be a valid graphic reference.
	' );

	-- TITLE: Include Repository Object References in help items
	-- NODE : Include Repository Object References in help items
	INSERT INTO odwa_help_text VALUES
	(250, 
	5, 
	'
	Just like multi line text stored in the Repository for any repository object, Help 
	 Item text may include references to Repository Objects. Such references are translated
	 to hyperlinks from the Help Item to the ROB Report or Browser window for the indicated
	 object.<BR><BR>All object references are included in brackets ([]).The following
	 types of references can be used in ROB help items:<BR><BR>*   to a Configuration:^[CFG=cfgname^]
	 and  ^[CFG=cfgname;'||'&'||'LT;VLABEL=version label'||'&'||'GT;^] <BR>*   to a Workarea:
	  ^[WA=waname^]<BR>*   to an object irid:  ^[IRID=irid value^]<BR>*   to an object
	 ivid:  ^[IVID=ivid value^]<BR>*   to an object: ^[objectname;TYPE=short name type'||'&'||'GT;;'||'&'||'LT;VLABEL=version
	 label'||'&'||'GT;^] <BR>    and ^[objectCRN;'||'&'||'LT;TYPE=short name type'||'&'||'GT;'||'&'||'LT;VLABEL=version
	 label'||'&'||'GT;^]<BR>    Note that TYPE and VLABEL are optional!<BR><BR>The object
	 CRN is the repository folder path to an object, composed of Folder Names, slashes
	 (/) and finally the object name. (folder/folder/objectname)<BR><BR>Example of object
	 references are:<BR><BR>^[WA=GLOBAL SHARED WORKAREA^] : [WA=GLOBAL SHARED WORKAREA]<BR>
	 ^[SYSTEM FOLDER/Oracle Forms;^] [SYSTEM FOLDER/Oracle Forms;<TYPE=LAN>]<BR> ^[SYSTEM
	 FOLDER/Oracle Forms;'||'&'||'LT;TYPE=LAN'||'&'||'GT^] [SYSTEM FOLDER/Oracle Forms;<TYPE=LAN>]<BR>
	 ^[IRID=1754353890218037199243682700120836153^][IRID=1754353890218037199243682700120836153]
	' );

	-- TITLE: Repository Navigator
	-- NODE : Repository Navigator
	INSERT INTO odwa_help_text VALUES
	(400, 
	5, 
	'
	In the ROB Repository Navigator, you can browse through the workareas and configurations 
	 of the Repository through a tree-style interface. You can also access all containers
	 directly, or access the Wastebasket. These four entry types are the root nodes of
	 the navigator tree.<BR><BR>If you use the Workarea entry (and you have the right
	 privileges), the Navigator offers the interface to perform check out, check in,
	 undo check out, file download and file upload. Or you can check the workarea for
	 newer versions. For more information see the related help.<BR><BR><B>The Navigator
	 Tree</B><BR>In the navigator tree you can expand by clicking the {nodecl1.jpg, ALT="Expand Node"} symbol
	 in front of the folder, workarea or configuration. You will see the folder and sub
	 folders. With the {nodeop2.jpg, ALT="Collapse node"} symbol you can collapse the tree. If a folder contains
	 files or structured objects a node will be displayed with the word files and in
	 brackets the number of files. For structured objects you will get nodes for every
	 element type that is present in that folder. Behind the element type the number
	 of elements of that type is shown. You will not see the contents of the folder using
	 the {nodecl1.jpg, ALT="Expand node"} symbol.<BR> You can see the contents of a folder by clicking on
	 the name of the folder or expanding and then clicking on the element type or the
	 file type. If you do that on the right hand side all objects in that folder will
	 be shown. Remember that if you click on a folder with a lot of structured elements
	 it will take a while to show all elements. It is better to expand using the {nodecl1.jpg, ALT="Expand node"}
	 symbol and then choose the element type you want to need to take a look at.<BR><BR><B>The
	 Objects Pane</B><BR>On the right hand side you can see all objects in a particular
	 folder, workarea or configuration. You have the ability to order the objects on
	 name or date modified (ascending and descending) by clicking on name or date. Remember
	 that names in uppercase become for file names in lowercase. You can also start the
	 object browser ({browsemed.gif, ALT="Object browser"}), the version history viewer ({vhv.gif, ALT="Version history viewer"}) for a specific
	 object or get more information using the yellow {info.gif, ALT="Information"} symbol. <br>If you click
	 on an object that is a file the file will be opened. If you did not link the file
	 to a specific application you will be asked to pick an application.<BR>If the object
	 is a structured object clicking on the name will start up the Report for that object.
	 If no Report is available it will start the object browser for that object.<BR>You
	 can see that an object is checked out by the check mark {check_mark.gif, ALT="Check mark"}in front
	 of it or the letters CO behind the version number. In the information window you
	 can see who has checked out the object.<BR>
	' );

	-- TITLE: Repository Security Manager
	-- NODE : Repository Security Manager
	INSERT INTO odwa_help_text VALUES
	(405, 
	5, 
	'
	 In Oracle Repository 6i, there are lots of priviliges that have to be managed: privileges 
	 for workareas, folders, subfolders and configurations, and those for each individual
	 user. The Repository Security Manager allows you to Grant/Revoke privileges for users/roles.
	' );

	-- TITLE: Revoking Roles
	-- NODE : Revoking Roles
	INSERT INTO odwa_help_text VALUES
	(1460, 
	5, 
	'
	To revoke a role from a user, you need to have Grant privilege on the role.<BR><BR>Either 
	 navigate to the user and then to its roles, or navigate to the role and then
	 to its ''granted to'' users/roles.<ol><li>Click on the Revoke Role icon {deletiongr.gif, ALT="Revoke"}.</li><li>Decide
	 if you also want to reconcile. If you check this box, you revoke privileges granted
	 to the user through this role, if they are not also granted via another role. <b>Warning:
	 if the privileges of this role were also directly granted to the user but not through
	 any other role, they will still be revoked!</b></li><li>Press reconcile.</li></ol>Remember
	 that, unless you checked the Reconcile box, after the revoke of the role the user
	 still has all the access priviliges he received from the role. he just will not
	 get any new privileges from the role (since he does not have it anymore). To remove
	 all privileges a user has for now obvious reason (not through any role he currently
	 has), you could do a reconcile (see <A href="javascript:parent.showHelp(140)">Reconciling</A>).
	' );

	-- TITLE: Upload and Check In a New File
	-- NODE : Upload and Check In a New File
	INSERT INTO odwa_help_text VALUES
	(1540, 
	5, 
	'
	Uploading and checking in a new file is straight forward if you use ROB: <BR><B>1. 
	 Choose the work area in the navigator tree</B><BR>You can only upload a file in
	 the context of a workarea and you need to have the proper access rights to this
	 workarea.<BR><B>2. Choose the folder (click on the name) in which you want to upload
	 the new file</B><BR>You can only upload files in folders or application systems
	 and you need to have the proper access rights to this folder.<BR><B>3. Upload the
	 file</B><BR>In the right pane you will see a blue {addition.gif, ALT="Addition"} symbol for uploading
	 new files right behind the folder name. If you click on it you can give a description
	 to the file and indicate from where it needs to be uploaded. Click OK and your file
	 is uploaded. <BR><B>4. Check in the file (optional)</B><BR>If you want to bring
	 your file under configuration management and give it a version you should check
	 in the new file by clicking on the check in symbol {checkin.gif, ALT="Check in"} behind the file
	 you just uploaded. For more information see <A href="javascript:parent.showHelp(110)">Check
	 In</A>. If you only wanted to save a working copy than you can wait with the check
	 in of the file and do it later.<BR><B>5. Check in the folder</B><BR>Remember that
	 you can only upload new files if the folder is checked out. ROB does the folder
	 check out automatically but you yourself should check in the folder to make your
	 file available to other workareas as well. If you have more new files to upload,
	 first complete this task and check them in. As a final step you can then check in
	 the folder. Click on the check in symbol {checkin.gif, ALT="Check in"} behind the folder to do that.<BR><BR><B>WARNING</B>:
	 Undoing a check out of a folder can have the consequence that files that are added
	 do not have an owning folder and therefore are transferred into the lost+found.
	 Getting things back from the lost+found into your folder will take the repository
	 manager a lot of time since he needs to use the command line interface. So NEVER
	 undo a check out of a folder unless you are completely sure no new files where added
	 since the folder was checked out.
	' );

	-- TITLE: Check Out (and Download a File)
	-- NODE : Check Out (and Download a File)
	INSERT INTO odwa_help_text VALUES
	(120, 
	5, 
	'
	If you want to change a file you must check it out to so others know that you will 
	 change this file and other workareas cannot touch it.<BR><B>1. Select a workarea</B><BR>Select
	 the workarea in the navigator tree. You should have version privileges for this
	 workarea.<BR><B>2. Select the folder</B><BR>Select the folder or application system
	 the file is located in and click on the folder to show all the files that are in
	 the folder. You should have version privileges on this folder.<BR><B>3. Check out
	 and download the file</B><BR>Click on the check out symbol {checkout.gif, ALT="Check out"} behind
	 the file and you will be asked to give some information why you want to check this
	 file out (Also see <A href="javascript:parent.showHelp(1370)">Check Out Notes</A>).
	 You can also lock the main branch so you will be the first to check in on the main
	 branch. <BR>Together with the check out you can also download the file. It is recommended
	 to always do this, since the copy of the file that you have on your file system
	 may be out of date. You will be asked to save the file or pick an application to
	 open the file.<BR><BR><B>NOTE</B>: Be aware that although you have checked out the
	 file, this does not mean that nobody else can change it or check it in. Persons
	 that have access right to the workarea can check in the file while you have checked
	 it out. It depends a bit on how the workareas are set up if this will be a problem
	 or not. If you think it is a problem you should probably talk with your repository
	 manager to change the set up.<BR> <BR><B>Checking out structured objects</B><BR>You
	 can also check out structured objects. It works more or less the same as a file,
	 except that you can not download the structured object. After you have checked out
	 the structured object, you or someone else in the workarea can change the structured
	 object through the Oracle Designer modeling tools, the Design Editor or the RON.<BR>
	' );

	-- TITLE: Reconciling
	-- NODE : Reconciling
	INSERT INTO odwa_help_text VALUES
	(140, 
	5, 
	'
	 Repository Roles are <b>not</b> dynamic. That means: if you grant a role to a user, 
	 the user does not instantaneously inherit the privileges granted to the role. If
	 the role is allowed to see a certain folder, the user will not be able to see that
	 folder just by granting the role to the user. The Role also needs to be reconciled
	 for that user.<BR><BR>Reconciling means: ensuring that a user has all the Folder,
	 Workarea and Configuration privileges that he ''deserves'' as a result of the role
	 he has been granted. During the reconcile process, the user is granted directly
	 each privilege that is granted to the role that has been granted to him. You can
	 do that by either reconciling the role or by reconciling the user.<BR>
	' );

	-- TITLE: Granting Configurations
	-- NODE : Granting Configurations
	INSERT INTO odwa_help_text VALUES
	(1420, 
	5, 
	'
	In the ROB Security Manager, there are two ways to grant access privileges on configurations:<BR><BR><B>Starting 
	 at the user</b><BR><BR>After navigating to the user , you will see in the upper right corner a configuration
	 icon {configurationgr.gif, ALT="Configuration"}. If you click on it, you will get a list of configurations.
	 In this list you can choose one or more configurations (by using shift- or ctrl-click).
	 Specifiy the grant options for these configurations and press save.<br><BR><b>Starting
	 at an individual configuration</b><BR>After navigating to a certain configuration,
	 you will see the {db_user_rolegr.gif, ALT="Grant Roles"} icon in the upper right corner if you have
	 Admin privilege on this configuration. If you click on it, you will see a list of
	 roles and users. In this list you can choose one or more grantees (by using shift-
	 or ctrl-click). Specifiy the grant options for these roles/users and press save.
	' );

	-- TITLE: Granting Privileges
	-- NODE : Granting Privileges
	INSERT INTO odwa_help_text VALUES
	(220, 
	5, 
	'
	 There are three element types to which you can grant access privileges: Workareas,
	 Configurations, and Folders. There are two ways to do this:<ol><li>through the Grant
	 Access Privileges dialog in the Repository Object Navigator (RON) of Oracle Repository</li><li>through
	 the Security Manager of Repository Object Browser</li></ol>In both cases you
	 need to have the Admin privilege on the relevant Workarea, Configuration or Folder.
	 <BR><BR>Here we will describe the second method: using the Security Manager. You
	 can use this method both for granting privileges to Roles, and for granting privileges
	 directly to Repository Users. For each element type the Security Manager offers
	 two ways to grant the privileges: <ul><li>starting at the role or user, to grant
	 multiple elements to one role/user</li><li>starting at an individual workarea, configuration
	 or folder, to grant this element to multiple roles/users</li></ul>
	' );

	-- TITLE: Graphics Manager
	-- NODE : Graphics Manager
	INSERT INTO odwa_help_text VALUES
	(406, 
	5, 
	'
	ROB already gives you the opportunity to easily include images into reports 
	 and other multi-line text sections (info window and object browser). For more information
	 on this see  <A href="javascript:parent.showHelp(270)">Include Graphic References
	 in Reports</A>.<BR><BR>The ROB Graphics Manager adds two important features to
	 graphics:<BR>- It allows you to create hotspots in graphics. With these hotspots
	 you can jump to any URL, another image or an ROB report. This functionality is
	 especially handy for Diagrams. For an Entity Relationship Diagram, for instance,
	  it is now very easy to create hotspots for every entity and link these to the ROB
	 Entity Reports. You can also use it for screen mock ups and link one screen to another
	 by making hot spots of the buttons.<BR>- It allows you to decouple the direct reference
	 to an image in the repository multi line textfield and link to an ROB code instead.
	 This is especially handy if you use the same image in more than one multi-line textfield
	 and the image name, URL or Repository Location changes.  In the Graphics Manager
	 you just change the URL , Repository Location or name and all references are automatically
	 linked to the new graphic through the ROB graphic code.<BR>
	' );

	-- TITLE: Granting Folders
	-- NODE : Granting Folders
	INSERT INTO odwa_help_text VALUES
	(1430, 
	5, 
	'
	 In the ROB Security Manager, there are two ways to grant access privileges on folders:<BR><BR><B>Starting 
	 at the role/user</b><BR><BR>After navigating to the user or to the role (or right
	 after creation of the role), you will see in the upper right corner a folder icon
	 {foldergr.gif, ALT="Grant Folder"}. If you click on it, you will get a list of root folders. Note that
	 for granting a subfolder, you can use the Browse button. In the list of root folders
	 you can choose one or more folders (by using shift- or ctrl-click). Specifiy the
	 grant options for these folders (and decide if you want to recurse through the subfolders)
	 and press save.<br><BR><b>Starting at an individual folder</b><BR><BR>After navigating
	 to a certain folder or subfolder (either via a workarea or configuration, or via
	 All Containers), you will see the {db_user_rolegr.gif, ALT="Grant User"} icon in the upper right corner
	 if you have Admin privilege on this folder. If you click on it, you will see a list
	 of roles and users. In this list you can choose one or more grantees (by using shift-
	 or ctrl-click). Specifiy the grant options for these roles/users and press save.
	' );

	-- TITLE: Granting Workareas
	-- NODE : Granting Workareas
	INSERT INTO odwa_help_text VALUES
	(1410, 
	5, 
	'
	In the ROB Security Manager, there are two ways to grant access privileges on workareas 
	 to a role or user:<BR><BR><B>Starting at the role/user</b><BR><BR>After navigating
	 to the user or to the role (or right after creation of the role), you will see in
	 the upper right corner a workarea icon {workareagr.gif, ALT="Workarea"}. If you click on it, you
	 will get a list of workareas. In this list you can choose one or more workareas
	 (by using shift- or ctrl-click). Specifiy the grant options for these workareas
	 and press save.<br><BR><b>Starting at an individual workarea</b><BR>After navigating
	 to a certain workarea, you will see the {db_user_rolegr.gif, ALT="Grant Role"} icon in the upper right
	 corner if you have Admin privilege on this workarea. If you click on it, you will
	 see a list of roles and users. In this list you can choose one or more grantees
	 (by using shift- or ctrl-click). Specifiy the grant options for these roles/users
	 and press save.
	' );

	-- TITLE: 3. Connect the diagram gif to the diagram element
	-- NODE : 3. Connect the diagram gif to the diagram element
	INSERT INTO odwa_help_text VALUES
	(1250, 
	5, 
	'
	The last step you have to do is to connect the diagram gif, with the hotspots that 
	 you have just created, and link it in such away with the diagram element, that if
	 you select the diagram report it shows up in that report. Go to the related diagram
	 in the Repository Object Navigator and add the following to the diagram description
	 or notes ^{GRAPHIC=GRAPHIC_CODE^}, where you should replace the graphic_code with
	 the code of the graphic that you recorded in the graphic manager of Oracle Designer
	 Web Assistant.<BR><BR>You can test if it is working by going to the Reports and
	 select the work area or configuration, select the diagram type and open the Report
	 of the diagram.
	' );

	-- TITLE: 1. Create or Select a Graphic Category
	-- NODE : 1. Create or Select a Graphic Category
	INSERT INTO odwa_help_text VALUES
	(1170, 
	5, 
	'
	Before you make the graphic known to ROB you have to create a category or choose 
	 a category that already exists. Categories are mainly there to organize your graphics.<BR>Creating
	 a category is simple and straightforward. When you enter the graphics manager just
	 click on the green add-button on the right. Just fill in the name and description
	 and your are ready.<BR>If you already had created a category, it is even simpler.
	 Just open the tree and select the category to which you want to add a graphic. After
	 you have selected it you can add the graphic by clicking on the green add-button.<BR>
	' );


	-- TITLE: 2. Add a Graphic to ROB
	-- NODE : 2. Add a Graphic to ROB
	INSERT INTO odwa_help_text VALUES
	(1180, 
	5, 
	'
	To create hotspots in your images you must let ROB know which image you want to 
	 ''hotspot''. You can do this by adding a graphic.<BR>If you have created a graphic
	 category you can select this category by opening the tree, select the category so
	 it turns bold and then hit the green add button on the right to add your graphic. You
	 give the graphic a code. This can be anything although a short name is probably
	 best. You can use this code directly in multi-line text in the Oracle Repository
	 to refer to this graphic. For more information see Repository Reports, Including
	 Graphics in Reports. You now have to choose where the graphic is stored. You have
	 three options, your webserver, the Oracle Repository or the Intra/Internet. If you
	 choose the first, fill in the file name. If you choose the Oracle Repository hit
	 the browse button to start the Repository Object Selector that helps you to find
	 your graphic. For the last option you can just fill in an URL. <BR>Add a description
	 and click on apply. Now the Graphics Manager will show you the graphic.<BR><BR>By
	 choosing the hotspot editor button you can add hotspots to this graphic.<BR>
	' );

	-- TITLE: 3. Create hotspots in a Graphic using the Hotspot Editor
	-- NODE : 3. Create hotspots in a Graphic using the Hotspot Editor
	INSERT INTO odwa_help_text VALUES
	(409, 
	5, 
	'
	<BR><BR>After you have added the graphic to ROB, choose
	 the Hotspot Editor. By clicking the green add button.<BR>You can enter a sequence
	 which is only important if you have overlapping hotspots like subtypes. See help
	 on overlapping hotspots.<BR> Fill in the label and the alt text, this is the text
	 that you will see when you will move over the hotspot in your graphic.<BR>To record
	 the dimensions just click on the upper left corner of your hotspot to be in the graphic.
	 Then click on the lower right hand corner an now you have identified your hotspot.<BR>Of
	 course you added your hotspot because you want to link it to somewhere else. You
	 can either link it to another ROB graphic. Just fill in the code of the graphic.
	 Link it to another repository object or an URL.<BR><BR>If you link it to a Repository
	 object use  the Repository Object Selector to select the object. Be aware that if
	 you do not choose an element type you will have to select from a long list of objects
	 and it can take a while. Therefore always first choose an element type.<BR><BR>If
	 you want to test your hotspots click on the graphic an reload the frame (right mouse).
	 You can now check if all your hotspots are working. If you want to add more hotspots
	 always go back to the graphic first.<BR>
	' );

	-- TITLE: ROB On Line Help
	INSERT INTO odwa_help_text VALUES
	(1000, 
	5, 
	'
	<img SRC="/rob_images/rob_splash.gif" BORDER="0" ALT="ROB Splash image">
	<BR><FONT SIZE="6" FACE="MS Sans Serif">Repository Object Browser</FONT>
	<HR><FONT SIZE="2" COLOR="black" FACE="Comic Sans MS">
	<BR> Repository Object Browser <BR> (c) Oracle Corporation 2002</FONT>
	' );

	-- TITLE: 2. Use the Hotspot Wizard.
	-- NODE : 2. Use the Hotspot Wizard.
	INSERT INTO odwa_help_text VALUES
	(1210, 
	5, 
	'
	Like you would have done for normal graphics you need to make the graphic known 
	 to ROB and you have to put the graphic in a certain category. See step 1 and 2
	 in the graphics manager. <BR> You click on the hotspot editor. Go directly to the
	 magic button and launch the hotspot wizard. <BR><BR> This wizard asks you to select
	 the diagram that belongs to your graphic. Use the Repository Object Selector to
	 select the diagram. Choose the element type diagram so you can find the diagram
	 faster and easier.<BR> After you have selected the diagram hit the apply button
	 and now the hotspot wizard will create default hotspots for you for every element
	 in the diagram. It will fill in a label, an Alt text and the link to the repository
	 object automatically. The only thing you have to do is select the hotspot in the
	 tree. Go to the graphic select the upper left hand corner of the area that you want
	 to hotspot (for instance the upper left corner of an entity) click and then select
	 the lower right hand corner. Apply and you are ready. Select the next hotspot and
	 repeat the steps.<BR> 
	' );

	-- TITLE: 1. Create Graphic for an Oracle Designer Diagram
	-- NODE : 1. Create Graphic for an Oracle Designer Diagram
	INSERT INTO odwa_help_text VALUES
	(1130, 
	5, 
	'
	<BR>Creating images (gif or jpeg files) of diagrams can be done in several ways. 
	 Each method requires certain tools to be available. We will describe two different
	 methods, each with a different set of tools.<BR><BR>1. Using Paint and Netscape
	 Composer<BR>2. Using MS Word (with Internet Assistant)<BR><BR>Making the
	 diagrams clickable is done using the ROB Hotspot Editor. The steps for a diagram
	 are described in the following help topic:
	' );

	-- TITLE: Overlapping Hotspots (e.g. Super and Sub type Entities)
	-- NODE : Overlapping Hotspots (e.g. Super and Sub type Entities)
	INSERT INTO odwa_help_text VALUES
	(1050, 
	5, 
	'
	When hotspots areas overlap, the first hotspot area definition will take precedence. 
	 That means that if a particular area has been claimed by two or more hotspot definitions,
	 only the first definition will actually result in a hyperlink being available. If
	 hotspots have partial overlap, setting the sequence of those hotspots will determine
	 which hotspots gets hold of a particular area. <BR> <BR><b>Super-Types and Sub-Type
	 entities on ER-Diagrams</b><BR>The hot-spots areas you define, are interpreted starting
	 from the top downwards. Any area on the screen can only support one link, and it
	 will always be the first one in the list if there are more. New hotspots are added
	 to the bottom of the list by ROB (the list is built from the top down), but by
	 setting the Hotspot sequence property you can influence the order of the list. <BR><BR><pre>(1,1)
	  <BR>_______________________  <BR>| ________  ________   |  <BR>| | 2,2   | |6,2
		|  |  <BR>| |____4,4| |____8,4|  |  <BR>|______________________|  <BR>      
				 (10,7)  <BR></pre> <BR>This can be important for Entity Relationship
	 Diagrams where Super-type entities occupy an area that overlaps the area taken up
	 by each of its supertypes. For the ROB to be able to identify the links from sub-types,
	 they should not be overlaid by the supertype!  You should ensure to<B> first</B>
	 create the hotspots for the <B>sub-types</B> and only after that the super-type.
	 This way, you make sure the supertype area does not overlay and obscure or hide
	 the underlying/superposed sub-types areas.  <BR>(2,2) x (4,4)    Sub Type 1 <BR>
	 (6,2) x (8,4)    Sub Type 2  <BR>(1,1) x (10,7)  SuperType <BR><BR> This way, you
	 make sure the supertype area does not overlay and obscure or hide the underlying/superposed
	 sub-types areas.  <BR> <BR>If you did it the other way around, first the super type
	 and then the subtype, the ROB Hotspot Editor allows you to change the sequence
	 of the hotspot through the Sequence property for the Hotspot.  You can change the
	 sequence of the hotspots so  the SubType Hotspots will come before the SuperType
	 Hotspot. <BR>
	' );

	-- TITLE: Change how ROB recognizes Data Event Types
	-- NODE : Change how ROB recognizes Data Event Types
	INSERT INTO odwa_help_text VALUES
	(1290, 
	5, 
	'
	A Data Event is a Designer Process Event that represents a DML action. Usually, 
	 this kind of event is used to record the triggers for a Business Rule (for example,
	 the rule that a Salesman must have a Commission is triggered by the Creation of
	 an Employee, or the Update of an Employee Job or Commission).<BR><BR>ROB needs
	 to know which kind of operation the Event represents: Create, Update or Delete.
	 By default, ROB requires that the word ''CREATE'', ''UPDATE'', or ''DELETE'' occurs
	 in the On Condition property of the Process Event. You can change this default behavior
	 by updating the function cdwp_chk_event. The script for recreating this function
	 can be found in '||'&'||'lt;ROB Home'||'&'||'gt;/ddl/cdwp_cev.fnc. Do not change
	 any of the arguments, but it is OK to change the body of the function. <BR><BR>The
	 argument p_event is ''C'' when ROB needs to know if this is a Create Event, ''U''
	 when ROB needs to know if it is an Update Event, and ''D'' when ROB needs to know
	 if it is a Delete Event. If, based on the other input arguments, you can determine
	 that a Process Event represents the right kind of DML action, return ''Y''. <BR><BR>Execute
	 the modified script while logged in as the ROB Owner. Other ROB packages will
	 temporarily become invalid, but they will automatically recompile when you use the
	 relevant components of ROB. 
	' );

	-- TITLE: Change how ROB recognizes Business Rules
	-- NODE : Change how ROB recognizes Business Rules
	INSERT INTO odwa_help_text VALUES
	(1280, 
	5, 
	'
	By default, ROB thinks a Business Function is a Business Rule if the Function Label 
	 starts with ''BR''. You can change this by editing the stored function cdwp_chk_fun_is_business_rule.
	 You can find the script for replacing this function in '||'&'||'lt;ROB Home'||'&'||'gt;/ddl/cdwp_brf.fnc.
	 Do not change any of the arguments, but it is OK to change the body of the function.
	 If, based on the input arguments, you can determine that a Business Function represents
	 a Business Rule, return ''Y'', otherwise return ''N''.<BR><BR>Execute the modified
	 script while logged in as the ROB Owner. Other ROB packages will temporarily become
	 invalid, but they will automatically recompile when you use the relevant components
	 of ROB.
	' );

	-- TITLE: Finding Reports by Element Type
	-- NODE : Finding Reports by Element Type
	INSERT INTO odwa_help_text VALUES
	(1300, 
	5, 
	'
	The first tab page of the Repository Reports component (''Element Types'') offers 
	 you two ways to select an element type: direct hyperlinks and the launchpad. The
	 Element Type launchpad presents the following image for quick access to the desired
	 elements:<BR><BR>{lpad1.gif}
	' );

	-- TITLE: Repository Search
	-- NODE : Repository Search
	INSERT INTO odwa_help_text VALUES
	(402, 
	5, 
	'
	The Repository Search is a flexible tool to quickly collect a wealth of information 
	 about the objects stored in the repository. Based upon a series of search criteria,
	 you can have the search tool rapidly answer questions for you such as:<BR><BR>Show
	 me all objects ...<BR>... with a name like ...<BR>... currently checked out in a
	 certain workarea<BR>... checked out in the last couple of days<BR>... checked in
	 by a certain developer, in a certain period<BR>... of type file that contain a certain
	 string<BR>... created since date X<BR>... in the Wastebasket<BR>...<BR><BR>In the
	 top of the window you can enter your search criteria. Pressing the Search button
	 {search_round.gif, ALT="Search"} will invoke the Search query. Pressing the Reset button {reset_round.gif, ALT="Reset"}
	  will remove all search criteria from all four tab-sheets and render a fresh search
	 environment.<BR><BR>The search results will be shown in the bottom of the window.
	 You can sort the result by name, path,  type, date modified. You can open the object
	 by clicking on the name, or you can ask more information through the version history
	 viewer {vhv.gif, ALT="Version history viewer"}, the object browser {browsemed.gif, ALT="Object browser"} or the information window {info.gif, ALT="Information"}.
	 You can also show the sql that was used to get the result. You can copy and paste
	 the query to use it again later.<BR>
	' );

	-- TITLE: Repository Search
	-- NODE : Repository Search
	INSERT INTO odwa_help_text VALUES
	(402, 
	10, 
	'
	<BR>Note: if a search takes particularly long to run (e.g. more than 10 minutes) 
	 your browser or webserver session may time out and instead of getting the search
	 result, you may get the warning ''Document contained no data''. Possible solutions:
	 change the setting of the WebServer and/or the Browser, to have them allow more
	 time before a session/request is timed out. Or: change the search criteria to be
	 more selective. Or add the additional where clause 1=2 and copy and paste the query
	 (minus the line AND 1=2) into SQL*Plus or another environment.
	' );

	-- TITLE: The Contents of Repository Reports
	-- NODE : The Contents of Repository Reports
	INSERT INTO odwa_help_text VALUES
	(1310, 
	5, 
	'
	Reports are as condensed as possible: For each element type, the report contains 
	 only properties that have a value and lists of details if they exist. The layout
	 is styled after the Oracle Method and CDM Manuals. The reports are laid out in 
	 such a way that printing them renders very acceptable results.<BR><BR>Element definitions
	 in Designer are characterized not just by their own properties but usually to a
	 large extent by their references to and dependencies on other objects. For example
	 an entity and its relationships, a business function and its data usages and event
	 triggers and of course tables with their foreign keys and associated data logic
	 as well as modules with data usages, module network and associated business rules.
	 ROB reports leverage the browser hyperlink functionality by providing hyperlinks
	 for each object reference and dependency displayed in the ROB reports. By simply
	 clicking on associated elements in the report, the user can easily navigate through
	 complex dependency structures. For example from Module to Table to underlying Entity
	 to associated Domain and back.<BR><BR>Note: references to other objects potentially
	 refer to objects in another folder or application system than the one owning the
	 object that is the focus of the current report. You are only allowed to actually
	 navigate to objects that are owned by containers (folder/application system) that
	 you have access to. If that is not the case, instead of a hyperlink, you will see
	 the name of the referenced object followed by the {noacc.gif, ALT="No access"} icon, with an ALT
	 text stating: <i>Object is owned by a Folder on which USER has no access privileges.</i>.
	 <BR><B>Also See</B>
	 <BR><A href="javascript:parent.showHelp(1710)">What is CDM?</A>. 
	' );

	-- TITLE: Finding Reports by CDM Deliverable
	-- NODE : Finding Reports by CDM Deliverable
	INSERT INTO odwa_help_text VALUES
	(1330, 
	5, 
	'
	On the start page of the Repository Reports, you can find three tab pages: Element 
	 Type, CDM Fast Track and CDM Classic. <BR><BR>If you are working on a particular
	 CDM Deliverable, choose the tab page of the CDM Method you use (Fast Track or Classic).
	 Then, search the list of deliverables for the one you are working on. Following
	 the deliverable is a set of hyperlinks to all the relevant ROB Reports.
	 <BR><B>Also See</B>
	 <BR><A href="javascript:parent.showHelp(1710)">What is CDM?</A>. 
	' );

	-- TITLE: Support for CDM RuleFrame in Reports
	-- NODE : Support for CDM RuleFrame in Reports
	INSERT INTO odwa_help_text VALUES
	(1260, 
	5, 
	'
	CDM RuleFrame(See <A href="javascript:parent.showHelp(1710)">What is CDM?</A>.)
	 is a way to store business rules in Designer and to generate them 
	 into a structured business rule framework in the database server.ROB can present
	 the CDM RuleFrame objects in Designer as if they were separate element types.<BR><BR>It
	 concerns the following element types:<ul><li>Business Rules <BR>(which are actually
	 stored as Business Functions in Designer)</li><li>Business Rule Design Definitions
	 <BR>(which are actually stored as Table Triggers and corresponding PL/SQL Definitions
	 in Designer)</li></ul>In addition, ROB knows how to link these element types to
	 each other and to Entities, Functions, Tables and Modules. Even if you only recorded
	 (Data) Events that trigger a Business Rule, and the data usages of a Business Function,
	 ROB can see that the data usage triggers a data event, and so implicitly triggers
	 the Business Rule.
	' );

	-- TITLE: Check In Branch
	-- NODE : Check In Branch
	INSERT INTO odwa_help_text VALUES
	(1340, 
	5, 
	'
	You can check in an object to a branch other than the one from which it was checked 
	 out. The default value for the Check In Branch is derived as follows:<ul><li>If
	 a default check in branch has been specified for the current workarea, that branch
	 is taken as default value for this item, unless other versions than the current
	 one (or immediate predecessors / successors) already exist on that branch (which
	 would prevent checking in on that branch); in that case the current branch is taken
	 as default.</li><li>If no default check in branch is indicated for the current workarea,
	 then the current branch from which the object was checked out, is taken as default.</li></ul>The
	 list of branches contains only entries that represent ''accessible'' branches. That
	 means: branches that not already contain versions of this object, other than the
	 current version (or immediate predecessors / successors).
	' );

	-- TITLE: Check In with immediate Check Out
	-- NODE : Check In with immediate Check Out
	INSERT INTO odwa_help_text VALUES
	(111, 
	5, 
	'
	You can choose to immediately Check Out again after Checking In. In that case you 
	 have to tick the checkbox ''Check Out'' in the Check In dialog.<BR><BR>This enables
	 you to continue working on the object after ensuring that<ul><li>the latest version
	 is available to other users,</li><li>the current state has been safely stored (savepoint
	 is set).</li></ul>If the object was initially checked out with a lock, it will be
	 checked out again with lock. The current check out notes will be reused for the
	 new check out.
	' );

	-- TITLE: Version Label
	-- NODE : Version Label
	INSERT INTO odwa_help_text VALUES
	(1350, 
	5, 
	'
	The version label is attached to the object when checked in. Depending on the repository 
	 policy, this version label can be generated automatically by the system, or defined
	 by the user.'||'&'||'nbsp; ROB will always display a default value, which is the
	 one generated by the Automatic Version Generation algorithm, assuming the object
	 is checked in on the same branch it was checked out of. You can override this default
	 value with any value up to 32 characters. Note that the version label must be unique
	 among all versions of the object.
	' );

	-- TITLE: Search and Repository Access Privileges
	-- NODE : Search and Repository Access Privileges
	INSERT INTO odwa_help_text VALUES
	(1590, 
	5, 
	'
	The Repository Search facility adheres to the Repository Access Privileges. That 
	 means: a user performing a search will only see objects in the search result that
	 he is allowed to see (because they are owned by Folders that he has at least Select-privilege
	 on). This is of course the proper way to the work: it would be confusing is a search
	 operation renders results that are otherwise invisible to the user.<BR><BR>However,
	 for some users it would be extremely useful to be able to perform a truly global
	 search in the Repository, without the need to have access to every single folder
	 in the repository. For example the Repository Administrator or Enterprise Configuration
	 Manager probably should be able to search across the entire repository. We have
	 catered for these types of users in the following way: <BR>the table ODWA_PREFERENCES
	 contains a number of preferences that influence the workings of the Oracle Designer
	 Web Assistant. One such preference is called <b>global_search_users</b>. The value
	 of this preference should be a comma-delimited list of database/Repository usernames
	 of users that are allowed to perform a global Search, ignoring access privileges.
	 To set the value of this preference, you could use a statement like this:<BR><pre>update
	 odwa_preferencesset    preference_value  = ''USER1,USER2''where  preference_name
	   = ''global_search_users''/</pre><BR>After committing this statement, USER1 and
	 USER2 can perform searches in ROB that do not take their access privileges into
	 account; they may see objects in the search result that strictly speaking are not
	 accessible to them. We recommend to only allow few, trusted and skilled users to
	 perform these global searches. 
	' );

	-- TITLE: Basic Search Options
	-- NODE : Basic Search Options
	INSERT INTO odwa_help_text VALUES
	(1090, 
	5, 
	'
	With the basic search you can search on name, element type, work area or folder.<BR><BR><B>Name</B><BR>The 
	 name search is case insensitive and you can use_ ,  % or * as wildcards e.g. customer%
	 to get all objects whose name start with customer. Or *.fm_ to find all objects
	 with an extension that starts with <i>fm</i> and has one additional character. If
	 you want to search case sensitive check the check box behind name. Note that a case
	 sensitive search is faster than a case-insensitive.<BR><BR><B>Tip latest</B><BR>Tip
	 latests means that only the latest version will be shown for each branch. If you
	 want to see all versions uncheck this checkbox<BR><BR><B>Include Nested Folders</B><BR>If
	 you check this checkbox the search will not only look in the given folder but also
	 in all of its subfolders. Depending of the number of subfolders this query may take
	 longer to very long.<BR><BR>As an alternative to checking this check-box (which
	 instructs the search tool to traverse the entire nested folder structure and results
	 in a rather nasty execution plan) you can make use of an additional where-clause
	 (see the Advanced search options). Instead of explicitly walking through the folder-tree,
	 we can instruct the search tool to only return objects whose Folder-path is LIKE
	 a certain value. The where-clause required for this:<BR><pre> jr_name.get_path(e.ivid,''NAME'',''/'',0)
	 like ''Folderpath/%'' </pre><BR>If for example we want to look for all objects in
	 the <B>HRM/oracle/....</B> folder tree, instead of selecting the HRM/oracle folder
	 and checking the <i>include nested</i> check box, we could add the additional where
	 clause:<BR><pre> jr_name.get_path(e.ivid,''NAME'',''/'',0) like ''HRM/oracle/%''
	 </pre><BR>and the result would be the same. This second approach in most cases seems
	 to render a result much faster than the first (included nested), especially when
	 there are additional search criteria (such as name, type).
	' );

	-- TITLE: Check Out Notes
	-- NODE : Check Out Notes
	INSERT INTO odwa_help_text VALUES
	(1370, 
	5, 
	'
	The Check Out Notes are meant to describe why you are doing this check out. The 
	 notes can be seen by other users, if they are wondering what you are doing with
	 the object. You typically describe what you plan to do, why (for example enhancement
	 request or bug number), and how long it will probably take. They will also be used
	 as the default for the Check In notes. The Check In notes are meant to describe
	 what changes were made, so it will help you remember if you already fill in what
	 you know at the moment of Check Out.
	' );

	-- TITLE: Repository - File System Synchronization (technical notes)
	-- NODE : Repository - File System Synchronization (technical notes)
	INSERT INTO odwa_help_text VALUES
	(290, 
	5, 
	'
	This is a technical description of the way file synchronization works in the RON 
	 (Repository Object Navigator) of Oracle Repository.<P>It is assumed that normally,
	 any editing of the file''s contents is done using filesystem facilities (editors,
	 graphics tools, for example), and that the repository is used for managing versions
	 of the contents (creating versions, comparing and merging, for example).</P><P>Synchronization
	 is a scheme for keeping the contents of operating system files in step with their
	 equivalents in the repository, and vice versa, so that when one set of contents changes,
	 the other set of contents are refreshed to reflect the changes. Synchronization can
	 therefore either cause the file system be refreshed from the repository (download),
	 or cause the repository contents to be refreshed from the file system (upload). </P><P>One
	 of two approaches to synchronization can be adopted by the caller: <BR><BR><UL>
	  <LI>Mapped - This uses a pre-defined folder mapping between    a root container
	 in the repository and a corresponding operating system folder. <BR>    <BR>  </LI>
	  <LI>Unmapped - This does not require a folder mapping: the File Service uses a
	 supplied    repository path and file system path to perform the synchronization.
	 </LI></UL><P><STRONG>Notes:</STRONG> <BR><BR><OL>  <LI>Synchronization is not automatic.
	 The calling application must schedule a call to    perform the synchronize operation
	 explicitly according to its own requirements (for    example, in response to a user
	 request, or when a check-in or checkout operation is    performed). <BR>    <BR>
	  </LI>  <LI>The repository used for synchronization is the one specified in the
	 RepositoryConnection Object created by each FileService object. <BR>    <BR>  </LI>
	  <LI>The decision about whether to upload or download is determined by establishing
	 which    ''edition'' of a file has most recently changed. The most recently changed
	 edition replaces    any other edition. <BR>    <BR>  </LI>  <LI>All operations described
	 here require a context workarea to be set. <BR>    <BR>  </LI>  <LI>The contents
	 of a file are stored into the CONTENTS_CLOB, CONTENTS_BLOB, or    COMPRESSED_CONTENTS
	 column of a PRIMARY_ACCESS_FILE object in the repository, depending on    whether
	 the file''s type is defined in the File Type Registry  (FTR) as text, binary,  
	  or compressed. If the file''s name matches a pattern defined in the File Type Registry
	 as    COMPRESSED, uploading compresses the file before storing it in the repository,
	 and    decompresses the contents before downloading. <BR>    <BR>  </LI>  <LI>In
	 general, the repository definitions of container objects are not updated by upload
		and download operations. The exception is where the caller specifies that a folder
	 that    has new files added to it must be versioned).  </LI></OL>
	' );

	-- TITLE: Repository - File System Synchronization (technical notes)
	-- NODE : Repository - File System Synchronization (technical notes)
	INSERT INTO odwa_help_text VALUES
	(290, 
	10, 
	'
	<P>Synchronization can operate at file level, container level, or workarea level. 
	 <BR><BR><UL>  <LI>Synchronizing a single file results in the specified file being
	 uploaded or downloaded    (if the checking of its <A HREF="#CRCCalc">CRC</A> so
	 indicates). <BR>    <BR>  </LI>  <LI>Synchronizing a container synchronizes all
	 files in that container and any sub    containers, if recursion is specified. <BR>
		<BR>  </LI>  <LI>Synchronizing a workarea results in synchronization of all mapped
	 containers in that    workarea. </LI></UL><P>If a file has changed in both the repository
	 and the file system, then the synchronization process attempts to rename the file
	 system file to <filename>.KEEPand then downloads the repository copy. The repository
	 user must then decide which copy is required.</P><P>The synchronization process maintains
	 and compares the CRC values found in: <BR><BR><UL>  <LI>The repository <BR>    <BR>
	  </LI>  <LI>The .RVI file <BR>    <BR>  </LI>  <LI>The file system </LI></UL><P>and
	 either uploads or downloads depending on the results, as follows: <OL>  <LI>If the
	 repository and file system CRCs are the same, the file has not been changed, no
		action is taken with respect to the specific file, and if synchronization must
	 be    restarted, files that were found to be unchanged are not processed a second
	 time. <BR>    <BR>  </LI>  <LI>If they are different,  the .RVI CRC is compared.
	 <P>If the repository and .RVI CRCs are the same, this is taken to mean the file
	 system file has changed. If the file    system CRC and the .RVI CRC are the same,
	 this is taken to mean that the repository file    has changed. If all three CRCs
	 are different, both the file system file and the repository    file have changed.
	 In that case, the synchronization process:<OL>      <LI>Makes a copy of the file
	 system file. The name of the copy has an extension of ''.keep''. </LI>      <LI>Refreshes
	 the file system file with the version in the repository. </LI>    </OL>  </LI></OL><P>Following
	 the first successful synchronize operation, further attempts at synchronization require
	 the .RVI file to be available. </P><P><STRONG>Note:</STRONG> Using upload or download
	 does not create or use a .RVI file. </P><P>To perform file synchronization, the
	 caller instantiates the FileService class, and calls its <A HREF="#cfs_synchronize">synchronize</A>
	 method. </P><H4>Deleting Removed Files During Synchronization</H4><P>During a synchronize
	 operation, files that have been ''removed'' from the repository by deletion or by
	 exclusion from the workarea can also optionally be deleted from the filesystem.</P><P>For
	 this to occur, the file must have been synchronized at least once prior to being removed
	 from the repository, otherwise it is considered to be a new file (and uploaded accordingly).</P><P>If
	 you choose not to delete a ''removed'' file from the file system, it continues to
	 be marked as a removed file (unless the repository file reappears as a result of
	 refreshing the workarea). To get the file to be uploaded to the repository again,
	 it must be explicitly uploaded. To process a number of removed files in this way,
	 upload a parent folder with the FS_RECURSE flag set and the FS_OVERWRITE flag unset
	 (that is, upload new files only). </P><P>Deletion of ''removed'' folders is not currently
	 implemented. </P>
	' );

	-- TITLE: Getting Started - End Users
	-- NODE : Getting Started - End Users
	INSERT INTO odwa_help_text VALUES
	(180, 
	5, 
	'
	As an End User you will normally start in the <A href="javascript:parent.showHelp(403)">Report 
	 section</A>{ssreports.gif, ALT="Report section"}. From there you can choose an element or a project deliverable
	 that you need to review.  With a few clicks you can see all the system documentation
	 without having to struggle through a large pile of papers. These are the steps that
	 you need to take:<BR><BR><B>1. Choose a Workarea or Configuration</B><BR> A workarea
	 is an area that the development team uses to develop the system at hand. They can
	 ask you to review certain elements when they are developing it. If the project team
	 delivers the system documentation more formally they will probably have made a configuration,
	 which you can compare with a release.<BR><BR><B>2. Choose the way you want to review
	 per element or per CDM Fast Track or CDM Classic Deliverable</B><BR>You have three
	 entry points to get to the system documentation. First you can just choose an element
	 like Business Functions. This will provide a list with all the Business Functions
	 in the workarea of configuration. You can also review per deliverable as described
	 in the project plan. Choose the approach the project team is following by clicking
	 on the tabs on top of the page and then choose the deliverable.<BR><BR><B>3. Drill
	 down the elements you need to review</B><BR>Some elements have Reports for others
	 you have to start to use the object browser. The Reports give you the opportunity
	 to not only see all the properties but also all the relation to other elements.
	 For instance an Entity Report includes information about related Business Rules
	 and Business Functions that use the particular Entity. Through the hyperlinks you
	 can immediately drill down to these related elements.<BR>When Reports are not available
	 you can use the Object Browser to get information about the properties of the element
	 and the subordinate relationships.<BR>If you want to open files just go to the files
	 section this will provide you with a list of files in the context area. By clicking
	 on the name you can open the file. You can also get more info about the file by
	 clicking on the information symbol {info.gif, ALT="Information"}.
	 <BR><B>Also See</B>
	 <BR><A href="javascript:parent.showHelp(1710)">What is CDM?</A>. 
	' );

	-- TITLE: Automatic check out of folder / application system
	-- NODE : Automatic check out of folder / application system
	INSERT INTO odwa_help_text VALUES
	(1390, 
	5, 
	'
	The ROB file uploaded will automatically check out the folder or application system, 
	 when all of the following conditions hold:<BR><BR>1. The user wants to upload a
	 new file<BR>2. The Folder or Application System is currently checked in<BR>3. The
	 user has the Version privilege on the current Workarea and Folder/Application System<BR><BR>The
	 Check Out notes of the Folder/Application System will reflect the fact that it was
	 automatically checked out through ROB because of a user request to upload a new
	 file.<BR><BR>The tool will not automatically check in the Folder or Application
	 System.<BR><BR>
	' );

	-- TITLE: Getting Started - Repository Managers
	-- NODE : Getting Started - Repository Managers
	INSERT INTO odwa_help_text VALUES
	(200, 
	5, 
	'
	As Repository Manager you normally start in the main start screen {sshome.gif, ALT="Start screen"}of 
	 the Repository Object Browser.  From there you can reach all functionality like
	 the Repository Navigator, Repository Search and the Object Browser. In addition
	 there are three management tasks you can perform:<BR>- Browse and Manage Users,
	 Roles and Privileges <BR>- Manage Graphics that are used in ROB, under the option
	 Management Facility<BR>- Purge Data that is used in ROB tables <BR>
	' );

	-- TITLE: Check In Notes
	-- NODE : Check In Notes
	INSERT INTO odwa_help_text VALUES
	(1360, 
	5, 
	'
	The check in notes should list the changes made between the previous version and 
	 the version you are checking in. Typically these notes will contain an indication
	 of:<ul><li>what changes were made, functionally and otherwise</li><li>why were these
	 changes made (reference to Bug Id, Enhancement Request, Change Report)</li><li>which
	 interface elements were changed/added/removed</li><li>which dependencies on external
	 elements were changed</li></ul>The default for the Check In Notes is taken from
	 the Check Out notes.
	' );

	-- TITLE: Check In (and Upload Existing Files)
	-- NODE : Check In (and Upload Existing Files)
	INSERT INTO odwa_help_text VALUES
	(110, 
	5, 
	'
	If you are ready with your changes you can check in and upload your file using ROB.<BR><B>1. 
	 Choose the workarea<BR>2. Choose the folder <BR>3. Check in the file and automatically
	 upload</B><BR>Click on the check in symbol {checkin.gif, ALT="Check in"} behind the file and check
	 in and immediately upload the file. You will be asked on which branch you want to
	 check in. This is normally the MAIN branch but might be a different one depending
	 on how you have set up branching. Also see <Ahref="javascript:parent.showHelp(1340)">Check
	 In Branch</A>. You can also immediately <Ahref="javascript:parent.showHelp(111)">Check
	 Out again</A> if you want to proceed working. Furthermore you will be asked to provide
	 a <Ahref="javascript:parent.showHelp(1350)">Version Number</A> and <Ahref="javascript:parent.showHelp(1360)">Check
	 In Notes</A>. As a last step you have to provide the file location.<BR> After clicking
	 on the Upload and Check in button the file will be checked in and uploaded at the
	 same time.
	' );

	-- TITLE: Undo Check Out
	-- NODE : Undo Check Out
	INSERT INTO odwa_help_text VALUES
	(130, 
	5, 
	'
	When an object is checked out, the ROB Repository Navigator offers you the option 
	 of undoing the check out. You must have navigated to the object by first choosing
	 the workarea into which the object was checked out. Then click on the undo checkout
	 symbol {undocheckout.gif, ALT="Undo checkout"} behind the file.<BR><BR>After the Undo Check Out, the
	 checked out version is deleted. The navigator automatically requeries and now shows
	 the object version it was checked out from.<BR><BR>When you Undo Check Out for a
	 file, you can also choose to download immediately after undoing the check out (so
	 you will then download the predecessor of the checked out object).<BR><BR><B>Undo
	 Check Out of a Folder</B><BR>WARNING: Undo check out of a folder can have the consequence
	 that objects that are added do not have an owning folder and therefore are transferred
	 into the lost+found. Getting things back from the lost+found into your folder will
	 take the repository manager a lot of time since he needs to use the command line
	 interface. So NEVER undo a check out of a folder unless you are completely sure
	 no new files or objects where added since the folder was checked out. 
	' );

	-- TITLE: Management Facility
	INSERT INTO odwa_help_text VALUES
	(1550, 
	5, 
	'
	The management facility offers functionality to more easily manage the Oracle Repository 
	 especially in the area of access right to the Oracle Repository  and it offers functionality
	 to manage ROB itself. You have the ability to purge ROB data and use the Graphics
	 Manager. You may delegate the functionality of the Graphics Manager to a teamlead
	 or a developer because the graphics managers allows you to enhance the system documentation
	 with clickable graphics. 
	' );

	-- TITLE: Uploading Files
	-- NODE : Uploading Files
	INSERT INTO odwa_help_text VALUES
	(100, 
	5, 
	'
	Uploading a file in the repository you normally do for a new file or when you changed 
	 the file. If you want to bring your file under configuration management you also
	 need to check it in. For more information see<A href="javascript:parent.showHelp(1540)">Upload
	 and Check In a New File</A> and<A href="javascript:parent.showHelp(110)">Check In
	 (and Upload Existing Files)</A>.<BR><BR>If you only want to do an upload to save a working copy, you typically
	 do not check in the file. For a new file you can do as described in the section
	 <A href="javascript:parent.showHelp(1540)">Upload and Check In a New File</A> and
	 not do the check in. For an existing file you can click on the upload symbol {upload.gif, ALT="Upload"}
	 behind the file to just upload the file. <BR><BR><i>Files are not compressed when
	 uploaded</i><BR>You may have indicated in the Repository File Registry that files
	 with certain extensions should be stored in compressed format to save space. Unfortunately,
	 the ROB Upload mechanism cannot perform the compression of files. Therefore, regardless
	 of the setting in the File Registry, any file uploaded through ROB will be uncompressed.<BR><BR>Also
	 see: <a href="javascript:parent.showHelp(1380)">Known Restrictions of File Upload</A>
	' );

	-- TITLE: Repository Object Browser
	-- NODE : Repository Object Browser
	INSERT INTO odwa_help_text VALUES
	(401, 
	5, 
	'
	The Repository Object Browser allows you to select an element and view all its properties 
	 (on the right hand side). You can also view all the relationships and secondary
	 elements that are owned by the selected object. If you click on these relationships
	 or secondary elements, their properties are shown on the right hand pane. This means
	 for instance that if you choose an entity you can see the attributes, the relationships
	 and the unique identifiers. <BR>The Repository Object Browser works for all structured
	 elements and is very much like the Repository Object Navigator of the Oracle Repository
	 on the web. Just hit the browse button {browse_round.gif, ALT="Browse"} select an object with
	 the Repository Object Selector and that''s all. <BR><BR>If the properties include
	 a multi-line text field with text you can click on it to better read the text. You
	 also have the ability to jump to reports or the object browser of objects that are
	 mentioned in the properties. For instance a relationship of an entity has a property
	 ''other entity''. By clicking on this other entity you launch the report of this
	 other entity.<BR><BR>All properties that are mandatory in Oracle Designer have a
	 red prompt. Default you only see the properties that have a value. If you want to
	 see all the properties you can click on the glasses-button {prop_zoomout.gif, ALT="Show all properties"} that
	 you can find in the title bar of the property palette.<BR>
	' );

	-- TITLE: Purge Session Data
	-- NODE : Purge Session Data
	INSERT INTO odwa_help_text VALUES
	(1560, 
	5, 
	'
	To operate ROB needs to hold some session data. Every time a page is requested 
	 by the Browser from the ROB cartridge in the WebServer, a new session context is
	 created by the ROB database application. This new session context is derived from
	 the session that did the page request superseded by any new context settings passed
	 along in the page request. To properly support the Back operation in the Web Browser,
	 as well as return to URLs visited in earlier sessions, the Session information is
	 recorded by ROB in a table called ODWA_SESSIONS. The number of rows in this table
	 increases with the number of page requests done from the ROB application. <BR>This
	 does not only mean that database space is held, it also results in slight but eventually
	 noticeable performance degradation for new page requests, since every time the originating
	 session record is looked up in this table.<BR>It is recommended to periodically
	 purge this old session data through this screen. 
	' );

	-- TITLE: Check Newer Versions for Workarea
	-- NODE : Check Newer Versions for Workarea
	INSERT INTO odwa_help_text VALUES
	(1570, 
	5, 
	'
	A preview of a workarea refresh and the workarea refresh itself can take quite a 
	 long time. To give you an idea what might happen during the refresh ROB offers
	 the option to speedily check for newer versions. In this way you can better decide
	 if you want to do a refresh or not.<BR> You can check for newer version following
	 these step:<BR><B>1. Click on a workarea</B><BR><B>2. Start up the Object Browser
	 for this workarea</B><BR>On the right hand side you see the workarea with behind
	 it the object browser symbol {browsemed.gif, ALT="Object browser"}. Click on this symbol to start the
	 Object Browser.<BR><B>3. Check for new versions</B><BR>This will give you a list
	 of: <BR>- Later versions for objects in Workarea <BR>- Objects owned by Folder Versions
	 already in workarea  but not yet themselves in the workarea - Objects owned by Folders
	 (not yet in the workarea) that are owned by Folders Versions that are already in
	 workarea<BR> - Objects not yet in the workarea that are owned by newer versions
	 of Folders already in workarea<BR><B>NOTE</B>: This overview is not the same as
	 a preview of the workarea refresh. It only gives you an indication of newer versions.
	 If your workarea is intended to work with the newest versions of objects it might
	 be that it comes close to the preview of the workarea refresh.<BR>
	' );

	-- TITLE: Known Restrictions of the File Upload functionality
	-- NODE : Known Restrictions of the File Upload functionality
	INSERT INTO odwa_help_text VALUES
	(1380, 
	5, 
	'
	The file upload facility suffers from some known restrictions when used with a WebServer 
	 that is not running on the NT operating system. <BR><BR><i>Compression</i><BR>Since
	 for other operating systems, the Repository Java File API is not available, the
	 ROB upload functionality cannot make use of the Repository Compression algorithm
	 that normally is applied to files of file types that have been defined as Compressed
	 in the Repository File Registry. All files uploaded through ROB (not on an NT Web
	 Server) will be uncompressed.<BR><BR><i>CRC value</i><BR>Along the same lines, the
	 upload with WebServers cannot use the Repository algorithm to calculate the CRC (Cyclic
	 Redundancy Check) for the file that is being uploaded. This value is not required.
	 However, it is used in the Repository File System Synchronization algorithm. See
	 for details <Ahref="javascript:parent.showHelp(290)">Repository-File System Synchronization</A><BR><BR>The
	 CRC values are set to NULL for all files uploaded through ROB. Currently developed
	 by the iDevCoE: a utility that can be used to calculate those CRC values for files
	 that were uploaded through ROB. This utility can be run as a batch job on any Windows
	 NT Client. See for details  <Ahref="javascript:parent.showHelp(1030)">CRC Corrector
	 Utility</A>
	' );

	-- TITLE: CRC Corrector Utility
	-- NODE : CRC Corrector Utility
	INSERT INTO odwa_help_text VALUES
	(1030, 
	5, 
	'
	The CRC Corrector Utility consists of a Java Application, packaged in a jar-file, 
	 that can be run from a bat-file. It accepts the following parameters (at least one
	 them should have a value):<BR><BR>* waName - name of a Workarea<BR>* folderIrid
	 - irid value of a Folder<BR>* objectIrid - irid of a Repository Object<BR><BR>All
	 files within the context specified by these parameters where the CRC value is NULL
	 are processed and will be updated with their proper CRC value. For example: if the
	 utility is run with only a value for folderIrid, then all versions of files owned
	 by that folder with a CRC is NULL are processed. If the context parameters are set
	 to waName=MY_WA and folderIrid=3267321763215, then for all files owned by the indicated
	 folder the versions in the MY_WA Workarea are inspected and when the CRC value is
	 NULL the file version is processed.<BR><BR>This utility is currently being developed
	 by the iDevCoE. It may be published on OTN and it may be made available through
	 Oracle Consulting. Do not hesitate to ask for it if the nullification of the CRC
	 values get in your way.
	' );

	-- TITLE: Audit Search Options
	-- NODE : Audit Search Options
	INSERT INTO odwa_help_text VALUES
	(1120, 
	5, 
	'
	With the audit search tab you can actually see what people are doing. You can answer 
	 question like what did this person change the last week. <BR><BR><B>Date fields</B><BR>After-date
	 fields also include the date that you specify. In other words after means on and
	 after. You can also specify an hour or an hour and minutes.<BR><B>Wastebasket State</B><BR>If
	 you delete an object it will go to the wastebasket first. You can also see objects
	 in the wastebasket by choosing ''only wastebasket contents''.<BR>
	' );

	-- TITLE: Repository Object Selector
	-- NODE : Repository Object Selector
	INSERT INTO odwa_help_text VALUES
	(1580, 
	5, 
	'
	The Repository Object Selector is a generic facility to select objects. It is used 
	 in many components of the Repository Object Browser. The functionality is quite straight forward. You
	 need to know the following to make optimal use of the Repository Object Selector.<BR><BR><B>Selecting
	 folders, workareas or configurations</B><BR>If you need to select a folder you need
	 to click on the symbol before the folder name. Clicking on the folder name it self
	 will drill down to the subfolders and the objects in that folder. This is also true
	 for workareas and configurations.<BR><B>Element Type Filter</B><BR>If you open a
	 folder with a lot of different elements you might notice that it takes a while before
	 all these elements are shown on the screen. To make this faster you can filter the
	 elements by specifying the element type e.g. diagrams. Now only the diagrams are
	 displayed.
	' );

	-- TITLE: Version Search Options
	-- NODE : Version Search Options
	INSERT INTO odwa_help_text VALUES
	(1110, 
	5, 
	'
	The version search tab gives you the capability to search objects by their version 
	 information. The search fields are quite straight forward. <BR><B>Date fields</B><BR>After-date
	 fields also include the date that you specify. In other words after means on and
	 after. You can also specify an hour or an hour and minutes.<BR><B>Root Versions
	 Only</B><BR>If you check this check box only the first version of an object will
	 be shown this object will always be on the main branch.<BR><B>Check In Notes Contain</B><BR>This
	 field can be very useful if you for instance refer to an issue number in the check
	 in notes. Just specify the issue number and all objects that have this issue number
	 in the check in notes will be shown.<BR>
	' );

	-- TITLE: ROB Operations
	-- NODE : ROB Operations
	INSERT INTO odwa_help_text VALUES
	(1020, 
	5, 
	'
	As an ROB Administrator you do not have to do much to keep it running. You might 
	 need to manage the preferences or purge the ROB session data</A> now and then, that''s all.
	' );

	-- TITLE: On Line Help System
	-- NODE : On Line Help System
	INSERT INTO odwa_help_text VALUES
	(150, 
	5, 
	'
	The ROB On Line Help System contains entries for many different aspects of the 
	 ROB tools and facilities. The On Line Help System is partly context 
	 sensitive; that means: a number of ROB facilities contain direct links, through the help gif
	 <IMG SRC="/rob_images/help.gif"> to associated help items.
	' );

	-- TITLE: Repository Reports
	-- NODE : Repository Reports
	INSERT INTO odwa_help_text VALUES
	(403, 
	5, 
	'
	An important component in ROB is formed by more than a dozen reports. For the most 
	 important Designer Element Types, ROB provides reports with all the relevant details
	 of selected objects. These reports are particularly useful to less skilled Designer
	 users, for example acceptance testers, QA staff, or application end-users. <BR>The
	 reports are accessible from the Repository Reports section {ssreports.gif, ALT="Repository reports"}, but
	 also through object hyperlinks in the Repository Navigator tool, the Repository
	 Object Browser and the Repository Search Facility. <BR><BR>The basic way of working
	 is as follows:<BR><B>1. Choose a context Workarea or Configuration</B><BR>Use the
	 drop down list for this. This list only shows the workareas and configurations that
	 you have access to.<BR><B>2. Choose an Element Type</B><BR>There is also an element type for uploaded files.<BR><B>
	 3. Now a list of elements of the requested type in this workarea/configuration is shown</B><BR>This
	 list can be ordered on name or date modified.<BR><B>4. Pick the element you are
	 looking for and click on the name to start the report</B><BR>On top of the report
	 you have hyperlinks to jump to different sections within the report. In the report
	 itself there are  a number of hyperlinks that allow you to navigate to reports of
	 other objects. Reports can also contain graphics that may link you to other reports,
	 images or somewhere on the internet or intranet. 
	' );

	-- TITLE: Enhancing the Repository Reports
	-- NODE : Enhancing the Repository Reports
	INSERT INTO odwa_help_text VALUES
	(1320, 
	5, 
	'
	Reports can be further enhanced through the use of Graphics. Simple tags in the 
	 Multi Line Text blocks of Designer elements are interpreted by ROB and translated
	 into images in the Reports. The navigation options can also be extended, even in
	 two ways: <BR>1. The multi line text blocks can contain references to repository
	 objects, again using simple tags, <BR>2. The graphics can be made ''clickable''
	 through the definition of hotspots. These hotspots can associate an area on the
	 image with an object in the repository, another graphic or even a simple URL on
	 the Intranet or Internet. In the report, such hotspot definitions lead to clickable
	 areas that provide navigation to whatever is associated  with the hotspot. You can
	 create hotspots using the <A href="javascript:parent.showHelp(406)">ROB Graphics
	 Manager</A>.<BR><BR>
	' );

	-- TITLE: Include Repository Object References in Reports
	-- NODE : Include Repository Object References in Reports
	INSERT INTO odwa_help_text VALUES
	(280, 
	5, 
	'
	Additional references between Repository Objects and their navigation options can 
	 be added to the reports, by specifying such references in the Multi Line Text blocks
	 of the repository object with the reference(s). Such references are translated to
	 hyperlinks from the object to the ROB Report or Browser window for the associated
	 object.<BR><BR>All object references are included in brackets (^[ ^]). The following
	 types of references can be used.<BR><BR>*   to an object: ^[objectname;TYPE=short
	 name type'||'&'||'GT;;'||'&'||'LT;VLABEL=version label'||'&'||'GT;^] <BR>    and
	 ^[objectCRN;'||'&'||'LT;TYPE=short name type'||'&'||'GT;'||'&'||'LT;VLABEL=version
	 label'||'&'||'GT;^]<BR>    Note that TYPE and VLABEL are optional!<BR>*   to a Configuration:^[CFG=cfgname^]
	 and  ^[CFG=cfgname;'||'&'||'LT;VLABEL=version label'||'&'||'GT;^] <BR>*   to a Workarea:
	  ^[WA=waname^]<BR>*   to an object irid:  ^[IRID=irid value^]<BR>*   to an object
	 ivid:  ^[IVID=ivid value^]<BR><BR>The object CRN is the repository folder path to
	 an object, composed of Folder Names, slashes (/) and finally the object name. (folder/folder/objectname)<BR><BR>Example
	 of object references are:<BR><BR>^[EMPLOYEE^] : This will start up the Entity Report
	 of entity Employee. <BR>^[WA=GLOBAL SHARED WORKAREA^] : [WA=GLOBAL SHARED WORKAREA]<BR>
	 ^[SYSTEM FOLDER/Oracle Forms;^] [SYSTEM FOLDER/Oracle Forms;<TYPE=LAN>]<BR> ^[SYSTEM
	 FOLDER/Oracle Forms;'||'&'||'LT;TYPE=LAN'||'&'||'GT^] [SYSTEM FOLDER/Oracle Forms;<TYPE=LAN>]<BR>
	 ^[IRID=1754353890218037199243682700120836153^][IRID=1754353890218037199243682700120836153]
	' );

	-- TITLE: Add a New ROB User
	-- NODE : Add a New ROB User
	INSERT INTO odwa_help_text VALUES
	(1240, 
	5, 
	'
	[Text removed] 
	' );

	-- TITLE: Create Folder
	-- NODE : Create Folder
	INSERT INTO odwa_help_text VALUES
	(1600, 
	5, 
	'
	The {addfolder.gif, ALT="Add Folder"} Add Folder icon is shown in the right pane of the Repository 
	 Navigator whenever the following conditions are met:<BR>* a workarea context is
	 set<BR>* the user has the Manage Containers System privilege (assigned in the Repository
	 Administration Utility by the Repository Owner)<BR>* the user has the Insert privilege
	 on the current workarea<BR>* if a folder is selected: the user has the Insert privilege
	 on the current folder; if the folder is checked in, the user also needs the Version
	 privilege on both the Workarea and the Folder<BR><BR>Pressing the icon will bring
	 up a window in which the name and a description of a new folder can be provided.
	 When OK is pressed, the new folder is created. If no folder was selected at the
	 time, a new root folder is created. Else a nested folder is created, under the selected
	 folder. In the latter case, the owning folder may have been checked out during the
	 create folder operation.<BR><BR>When the folder creation is complete, a Success
	 window is displayed, telling you so. From this window, you can return to the Navigator
	 window or jump to the Security Manager to grant access privileges on the Folder
	 to selected Users and Roles.<BR><BR>When you return to the Navigator window, the
	 right pane will be refreshed automatically. However, the tree with Workareas and
	 Folders on the left hand is not refreshed automatically. You may have to select
	 the Workarea and press the Refresh icon {requery.gif, ALT="Refresh"} to see the new folder in the
	 tree (and if the owning folder had to be checked out, also see the checked out version
	 of the owning folder).
	' );

	-- TITLE: Troubleshooting
	-- NODE : Troubleshooting
	INSERT INTO odwa_help_text VALUES
	(1220, 
	5, 
	'
	If you have a problem first go over this list to find if your problem can be solved 
	 by one of the answers to the questions below. <BR><BR><B>1. If I click on an object to open a Report
	 or the Repository Object Browser nothing happens.</B><BR>The ROB opens a new window when you start up a Report or the Object Browser. If you already
	 have opened a window that has a Report or the browser in it ROB will use that
	 window if you click on another object. This window is however not displayed on
	 top. With '||'&'||'lt;ALT'||'&'||'gt;- '||'&'||'lt;TAB'||'&'||'gt;you can go to
	 the browser window that displays the report that you had asked for.<BR><BR><B>2.
	 If I press '||'&'||'lt;ENTER'||'&'||'gt; in the Search tool an hour glass is displayed
	 but nothing happens.</B><BR>Just use the search button instead of the '||'&'||'lt;ENTER'||'&'||'
	 gt; button and the search will start.<BR><BR><B>3. Navigator tree disappears</B><BR>Sometimes
	 when you are in a tree-style interface (navigator, security manager, graphics manager,
	 object browser) refreshing multiple times using the {requery.gif, ALT="Refresh"} symbol might cause
	 a javascript error with the consequence that the tree will disappear. Just close
	 the window or go to home and restart the component.<BR><BR><B>4. When using Internet
	 Explorer the User Interface does not behave correctly</B><BR>There have been reported
	 some small issues when using IE 5.5. Sometimes graphics are not displayed correctly.
	 Refresh the pages and most of the time the graphic will be there. <BR>Sometimes
	 windows are not centered correctly. Just move the window to the center and you are
	 able to close or enlarge it.<BR>If you use the back button in IE you might find
	 that you get a java script error in the different trees. Just close the window and
	 restart the ROB component you were working in.<BR><BR><B>5. When I do check in
	 through the Repository Navigator I get an error</B><BR>This error might be caused
	 because someone else is performing an action in the same folder or with the same
	 file in another session and you have not refreshed your screen. Just refresh your
	 screen by using the {requery.gif, ALT="Refresh"} symbol. Best is to at least requery the parent
	 folder or workarea. If this does not work leave ROB close your internet browser
	 and start ROB again.<BR><BR><B>6. The tree in the Repository Navigator is not properly
	 refreshed</B><BR>After specific operations from the right pane of the navigator,
	 such as File Upload, Check Out/Check In/Undo Check Out Folder, Create Folder, the
	 navigator tree may not reflect the new situation properly, since it was not refreshed
	 by the tool. Refreshing the navigator tree is never done automatically and is always
	 a user action. Note that refreshing a node effectively means: refreshing all children
	 of that node, but not the node itself. A common problem is where the folder that
	 is selected in the tree was checked out in the right hand pane. If the tree is not
	 refreshed, it will show the version that is not checked out and that is no longer
	 in the workarea. Selecting this version will lead to an erroneous situation. The
	 workaround here is to select (in the tree) the parent folder or the workarea and
	 then refresh by clicking on the {requery.gif, ALT="Refresh"} requery icon.<BR><BR>
	' );

	-- TITLE: Troubleshooting
	-- NODE : Troubleshooting
	INSERT INTO odwa_help_text VALUES
	(1220, 
	10, 
	'
	<B>7. Download files that are not uploaded in repository gives error</B><BR>If you 
	 only create a file in the Oracle Repository and do not upload the file (something
	 you probably never want to do), downloading this file in ROB results in an error.
	 This error will look something like this: ORA-06512: at "SYS.DBMS_LOB". If you upload
	 the file in the repository the download in ROB will work fine again.<BR><BR><B>8.
	 Files are not compressed when uploaded</B><BR>You may have indicated in the Repository
	 File Registry that files with certain extensions should be stored in compressed
	 format to save space. Unfortunately, the ROB Upload mechanism cannot perform the
	 compression of files. Therefore, regardless of the setting in the File Registry,
	 any file uploaded through ROB will be uncompressed.<BR><BR><B>9. Compressed Files
	 can not be downloaded</B><BR>You may have indicated in the Repository File Registry
	 that files with certain extensions should be stored in compressed format to save
	 space. As a result, a number of files in the repository may be stored in compressed
	 format. The ROB download operation is based on a very fast but simple mechanism:
	 it streams the raw contents of the BLOB object holding the file to the browser.
	 It does not perform decompression. To prevent that you download a file with useless
	 format, download of compressed files is not possible in ROB. ROB will let you
	 now through an error message that you were trying to download a compressed file.
	 You should download the file using the RON or the command line interface of the
	 Oracle Repository. If you still want to be able to download these files you should
	 turn of the compression. You can do that in the RON - Utilities - Edit File Registry.<BR><BR><B>10.
	 Support for User Extensibility</B><BR>The support in ROB for User Extensibility
	 is concentrated in the Search tool and the Browse facility. If you search objects
	 by element type, name or any other criterion, you may find instances of User Extended
	 element types. You can then open the VHV or Browser for the element. The browser
	 will show the default properties as well as the UE properties and UE Text Usages.
	 There are no reports for UE Element Types, nor does any of the reports show UE properties
	 or associations. Only UE text usages are shown. The Navigator does show UE Element
	 Types. <i>Access on the CI-views created for the UE-element types must be granted
	 to the ROB owner, in order to make instances of those element types visible in
	 the Explorer Pane of the Navigator.</i><BR><BR>
	' );

	-- TITLE: Create Diagram Image using Netscape Composer
	-- NODE : Create Diagram Image using Netscape Composer
	INSERT INTO odwa_help_text VALUES
	(1150, 
	5, 
	'
	The easiest way though not always with the best results to create an image file 
	 for an Oracle Designer diagram is the approach using Netscape Composer. <BR><BR>The steps are as follows:<BR>* Open
	 the Diagram using the relevant diagrammer tool in Oracle Designer<BR>* Without selecting
	 any element on the diagram, select the menu option Copy from the Edit menu<BR>*
	 Open (a new document) in Paint<BR>* Paste the contents of the clipboard (the diagram)
	 to Paint<BR>* Save the document in Paint; this will result in a BMP-format image
	 file)<BR>* Open a blank page in Netscape Composer<BR>* Include Image, select the
	 BMP file you just created from Paint<BR>* Netscape Composer will convert the BMP
	 file to a JPEG file format and display the image on the screen<BR>* Click on the
	 image, select Save Image and save the JPG file to an appropriate directory on your
	 file system<BR>* Now you can either move the file to the Image Directory of your
	 WebServer, or upload it into the Repository<BR>  - An image file on the WebServer''s
	 file system can be referenced in the Multi Line Text blocks of Repository Objects
	 through ^{filename^}<BR>  - An image file in the Repository can be referenced in
	 the Multi Line Text blocks of Repository Objects through ^{REP_FILE=<folderpath>/<filename>^},
	 for example: ^{REP_FILE=HSD65/ERD.JPG^}<BR><BR>If you want to create hotspots for
	 the image, you should define a Graphic in ROB and link this image-file to that
	 graphic. <a href="javascript:parent.showHelp(1180)"> See Add a Graphic to ROB</a>
	' );

	-- TITLE: Advanced Search Options
	-- NODE : Advanced Search Options
	INSERT INTO odwa_help_text VALUES
	(1100, 
	5, 
	'
	The advanced search offers you some powerful search capabilities.<BR><BR><B>Irid, 
	 Ivid</B><BR>You can just fill in the irid or the ivid of and object or object version.
	 This can be very handy if you get an error in Oracle Designer and an irid or ivid
	 is given and you do not know which object that is. Just copy the irid or ivid from
	 the error or warning message and paste it in the ROB search.<BR><B>Additional Where
	 Clause</B><BR>Additional where clause gives you the opportunity to extend the search
	 with your own additional where clause. If you have chosen an element type on the
	 basic search tab you can refer to any column name for that element type. You can
	 also add your own subquery. <BR>To find the column name in the RON go to the object
	 open the property palette and click on the prompt of the column that you want to
	 use then press the '||'&'||'lt;F5'||'&'||'gt; button. Now you can see the column
	 name. In the clause you do not have to specify the AND operator. ROB does that
	 for you.<BR><B>Multi Line Text Contains</B><BR>Just fill in a piece of text that
	 you are looking for and ROB will search through all multi line text at the PAC
	 level. That means for example that if you select element type Table Definition and
	 also provide a value for this search criterion, the search facility will look for
	 Multi Line Text (such as Description, Notes, User Help Text) at the level of the
	 Table Definition. It will not look to the Multi Line Text of the secondary elements
	 of the Table Definition, such as Columns, Constraints and Triggers.<BR><B>File Contains</B><BR>This
	 search field will check the if the text you type in occurs anywhere in the File.
	 Note that this search option only has an effect if the element type <b>File</b>
	 has been selected on the first tab-sheet (Basic).<BR>
	 <B>Dependency Type</B><BR>Select the kind of dependency you want to search the object with.
	 <BR><B>Global Name Domain/Type</B><BR> Type in the Global Domain type number of the dependant object, 
	 the search will be performed for all the objects that has the dependency (of type filled in the 
	 Dependency type text box) with the object having this type number.
	 <BR><B>Global Name:</B><BR> Just type in the global name of the dependant object.<BR> For example if you 
	 want to search for all the Oracle Reports modules, select the element type as "modules", dependency type as "Uses"
	 and type "Oracle Reports" in the global name, then click on search.
	 <BR><B>Used by</B><BR>Click on the browse button to select the element which uses the element under search.<BR>
	' );

	-- TITLE: Including Graphics in Reports
	-- NODE : Including Graphics in Reports
	INSERT INTO odwa_help_text VALUES
	(270, 
	5, 
	'
	Reports for Repository Objects can be illustrated with Graphics. The repository 
	 object is associated wit one or more graphics through simple tags that are included
	 in one of the Multi Line Text blocks of the objects (for example: Description, Notes,
	 User Help Text). There are three way of creating a reference to a graphic:<BR><BR>1)
	 Include the name of a gif-file stored in the /rob_images/ directory between curly
	 brackets; e.g.: ^{help.gif^} {help.gif, ALT="Help"} <BR>2) Include the name of an ODWA_GRAPHIC
	 in the help item as follows: ^{GRAPHIC=graphicCode^}. You can create ROB graphics
	 using the <A href="javascript:parent.showHelp(406)">ROB Graphics Manager</A>.<BR>3)
	 Include the ivid of a file (type gif/jpg) containing a graphic you want to display,
	 stored somewhere in the Repository, in the following way: ^{REPFILE=ivid^}<BR><BR>ROB
	 will try to interpret the reference between the curly bracket and will replace the
	 brackets with the actual image you refer to.<BR>A good example of a graphic that
	 you want to see in your reports is an entity relationship diagram. <BR><BR>You can show curly brackets by using ^
	 as an escape character. Alternatively, any string between curly brackets that does
	 not contain either a period, the tag GRAPHIC= or the tag REP_FILE= is not considered
	 a valid graphic reference and is therefore shown as a literal string. For example:
	 {string between curly brackets} is shown, since it does not appear to be a valid
	 graphic reference.
	' );

	-- TITLE: 4. Designer Diagrams and Hotspots
	-- NODE : 4. Designer Diagrams and Hotspots
	INSERT INTO odwa_help_text VALUES
	(1200, 
	5, 
	'
	One of the most popular applications of the concept of Graphics in ROB is the inclusion 
	 of Diagrams in ROB reports. Diagrams, such as Entity Relationship Diagrams {entity_relationship_diagrammer.gif, ALT="Entity relationship diagrammer"}
	 (ERD) or Data Diagram {data_diagram.gif, ALT="Data diagram"} (DD) present an often accessible overview
	 of a large collection of related objects such as Entities or Table Definitions.
	 Showing these diagrams on the Web brings this overview to the end users that do
	 not necessarily go into the Oracle Designer toolset themselves. It also provides
	 quick and easy access through simple browsing to diagrams to analysts and developers.<BR><BR><b>Hotspots
	 and Clickable Diagrams</b>Even more value is added to the concept of diagrams as
	 Graphics when they can be used as portal to reports for the objects shown on the
	 diagram. Making the diagram <i>clickable</i> means: enabling the end user to click
	 on objects shown on the diagram, thereby providing a hyperlink/navigation short
	 cut to the report for the clicked-on object. For example: if we make an entity relationship
	 diagram clickable, it means that an ROB user can click on the entities displayed
	 in the diagram and jump to the associated entity report. As a bonus, clickable objects
	 on diagram will show a balloon help text with the full name of the object. Refer
	 to the related help text below this subject <BR><BR>Unfortunately, diagrams that are shown in ROB are
	 not dynamically extracted from the Oracle Designer tables. ROB can only show images
	 of diagrams. And you have to create such images yourself. Note that is also means
	 that if you change the diagram in Oracle Designer after you have created the image
	 of the diagram, the image and the real diagram are no longer in synch. This probably
	 means that for diagrams that undergo many changes you have to periodically create
	 fresh images.<BR>
	' );

	-- TITLE: Downloading Files
	-- NODE : Downloading Files
	INSERT INTO odwa_help_text VALUES
	(1400, 
	5, 
	'
	Wherever you see the name of a file listed in the Repository Navigator, you can 
	 download the file just by clicking on the name. The standard browser download dialog
	 will be started. For example, you can be offered the choice of saving the file or
	 opening it. If you want to change the file it is best the check out the file first.
	 Also see <Ahref="javascript:parent.showHelp(120)">Check out (and Download a File)</A>.<BR><BR><i>Compressed
	 Files are NOT downloaded</i><BR>You may have indicated in the Repository File Registry
	 that files with certain extensions should be stored in compressed format to save
	 space. As a result, a number of files in the repository may be stored in compressed
	 format. The ROB download operation is not capable of uncompressing these files.
	 Downloading such files in their compressed format is senseless, since you cannot
	 open or edit those files. Whenever you attempt to download such a compressed file,
	 ROB will display a warning page, informing you that the file is compressed and
	 cannot be downloaded. You will have to use the Repository Client Tools RON or Command
	 Line Interface to download this file. <BR>
	' );

	-- TITLE: Download Zipfile for Folder Tree (with contents)
	-- NODE : Download Zipfile for Folder Tree (with contents)
	INSERT INTO odwa_help_text VALUES
	(1630, 
	5, 
	'
	The <i>Download Folder Tree plus contents</i> feature, available in the Repository 
	 Navigator through the {AllFolders, ALT="All folders"} icon, whenever a folder has been selected in
	 the context of either a Workarea or a Configuration, allows users to download a
	 zip file that contains:<BR><UL><LI>all files in the current folder</LI><LI>all folders
	 in the current folder</LI><LI>all files and all folders in each folder of the folder
	 tree with the current folder as root</LI></UL>When this icon is clicked on, the
	 browser will present the user with the Save As dialog preceding file download. The
	 suggested name will be <Current Folder Name>.zip. The file that is downloaded is
	 a zip-file that contains all files in the folder tree in the same folder structure as in the
	 repository. The version of the file that is included in the zipfile,  is the relevant
	 version in the current Workarea or Configuration context. Note that files that are
	 stored in compressed format in the Repository are <b>not</b> included in the zipfile.
	 This feature provides the easiest way for refreshing a file system folder structure
	 from the repository through a web interface.<BR><BR>
	' );

	-- TITLE: Download Folder Contents (zip-file)
	-- NODE : Download Folder Contents (zip-file)
	INSERT INTO odwa_help_text VALUES
	(1620, 
	5, 
	'
	The <i>Download Folder contents</i> feature, available in the Repository Navigator 
	 through the {folder$o$m.gif, ALT="Folder"} icon, whenever a folder has been selected in the context
	 of either a Workarea or a Configuration, allows users to download all files in a
	 folder at once. When this icon is clicked on, the browser will present the user
	 with the Save As dialog preceding file download. The suggested name will be <Current
	 Folder Name>.zip. The file that is downloaded is a zip-file that contains all files
	 in the currently selected folder. The version of the file that is included in the
	 zipfile,  is the relevant version in the current Workarea or Configuration context.
	 Note that files that are stored in compressed format in the Repository are <b>not</b>
	 included in the zipfile.<BR><BR>
	' );

	-- TITLE: Parsing Repository Objects for Dependencies
	-- NODE : Parsing Repository Objects for Dependencies
	INSERT INTO odwa_help_text VALUES
	(1640, 
	5, 
	'
	Whenever an object version shown in the Repository Object Browser does not have 
	 any dependency data defined against it, the navigator will contain a node that shows
	 something like:<BR><BR><b><i>{dependancy_manager.gif, ALT="Dependency manager"} No Dependency Data Available</i></B><BR><BR>When
	 you select this node, the property palette on the right side of the screen changes:
	 it is titles Dependencies Palette and it contains the Parse Status (when was this
	 object parsed for dependencies if at all) and a button {parse_for_dependencies_round.gif, ALT="Parse for dependencies"}.
	 By clicking on the button , a parse process can be invoked.<BR><BR>If there are
	 already dependencies recorded for the object, the node looks like:<BR><b><i>{dependancy_manager.gif, ALT="Dependency manager"}Dependencies</i></B><BR><BR>When
	 you select this node, the property palette on the right side of the screen changes:
	 it is titles Dependencies Palette and it contains the Parse Status (when was this
	 object parsed for dependencies if at all) and a button {parse_for_dependencies_round.gif, ALT="Parse for dependencies"}.
	 By clicking on the button , a parse process can be invoked.<BR><BR><h3>Parsing for
	 dependencies:</h3><br>It is important to note that this parse process is NOT the
	 standard Dependency Parse process that you can run from the Repository Dependency
	 Manager or the Command Line Tool. It is a parser written in PL/SQL and implemented
	 inside the database. It can parse two types of dependencies:<br><ul><li>Dependencies
	 that are derived from Structured Elements as defined the Designer Meta Model; for
	 example: Entity => relationship to Entity, => attribute reference to Domain or Module=>
	 call to Module, usage of Table, usage of Column, usage of Language etc.</li><li>Dependencies
	 that are defined explicitly by the developer in the Multi Line Text of any structured
	 elements (e.g. Notes, Description, PL/SQL Block) or in a file; the syntax for defining
	 dependencies in order for them to be picked up by the parser is the following:<br><pre>'||'&'||'lt;dependency
	 type=''Uses'' subtype=''SELECT'''||'&'||'gt;   '||'&'||'lt;target name=''EMP'' type=''TABLE''/'||'&'||'gt;'||'&'||'lt;/dependency'||'&'||'gt;</pre>Replace
	 subtype SELECT with the appropriate value for the current case; examples are: INSERT,
	 UPDATE, DELETE, CALL, INCLUDE or anything else you come up with. <br><br>Indicate
	 the name of the target; that is the object on which there is a dependency; indicate
	 childelements through a combination of parent.child such as columns with TABLENAME.COLUMNNAME
	 and procedures in packages with PACKAGENAME.PROCEDURENAME. Also define the type
	 of the target object.</li></ul><br>Once the dependency parse is done, a simple report
	 is shown that lists the execution time, the number of objects parsed and the number
	 of dependencies found.
	' );

	-- TITLE: Dependency Data
	-- NODE : Dependency Data
	INSERT INTO odwa_help_text VALUES
	(1610, 
	5, 
	'
	The Repository Object Browser will also display {dependancy_manager.gif, ALT="Dependency manager"}
	 Dependency data for objects, if those objects have been parsed (from either the
	 Command Line Tool (da command) or the Dependency Manager. The Dependency data displayed
	 consists of three parts:<BR><BR>* {property_pallette.gif, ALT="Property pallette"}Details - all secondary
	 elements recognized by the Dependency Parser. For example a Java File typically
	 will contain Class Definitions or a Package create script will contain PL/SQL Routines.
	 For each detail, the Browser will list all usages made of it. So for example the
	 PL/SQL Routine found in a Package will list all the objects that make a call to
	 this routine.<BR>* {uses.gif, ALT="Uses"} Uses - all usages made of other elements by the object
	 under scrutiny. Here you will find for example all tables and columns used by a
	 Form, a Package or a SQL script. And all PL/SQL routines called by those objects.
	 For all usages, the property palette displays all (parsed) objects that provide
	 the detail that is the object of this usage.<BR>* {usedby.gif, ALT="Used by"} Used By - all usages
	 made of this element by other elements are listed.<BR><BR>Note that you have to
	 parse objects for dependencies yourself in order to have the Repository Object Browser
	 display any dependencies. Also note that you will only see usages of an element
	 by other elements that have been parsed. It cannot decisively be concluded that
	 an object has no impact (and can therefore freely be changed) if the {usedby.gif, ALT="Used by"}
	 Used By-node lists no usages. It simply indicates that no objects have been parsed
	 that make use of this object. But there may be many objects, still to be parsed,
	 that also make use of the object.
	' );

	-- TITLE: Search Library
	-- NODE : Search Library
	INSERT INTO odwa_help_text VALUES
	(1650, 
	5, 
	'
	Some queries are used many times. For example queries to find out all objects checked 
	 in or changed in the last few days, all objects currently checked out (by the user,
	 in a certain workarea), find all objects with a certain status, all Problems assigned
	 to a user etc. The Query Library feature allows you to save a set of Search criteria
	 and reuse them.<BR><BR>Any query you have assembled by defining search criteria
	 can be saved to the Query Library by pressing the {save_round.gif, ALT="Save"} button. You will
	 assign a category, a name and possibly a description to the query. If you want to,
	 you can publish the query to Public; that means that any user can select that query
	 in the Query Library to perform a search with. <BR><BR>To run a search using a saved
	 query, press the {library_round.gif, ALT="Library"} button on the Search tool. The library will
	 pop up and present a tree navigator with the available query categories. Navigate
	 to the query you want to run and press the Search button in the right side query
	 palette.<BR><BR>Note that you can not view or edit the query criteria directly.
	 If you want to look at the query criteria for query in the library, you have to
	 select that query and perform the search. The tabsheets in the Search library will
	 be refreshed with the criteria that were saved in the library. To change a saved
	 query, select the query in the library, press Search, edit the search criteria and
	 press Save to save the changed query to the Query Library.<BR><BR>Also note: to
	 make the query more generic/dynamic, you use the keywords USER and SYSDATE instead
	 of hard-coded values for a date or a user. For example to create a reusable query
	 that returns all objects currently checked out by the current user, you select USER
	 from the poplist rather than the username of the current user. That way this query
	 can be performed by other users and result in their checked out objects.
	' );

	-- TITLE: Manage ROB Preferences
	-- NODE : Manage ROB Preferences
	INSERT INTO odwa_help_text VALUES
	(1700, 
	5, 
	'
	Repository Object Browser maintains the system dependent settings (preferences), such as the path to image file''s location, the 
	URL base to the ROB Servlets, etc., in a table. Every time the value of these settings is required ROB queries it 
	from this table. The values stored in the table can be managed through the 
	Manage ROB Preferences page {vev.gif, ALT="Manage ROB Preferences"}. The various preferences that can be managed through this page are:
	<UL>
		<LI><B>Virtual Directory path for ROB Images.</B> This preference holds the webserver''s virtual directory path 
		that points to the physical directory where the image files are stored. The default value of this preference is 
		''/rob_images/''. Change this preference if you have mapped the image file directory to a different virtual path.
		<LI><B>Enable File upload/download?</B> Check this box if the file upload is configured (see 
		ROB configuration guide) and if you want to enable the file upload. 
		<LI><B>Complete URL base to the File Upload/Download Servlets.</B> This preference holds the URL base from where the 
		file upload/download servlets can be accessed (see the ROB Configuration Guide).<BR>
		(<B>Note:</B> The file upload will not be enabled until this preference has a non-null value and the enable 
		servlets option is checked).
		<LI><B>Enable Custom Development Method (CDM) objects.</B> Check this box if you are using Custom Development Method (CDM) 
		objects. (<A href="javascript:parent.showHelp(1710)">What is CDM?</A>)
		<LI><B>Users with Global Search permissions.</B> This preference holds a comma delimited list of repository 
		user names that are allowed to perform a global search, regardless of access privileges.
		<LI><B>Default Charset for ROB.</B> This preference holds the name of the charset the ROB pages have. The value 
		saved in this preference will be included in all the ROB HTML pages as the default charset.
	</UL>
	');

	-- TITLE: What is CDM?
	INSERT INTO odwa_help_text VALUES
	(1710, 
	5, 
	'
	CDM is the Oracle Custom Development Method, a full lifecycle method developed and supported by Oracle Consulting for delivering custom computer application solutions. CDM and support for Oracle Designer feature are bundled in the Oracle iDevelopment Accelerators. See <A href="http://otn.oracle.com/consulting/9iServices/idev.html" target=_blank>Using Oracle Designer and the Oracle iDevelopment Accelerators</A>, which is on Oracle''s Technology Network (OTN). 
	<BR>
	<BR>Repository Object Browser can recognize objects and methodologies specific to CDM. By default this feature is turned off. To enable this feature, go to the Manage ROB Preferences page and check the box for "Enable Custom Development Method (CDM) objects".
	');



	-- Removethe data from Preferences table
	DELETE FROM odwa_preferences;

	insert into odwa_preferences (preference_name, preference_value, preference_description)
	values ( 'image_path', '/rob_images/' ,'Name of virtual directory mapped by the WebServer to the physical directory holding the ROB images.');  

	insert into odwa_preferences (preference_name, preference_value, preference_description)
	values ('edit_help_allowed', 'N', 'Is creation and editing of help items allowed? When Y the Edit Help option gets enabled.');

	insert into odwa_preferences (preference_name, preference_value, preference_description)
	values ('servlet_urlbase', '', 'The Base part of the URL (host, port and ServletZone) to access the ROB servlets (e.g. http://localhost/rob/');

	insert into odwa_preferences (preference_name, preference_value, preference_description)
	values ('servlets_enabled', 'N', 'Is a Java WebServer configured with the ROB Servlets for file uploading?');

	insert into odwa_preferences (preference_name, preference_value, preference_description)
	values ('global_search_users', '', 'A comma delimited list of database/repository user names that are allowed to perform a global search, regardless of access privileges.');

	insert into odwa_preferences (preference_name, preference_value, preference_description)
	values ('use_cdm', 'N', 'Preference to indicate that the repository contains CDM objects');

	insert into odwa_preferences (preference_name, preference_value, preference_description)
	values ('charset', 'ISO-8859-1', 'Preference to indicate what charset the application data is');



	-- Remove the data from the pie_element types
	DELETE FROM pie_element_types;

	insert into pie_element_types
	values
	('Business Function','FUNCTION',5024,'Business Functions','function.gif'
	,'cdwp_fun.root_business_functions','FUN','cdwp_fun.list_business_functions',70
	);

	insert into pie_element_types
	values
	('Diagram','DIAGRAM',4941,'Diagrams','diagram.gif'
	,'cdwp_dia.short_list_diagrams','DIA','cdwp_dia.list_diagrams',60
	);

	insert into pie_element_types
	values
	('Business Terminology','TERM',4994,'Business Terminology','term.gif'
	,'cdwp_ter.short_list_ter','TER','cdwp_ter.list_ter',30
	);

	insert into pie_element_types
	values
	('Process Models','PROCESS MODEL',1,'Process Model','process_model_diagrammer.gif'
	,'cdwp_prc.short_list_process_models','PRC','cdwp_prc.list_process_models',100
	);

	insert into pie_element_types
	values(
	'Domain','DOMAIN',5020,'Domains','domain.gif','cdwp_dom.short_list_domains','DOM','cdwp_dom.list_domains',90
	);

	insert into pie_element_types
	values(
	'Entity','ENTITY',5002,'Entities','entity.gif'
	,'cdwp_ent.short_list_entities','ENT','cdwp_ent.list_entities',10
	);

	insert into pie_element_types
	values(
	'Table Definition','TABLE_DEFINITION',4974,'Table Definitions','table.gif'
	,'cdwp_tbl.short_list_table_definitions','TBL','cdwp_tbl.list_table_definitions',20
	);

	insert into pie_element_types
	values(
	'Business Rule','Business_Rule',-5024,'Business Rules','system_privilege.gif'
	,'cdwp_br.root_business_rules','BR','cdwp_br.list_business_rules', 40
	);


	insert into pie_element_types
	values(
	'PL/SQL Definitions','PLSQL_MODULES',4907,'PL/SQL Definitions','plsql.gif'
	,'cdwp_plm.short_list_plm_definitions','PLM','cdwp_plm.list_plm_definitions', 110
	);

	insert into pie_element_types
	values(
	'Business Rule Design Definition','BUSINESS_RULE_DESIGN_DEFINITION',-4907,'Business Rule Design Definitions','brdd.gif'
	,'cdwp_brd.short_list_brdd_definitions','BRDD','cdwp_brd.list_brdd_definitions', 80
	);

	insert into pie_element_types
	values(
	'View Definition','VIEW_DEFINITION',4977,'View Definitions','view.gif'
	,'cdwp_vw.short_list_vw_definitions','VW','cdwp_vw.list_vw_definitions', 50
	);

	insert into pie_element_types
	values(
	'Module','MODULE',4908,'Modules','module.gif'
	,'cdwp_mde.short_list_mde_definitions','GEM','cdwp_mde.list_mde_definitions',140
	);

	insert into pie_element_types
	values(
	'Reusable Module Component','MODULE_COMPONENT',5053,'Reusable Module Components','reusable_mco.gif'
	,'cdwp_mco.short_list_mco_definitions','RMC','cdwp_mco.list_mco_definitions',145
	);

	-- 1.5
	insert into pie_element_types
	values(
	'File','PRIMARY_ACCESS_FILE',4819,'Files','file.gif'
	,'''','FILES','cdwp_fil.download_file',149
	);

	-- 1.3  new
	insert into pie_element_types
	values(
	'Reusable List of Values','REUSABLE_LOV',5056,'Reusable Lists of Values','lov_reusable.gif'
	,'cdwp_mco.short_list_lov_definitions','RLV','cdwp_mco.list_lov_definitions',144
	);


  -- Register 4_6 Upgrade in the RM$PATCHES RM$PATCHES table
  rmpatch.install('CI04012.4_6_UPGRADE');

  rmpatch.installed_ok;

  commit;

EXCEPTION

  WHEN OTHERS THEN
    dbms_output.put_line('* Exception Raised  ');
    dbms_output.put_line('...ERROR: '||substrb(sqlerrm,1,240));
    rollback work;
    RAISE;

END;
/
