Difference between revisions of "Relate Issues And Change Orders"
| Line 33: | Line 33: | ||
tab_banner("Related Issues List"); | tab_banner("Related Issues List"); | ||
docWriteln("<TABLE ID=tbl101 CLASS=tab summary='Issue List Notebook Tab row " + (_dtl.rowNum + 1) + "'>"); | docWriteln("<TABLE ID=tbl101 CLASS=tab summary='Issue List Notebook Tab row " + (_dtl.rowNum + 1) + "'>"); | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
<PDM_IF $args.impacted_chg.length == 0 > | <PDM_IF $args.impacted_chg.length == 0 > | ||
<PDM_MACRO NAME=dtlStartRow> | <PDM_MACRO NAME=dtlStartRow> | ||
Revision as of 13:04, 25 May 2009
PROCEDURE CREATING THE LREL RELATIONSHIP
2.1 Create a LREL relation between Issue and Change Order Step1: Write a majic file called “lrel1.maj”, in site\mods\majic folder
LREL lrel1 iss impacted_iss <> chg impacted_chg;
Step2: Recycle the service Step3: Verify if these objects have been created properly by giving the commands Bop_sinfo –da chg Bop_sinfo –da iss We can check the same in wsp_schema as well Explanation: Impacted_iss is the Lrel object to the Issue Table Impacted_chg the Lrel object to the chg Table
2.2 Create a customised htmpl tab page called as “Chg_iss_tab.htmpl”
<html lang="en"><HEAD>
<PDM_PRAGMA RELEASE=110>
<PDM_WSP mode=edit factory=chg preview="NBTAB=chg_iss_tab">
<PDM_INCLUDE FILE=styles.htmpl>
<PDM_INCLUDE FILE=std_head.htmpl busy=no>
<SCRIPT LANGUAGE="JavaScript" SRC="$CAisd/scripts/sitemods.js"></SCRIPT>
</HEAD>
<BODY>
<PDM_INCLUDE FILE=std_body.htmpl filename="">
<PDM_FORM NAME="frmDTLRO">
<SCRIPT LANGUAGE="JavaScript">
tab_banner("Related Issues List");
| ");
docWriteln("No Issue Attached"); docWriteln(" | ");
<PDM_MACRO NAME=dtlEndTable>
<PDM_ELSE>
var counter=0;
<PDM_LIST SOURCE=args.impacted_chg>
var sClass;
if(counter%2)
sClass = "results1";
else
sClass = "results0";
counter++;
var strHTML="||
| ");
var start_a_tag = "<A" + detailNextID(true) + " HREF=\"javascript:showDetailWithPersid('" +
'<PDM_FMT ESC_STYLE=C>$args.impacted_chg.persistent_id</PDM_FMT>' +
"')\">";
var ecsaped_name=<PDM_FMT ESC_STYLE=C>"$args.impacted_chg.ref_num"</PDM_FMT>; end_a_tag="</A>"; docWriteln(start_a_tag+ecsaped_name+end_a_tag); docWriteln(" | ");
docWriteln('<PDM_FMT ESC_STYLE=C PAD=NO>$args.impacted_chg.status.sym</PDM_FMT> | '); docWriteln('<PDM_FMT ESC_STYLE=C PAD=NO>$args.impacted_chg.description</PDM_FMT> | '); docWriteln("
</SCRIPT> </PDM_FORM> </BODY> </HTML> <PDM_IF 0>
.3 Modifications to detail_chg Create a button to attach issues ImgBtnCreate("UPDATE_LREL", "Attach Issues", "update_lrel('chg', '$args.persistent_id', 'iss', 'impacted_chg', 'Issues', msgtext(211), )", true, 0);
Include a Tab called “Related Issues”
<PDM_TAB ID=rel FILE="chg_iss_tab.htmpl" NAME="Related Issues">
2.4 Modifications to list_iss Add the Below line <PDM_IF "$args.KEEP.ForLrel" == "1"> document.writeln('<INPUT TYPE=hidden NAME=HTMPL VALUE=update_lrel_iss.htmpl>'); </PDM_IF>
After the line <PDM_IF "$args.KEEP.Forchild" == "1"> document.writeln('<INPUT TYPE=hidden NAME=HTMPL VALUE=update_lrel_iss.htmpl>'); </PDM_IF>
Explanation:
This is added so that when we search for the Issues to be attached to the current Change Request the search page will not go to the default list page but go to the update_lrel_iss page.
Note: Follow the above 4 points with the object Iss(Issue) also
3. HOW TO ATTACH ISSUES TO CHANGE ORDERS
Login to the tool and open the Change Order:
When you click on attach issues
Click Search
Add the Tickets that needs to be attached and then see the tab “Issues” to find all the attached Issues to the current Change Order
