SDU - User contributions [en]

Calculating the Time when the Service Type is Stopped

2009-05-26T09:30:18Z

MaryNancy:

== Calculating the Total time when the service type is stopped==

1. ABSTRACT
This document describes the procedure followed for calculating the total time when the service stopped

2. DATABASE CUSTOMIZATIONS
<source lang="html4strict">
Name Type Default Value comments
ztime_sec Integer 0 This stores the total seconds when the status was on HOLD.
zwait_flag Integer This is a flag variable which keeps track if the previous status is HOLD
zwait_time Date This stores the Last time , when the status was on HOLD
</source>

3. CONTENTS OF THE MOD AND SPEL FILE

Mod File:
<source lang="html4strict">
MODIFY cr status ON_POST_VAL set_zcrtime () 300 ;
</source>

Spel File
<source lang="JavaScript">
cr.status::set_zcrtime(...)
{
int curr_time;
int time_sec;
int wait_time;
int temp_time;

curr_time = (int) now();
wait_time = (int) zwait_time;
time_sec=(int) ztime_sec;

if (status.hold == 1 && status!="RE")
{

zwait_time=now();
zwait_flag=1;
}
if ((status.hold != 1 || Status == "RE") && zwait_flag==1)
{
temp_time = curr_time - wait_time;
zwait_flag =0;
ztime_sec= temp_time + time_sec;

}

return;
}
</source>

Calculating the Time when the Service Type is Stopped

2009-05-26T09:29:28Z

MaryNancy:

== Calculating the time when the service type is stopped ==

1. ABSTRACT
This document describes the procedure followed for calculating the total time when the service stopped

2. DATABASE CUSTOMIZATIONS
<source lang="html">
Name Type Default Value comments
ztime_sec Integer 0 This stores the total seconds when the status was on HOLD.
zwait_flag Integer This is a flag variable which keeps track if the previous status is HOLD
zwait_time Date This stores the Last time , when the status was on HOLD
</source>

3. CONTENTS OF THE MOD AND SPEL FILE

Mod File:
<source lang="html4strict">
MODIFY cr status ON_POST_VAL set_zcrtime () 300 ;
</source>

Spel File
<source lang="JavaScript">
cr.status::set_zcrtime(...)
{
int curr_time;
int time_sec;
int wait_time;
int temp_time;

curr_time = (int) now();
wait_time = (int) zwait_time;
time_sec=(int) ztime_sec;

if (status.hold == 1 && status!="RE")
{

zwait_time=now();
zwait_flag=1;
}
if ((status.hold != 1 || Status == "RE") && zwait_flag==1)
{
temp_time = curr_time - wait_time;
zwait_flag =0;
ztime_sec= temp_time + time_sec;

}

return;
}
</source>

Calculating the Time when the Service Type is Stopped

2009-05-26T09:28:32Z

MaryNancy:

== Calculating the time when the service type is stopped ==

1. ABSTRACT
This document describes the procedure followed for calculating the total time when the service stopped

2. DATABASE CUSTOMIZATIONS
<source>
Name Type Default Value comments
ztime_sec Integer 0 This stores the total seconds when the status was on HOLD.
zwait_flag Integer This is a flag variable which keeps track if the previous status is HOLD
zwait_time Date This stores the Last time , when the status was on HOLD
</source>

3. CONTENTS OF THE MOD AND SPEL FILE

Mod File:
<source lang="html4strict">
MODIFY cr status ON_POST_VAL set_zcrtime () 300 ;
</source>

Spel File
<source lang="JavaScript">
cr.status::set_zcrtime(...)
{
int curr_time;
int time_sec;
int wait_time;
int temp_time;

curr_time = (int) now();
wait_time = (int) zwait_time;
time_sec=(int) ztime_sec;

if (status.hold == 1 && status!="RE")
{

zwait_time=now();
zwait_flag=1;
}
if ((status.hold != 1 || Status == "RE") && zwait_flag==1)
{
temp_time = curr_time - wait_time;
zwait_flag =0;
ztime_sec= temp_time + time_sec;

}

return;
}
</source>

