Difference between revisions of "Relate Issues And Change Orders"
(added some formatting and code tags. Made the images resizable.) |
|||
Line 1: | Line 1: | ||
− | + | '''Creating a LREL between Changes and Issues''' | |
+ | = Adding the Cutomization = | ||
+ | ==Create a LREL relation between Issue and Change Order == | ||
+ | # Write a majic file called “lrel1.maj”, in site\mods\majic folder with the following contents: | ||
− | + | <source lang="text" >LREL lrel1 iss impacted_iss <> chg impacted_chg;</source> | |
− | + | ||
− | + | # Recycle the service | |
+ | # Verify if these objects have been created properly by giving the commands | ||
− | + | <tt>Bop_sinfo –da chg </tt> | |
− | + | ||
− | Bop_sinfo –da chg | + | <tt>Bop_sinfo –da iss</tt> |
− | Bop_sinfo –da iss | + | |
− | + | We can check the same information in the wsp_schema table from the MDB. | |
Explanation: | Explanation: | ||
− | |||
− | |||
+ | * ''Impacted_iss'' is the Lrel object to the Issue Table | ||
+ | * ''Impacted_chg'' the Lrel object to the chg Table | ||
− | |||
+ | == Create a customised htmpl tab page called “Chg_iss_tab.htmpl” == | ||
+ | <source lang="html4strict"> | ||
<html lang="en"><HEAD> | <html lang="en"><HEAD> | ||
<PDM_PRAGMA RELEASE=110> | <PDM_PRAGMA RELEASE=110> | ||
Line 77: | Line 81: | ||
</HTML> | </HTML> | ||
<PDM_IF 0> | <PDM_IF 0> | ||
− | + | </source> | |
− | + | == Modifications to 'detail_chg.htmpl' == | |
Create a button to attach issues | Create a button to attach issues | ||
+ | <source lang="JavaScript"> | ||
ImgBtnCreate("UPDATE_LREL", "Attach Issues", "update_lrel('chg', '$args.persistent_id', 'iss', 'impacted_chg', 'Issues', msgtext(211), '')", true, 0); | ImgBtnCreate("UPDATE_LREL", "Attach Issues", "update_lrel('chg', '$args.persistent_id', 'iss', 'impacted_chg', 'Issues', msgtext(211), '')", true, 0); | ||
+ | </source> | ||
Include a Tab called “Related Issues” | Include a Tab called “Related Issues” | ||
− | + | <source lang="JavaScript"> | |
<PDM_TAB ID=rel FILE="chg_iss_tab.htmpl" NAME="Related Issues"> | <PDM_TAB ID=rel FILE="chg_iss_tab.htmpl" NAME="Related Issues"> | ||
+ | </source> | ||
− | + | == Modifications to 'list_iss.htmpl' == | |
Add the Below line | Add the Below line | ||
+ | <source lang="JavaScript"> | ||
<PDM_IF "$args.KEEP.ForLrel" == "1"> | <PDM_IF "$args.KEEP.ForLrel" == "1"> | ||
document.writeln('<INPUT TYPE=hidden NAME=HTMPL VALUE=update_lrel_iss.htmpl>'); | document.writeln('<INPUT TYPE=hidden NAME=HTMPL VALUE=update_lrel_iss.htmpl>'); | ||
</PDM_IF> | </PDM_IF> | ||
− | + | </source> | |
After the line | After the line | ||
+ | <source lang="JavaScript"> | ||
<PDM_IF "$args.KEEP.Forchild" == "1"> | <PDM_IF "$args.KEEP.Forchild" == "1"> | ||
document.writeln('<INPUT TYPE=hidden NAME=HTMPL VALUE=update_lrel_iss.htmpl>'); | document.writeln('<INPUT TYPE=hidden NAME=HTMPL VALUE=update_lrel_iss.htmpl>'); | ||
</PDM_IF> | </PDM_IF> | ||
− | + | </source> | |
Explanation: | 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. | 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. | ||
Line 105: | Line 115: | ||
'''Note: Follow the above 4 points with the object Iss(Issue) also''' | '''Note: Follow the above 4 points with the object Iss(Issue) also''' | ||
− | + | = How to use the Customization = | |
− | + | ||
− | [[Image:detail_chg.jpg]] | + | After logging in the Service Desk web interface, open a Change Order: |
+ | [[Image:detail_chg.jpg|480px|center|frame]] | ||
+ | |||
+ | When you click on 'Attach Issues' the search filter for Issues will be shown: | ||
+ | [[Image:Attach_Issues.jpg|280px|center|frame]] | ||
− | + | Click Search and you'll get a list of Issues | |
− | [[Image: | + | [[Image:search.jpg|480px|center|frame]] |
− | + | 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 | |
− | 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 | + | [[Image:Final.jpg|480px|center|frame]] |
− | + | ||
− | [[Image:Final.jpg]] | + |
Revision as of 13:43, 25 May 2009
Creating a LREL between Changes and Issues
Contents
Adding the Cutomization
Create a LREL relation between Issue and Change Order
- Write a majic file called “lrel1.maj”, in site\mods\majic folder with the following contents:
<source lang="text" >LREL lrel1 iss impacted_iss <> chg impacted_chg;</source>
- Recycle the service
- 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 information in the wsp_schema table from the MDB. Explanation:
- Impacted_iss is the Lrel object to the Issue Table
- Impacted_chg the Lrel object to the chg Table
Create a customised htmpl tab page called “Chg_iss_tab.htmpl”
<source lang="html4strict"> <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> </source>
Modifications to 'detail_chg.htmpl'
Create a button to attach issues <source lang="JavaScript"> ImgBtnCreate("UPDATE_LREL", "Attach Issues", "update_lrel('chg', '$args.persistent_id', 'iss', 'impacted_chg', 'Issues', msgtext(211), )", true, 0); </source>
Include a Tab called “Related Issues” <source lang="JavaScript"> <PDM_TAB ID=rel FILE="chg_iss_tab.htmpl" NAME="Related Issues"> </source>
Modifications to 'list_iss.htmpl'
Add the Below line <source lang="JavaScript"> <PDM_IF "$args.KEEP.ForLrel" == "1"> document.writeln('<INPUT TYPE=hidden NAME=HTMPL VALUE=update_lrel_iss.htmpl>'); </PDM_IF> </source> After the line <source lang="JavaScript"> <PDM_IF "$args.KEEP.Forchild" == "1"> document.writeln('<INPUT TYPE=hidden NAME=HTMPL VALUE=update_lrel_iss.htmpl>'); </PDM_IF> </source>
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
How to use the Customization
After logging in the Service Desk web interface, open a Change Order:
When you click on 'Attach Issues' the search filter for Issues will be shown:
Click Search and you'll get a list of Issues
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