Why not allow Business Rule Design Transformer to overwrite existing BRDDs

Question

Hi,
It can be quite annoying during development to continually having to remove the BRDD Trigger and PL/SQL Definition when running the BR Design Transformer reveals missing information in the BR Analysis definition. It seems that it would be practical to have at least the option to have the Business Rule Design Transformer overwrite an existing Business Rule Design Definition.
You could think of an additional parameter in this utilily labeled "Overwrite existing BRDD?" with allowable values Y(es) and N(o) with No as default (so that the default functionality is the same as before).
Below you find the code that can be added to the HSU_BRTR package to realize such a functional improvement. Maybe you can consider it for a next release...?!
best regards,
Lucas Jellema
AMIS Services BV
code to add to HSU_BRTR to provide a parameter that allows the user to specify whether or not the HSU_BRTR is allowed to overwrite an existing BRDD:
in the revision history:
09-jan-2003 Lucas Jellema
6.5.2.3AMIS1.1 Added new parameter and supporting code that allows user to indicate
whether existing Business Rule Design Definitions may be/should be overwritten
at the end of procedure install
hsu_install.add_parameter
( PACKAGE_NAME -- package name
, 40 -- sequence
, 'Overwrite existing BRDDs?' -- prompt
, 'N' -- default value actual
, 'No' -- default value displayed
, 'Y' -- mandatory
, 'N' -- allow multi-select
, 'N' -- include shared elements
, '' -- element type short name
, '' -- sql expression actual
, '' -- sql expression displayed
, null -- where clause
, null -- synchronize with
, null -- foreign key column
, -- help text
'Choose whether you want this utility to overwrite existing Business Rule Design Definitions.'
hsu_install.add_allowable_value
( PACKAGE_NAME -- package name
, 40 -- parameter
, 1 -- sequence
, 'Y' -- actual value
, 'Yes' -- displayed value
hsu_install.add_allowable_value
( PACKAGE_NAME -- package name
, 40 -- parameter
, 2 -- sequence
, 'N' -- actual value
, 'No' -- displayed value
--------6.5.2.3AMIS1.1
Just before procedure transform_stage2
procedure delete_brdds
( p_tbl_id in ci_table_definitions.id%type
, p_br_name in varchar2
-- Purpose Delete existing Business Rule Design Definition
-- Usage from run procedure
-- Remarks Find PL/SQl Module Definition based on Business Rule Label
is
cursor c_brdd
( b_tbl_id in ci_table_definitions.id%type
, b_br_name in varchar2
is
select trg.id trg_id
, trg.name name
, plm.id plm_id
from ci_database_triggers trg
, ci_plsql_modules plm
where trg.table_definition_reference = b_tbl_id
and trg.plsql_module_reference = plm.id
and plm.name = b_br_name
begin
-- loop over journalling busrules of this application
<<brdd>>
for r_brdd in c_brdd(p_tbl_id, p_br_name) loop
-- delete busrule (delete of trigger is since 6i not enough anymore, so
-- explicitly delete PL/SQL module also)
bllog.write
( 'Deleting trigger '||r_brdd.name||' and PL/SQL module '
||hsu_name.get_name_and_path(r_brdd.plm_id)
||', a new business rule design definition overwrites this old one.'
, bllog.information
bltrg.del(r_brdd.trg_id);
blplm.del(r_brdd.plm_id);
end loop brdd;
end delete_brdds;
inside procedure transform_stage2
(just before the comment: -- check if BRDD with this plm_name already exists)
if p_overwrite_br = 'Y'
     then
delete_brdds
( p_tbl_id => g_trg_tbl(i).tbl_id
, p_br_name => l_plm_name
     end if; -- find_trg and overwrite =Y
A new parameter in procedure transform_br_fun
procedure transform_br_fun
, p_overwrite_br in varchar2 default 'N' -- 6.5.2.3AMIS1.1
use the parameter p_overwrite_br in the call to transform_stage2
transform_stage2
( p_fun_id => p_fun_id
, p_fun_label => r_fun.fun_function_label
, p_fun_short_definition => r_fun.fun_short_definition
, p_msg_prefix => p_msg_prefix
, p_msg_language => p_msg_language
, p_rule_type => l_rule_type
               , p_overwrite_br => p_overwrite_br -- 6.5.2.3AMIS1.1
new parameter p_overwrite_br in the procedure run
NOTE: in both PACKAGE SPECIFICATION and BODY
, p_overwrite_br in varchar2 default'N' -- 6.5.2.3AMIS1.1
use the parameter p_overwrite_br in all calls to transform_br_fun inside procedure run
transform_br_fun
( p_fun_id => r_fun_tree.id
, p_msg_prefix => p_msg_prefix
, p_msg_language => p_msg_language
, p_create_att_usages => p_create_att_usages
, p_overwrite_br => p_overwrite_br -- 6.5.2.3AMIS1.1

Answer 1

Among the alternatives not mentioned... Using a TiVo DVR, rather than the X1; a Roamio Plus or Pro would solve both the concern over the quality of the DVR, as well as providing the MoCA bridge capability the poster so desperately wanted the X1 DVR to provide. (Although the TiVo's support only MoCA 1.1.) Just get a third-party MoCA adapter for the distant location. Why the hang-up on having a device provided by Comcast? This seems especially ironic given the opinions expressed regarding payments over time to Comcast. If a MoCA 2.0 bridge was the requirement, they don't exist outside providers. So couldn't the poster have simply requested a replacement XB3 from the local office and configured it down to only providing MoCA bridging -- and perhaps as a wireless access point? Comcast would bill him the monthly rate for the extra device, but such is the state of MoCA 2.0. Much of the OP sounds like frustration over devices providing capabilities the poster *thinks* they should have.