Calculating the Time when the Service Type is Stopped

2009-05-26T09:27:45Z

MaryNancy: /* Calculating the time when the service type is stopped */

== Calculating the time when the service type is stopped ==

1. ABSTRACT
This document describes the procedure followed for calculating the total time when the service stopped

2. DATABASE CUSTOMIZATIONS
<source lang="html4strict">
Name Type Default Value comments
ztime_sec Integer 0 This stores the total seconds when the status was on HOLD.
zwait_flag Integer This is a flag variable which keeps track if the previous status is HOLD
zwait_time Date This stores the Last time , when the status was on HOLD
</source>

3. CONTENTS OF THE MOD AND SPEL FILE

Mod File:
<source lang="html4strict">
MODIFY cr status ON_POST_VAL set_zcrtime () 300 ;
</source>

Spel File
<source lang="JavaScript">
cr.status::set_zcrtime(...)
{
int curr_time;
int time_sec;
int wait_time;
int temp_time;

curr_time = (int) now();
wait_time = (int) zwait_time;
time_sec=(int) ztime_sec;

if (status.hold == 1 && status!="RE")
{

zwait_time=now();
zwait_flag=1;
}
if ((status.hold != 1 || Status == "RE") && zwait_flag==1)
{
temp_time = curr_time - wait_time;
zwait_flag =0;
ztime_sec= temp_time + time_sec;

}

return;
}
</source>

Calculating the Time when the Service Type is Stopped

2009-05-26T09:26:06Z

MaryNancy:

== Calculating the time when the service type is stopped ==

1. ABSTRACT
This document describes the procedure followed for calculating the total time when the service stopped

2. DATABASE CUSTOMIZATIONS
<source lang="html4strict">
Name Type Default Value comments
ztime_sec Integer 0 This stores the total seconds when the status was on HOLD.
zwait_flag Integer This is a flag variable which keeps track if the previous status is HOLD
zwait_time Date This stores the Last time , when the status was on HOLD
</source>

3. CONTENTS OF THE MOD AND SPEL FILE

Mod File:
<source lang="html4strict">
MODIFY cr status ON_POST_VAL set_zcrtime () 300 ;
</source>

Spel File
<source lang="JavaScript">
cr.status::set_zcrtime(...)
{
int curr_time;
int time_sec;
int wait_time;
int temp_time;

curr_time = (int) now();
wait_time = (int) zwait_time;
time_sec=(int) ztime_sec;

if (status.hold == 1 && status!="RE")
{

zwait_time=now();
zwait_flag=1;
}
if ((status.hold != 1 || Status == "RE") && zwait_flag==1)
{
temp_time = curr_time - wait_time;
zwait_flag =0;
ztime_sec= temp_time + time_sec;

}

return;
}
</source>

Calculating the Time when the Service Type is Stopped

2009-05-26T09:25:10Z

MaryNancy:

== Calculating the time when the service type is stopped ==

1. ABSTRACT
<tt>This document describes the procedure followed for calculating the total time when the service stopped.</tt>

2. DATABASE CUSTOMIZATIONS
<source lang="html4strict">
'''Name Type Default Value comments'''
ztime_sec Integer 0 This stores the total seconds when the status was on HOLD.
zwait_flag Integer This is a flag variable which keeps track if the previous status is HOLD
zwait_time Date This stores the Last time , when the status was on HOLD
</source>

3. CONTENTS OF THE MOD AND SPEL FILE

Mod File:
<source lang="html4strict">
MODIFY cr status ON_POST_VAL set_zcrtime () 300 ;
</source>

