Difference between revisions of "Relate Issues And Change Orders"
| Line 20: | Line 20: | ||
| − | + | [code] | |
| − | + | <PDM_IF 0> | |
| − | + | ||
chg_iss_tab.htmpl | chg_iss_tab.htmpl | ||
WHEN PRESENTED: | WHEN PRESENTED: | ||
| Line 93: | Line 92: | ||
@(#)$Id: chg_iss_tab.htmpl,v 1.18 2006/03/21 18:16:57 jenji01 Exp $ | @(#)$Id: chg_iss_tab.htmpl,v 1.18 2006/03/21 18:16:57 jenji01 Exp $ | ||
</PDM_IF> | </PDM_IF> | ||
| − | + | [/code] | |
| + | |||
| + | '''Note: Follow the above 4 points with the object Iss(Issue) also''' | ||
3. HOW TO ATTACH ISSUES TO CHANGE ORDERS | 3. HOW TO ATTACH ISSUES TO CHANGE ORDERS | ||
Revision as of 12:51, 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”
[code]
<PDM_IF 0>
chg_iss_tab.htmpl
WHEN PRESENTED:
When we need to relate issues with Change Order
INTENT:
Display a notebook page for to show all the related Changes
Note: <location of pdmcgi>?OP=SHOW_DETAIL+PERSID=<persistent_id>+ HTMPL=<notebook page htmpl file name> for example: http://test_machine/scripts/pdmcgi.exe?OP= SHOW_DETAIL+PERSID=cr:13677+HTMPL=crro_alg_tab.htmpl </PDM_IF> <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("| Ref# | "); docWriteln("Status | "); docWriteln("Description | "); docWriteln("");
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> @(#)$Id: chg_iss_tab.htmpl,v 1.18 2006/03/21 18:16:57 jenji01 Exp $ </PDM_IF> [/code]
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