Spel File
<source lang="JavaScript">
cr.status::set_zcrtime(...)
{
int curr_time;
int time_sec;
int wait_time;
int temp_time;

curr_time = (int) now();
wait_time = (int) zwait_time;
time_sec=(int) ztime_sec;

if (status.hold == 1 && status!="RE")
{

zwait_time=now();
zwait_flag=1;
}
if ((status.hold != 1 || Status == "RE") && zwait_flag==1)
{
temp_time = curr_time - wait_time;
zwait_flag =0;
ztime_sec= temp_time + time_sec;

}

return;
}
</source>

Calculating the Time when the Service Type is Stopped

2009-05-26T09:22:54Z

MaryNancy:

== Calculating the time when the service type is stopped ==

1. ABSTRACT
This document describes the procedure followed for calculating the total time when the service stopped.

2. DATABASE CUSTOMIZATIONS
<source lang="JavaScript">
Name Type Default Value comments
ztime_sec Integer 0 This stores the total seconds when the status was on HOLD.
zwait_flag Integer This is a flag variable which keeps track if the previous status is HOLD
zwait_time Date This stores the Last time , when the status was on HOLD
</source>

3. CONTENTS OF THE MOD AND SPEL FILE

Mod File:
<source lang="html4strict">
MODIFY cr status ON_POST_VAL set_zcrtime () 300 ;
</source>

Spel File
<source lang="JavaScript">
cr.status::set_zcrtime(...)
{
int curr_time;
int time_sec;
int wait_time;
int temp_time;

curr_time = (int) now();
wait_time = (int) zwait_time;
time_sec=(int) ztime_sec;

if (status.hold == 1 && status!="RE")
{

zwait_time=now();
zwait_flag=1;
}
if ((status.hold != 1 || Status == "RE") && zwait_flag==1)
{
temp_time = curr_time - wait_time;
zwait_flag =0;
ztime_sec= temp_time + time_sec;

}

return;
}
</source>

Calculating the Time when the Service Type is Stopped

2009-05-26T09:21:34Z

MaryNancy:

== Calculating the time when the service type is stopped ==

1. ABSTRACT
This document describes the procedure followed for calculating the total time when the service stopped.

2. DATABASE CUSTOMIZATIONS
Name Type Default Value comments
ztime_sec Integer 0 This stores the total seconds when the status was on HOLD.
zwait_flag Integer This is a flag variable which keeps track if the previous status is HOLD
zwait_time Date This stores the Last time , when the status was on HOLD

3. CONTENTS OF THE MOD AND SPEL FILE

Mod File:
<source lang="html4strict">
MODIFY cr status ON_POST_VAL set_zcrtime () 300 ;
</source>

Spel File
<source lang="JavaScript">
cr.status::set_zcrtime(...)
{
int curr_time;
int time_sec;
int wait_time;
int temp_time;

curr_time = (int) now();
wait_time = (int) zwait_time;
time_sec=(int) ztime_sec;

if (status.hold == 1 && status!="RE")
{

zwait_time=now();
zwait_flag=1;
}
if ((status.hold != 1 || Status == "RE") && zwait_flag==1)
{
temp_time = curr_time - wait_time;
zwait_flag =0;
ztime_sec= temp_time + time_sec;

}

return;
}
</source>

Calculating the Time when the Service Type is Stopped

2009-05-26T09:19:13Z

MaryNancy: New page: == Calculating the time when the service type is stopped == 1. ABSTRACT This document describes the procedure followed for calculating the total time when the service stopped. 2. DATA...

== Calculating the time when the service type is stopped ==

1. ABSTRACT
This document describes the procedure followed for calculating the total time when the service stopped.

2. DATABASE CUSTOMIZATIONS
Name Type Default Value comments
ztime_sec Integer 0 This stores the total seconds when the status was on HOLD.
zwait_flag Integer This is a flag variable which keeps track if the previous status is HOLD
zwait_time Date This stores the Last time , when the status was on HOLD

3. CONTENTS OF THE MOD AND SPEL FILE

Mod File
MODIFY cr status ON_POST_VAL set_zcrtime () 300 ;

Spel File
cr.status::set_zcrtime(...)
{
int curr_time;
int time_sec;
int wait_time;
int temp_time;

curr_time = (int) now();
wait_time = (int) zwait_time;
time_sec=(int) ztime_sec;

if (status.hold == 1 && status!="RE")
{

zwait_time=now();
zwait_flag=1;
}
if ((status.hold != 1 || Status == "RE") && zwait_flag==1)
{
temp_time = curr_time - wait_time;
zwait_flag =0;
ztime_sec= temp_time + time_sec;

}

return;
}

Relate Issues And Change Orders

2009-05-25T13:05:50Z

MaryNancy:

== '''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("<TABLE ID=tbl101 CLASS=tab summary='Issue List Notebook Tab row " + (_dtl.rowNum + 1) + "'>");
docWriteln("<TR>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Ref#</TH>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Status</TH>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Description</TH>");
docWriteln("</TR>");
<PDM_IF $args.impacted_chg.length == 0 >
<PDM_MACRO NAME=dtlStartRow>
docWriteln("<TD ALIGN=middle class=detailro>");
docWriteln("No Issue Attached");
docWriteln("</TD>");
<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="<TR class=" + sClass + ">";

docWriteln(strHTML);

docWriteln("<TD VALIGN=TOP class=detailroTab>");
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("</TD>");
docWriteln('<TD VALIGN=TOP class=detailroTab><PDM_FMT ESC_STYLE=C PAD=NO>$args.impacted_chg.status.sym</PDM_FMT></TD>');
docWriteln('<TD VALIGN=TOP class=detailroTab><PDM_FMT ESC_STYLE=C PAD=NO>$args.impacted_chg.description</PDM_FMT></TD>');
docWriteln("</TR>");
</PDM_LIST>
</PDM_IF>
docWriteln("</TABLE>");
</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:
[[Image:detail_chg.jpg]]

When you click on attach issues
[[Image:Attach_Issues.jpg]]

Click Search[[Image:search.jpg]]
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]]

Relate Issues And Change Orders

2009-05-25T13:04:34Z

MaryNancy:

== '''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("<TABLE ID=tbl101 CLASS=tab summary='Issue List Notebook Tab row " + (_dtl.rowNum + 1) + "'>");

<PDM_IF $args.impacted_chg.length == 0 >
<PDM_MACRO NAME=dtlStartRow>
docWriteln("<TD ALIGN=middle class=detailro>");
docWriteln("No Issue Attached");
docWriteln("</TD>");
<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="<TR class=" + sClass + ">";

docWriteln(strHTML);

docWriteln("<TD VALIGN=TOP class=detailroTab>");
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("</TD>");
docWriteln('<TD VALIGN=TOP class=detailroTab><PDM_FMT ESC_STYLE=C PAD=NO>$args.impacted_chg.status.sym</PDM_FMT></TD>');
docWriteln('<TD VALIGN=TOP class=detailroTab><PDM_FMT ESC_STYLE=C PAD=NO>$args.impacted_chg.description</PDM_FMT></TD>');
docWriteln("</TR>");
</PDM_LIST>
</PDM_IF>
docWriteln("</TABLE>");
</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:
[[Image:detail_chg.jpg]]

When you click on attach issues
[[Image:Attach_Issues.jpg]]

Click Search[[Image:search.jpg]]
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]]

Relate Issues And Change Orders

2009-05-25T13:01:49Z

MaryNancy:

Relate Issues And Change Orders

2009-05-25T12:58:57Z

MaryNancy:

Relate Issues And Change Orders

2009-05-25T12:56:22Z

MaryNancy:

== '''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”

<nowiki>
<html lang="en"><HEAD></nowiki>
<nowiki><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("<TABLE ID=tbl101 CLASS=tab summary='Issue List Notebook Tab row " + (_dtl.rowNum + 1) + "'>");
docWriteln("<TR>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Ref#</TH>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Status</TH>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Description</TH>");
docWriteln("</TR>");
<PDM_IF $args.impacted_chg.length == 0 >
<PDM_MACRO NAME=dtlStartRow>
docWriteln("<TD ALIGN=middle class=detailro>");
docWriteln("No Issue Attached");
docWriteln("</TD>");
<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="<TR class=" + sClass + ">";

docWriteln(strHTML);

docWriteln("<TD VALIGN=TOP class=detailroTab>");
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("</TD>");
docWriteln('<TD VALIGN=TOP class=detailroTab><PDM_FMT ESC_STYLE=C PAD=NO>$args.impacted_chg.status.sym</PDM_FMT></TD>');
docWriteln('<TD VALIGN=TOP class=detailroTab><PDM_FMT ESC_STYLE=C PAD=NO>$args.impacted_chg.description</PDM_FMT></TD>');
docWriteln("</TR>");
</PDM_LIST>
</PDM_IF>
docWriteln("</TABLE>");
</SCRIPT>
</PDM_FORM>
</BODY>
</HTML>
<PDM_IF 0>
</nowiki>
'''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:
[[Image:detail_chg.jpg]]

When you click on attach issues
[[Image:Attach_Issues.jpg]]

Click Search[[Image:search.jpg]]
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]]

Relate Issues And Change Orders

2009-05-25T12:54:03Z

MaryNancy:

Relate Issues And Change Orders

2009-05-25T12:51:09Z

MaryNancy:

== '''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("<TABLE ID=tbl101 CLASS=tab summary='Issue List Notebook Tab row " + (_dtl.rowNum + 1) + "'>");
docWriteln("<TR>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Ref#</TH>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Status</TH>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Description</TH>");
docWriteln("</TR>");
<PDM_IF $args.impacted_chg.length == 0 >
<PDM_MACRO NAME=dtlStartRow>
docWriteln("<TD ALIGN=middle class=detailro>");
docWriteln("No Issue Attached");
docWriteln("</TD>");
<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="<TR class=" + sClass + ">";

docWriteln(strHTML);

docWriteln("<TD VALIGN=TOP class=detailroTab>");
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("</TD>");
docWriteln('<TD VALIGN=TOP class=detailroTab><PDM_FMT ESC_STYLE=C PAD=NO>$args.impacted_chg.status.sym</PDM_FMT></TD>');
docWriteln('<TD VALIGN=TOP class=detailroTab><PDM_FMT ESC_STYLE=C PAD=NO>$args.impacted_chg.description</PDM_FMT></TD>');
docWriteln("</TR>");
</PDM_LIST>
</PDM_IF>
docWriteln("</TABLE>");
</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:
[[Image:detail_chg.jpg]]

When you click on attach issues
[[Image:Attach_Issues.jpg]]

Click Search[[Image:search.jpg]]
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]]

Relate Issues And Change Orders

2009-05-25T12:49:53Z

MaryNancy:

== '''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”

'''Note: Follow the above 4 points with the object Iss(Issue) also'''
<nowiki><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("<TABLE ID=tbl101 CLASS=tab summary='Issue List Notebook Tab row " + (_dtl.rowNum + 1) + "'>");
docWriteln("<TR>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Ref#</TH>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Status</TH>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Description</TH>");
docWriteln("</TR>");
<PDM_IF $args.impacted_chg.length == 0 >
<PDM_MACRO NAME=dtlStartRow>
docWriteln("<TD ALIGN=middle class=detailro>");
docWriteln("No Issue Attached");
docWriteln("</TD>");
<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="<TR class=" + sClass + ">";

docWriteln(strHTML);

docWriteln("<TD VALIGN=TOP class=detailroTab>");
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("</TD>");
docWriteln('<TD VALIGN=TOP class=detailroTab><PDM_FMT ESC_STYLE=C PAD=NO>$args.impacted_chg.status.sym</PDM_FMT></TD>');
docWriteln('<TD VALIGN=TOP class=detailroTab><PDM_FMT ESC_STYLE=C PAD=NO>$args.impacted_chg.description</PDM_FMT></TD>');
docWriteln("</TR>");
</PDM_LIST>
</PDM_IF>
docWriteln("</TABLE>");
</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>
</nowiki>

3. HOW TO ATTACH ISSUES TO CHANGE ORDERS
Login to the tool and open the Change Order:
[[Image:detail_chg.jpg]]

When you click on attach issues
[[Image:Attach_Issues.jpg]]

Click Search[[Image:search.jpg]]
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]]

Link chg iss

2009-05-25T12:48:46Z

MaryNancy:

<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("<TABLE ID=tbl101 CLASS=tab summary='Issue List Notebook Tab row " + (_dtl.rowNum + 1) + "'>");
docWriteln("<TR>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Ref#</TH>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Status</TH>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Description</TH>");
docWriteln("</TR>");
<PDM_IF $args.impacted_chg.length == 0 >
<PDM_MACRO NAME=dtlStartRow>
docWriteln("<TD ALIGN=middle class=detailro>");
docWriteln("No Issue Attached");
docWriteln("</TD>");
<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="<TR class=" + sClass + ">";

docWriteln(strHTML);

docWriteln("<TD VALIGN=TOP class=detailroTab>");
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("</TD>");
docWriteln('<TD VALIGN=TOP class=detailroTab><PDM_FMT ESC_STYLE=C PAD=NO>$args.impacted_chg.status.sym</PDM_FMT></TD>');
docWriteln('<TD VALIGN=TOP class=detailroTab><PDM_FMT ESC_STYLE=C PAD=NO>$args.impacted_chg.description</PDM_FMT></TD>');
docWriteln("</TR>");
</PDM_LIST>
</PDM_IF>
docWriteln("</TABLE>");
</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>

Link chg iss

2009-05-25T12:48:11Z

MaryNancy: Removing all content from page

Link chg iss

2009-05-25T12:47:45Z

MaryNancy: New page: <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 ...

Relate Issues And Change Orders

2009-05-25T12:46:47Z

MaryNancy:

Relate Issues And Change Orders

2009-05-25T12:43:35Z

MaryNancy:

File:Final.jpg

2009-05-25T12:40:44Z

MaryNancy:

File:Search.jpg

2009-05-25T12:39:45Z

MaryNancy:

File:Attach Issues.jpg

2009-05-25T12:39:09Z

MaryNancy:

File:Detail chg.jpg

2009-05-25T12:38:33Z

MaryNancy:

Relate Issues And Change Orders

2009-05-25T12:35:52Z

MaryNancy: New page: == '''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 folde...

== '''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”
<PDM_IF 0>
cnt_env_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("<TABLE ID=tbl101 CLASS=tab summary='Issue List Notebook Tab row " + (_dtl.rowNum + 1) + "'>");
docWriteln("<TR>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Ref#</TH>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Status</TH>");
docWriteln("<th scope=col ALIGN=LEFT class=results>Description</TH>");
docWriteln("</TR>");
<PDM_IF $args.impacted_chg.length == 0 >
<PDM_MACRO NAME=dtlStartRow>
docWriteln("<TD ALIGN=middle class=detailro>");
docWriteln("No Issue Attached");
docWriteln("</TD>");
<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="<TR class=" + sClass + ">";

docWriteln(strHTML);

docWriteln("<TD VALIGN=TOP class=detailroTab>");
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("</TD>");
docWriteln('<TD VALIGN=TOP class=detailroTab><PDM_FMT ESC_STYLE=C PAD=NO>$args.impacted_chg.status.sym</PDM_FMT></TD>');
docWriteln('<TD VALIGN=TOP class=detailroTab><PDM_FMT ESC_STYLE=C PAD=NO>$args.impacted_chg.description</PDM_FMT></TD>');
docWriteln("</TR>");
</PDM_LIST>
</PDM_IF>
docWriteln("</TABLE>");
</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>
2.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:
[[Image:detail_chg.jpg]]

When you click on attach issues
[[Image:Attach_Issues.jpg]]

Click Search[[Image:search.jpg]]
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]]