SDU - User contributions [en]

Refresh Customer Info Before Saving the Ticket

2008-08-08T17:48:14Z

Svetazk:

__NOTOC__
== Overview ==
This article provides customization to detail_in.htmpl for refreshing end user location and phone (as displayed on the form) when the end user changes BEFORE saving the change. The code works, but I am not crazy about it. I am hoping that someone can find a more elegant way to implement the same. I have only implemented and did limited testing in development, so the code has not been tested in the real world environment.

My understanding of the code is very limited, and was gained by trial and error, so my explanation and terminology might not be correct.

There are functions that you can use to call the server, I only mention two of them here: upd_workframe() and display_new_page(). In calls to these functions you can specify a callback function that will receive the results of the server lookup. In this code, I used two calls to display_new_page(): zCustomerLocationCallback() was specified as the callback in the 1st call, and zCustomerPhoneCallback() in the second one.

I encountered a few problems. First, I could not find a way to look up both location and phone in one server call, even though they both would be a lookup of the same record based on the same contact UUID. As a result, I had to do two server calls. Another problem is that if you try to do one server call after another, only the callback that was evoked by the last one will be executed. In other words, if in backfill_cnt_event() I had the following code, I would only see the phone being refreshed:
<source lang="javascript">
upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + cntID,
"func=parent.ahdframe.get_svc_callback");
display_new_page(url,ahdframeset.workframe); // with url for zCustomerLocationCallback()
…..
display_new_page(url,ahdframeset.workframe); // with url for zCustomerPhoneCallback()
</source>

That means that if you want to execute more than one callback per event, you have to call the next one from the previous. In this particular scenario, I had to execute 3 callback functions when an end user changes:
 1. Service contract check (upd_workframe("GET_SVC_CONTRACT"..) - out of the box behavior)
 2. Location lookup
 3. Phone lookup
 So I had to “chain” them: location callback function triggers phone callback, and phone callback triggers Service contract check.

I based my code on nr_inv_tab.htmpl and nr_ops.js: this code causes the manufacturer to be refreshed when the model of the asset changes. zcustomerChanged() is based on ModelChanged(), and the 2 callback functions are based on modelChangedCallback(). The difference is that I could not use onBlur() or on Change(), because I needed contact UUID, not the combo name(there can be duplicates), and it wouldn’t be available there. That’s why I used function
<source lang="javascript">
backfill_cnt_event( form_name, base_name, lname, fname, mname, cntID, caller_type )
</source>
where cntID is the new contact UUID. Also, I noticed that in nr_inv_tab.htmpl vendor only gets refreshed if the model is selected from the model search window, and not if you type it in and tab out. My code works in both scenarios.

== View the Complete Code ==
Coming soon

== Customization Steps ==
=== Step 1. Add customer location and phone ===
Note that Ids are important here - they will be used by the callback functions to refresh the fields.
<source lang="javascript">
<PDM_MACRO NAME=dtlReadonly hdr="End User Location" attr="customer.location" id=custloc>
<PDM_MACRO NAME=dtlReadonly hdr="End User Phone" attr="customer.phone_number" id=custphone>
</source>
=== Step 2. Modify function backfill_cnt_event() as follows ===
Comment out (or delete) Contract enforcement code and add a call the new custom function. It will look as follows:
<source lang="javascript">
function backfill_cnt_event( form_name, base_name, lname, fname, mname,
cntID, caller_type )
{
if (_dtl.edit && !_dtl.skip_agt_check)
{
var f = void(0);
var r = form_name.match(/main_form([0-9]*)/);
if ( r != null ) {
if ( r[1].length == 0 )
f = _dtl.form[0];
else
f = _dtl.form[r[1]-0];
}
detailAgtCheck(f, base_name, cntID, prop_ref);
}
detailCntBackfill( form_name, base_name, lname, fname, mname,
cntID, caller_type );

// sk: if user org has a service contract, the following code will clear out the category after changing user
// if it is not a private category from the contract under the contract, and will display message:
// "The current category can not be used with the current End User. The category has been reset."
// Contract enforcement:
/*
if (ahdtop.cfgNX_CLASSIC_SLA_PROCESSING != 'Yes' &&
base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1) {

upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + cntID,
"func=parent.ahdframe.get_svc_callback");
}
*/
// Note: even if remove "typeof cntID != "undefined" && cntID.length > 1", zRefreshCustomerInfo() still does not get called
if (base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1)
{
zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type);
}
}
</source>

=== Step 3. Add the following code at the end of backfill_cnt_event() ===
<source lang="javascript">
if (base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1)
{
zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type);
}
</source>
=== Step 4. Add the following java script code before function backfill_cnt_event() ===
<source lang="javascript">
var zcurrCustID="";

// Based on modelChanged() in nr_ops.js
function zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type ) {
//alert(cntID); //newly selected contact UUID
var zFID=document.forms["main_form"].elements["FID"].value;
var zSID=document.forms["main_form"].elements["SID"].value;
var zcntID=cntID.replace("U","");
zcntID=zcntID.replace("'","");

if (zcurrCustID == zcntID)
return;
zcurrCustID=cntID;

var url;
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
url=cfgCgi+"?SID="+zSID+"+FID="+zFID
+"+OP=SEARCH+FACTORY=cnt"
+"+KEEP.domset_name=RLIST_STATIC"
+"+QBE.EQ.id="+escape(zcntID)
+"+KEEP.backfill_attr=location.name"
+"+HTMPL=javascript:parent.ahdframe.zCustomerLocationCallback";
display_new_page(url,ahdframeset.workframe);
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
}

// Based on modelChangedCallback() in nr_ops.js
function zCustomerLocationCallback(persid,value,rel_attr_val)
{
set_action_in_progress(0);
//alert(persid); // cnt UUID with "cnt:" prefix
//alert(rel_attr_val); // cnt UUID without "cnt:" prefix
//alert(value); // location name
var e=document.getElementById("custloc");
if(e!=null)
e.innerHTML=value;

var zFID=document.forms["main_form"].elements["FID"].value;
var zSID=document.forms["main_form"].elements["SID"].value;
var url=cfgCgi+"?SID="+zSID+"+FID="+zFID
+"+OP=SEARCH+FACTORY=cnt"
+"+KEEP.domset_name=RLIST_STATIC"
+"+QBE.EQ.id="+escape(rel_attr_val)
+"+KEEP.backfill_attr=phone_number"
+"+HTMPL=javascript:parent.ahdframe.zCustomerPhoneCallback";
display_new_page(url,ahdframeset.workframe);
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
}

// Based on modelChangedCallback() in nr_ops.js
function zCustomerPhoneCallback(persid,value,rel_attr_val)
{
set_action_in_progress(0);
var e=document.getElementById("custphone");
if(e!=null)
e.innerHTML=value;

if (ahdtop.cfgNX_CLASSIC_SLA_PROCESSING != 'Yes') {
upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + rel_attr_val, "func=parent.ahdframe.get_svc_callback");
}
}
</source>

Refresh Customer Info Before Saving the Ticket

2008-08-08T17:34:01Z

Svetazk:

__NOTOC__
== Overview ==
This article provides customization to detail_in.htmpl for refreshing end user location and phone (as displayed on the form) when the end user changes BEFORE saving the change. The code works, but I am not crazy about it. I am hoping that someone can find a more elegant way to implement the same. I have only implemented and did limited testing in development, so the code has not been tested in the real world environment.

My understanding of the code is very limited, and was gained by trial and error, so my explanation and terminology might not be correct.

There are functions that you can use to call the server, I only mention two of them here: upd_workframe() and display_new_page(). In calls to these functions you can specify a callback function that will receive the results of the server lookup. In this code, I used two calls to display_new_page(): zCustomerLocationCallback() was specified as the callback in the 1st call, and zCustomerPhoneCallback() in the second one.

I encountered a few problems. First, I could not find a way to look up both location and phone in one server call, even though they both would be a lookup of the same record based on the same contact UUID. As a result, I had to do two server calls. Another problem is that if you try to do one server call after another, only the callback that was evoked by the last one will be executed. In other words, if in backfill_cnt_event() I had the following code, I would only see the phone being refreshed:
<source lang="javascript">
upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + cntID,
"func=parent.ahdframe.get_svc_callback");
display_new_page(url,ahdframeset.workframe); // with url for zCustomerLocationCallback()
…..
display_new_page(url,ahdframeset.workframe); // with url for zCustomerPhoneCallback()
</source>

That means that if you want to execute more than one callback per event, you have to call the next one from the previous. In this particular scenario, I had to execute 3 callback functions when an end user changes:
 1. Service contract check (upd_workframe("GET_SVC_CONTRACT"..) - out of the box behavior)
 2. Location lookup
 3. Phone lookup
 So I had to “chain” them: location callback function triggers phone callback, and phone callback triggers Service contract check.

I based my code on nr_inv_tab.htmpl and nr_ops.js: this code causes the manufacturer to be refreshed when the model of the asset changes. zcustomerChanged() is based on ModelChanged(), and the 2 callback functions are based on modelChangedCallback(). The difference is that I could not use onBlur() or on Change(), because I needed contact UUID, not the combo name(there can be duplicates), and it wouldn’t be available there. That’s why I used function
<source lang="javascript">
backfill_cnt_event( form_name, base_name, lname, fname, mname, cntID, caller_type )
</source>
where cntID is the new contact UUID. Also, I noticed that in nr_inv_tab.htmpl vendor only gets refreshed if the model is selected from the model search window, and not if you type it in and tab out. My code works in both scenarios.

== Customization Steps ==
=== Step 1. Add customer location and phone ===
Note that Ids are important here - they will be used by the callback functions to refresh the fields.
<source lang="javascript">
<PDM_MACRO NAME=dtlReadonly hdr="End User Location" attr="customer.location" id=custloc>
<PDM_MACRO NAME=dtlReadonly hdr="End User Phone" attr="customer.phone_number" id=custphone>
</source>
=== Step 2. Modify function backfill_cnt_event() as follows ===
Comment out (or delete) Contract enforcement code and add a call the new custom function. It will look as follows:
<source lang="javascript">
function backfill_cnt_event( form_name, base_name, lname, fname, mname,
cntID, caller_type )
{
if (_dtl.edit && !_dtl.skip_agt_check)
{
var f = void(0);
var r = form_name.match(/main_form([0-9]*)/);
if ( r != null ) {
if ( r[1].length == 0 )
f = _dtl.form[0];
else
f = _dtl.form[r[1]-0];
}
detailAgtCheck(f, base_name, cntID, prop_ref);
}
detailCntBackfill( form_name, base_name, lname, fname, mname,
cntID, caller_type );

// sk: if user org has a service contract, the following code will clear out the category after changing user
// if it is not a private category from the contract under the contract, and will display message:
// "The current category can not be used with the current End User. The category has been reset."
// Contract enforcement:
/*
if (ahdtop.cfgNX_CLASSIC_SLA_PROCESSING != 'Yes' &&
base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1) {

upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + cntID,
"func=parent.ahdframe.get_svc_callback");
}
*/
// Note: even if remove "typeof cntID != "undefined" && cntID.length > 1", zRefreshCustomerInfo() still does not get called
if (base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1)
{
zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type);
}
}
</source>

=== Step 3. Add the following code at the end of backfill_cnt_event() ===
<source lang="javascript">
if (base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1)
{
zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type);
}
</source>
=== Step 4. Add the following java script code before function backfill_cnt_event() ===
<source lang="javascript">
var zcurrCustID="";

// Based on modelChanged() in nr_ops.js
function zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type ) {
//alert(cntID); //newly selected contact UUID
var zFID=document.forms["main_form"].elements["FID"].value;
var zSID=document.forms["main_form"].elements["SID"].value;
var zcntID=cntID.replace("U","");
zcntID=zcntID.replace("'","");

if (zcurrCustID == zcntID)
return;
zcurrCustID=cntID;

var url;
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
url=cfgCgi+"?SID="+zSID+"+FID="+zFID
+"+OP=SEARCH+FACTORY=cnt"
+"+KEEP.domset_name=RLIST_STATIC"
+"+QBE.EQ.id="+escape(zcntID)
+"+KEEP.backfill_attr=location.name"
+"+HTMPL=javascript:parent.ahdframe.zCustomerLocationCallback";
display_new_page(url,ahdframeset.workframe);
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
}

// Based on modelChangedCallback() in nr_ops.js
function zCustomerLocationCallback(persid,value,rel_attr_val)
{
set_action_in_progress(0);
//alert(persid); // cnt UUID with "cnt:" prefix
//alert(rel_attr_val); // cnt UUID without "cnt:" prefix
//alert(value); // location name
var e=document.getElementById("custloc");
if(e!=null)
e.innerHTML=value;

var zFID=document.forms["main_form"].elements["FID"].value;
var zSID=document.forms["main_form"].elements["SID"].value;
var url=cfgCgi+"?SID="+zSID+"+FID="+zFID
+"+OP=SEARCH+FACTORY=cnt"
+"+KEEP.domset_name=RLIST_STATIC"
+"+QBE.EQ.id="+escape(rel_attr_val)
+"+KEEP.backfill_attr=phone_number"
+"+HTMPL=javascript:parent.ahdframe.zCustomerPhoneCallback";
display_new_page(url,ahdframeset.workframe);
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
}

// Based on modelChangedCallback() in nr_ops.js
function zCustomerPhoneCallback(persid,value,rel_attr_val)
{
set_action_in_progress(0);
var e=document.getElementById("custphone");
if(e!=null)
e.innerHTML=value;

if (ahdtop.cfgNX_CLASSIC_SLA_PROCESSING != 'Yes') {
upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + rel_attr_val, "func=parent.ahdframe.get_svc_callback");
}
}
</source>

Refresh Customer Info Before Saving the Ticket

2008-08-08T17:33:16Z

Svetazk:

__NOTOC__
== Overview ==
This article provides customization to detail_in.htmpl for refreshing end user location and phone (as displayed on the form) when the end user changes BEFORE saving the change. The code works, but I am not crazy about it. I am hoping that someone can find a more elegant way to implement the same. I have only implemented and did limited testing in development, so the code has not been tested in the real world environment.

My understanding of the code is very limited, and was gained by trial and error, so my explanation and terminology might not be correct.

There are functions that you can use to call the server, I only mention two of them here: upd_workframe() and display_new_page(). In calls to these functions you can specify a callback function that will receive the results of the server lookup. In this code, I used two calls to display_new_page(): zCustomerLocationCallback() was specified as the callback in the 1st call, and zCustomerPhoneCallback() in the second one.

I encountered a few problems. First, I could not find a way to look up both location and phone in one server call, even though they both would be a lookup of the same record based on the same contact UUID. As a result, I had to do two server calls. Another problem is that if you try to do one server call after another, only the callback that was evoked by the last one will be executed. In other words, if in backfill_cnt_event() I had the following code, I would only see the phone being refreshed:
<source lang="javascript">
upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + cntID,
"func=parent.ahdframe.get_svc_callback");
display_new_page(url,ahdframeset.workframe); // with url for zCustomerLocationCallback()
…..
display_new_page(url,ahdframeset.workframe); // with url for zCustomerPhoneCallback()
</source>

That means that if you want to execute more than one callback per event, you have to call the next one from the previous. In this particular scenario, I had to execute 3 callback functions when an end user changes:
 1. Service contract check (upd_workframe("GET_SVC_CONTRACT"..) - out of the box behavior)
 2. Location lookup
 3. Phone lookup
 So I had to “chain” them: location callback function triggers phone callback, and phone callback triggers Service contract check.

I based my code on nr_inv_tab.htmpl and nr_ops.js: this code causes the manufacturer to be refreshed when the model of the asset changes. zcustomerChanged() is based on ModelChanged(), and the 2 callback functions are based on modelChangedCallback(). The difference is that I could not use onBlur() or on Change(), because I needed contact UUID, not the combo name(there can be duplicates), and it wouldn’t be available there. That’s why I used function
<source lang="javascript">
backfill_cnt_event( form_name, base_name, lname, fname, mname, cntID, caller_type )
</source>
where cntID is the new contact UUID. Also, I noticed that in nr_inv_tab.htmpl vendor only gets refreshed if the model is selected from the model search window, and not if you type it in and tab out. My code works in both scenarios.

== Customization Steps ==
=== Step 1. Add customer location and phone ===
Note that Ids are important here - they will be used by the callback functions to refresh the fields.
<source lang="javascript">
<PDM_MACRO NAME=dtlReadonly hdr="End User Location" attr="customer.location" id=custloc>
<PDM_MACRO NAME=dtlReadonly hdr="End User Phone" attr="customer.phone_number" id=custphone>
<source lang="javascript">
=== Step 2. Modify function backfill_cnt_event() as follows ===
Comment out (or delete) Contract enforcement code and add a call the new custom function. It will look as follows:
<source lang="javascript">
function backfill_cnt_event( form_name, base_name, lname, fname, mname,
cntID, caller_type )
{
if (_dtl.edit && !_dtl.skip_agt_check)
{
var f = void(0);
var r = form_name.match(/main_form([0-9]*)/);
if ( r != null ) {
if ( r[1].length == 0 )
f = _dtl.form[0];
else
f = _dtl.form[r[1]-0];
}
detailAgtCheck(f, base_name, cntID, prop_ref);
}
detailCntBackfill( form_name, base_name, lname, fname, mname,
cntID, caller_type );

// sk: if user org has a service contract, the following code will clear out the category after changing user
// if it is not a private category from the contract under the contract, and will display message:
// "The current category can not be used with the current End User. The category has been reset."
// Contract enforcement:
/*
if (ahdtop.cfgNX_CLASSIC_SLA_PROCESSING != 'Yes' &&
base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1) {

upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + cntID,
"func=parent.ahdframe.get_svc_callback");
}
*/
// Note: even if remove "typeof cntID != "undefined" && cntID.length > 1", zRefreshCustomerInfo() still does not get called
if (base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1)
{
zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type);
}
}
</source>

=== Step 3. Add the following code at the end of backfill_cnt_event() ===
<source lang="javascript">
if (base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1)
{
zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type);
}
</source>
=== Step 4. Add the following java script code before function backfill_cnt_event() ===
<source lang="javascript">
var zcurrCustID="";

// Based on modelChanged() in nr_ops.js
function zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type ) {
//alert(cntID); //newly selected contact UUID
var zFID=document.forms["main_form"].elements["FID"].value;
var zSID=document.forms["main_form"].elements["SID"].value;
var zcntID=cntID.replace("U","");
zcntID=zcntID.replace("'","");

if (zcurrCustID == zcntID)
return;
zcurrCustID=cntID;

var url;
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
url=cfgCgi+"?SID="+zSID+"+FID="+zFID
+"+OP=SEARCH+FACTORY=cnt"
+"+KEEP.domset_name=RLIST_STATIC"
+"+QBE.EQ.id="+escape(zcntID)
+"+KEEP.backfill_attr=location.name"
+"+HTMPL=javascript:parent.ahdframe.zCustomerLocationCallback";
display_new_page(url,ahdframeset.workframe);
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
}

// Based on modelChangedCallback() in nr_ops.js
function zCustomerLocationCallback(persid,value,rel_attr_val)
{
set_action_in_progress(0);
//alert(persid); // cnt UUID with "cnt:" prefix
//alert(rel_attr_val); // cnt UUID without "cnt:" prefix
//alert(value); // location name
var e=document.getElementById("custloc");
if(e!=null)
e.innerHTML=value;

var zFID=document.forms["main_form"].elements["FID"].value;
var zSID=document.forms["main_form"].elements["SID"].value;
var url=cfgCgi+"?SID="+zSID+"+FID="+zFID
+"+OP=SEARCH+FACTORY=cnt"
+"+KEEP.domset_name=RLIST_STATIC"
+"+QBE.EQ.id="+escape(rel_attr_val)
+"+KEEP.backfill_attr=phone_number"
+"+HTMPL=javascript:parent.ahdframe.zCustomerPhoneCallback";
display_new_page(url,ahdframeset.workframe);
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
}

// Based on modelChangedCallback() in nr_ops.js
function zCustomerPhoneCallback(persid,value,rel_attr_val)
{
set_action_in_progress(0);
var e=document.getElementById("custphone");
if(e!=null)
e.innerHTML=value;

if (ahdtop.cfgNX_CLASSIC_SLA_PROCESSING != 'Yes') {
upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + rel_attr_val, "func=parent.ahdframe.get_svc_callback");
}
}
</source>

Refresh Customer Info Before Saving the Ticket

2008-08-08T17:32:22Z

Svetazk:

__NOTOC__
== Overview ==
This article provides customization to detail_in.htmpl for refreshing end user location and phone (as displayed on the form) when the end user changes BEFORE saving the change. The code works, but I am not crazy about it. I am hoping that someone can find a more elegant way to implement the same. I have only implemented and did limited testing in development, so the code has not been tested in the real world environment.

My understanding of the code is very limited, and was gained by trial and error, so my explanation and terminology might not be correct.

There are functions that you can use to call the server, I only mention two of them here: upd_workframe() and display_new_page(). In calls to these functions you can specify a callback function that will receive the results of the server lookup. In this code, I used two calls to display_new_page(): zCustomerLocationCallback() was specified as the callback in the 1st call, and zCustomerPhoneCallback() in the second one.

I encountered a few problems. First, I could not find a way to look up both location and phone in one server call, even though they both would be a lookup of the same record based on the same contact UUID. As a result, I had to do two server calls. Another problem is that if you try to do one server call after another, only the callback that was evoked by the last one will be executed. In other words, if in backfill_cnt_event() I had the following code, I would only see the phone being refreshed:
<source lang="javascript">
upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + cntID,
"func=parent.ahdframe.get_svc_callback");
display_new_page(url,ahdframeset.workframe); // with url for zCustomerLocationCallback()
…..
display_new_page(url,ahdframeset.workframe); // with url for zCustomerPhoneCallback()
</source>

That means that if you want to execute more than one callback per event, you have to call the next one from the previous. In this particular scenario, I had to execute 3 callback functions when an end user changes:
 1. Service contract check (upd_workframe("GET_SVC_CONTRACT"..) - out of the box behavior)
 2. Location lookup
 3. Phone lookup
 So I had to “chain” them: location callback function triggers phone callback, and phone callback triggers Service contract check.

I based my code on nr_inv_tab.htmpl and nr_ops.js: this code causes the manufacturer to be refreshed when the model of the asset changes. zcustomerChanged() is based on ModelChanged(), and the 2 callback functions are based on modelChangedCallback(). The difference is that I could not use onBlur() or on Change(), because I needed contact UUID, not the combo name(there can be duplicates), and it wouldn’t be available there. That’s why I used function
<source lang="javascript">
backfill_cnt_event( form_name, base_name, lname, fname, mname, cntID, caller_type )
</source>
where cntID is the new contact UUID. Also, I noticed that in nr_inv_tab.htmpl vendor only gets refreshed if the model is selected from the model search window, and not if you type it in and tab out. My code works in both scenarios.

== Customization Steps ==
=== Step 1. Add customer location and phone ===
Note that Ids are important here - they will be used by the callback functions to refresh the fields.
<source lang="javascript">
<PDM_MACRO NAME=dtlReadonly hdr="End User Location" attr="customer.location" id=custloc>
<PDM_MACRO NAME=dtlReadonly hdr="End User Phone" attr="customer.phone_number" id=custphone>
<source lang="javascript">
=== Step 2. Modify function backfill_cnt_event() as follows ===
Comment out (or delete) Contract enforcement code and add a call the new custom function. It will look as follows:
<source lang="javascript">
function backfill_cnt_event( form_name, base_name, lname, fname, mname,
cntID, caller_type )
{
if (_dtl.edit && !_dtl.skip_agt_check)
{
var f = void(0);
var r = form_name.match(/main_form([0-9]*)/);
if ( r != null ) {
if ( r[1].length == 0 )
f = _dtl.form[0];
else
f = _dtl.form[r[1]-0];
}
detailAgtCheck(f, base_name, cntID, prop_ref);
}
detailCntBackfill( form_name, base_name, lname, fname, mname,
cntID, caller_type );

// sk: if user org has a service contract, the following code will clear out the category after changing user
// if it is not a private category from the contract under the contract, and will display message:
// "The current category can not be used with the current End User. The category has been reset."
// Contract enforcement:
/*
if (ahdtop.cfgNX_CLASSIC_SLA_PROCESSING != 'Yes' &&
base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1) {

upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + cntID,
"func=parent.ahdframe.get_svc_callback");
}
*/
// Note: even if remove "typeof cntID != "undefined" && cntID.length > 1", zRefreshCustomerInfo() still does not get called
if (base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1)
{
zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type);
}
}
</source>

=== Step 3. Add the following code at the end of backfill_cnt_event() ===
<source lang="javascript">
if (base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1)
{
zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type);
}
</source">
=== Step 4. Add the following java script code before function backfill_cnt_event() ===
<source lang="javascript">
var zcurrCustID="";

// Based on modelChanged() in nr_ops.js
function zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type ) {
//alert(cntID); //newly selected contact UUID
var zFID=document.forms["main_form"].elements["FID"].value;
var zSID=document.forms["main_form"].elements["SID"].value;
var zcntID=cntID.replace("U","");
zcntID=zcntID.replace("'","");

if (zcurrCustID == zcntID)
return;
zcurrCustID=cntID;

var url;
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
url=cfgCgi+"?SID="+zSID+"+FID="+zFID
+"+OP=SEARCH+FACTORY=cnt"
+"+KEEP.domset_name=RLIST_STATIC"
+"+QBE.EQ.id="+escape(zcntID)
+"+KEEP.backfill_attr=location.name"
+"+HTMPL=javascript:parent.ahdframe.zCustomerLocationCallback";
display_new_page(url,ahdframeset.workframe);
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
}

// Based on modelChangedCallback() in nr_ops.js
function zCustomerLocationCallback(persid,value,rel_attr_val)
{
set_action_in_progress(0);
//alert(persid); // cnt UUID with "cnt:" prefix
//alert(rel_attr_val); // cnt UUID without "cnt:" prefix
//alert(value); // location name
var e=document.getElementById("custloc");
if(e!=null)
e.innerHTML=value;

var zFID=document.forms["main_form"].elements["FID"].value;
var zSID=document.forms["main_form"].elements["SID"].value;
var url=cfgCgi+"?SID="+zSID+"+FID="+zFID
+"+OP=SEARCH+FACTORY=cnt"
+"+KEEP.domset_name=RLIST_STATIC"
+"+QBE.EQ.id="+escape(rel_attr_val)
+"+KEEP.backfill_attr=phone_number"
+"+HTMPL=javascript:parent.ahdframe.zCustomerPhoneCallback";
display_new_page(url,ahdframeset.workframe);
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
}

// Based on modelChangedCallback() in nr_ops.js
function zCustomerPhoneCallback(persid,value,rel_attr_val)
{
set_action_in_progress(0);
var e=document.getElementById("custphone");
if(e!=null)
e.innerHTML=value;

if (ahdtop.cfgNX_CLASSIC_SLA_PROCESSING != 'Yes') {
upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + rel_attr_val, "func=parent.ahdframe.get_svc_callback");
}
}
</source>

Refresh Customer Info Before Saving the Ticket

2008-08-08T17:24:27Z

Svetazk: /* Overview */

__NOTOC__
== Overview ==
This article provides customization to detail_in.htmpl for refreshing end user location and phone (as displayed on the form) when the end user changes BEFORE saving the change. The code works, but I am not crazy about it. I am hoping that someone can find a more elegant way to implement the same. I have only implemented and did limited testing in development, so the code has not been tested in the real world environment.

My understanding of the code is very limited, and was gained by trial and error, so my explanation and terminology might not be correct.

There are functions that you can use to call the server, I only mention two of them here: upd_workframe() and display_new_page(). In calls to these functions you can specify a callback function that will receive the results of the server lookup. In this code, I used two calls to display_new_page(): zCustomerLocationCallback() was specified as the callback in the 1st call, and zCustomerPhoneCallback() in the second one.

I encountered a few problems. First, I could not find a way to look up both location and phone in one server call, even though they both would be a lookup of the same record based on the same contact UUID. As a result, I had to do two server calls. Another problem is that if you try to do one server call after another, only the callback that was evoked by the last one will be executed. In other words, if in backfill_cnt_event() I had the following code, I would only see the phone being refreshed:
<source lang="javascript">
upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + cntID,
"func=parent.ahdframe.get_svc_callback");
display_new_page(url,ahdframeset.workframe); // with url for zCustomerLocationCallback()
…..
display_new_page(url,ahdframeset.workframe); // with url for zCustomerPhoneCallback()
</source>

That means that if you want to execute more than one callback per event, you have to call the next one from the previous. In this particular scenario, I had to execute 3 callback functions when an end user changes:
1. Service contract check (upd_workframe("GET_SVC_CONTRACT"..) - out of the box behavior)
2. Location lookup
3. Phone lookup
So I had to “chain” them: location callback function triggers phone callback, and phone callback triggers Service contract check.

I based my code on nr_inv_tab.htmpl and nr_ops.js: this code causes the manufacturer to be refreshed when the model of the asset changes. zcustomerChanged() is based on ModelChanged(), and the 2 callback functions are based on modelChangedCallback(). The difference is that I could not use onBlur() or on Change(), because I needed contact UUID, not the combo name(there can be duplicates), and it wouldn’t be available there. That’s why I used function backfill_cnt_event( form_name, base_name, lname, fname, mname, cntID, caller_type ), where cntID is the new contact UUID. Also, I noticed that in nr_inv_tab.htmpl vendor only gets refreshed if the model is selected from the model search window, and not if you type it in and tab out. My code works in both scenarios.

I will upload the complete code of detail_in.htmpl. If you can’t find it, feel free to email me and I will send it to you.

Here are the customization steps.

Step 1. Add customer location and phone. Note that Ids are important here - they will be used by the callback functions to refresh the fields.
<PDM_MACRO NAME=dtlReadonly hdr="End User Location" attr="customer.location" id=custloc>
<PDM_MACRO NAME=dtlReadonly hdr="End User Phone" attr="customer.phone_number" id=custphone>

Step 2. Modify function backfill_cnt_event() as follows.
Comment out (or delete) Contract enforcement code and add a call the new custom function. It will look as follows:
function backfill_cnt_event( form_name, base_name, lname, fname, mname,
cntID, caller_type )
{
if (_dtl.edit && !_dtl.skip_agt_check)
{
var f = void(0);
var r = form_name.match(/main_form([0-9]*)/);
if ( r != null ) {
if ( r[1].length == 0 )
f = _dtl.form[0];
else
f = _dtl.form[r[1]-0];
}
detailAgtCheck(f, base_name, cntID, prop_ref);
}
detailCntBackfill( form_name, base_name, lname, fname, mname,
cntID, caller_type );

// sk: if user org has a service contract, the following code will clear out the category after changing user
// if it is not a private category from the contract under the contract, and will display message:
// "The current category can not be used with the current End User. The category has been reset."
// Contract enforcement:
/*
if (ahdtop.cfgNX_CLASSIC_SLA_PROCESSING != 'Yes' &&
base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1) {

upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + cntID,
"func=parent.ahdframe.get_svc_callback");
}
*/
// Note: even if remove "typeof cntID != "undefined" && cntID.length > 1", zRefreshCustomerInfo() still does not get called
if (base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1)
{
zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type);
}
}

Step 3. Add the following code at the end of backfill_cnt_event():
if (base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1)
{
zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type);
}

Step 4. Add the following java script code before function backfill_cnt_event().
var zcurrCustID="";

// Based on modelChanged() in nr_ops.js
function zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type ) {
//alert(cntID); //newly selected contact UUID
var zFID=document.forms["main_form"].elements["FID"].value;
var zSID=document.forms["main_form"].elements["SID"].value;
var zcntID=cntID.replace("U","");
zcntID=zcntID.replace("'","");

if (zcurrCustID == zcntID)
return;
zcurrCustID=cntID;

var url;
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
url=cfgCgi+"?SID="+zSID+"+FID="+zFID
+"+OP=SEARCH+FACTORY=cnt"
+"+KEEP.domset_name=RLIST_STATIC"
+"+QBE.EQ.id="+escape(zcntID)
+"+KEEP.backfill_attr=location.name"
+"+HTMPL=javascript:parent.ahdframe.zCustomerLocationCallback";
display_new_page(url,ahdframeset.workframe);
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
}

// Based on modelChangedCallback() in nr_ops.js
function zCustomerLocationCallback(persid,value,rel_attr_val)
{
set_action_in_progress(0);
//alert(persid); // cnt UUID with "cnt:" prefix
//alert(rel_attr_val); // cnt UUID without "cnt:" prefix
//alert(value); // location name
var e=document.getElementById("custloc");
if(e!=null)
e.innerHTML=value;

var zFID=document.forms["main_form"].elements["FID"].value;
var zSID=document.forms["main_form"].elements["SID"].value;
var url=cfgCgi+"?SID="+zSID+"+FID="+zFID
+"+OP=SEARCH+FACTORY=cnt"
+"+KEEP.domset_name=RLIST_STATIC"
+"+QBE.EQ.id="+escape(rel_attr_val)
+"+KEEP.backfill_attr=phone_number"
+"+HTMPL=javascript:parent.ahdframe.zCustomerPhoneCallback";
display_new_page(url,ahdframeset.workframe);
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
}

// Based on modelChangedCallback() in nr_ops.js
function zCustomerPhoneCallback(persid,value,rel_attr_val)
{
set_action_in_progress(0);
var e=document.getElementById("custphone");
if(e!=null)
e.innerHTML=value;

if (ahdtop.cfgNX_CLASSIC_SLA_PROCESSING != 'Yes') {
upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + rel_attr_val, "func=parent.ahdframe.get_svc_callback");
}
}

Refresh Customer Info Before Saving the Ticket

2008-08-08T17:22:03Z

Svetazk: New page: __NOTOC__ == Overview == This article provides customization to detail_in.htmpl for refreshing end user location and phone (as displayed on the form) when the end user changes BEFORE savi...

__NOTOC__
== Overview ==
This article provides customization to detail_in.htmpl for refreshing end user location and phone (as displayed on the form) when the end user changes BEFORE saving the change. The code works, but I am not crazy about it. I am hoping that someone can find a more elegant way to implement the same. I have only implemented and did limited testing in development, so the code has not been tested in the real world environment.

My understanding of the code is very limited, and was gained by trial and error, so my explanation and terminology might not be correct.

There are functions that you can use to call the server, I only mention two of them here: upd_workframe() and display_new_page(). In calls to these functions you can specify a callback function that will receive the results of the server lookup. In this code, I used two calls to display_new_page(): zCustomerLocationCallback() was specified as the callback in the 1st call, and zCustomerPhoneCallback() in the second one.

I encountered a few problems. First, I could not find a way to look up both location and phone in one server call, even though they both would be a lookup of the same record based on the same contact UUID. As a result, I had to do two server calls. Another problem is that if you try to do one server call after another, only the callback that was evoked by the last one will be executed. In other words, if in backfill_cnt_event() I had the following code, I would only see the phone being refreshed:
upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + cntID,
"func=parent.ahdframe.get_svc_callback");
display_new_page(url,ahdframeset.workframe); // with url for zCustomerLocationCallback()
…..
display_new_page(url,ahdframeset.workframe); // with url for zCustomerPhoneCallback()

That means that if you want to execute more than one callback per event, you have to call the next one from the previous. In this particular scenario, I had to execute 3 callback functions when an end user changes:
1. Service contract check (upd_workframe("GET_SVC_CONTRACT"..) - out of the box behavior)
2. Location lookup
3. Phone lookup
So I had to “chain” them: location callback function triggers phone callback, and phone callback triggers Service contract check.

I based my code on nr_inv_tab.htmpl and nr_ops.js: this code causes the manufacturer to be refreshed when the model of the asset changes. zcustomerChanged() is based on ModelChanged(), and the 2 callback functions are based on modelChangedCallback(). The difference is that I could not use onBlur() or on Change(), because I needed contact UUID, not the combo name(there can be duplicates), and it wouldn’t be available there. That’s why I used function backfill_cnt_event( form_name, base_name, lname, fname, mname, cntID, caller_type ), where cntID is the new contact UUID. Also, I noticed that in nr_inv_tab.htmpl vendor only gets refreshed if the model is selected from the model search window, and not if you type it in and tab out. My code works in both scenarios.

I will upload the complete code of detail_in.htmpl. If you can’t find it, feel free to email me and I will send it to you.

Here are the customization steps.

Step 1. Add customer location and phone. Note that Ids are important here - they will be used by the callback functions to refresh the fields.
<PDM_MACRO NAME=dtlReadonly hdr="End User Location" attr="customer.location" id=custloc>
<PDM_MACRO NAME=dtlReadonly hdr="End User Phone" attr="customer.phone_number" id=custphone>

Step 2. Modify function backfill_cnt_event() as follows.
Comment out (or delete) Contract enforcement code and add a call the new custom function. It will look as follows:
function backfill_cnt_event( form_name, base_name, lname, fname, mname,
cntID, caller_type )
{
if (_dtl.edit && !_dtl.skip_agt_check)
{
var f = void(0);
var r = form_name.match(/main_form([0-9]*)/);
if ( r != null ) {
if ( r[1].length == 0 )
f = _dtl.form[0];
else
f = _dtl.form[r[1]-0];
}
detailAgtCheck(f, base_name, cntID, prop_ref);
}
detailCntBackfill( form_name, base_name, lname, fname, mname,
cntID, caller_type );

// sk: if user org has a service contract, the following code will clear out the category after changing user
// if it is not a private category from the contract under the contract, and will display message:
// "The current category can not be used with the current End User. The category has been reset."
// Contract enforcement:
/*
if (ahdtop.cfgNX_CLASSIC_SLA_PROCESSING != 'Yes' &&
base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1) {

upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + cntID,
"func=parent.ahdframe.get_svc_callback");
}
*/
// Note: even if remove "typeof cntID != "undefined" && cntID.length > 1", zRefreshCustomerInfo() still does not get called
if (base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1)
{
zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type);
}
}

Step 3. Add the following code at the end of backfill_cnt_event():
if (base_name == "customer" && typeof cntID != "undefined" && cntID.length > 1)
{
zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type);
}

Step 4. Add the following java script code before function backfill_cnt_event().
var zcurrCustID="";

// Based on modelChanged() in nr_ops.js
function zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type ) {
//alert(cntID); //newly selected contact UUID
var zFID=document.forms["main_form"].elements["FID"].value;
var zSID=document.forms["main_form"].elements["SID"].value;
var zcntID=cntID.replace("U","");
zcntID=zcntID.replace("'","");

if (zcurrCustID == zcntID)
return;
zcurrCustID=cntID;

var url;
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
url=cfgCgi+"?SID="+zSID+"+FID="+zFID
+"+OP=SEARCH+FACTORY=cnt"
+"+KEEP.domset_name=RLIST_STATIC"
+"+QBE.EQ.id="+escape(zcntID)
+"+KEEP.backfill_attr=location.name"
+"+HTMPL=javascript:parent.ahdframe.zCustomerLocationCallback";
display_new_page(url,ahdframeset.workframe);
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
}

// Based on modelChangedCallback() in nr_ops.js
function zCustomerLocationCallback(persid,value,rel_attr_val)
{
set_action_in_progress(0);
//alert(persid); // cnt UUID with "cnt:" prefix
//alert(rel_attr_val); // cnt UUID without "cnt:" prefix
//alert(value); // location name
var e=document.getElementById("custloc");
if(e!=null)
e.innerHTML=value;

var zFID=document.forms["main_form"].elements["FID"].value;
var zSID=document.forms["main_form"].elements["SID"].value;
var url=cfgCgi+"?SID="+zSID+"+FID="+zFID
+"+OP=SEARCH+FACTORY=cnt"
+"+KEEP.domset_name=RLIST_STATIC"
+"+QBE.EQ.id="+escape(rel_attr_val)
+"+KEEP.backfill_attr=phone_number"
+"+HTMPL=javascript:parent.ahdframe.zCustomerPhoneCallback";
display_new_page(url,ahdframeset.workframe);
if(ahdframe.currentAction==0) // =0 if customer selected from contact list; =6 if typed in
{
set_action_in_progress(ACTN_AUTOFILL);
}
}

// Based on modelChangedCallback() in nr_ops.js
function zCustomerPhoneCallback(persid,value,rel_attr_val)
{
set_action_in_progress(0);
var e=document.getElementById("custphone");
if(e!=null)
e.innerHTML=value;

if (ahdtop.cfgNX_CLASSIC_SLA_PROCESSING != 'Yes') {
upd_workframe("GET_SVC_CONTRACT", "new_customer=cnt:" + rel_attr_val, "func=parent.ahdframe.get_svc_callback");
}
}

Sample Customizations

2008-08-08T17:19:46Z

Svetazk: /* List of Customizations */

__NOTOC__
[[Category:Customization]]
{{Global Header}}
{{Global Announcement}}

== Overview ==
Customizations are regarded as changes to the system that are not supportable by CA.

== List of Customizations ==
*[[Add Attachments to Configuration Items]]
*[[Add Checkbox, Date, Drop-down, Lookup, Readonly and Text Fields to Properties]]
*[[Add Contact Search to Employee/Customer Interface]]
*[[Add Custom Activity Log Action Macro]]
*[[Add Log Entry for Updates to Custom Fields]]
*[[Add Log Entry When a Property Value Changes on a Ticket]]
*[[Add Personalized Response to Manual Notification]]
*[[Add Posted By to Announcements Page]]
*[[Add Properties Count to Area/Category List]]
*[[Add Workflow to Employee/Customer Interface]]
*[[Auto-fill Fields Left Blank]]
*[[Automatically Attach an Asset/CI to a Change Order or Issue]]
*[[Automatically Remove Attached Events]]
*[[Automatically Set Assignee to Closing Analyst]]
*[[Automatically Set System Generated Activities to Internal]]
*[[Changing Announcements Order By]]
*[[Changing Error Alert Color and adding Error Alert Pop-ups]]
*[[Changing Requests to Incidents]]
*[[Changing Display of Contacts]]
*[[Conditional Display of Drop-Down Content]]
*[[Conditionally Attach an Event]]
*[[Configure Java Client to Use Web Client for Uploading Attachments]]
*[[Control the Request Areas Displayed to the End Users]]
*[[Count Ticket Reopens]]
*[[Display Web Site within Service Desk]]
*[[Default Properties Tab on New Ticket Creation]]
*[[Increasing Default Field Size]]
*[[List Tickets ORDER BY Group]]
*[[Make a Field Conditionally Required]]
*[[Only Assignee can Close]]
*[[Prevent Close of Requests, Incidents, and Problems if Change Order is Active]]
*[[Prevent Update to Past Activities]]
*[[Propagate Status to Children]]
*[[Priority and Impact Default to Empty]]
*[[Refresh customer info before saving the ticket]]
*[[Remove SLA Violation from Employee View]]
*[[Require a Solution in Order to Resolve]]
*[[Search Requests, Incidents, and Problems Simultaneously for Ticket Number]]
*[[Separate Prefixes for Requests, Incidents, and Problems]]
*[[Set Defaults on Manual Notify]]
*[[Set Priority Based on Urgency and Impact]]
*[[Set Request, Incident and Problem Status from Change Order]]
*[[Simplified Child Creation]]
*[[Single Sign-on with Cookies]]

Changing Error Alert Color and adding Error Alert Pop-ups

2008-05-13T19:14:32Z

Svetazk:

__NOTOC__
Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I made modifications to a couple of java script functions to change this behavior. Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
There are two different scenarios that lead to displaying of an alert message. If you want your color change to affect both scenarios, you will have to customize two Java script functions. 
The 1st scenario is triggered when an unconditionally required field (i.e. defined as required at the schema level) is not filled in. The function showAlertMsg() is called in this case, and that’s the one we need to modify. This scenario is covered by Part I of this article. 
The 2nd scenario is when either data partition constraints or SPL triggers enforce data validation. In this case, endDetail() is the function that needs to be modified. The details are provided in Part II of the article 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 

= Part I. Alerts for unconditionally required fields =

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy function showAlertMsg() from $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js 
Note: Any patches/updates to showAlertMsg() in $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js must be manually ported to showAlertMsg() in $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
If you want to change the color of the error messages, add this line:
<source lang="javascript">alertmsg.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, remove the condition that prevents pop-up for Analyst Interface. 
Original code:
<source lang="javascript">
if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
</source>
Modified code:
<source lang="javascript">
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
</source>

== Step 4. Clear your Web browser cache ==
Clear your Web browser cache to test (no need to recycle USD)

== Modified showAlertMsg() ==

<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// Commented out the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
// Change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

= Part II. Alerts for data constraint and spell trigger validations =

== Step 1. Add endDetail() function to sitemods.js ==
Copy function endDetail() from $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js 
Note: Any patches/updates to endDetail() in $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js must be manually ported to endDetail() in $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 2. Modify endDetail() in sitemods.js ==

If you want to change the color of the error messages, find line
<source lang="javascript">
e.style.display="block";
</source>

and add the following under it:
<source lang="javascript">if (AlertMsg.substr(0,15) != "Save Successful") e.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, find line
<source lang="javascript">
if(typeof e=="object"&&e!=null){
</source>

and add the following code under it:

<source lang="javascript">
if (AlertMsg.substr(0,15) != "Save Successful") // prevent popup for success messages
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',3);
}

</source>

== Step 3. Clear your Web browser cache ==
Clear your Web browser cache to test (no need to recycle USD)

== Modified endDetail() ==

<source lang="javascript">
function endDetail()
{
detailEndRow();
var out="";
if(_dtl.tableStarted)
out="</TABLE>\n";
if(_dtl.formStarted)
out+="</FORM>";
docWriteln(out);
_dtl.tableStarted=false;
if(typeof AlertMsg=="string"&&AlertMsg.length>0)
{
var e=document.getElementById("alertmsgText");
if(typeof e=="object"&&e!=null){
// Popup alert with same text that is displayed in alertmsg area of the form
if (AlertMsg.substr(0,15) != "Save Successful")
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',3);
}

e.innerHTML=AlertMsg;
e=document.getElementById("alertmsg");
e.style.display="block";
// display alert in red
if (AlertMsg.substr(0,15) != "Save Successful")
e.style.backgroundColor="red";
adjScrollDivHeight();
}
}
if(typeof _dtl.firstField=="string")
{
_dtl.firstField=document.getElementById(_dtl.firstField);
if(_dtl.firstField!=null)
{
_dtl.onload=window.onload;
window.onload=detailOnload;
}
else if(_dtl.edit)
_dtl.form[0].style.display="block";
}
if(_dtl.center)
docWriteln("</CENTER>");
if(typeof ahdtop=="object"&&typeof ahdtop.detailForms=="object"
&&(typeof alg_factory!="string"||alg_factory==propFactory))
{
if(typeof argPersistentID=="string"&&argPersistentID.length>0)
ahdtop.detailForms[argPersistentID]=window.parent;
if(propFactory=="chg"&&typeof argChgRefNum=="string")
ahdtop.detailForms["chg"+argChgRefNum]=window.parent;
else if((propFactory=="cr"||propFactory=="iss")&&typeof argRefNum=="string")
ahdtop.detailForms[propFactory+argRefNum]=window.parent;
}
if(_dtl.spellchk)
{
do_hiddenfm('spell_form','main_form');
}
} // endDetail()

</source>

----
<div align='center'>To make corrections or additions to this article, select the ''edit'' tab above. 
To discuss or ask questions about this article, select the ''discussion'' tab above.</div>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-05-13T19:11:30Z

Svetazk:

__NOTOC__
Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I made modifications to a couple of java script functions to change this behavior. Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
There are two different scenarios that lead to displaying of an alert message. If you want your color change to affect both scenarios, you will have to customize two Java script functions. 
The 1st scenario is triggered when an unconditionally required field (i.e. defined as required at the schema level) is not filled in. The function showAlertMsg() is called in this case, and that’s the one we need to modify. This scenario is covered by Part I of this article. 
The 2nd scenario is when either data partition constraints or SPL triggers enforce data validation. In this case, endDetail() is the function that needs to be modified. The details are provided in Part II of the article 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 

= Part I. Alerts for unconditionally required fields =

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy function showAlertMsg() from $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js 
Note: Any patches/updates to showAlertMsg() in $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js must be manually ported to showAlertMsg() in $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
If you want to change the color of the error messages, add this line:
<source lang="javascript">alertmsg.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, remove the condition that prevents pop-up for Analyst Interface. 
Original code:
<source lang="javascript">
if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
</source>
Modified code:
<source lang="javascript">
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
</source>

== Step 4. Clear your Web browser cache ==
Clear your Web browser cache to test (no need to recycle USD)

== Modified showAlertMsg() ==

<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// Commented out the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
// Change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

= Part II. Alerts for data constraint and spell trigger validations =

== Step 1. Add endDetail() function to sitemods.js ==
Copy function endDetail() from $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js 
Note: Any patches/updates to endDetail() in $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js must be manually ported to endDetail() in $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 2. Modify endDetail() in sitemods.js ==

If you want to change the color of the error messages, find line
<source lang="javascript">
e.style.display="block";
</source>

and add the following under it:
<source lang="javascript">if (AlertMsg.substr(0,15) != "Save Successful") e.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, find line
<source lang="javascript">
if(typeof e=="object"&&e!=null){
</source>

and add the following code under it:

<source lang="javascript">
if (AlertMsg.substr(0,15) != "Save Successful") // prevent popup for success messages
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',3);
}

</source>

== Step 3. Clear your Web browser cache ==
Clear your Web browser cache to test (no need to recycle USD)

----
<div align='center'>To make corrections or additions to this article, select the ''edit'' tab above. 
To discuss or ask questions about this article, select the ''discussion'' tab above.</div>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-05-13T19:09:47Z

Svetazk:

__NOTOC__
Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I made modifications to a couple of java script functions to change this behavior. Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
There are two different scenarios that lead to displaying of an alert message. If you want your color change to affect both scenarios, you will have to customize two Java script functions. 
The 1st scenario is triggered when an unconditionally required field (i.e. defined as required at the schema level) is not filled in. The function showAlertMsg() is called in this case, and that’s the one we need to modify. This scenario is covered by Part I of this article. 
The 2nd scenario is when either data partition constraints or SPL triggers enforce data validation. In this case, endDetail() is the function that needs to be modified. The details are provided in Part II of the article 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 

= Part I. Alerts for unconditionally required fields =

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy function showAlertMsg() from $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js 
Note: Any patches/updates to showAlertMsg() in $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js must be manually ported to showAlertMsg() in $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
If you want to change the color of the error messages, add this line:
<source lang="javascript">alertmsg.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, remove the condition that prevents pop-up for Analyst Interface. 
Original code:
<source lang="javascript">
if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
</source>
Modified code:
<source lang="javascript">
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
</source>

== Step 4. Clear your Web browser cache ==
Clear your Web browser cache to test (no need to recycle USD)

== Modified showAlertMsg() ==

<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// Commented out the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
// Change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

= Part II. Alerts for data constraint and spell trigger validations =

== Step 1. Add endDetail() function to sitemods.js ==
Copy function endDetail() from $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js 
Note: Any patches/updates to endDetail() in $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js must be manually ported to endDetail() in $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 2. Modify endDetail() in sitemods.js ==

If you want to change the color of the error messages, find line
<source lang="javascript">e.style.display="block";</source>
and add the following under it:
<source lang="javascript">if (AlertMsg.substr(0,15) != "Save Successful") e.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, find line
<source lang="javascript">
if(typeof e=="object"&&e!=null){
</source>

and add the following code under it:

<source lang="javascript">
if (AlertMsg.substr(0,15) != "Save Successful") // prevent popup for success messages
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',3);
}

</source>

== Step 3. Clear your Web browser cache ==
Clear your Web browser cache to test (no need to recycle USD)

----
<div align='center'>To make corrections or additions to this article, select the ''edit'' tab above. 
To discuss or ask questions about this article, select the ''discussion'' tab above.</div>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-05-13T19:09:10Z

Svetazk:

__NOTOC__
Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I made modifications to a couple of java script functions to change this behavior. Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
There are two different scenarios that lead to displaying of an alert message. If you want your color change to affect both scenarios, you will have to customize two Java script functions. 
The 1st scenario is triggered when an unconditionally required field (i.e. defined as required at the schema level) is not filled in. The function showAlertMsg() is called in this case, and that’s the one we need to modify. This scenario is covered by Part I of this article. 
The 2nd scenario is when either data partition constraints or SPL triggers enforce data validation. In this case, endDetail() is the function that needs to be modified. The details are provided in Part II of the article 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 

= Part I. Alerts for unconditionally required fields =

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy function showAlertMsg() from $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js 
Note: Any patches/updates to showAlertMsg() in $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js must be manually ported to showAlertMsg() in $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
If you want to change the color of the error messages, add this line:
<source lang="javascript">alertmsg.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, remove the condition that prevents pop-up for Analyst Interface. 
Original code:
<source lang="javascript">
if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
</source>
Modified code:
<source lang="javascript">
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
</source>

== Step 4. Clear your Web browser cache ==
Clear your Web browser cache to test (no need to recycle USD)

== Modified showAlertMsg() ==

<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// Commented out the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
// Change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

= Part II. Alerts for data constraint and spell trigger validations =

== Step 1. Add showAlertMsg() function to sitemods.js ==
Copy function endDetail() from $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js 
Note: Any patches/updates to endDetail() in $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js must be manually ported to endDetail() in $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 2. Modify endDetail() in sitemods.js ==

If you want to change the color of the error messages, find line
<source lang="javascript">e.style.display="block";</source>
and add the following under it:
<source lang="javascript">if (AlertMsg.substr(0,15) != "Save Successful") e.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, find line
<source lang="javascript">
if(typeof e=="object"&&e!=null){
</source>

and add the following code under it:

<source lang="javascript">
if (AlertMsg.substr(0,15) != "Save Successful") // prevent popup for success messages
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',3);
}

</source>

== Step 3. Clear your Web browser cache ==
Clear your Web browser cache to test (no need to recycle USD)

----
<div align='center'>To make corrections or additions to this article, select the ''edit'' tab above. 
To discuss or ask questions about this article, select the ''discussion'' tab above.</div>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-05-13T18:50:13Z

Svetazk:

Changing Error Alert Color and adding Error Alert Pop-ups

2008-05-13T18:49:18Z

Svetazk:

Changing Error Alert Color and adding Error Alert Pop-ups

2008-05-13T18:45:29Z

Svetazk:

Changing Error Alert Color and adding Error Alert Pop-ups

2008-05-13T18:42:52Z

Svetazk:

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T20:03:16Z

Svetazk:

Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I modified a java script function to change this behavior. 
Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 
Here is what needs to be done.

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy function showAlertMsg() from $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js 
Note: Any patches/updates to showAlertMsg() in $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js must be manually ported to showAlertMsg() in $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
If you want to change the color of the error messages, add this line:
<source lang="javascript">alertmsg.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, remove the condition that prevents pop-up for Analyst Interface. 
Original code:
<source lang="javascript">
if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
</source>
Modified code:
<source lang="javascript">
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
</source>

== Step 4. Clear your Web browser cache ==
Clear your Web browser cache to test (no need to recycle USD)

== Modified showAlertMsg() ==

<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// Commented out the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
// Change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T20:00:51Z

Svetazk:

Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I modified a java script file to change this behavior. 
Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 
Here is what needs to be done.

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy function showAlertMsg() from $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js 
Note: Any patches/updates to showAlertMsg() in $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js must be manually ported to showAlertMsg() in $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
If you want to change the color of the error messages, add this line:
<source lang="javascript">alertmsg.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, remove the condition that prevents pop-up for Analyst Interface. 
Original code:
<source lang="javascript">
if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
</source>
Modified code:
<source lang="javascript">
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
</source>

== Step 4. Clear your Web browser cache ==
Clear your Web browser cache to test (no need to recycle USD)

== Modified showAlertMsg() ==

<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// Commented out the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
// Change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:58:20Z

Svetazk: /* Step 2. Add showAlertMsg() function to sitemods.js */

Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I modified a java script file to change this behavior. 
Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 
Here is what needs to be done.

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy function showAlertMsg() from $NX_ROOT\bopcfg\www\wwwroot\scripts\detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
If you want to change the color of the error messages, add this line:
<source lang="javascript">alertmsg.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, remove the condition that prevents pop-up for Analyst Interface. 
Original code:
<source lang="javascript">
if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
</source>
Modified code:
<source lang="javascript">
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
</source>

== Step 4. Clear your Web browser cache ==
Clear your Web browser cache to test (no need to recycle USD)

== Modified showAlertMsg() ==

<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// Commented out the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
// Change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:54:42Z

Svetazk:

Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I modified a java script file to change this behavior. 
Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 
Here is what needs to be done.

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy code for function showAlertMsg() from detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
If you want to change the color of the error messages, add this line:
<source lang="javascript">alertmsg.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, remove the condition that prevents pop-up for Analyst Interface. 
Original code:
<source lang="javascript">
if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
</source>
Modified code:
<source lang="javascript">
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
</source>

== Step 4. Clear your Web browser cache ==
Clear your Web browser cache to test (no need to recycle USD)

== Modified showAlertMsg() ==

<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// Commented out the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
// Change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:54:01Z

Svetazk:

Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I modified a java script file to change this behavior. 
Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 
Here is what needs to be done.

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy code for function showAlertMsg() from detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
If you want to change the color of the error messages, add this line:
<source lang="javascript">alertmsg.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, remove the condition that prevents pop-up for Analyst Interface. 
Original code:
<source lang="javascript">
if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
</source>

== Step 4. Clear your Web browser cache ==
Clear your Web browser cache to test (no need to recycle USD)

Modified code:
<source lang="javascript">
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
</source>

== Modified showAlertMsg() ==

<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// Commented out the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
// Change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:53:00Z

Svetazk:

Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I modified a java script file to change this behavior. 
Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 
Here is what needs to be done.

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy code for function showAlertMsg() from detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
If you want to change the color of the error messages, add this line:
<source lang="javascript">alertmsg.style.backgroundColor="red";</source>

== Step 4. Clear your Web browser cache ==
Clear your Web browser cache to test (no need to recycle USD)

If you want error messages to be displayed in a pop-up, remove the condition that prevents pop-up for Analyst Interface. 
Original code:
<source lang="javascript">
if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
</source>
Modified code:
<source lang="javascript">
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
</source>

== Modified showAlertMsg() ==

<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// Commented out the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
// Change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:51:39Z

Svetazk: /* Modified code for showAlertMsg() */

Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I modified a java script file to change this behavior. 
Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 
Here is what needs to be done.

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy code for function showAlertMsg() from detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
If you want to change the color of the error messages, add this line:
<source lang="javascript">alertmsg.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, remove the condition that prevents pop-up for Analyst Interface. 
Original code:
<source lang="javascript">
if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
</source>
Modified code:
<source lang="javascript">
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
</source>

== Modified showAlertMsg() ==

<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// Commented out the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
// Change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:51:10Z

Svetazk:

Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I modified a java script file to change this behavior. 
Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 
Here is what needs to be done.

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy code for function showAlertMsg() from detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
If you want to change the color of the error messages, add this line:
<source lang="javascript">alertmsg.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, remove the condition that prevents pop-up for Analyst Interface. 
Original code:
<source lang="javascript">
if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
</source>
Modified code:
<source lang="javascript">
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
</source>

== Modified code for showAlertMsg() ==

<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// Commented out the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
// Change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:49:29Z

Svetazk: /* Step 3. Modify showAlertMsg() in sitemods.js */

Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I modified a java script file to change this behavior. 
Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 
Here is what needs to be done.

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy code for function showAlertMsg() from detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
If you want to change the color of the error messages, add this line:
<source lang="javascript">alertmsg.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, remove the condition that prevents pop-up for Analyst Interface. 
Original code:
<source lang="javascript">
if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
</source>
Modified code:
<source lang="javascript">
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
</source>

<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// Commented out the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
// Change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:48:55Z

Svetazk: /* Step 3. Modify showAlertMsg() in sitemods.js */

Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I modified a java script file to change this behavior. 
Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 
Here is what needs to be done.

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy code for function showAlertMsg() from detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
If you want to change the color of the error messages, add this line:
<source lang="javascript">alertmsg.style.backgroundColor="red";</source>

If you want error messages to be displayed in a pop-up, remove the condition that prevents pop-up for Analyst Interface.
Original code:
<source lang="javascript">
if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
</source>
Modified code:
<source lang="javascript">
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
</source>

<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// Commented out the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
// Change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:44:14Z

Svetazk: /* Step 3. Modify showAlertMsg() in sitemods.js */

Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I modified a java script file to change this behavior. 
Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 
Here is what needs to be done.

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy code for function showAlertMsg() from detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
Change alert background color
<source lang="javascript">alertmsg.style.backgroundColor="red";</source>
<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// Commented out the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
// Change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:40:43Z

Svetazk: /* Step 3. Modify showAlertMsg() in sitemods.js */

Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I modified a java script file to change this behavior. 
Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 
Here is what needs to be done.

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy code for function showAlertMsg() from detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// Commented out the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
// Change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:36:52Z

Svetazk: /* Step 3. Modify showAlertMsg() in sitemods.js */

Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. 
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well. 
I modified a java script file to change this behavior. 
Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. 
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts. 
Here is what needs to be done.

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy code for function showAlertMsg() from detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==
<source lang="javascript">
function showAlertMsg(msg,popup_alertmsg)
{
e=document.getElementById("alertmsgText");
if(e!=null&&typeof msg=="string"&&msg.length>0)
{
if(typeof AlertMsg!="string")
AlertMsg="";
if(AlertMsg.length>0)
AlertMsg+=" "+msg;
else
AlertMsg=msg;
if(e.innerHTML!=AlertMsg)
{
e.innerHTML=AlertMsg;
// sk: I commented our the original condition that prevents popups for analyst interface, and replaced it with a simplified one.
//if ((ahdtop.cstUsingScreenReader||ahdtop.cfgUserType!="analyst")&&(typeof popup_alertmsg!="boolean"||popup_alertmsg))
if (typeof popup_alertmsg!="boolean"||popup_alertmsg)
{
var popupMsg=AlertMsg.replace(RegExp(" ","gi"),"\\n")
.replace(RegExp('\n',"g"),"\\n")
.replace(RegExp('"',"g"),'\\"');
window.setTimeout('alert("'+popupMsg+'")',5);
}
}
var alertmsg=document.getElementById("alertmsg");
if(alertmsg!=null&&alertmsg.style.display!="block")
{
alertmsg.style.display="block";
//sk: change color for the message within the page, in addition to the popup
alertmsg.style.backgroundColor="red";
adjScrollDivHeight();
}
}
}
</source>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:29:52Z

Svetazk:

Add Log Entry When a Property Value Changes on a Ticket

2008-04-04T19:21:22Z

Svetazk:

__NOTOC__
This article provides instructions for adding entries to the [[Activity Log]] when a property value changes on a ticket.
The steps involved are creating a new [[Activity Notification]], adding [[Site-Defined Trigger|Site-Defined Triggers]], and writing SPEL code for functions used by the the triggers.

== Step 1. Create the Activity Notification ==
Create a new Activity Notification, “Property Update” in USD Web Client.
It can be done by copying an existing Activity Notification, "Field Update" via File | Copy menu option.
Use the code "PROP" for the new activity. This code will be used in the SPEL code when specifying log type:
<source lang="javascript">alg.type = "PROP";
chgalg.type = "PROP";
issalg.type = "PROP";</source>

== Step 2. Create the spell file ==
Create a spel file prop_log.spl in $NX_ROOT\site\mods\majic folder.
Note: if you change the name of the spel file, change the name of the dummy function in the beginning of the spel file accordingly

<source lang="javascript">
// Dummy function, just so RCS Id is embedded in compiled spell file...
string prp_log_spl_RCSID() { return "@(#)$Id: prp_log.spl,v 1.00 2007/21/0 21:54:25 lauke01 Exp $"; }

// Request property
cr_prp::zlog_value_change(...)
{
string ME;
ME = "cr_prp::zlog_value_change";

string prp_persid, cr_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
cr_persid = argv[6];
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "cr", "dob_by_persid", 0, cr_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object alg;
send_wait( 0, top_object(), "call_attr", "alg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new alg for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}

alg = msg[0];
alg.type = "PROP"; // Code that identifies "Property Update" Activity Notification
alg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
alg.time_spent = "00:00:00";
alg.call_req_id = cr_persid;
alg.analyst = log_agt;
alg.system_time = (int)now();
alg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

// Change Order property
prp::zlog_value_change(...)
{
string ME;
ME = "prp::zlog_value_change";

string prp_persid, chg_id, chg_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
chg_id = argv[6];
chg_persid = format("chg:%s",chg_id);
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "chg", "dob_by_persid", 0, chg_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object chgalg;
send_wait( 0, top_object(), "call_attr", "chgalg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new chgalg for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

chgalg = msg[0];
chgalg.type = "PROP"; // Code that identifies "Property Update" Activity Notification
chgalg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
chgalg.time_spent = "00:00:00";
chgalg.change_id = chg_id;
chgalg.analyst = log_agt;
chgalg.system_time = (int)now();
chgalg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

// Issue property
iss_prp::zlog_value_change(...)
{
string ME;
ME = "iss_prp::zlog_value_change";

string prp_persid, iss_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
iss_persid = argv[6];
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "iss", "dob_by_persid", 0, iss_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object issalg;
send_wait( 0, top_object(), "call_attr", "issalg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new issalg for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}

issalg = msg[0];
issalg.type = "PROP"; // Code that identifies "Property Update" Activity Notification
issalg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
issalg.time_spent = "00:00:00";
issalg.issue_id = iss_persid;
issalg.analyst = log_agt;
issalg.system_time = (int)now();
issalg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

</source>

== Step 3. Add the triggers ==
Using Schema Designer tool in Web Screen Painter, add the following site-defined triggers:

Table cr_prp (request property):
<source lang="text">POST_CI zlog_value_change(persistent_id,owning_cr,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

Table iss_prp (issue property):
<source lang="text">POST_CI zlog_value_change(persistent_id,owning_iss,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

Table prpr (change property):
<source lang="text">POST_CI zlog_value_change(persistent_id,object_id,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

== Step 4. Publish the Schema changes ==
The methods used to publish schema changes vary based on the Service Desk release.

For r11.x releases, follow these steps:
#Save your Schema changes
#Stop the Service Desk service
#Run [[pdm_publish]] from a command line
#Start the Service Desk service

For older release recycle the Service Desk service.

----
<div align='center'>To make corrections or additions to this article, select the ''edit'' tab above. 
To discuss or ask questions about this article, select the ''discussion'' tab above.</div>

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:17:18Z

Svetazk:

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:15:51Z

Svetazk:

Changing Error Alert Color and adding Error Alert Pop-ups
Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created.
We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well.
I modified a java script file to change this behavior.
Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to.
Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts.
Here is what needs to be done.

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy code for function showAlertMsg() from detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:14:23Z

Svetazk: /* Step 1. Create sitemods.js */

Changing Error Alert Color and adding Error Alert Pop-ups
Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well.
I modified a java script file to change this behavior. Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts.
Here is what needs to be done.

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

== Step 2. Add showAlertMsg() function to sitemods.js ==
Copy code for function showAlertMsg() from detail_form.js and paste it into $NX_ROOT\site\mods\www\wwwroot\scripts\sitemods.js

== Step 3. Modify showAlertMsg() in sitemods.js ==

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:10:34Z

Svetazk:

Changing Error Alert Color and adding Error Alert Pop-ups
Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well.
I modified a java script file to change this behavior. Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts.
Here is what needs to be done.

== Step 1. Create sitemods.js ==
If you don’t have sitemods.js in $NX_ROOT\site\mods\www\wwwroot\scripts, copy it from $NX_ROOT\bopcfg\www\wwwroot\scripts.

Changing Error Alert Color and adding Error Alert Pop-ups

2008-04-04T19:06:39Z

Svetazk: New page: Changing Error Alert Color and adding Error Alert Pop-ups Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successf...

Changing Error Alert Color and adding Error Alert Pop-ups
Our analysts complained that they were loosing tickets because USD displayed error messages in the same color, yellow, as successful save messages. The analysts would miss the error message and the click “Close Window” button thinking that the ticket was created. We had an issue open with CA, and their advice was to change BACKGROUND-COLOR for alertmsg class in styles_ahd.css. Of course, that would not do us any good, because it would apply to successful save messages as well.
I modified a java script file to change this behavior. Originally I did two things: made the color of the error messages red, and in addition to that, displayed the same error message in a pop-up. In the end we decided that red was too much, since we now have the pop-up. But at least we know how to change the color, if we want to. Please note that this change will affect all detail forms in all interfaces in USD, not only tickets for analysts.
Here is what needs to be done.

Sample Customizations

2008-04-04T19:04:01Z

Svetazk:

[[Category:Customization]]
Customizations are regarded as changes to the system that are not supportable by CA.
== List of Customizations ==

*[[Add Checkbox, Date, Drop-down, Lookup, Readonly and Text Fields to Properties]]
*[[Add Custom Activity Log Action Macro]]
*[[Add Log Entry for Updates to Custom Fields]]
*[[Add Log Entry When a Property Value Changes on a Ticket]]
*[[Add Posted By to Announcements Page]]
*[[Auto-fill Fields Left Blank]]
*[[Automatically Attach an Asset/CI to a Change Order or Issue]]
*[[Automatically Remove Attached Events]]
*[[Automatically Set Assignee to Closing Analyst]]
*[[Automatically Set System Generated Activities to Internal]]
*[[Changing Error Alert Color and adding Error Alert Pop-ups]]
*[[Changing Requests to Incidents]]
*[[Conditional Display of Drop-Down Content]]
*[[Conditionally Attach an Event]]
*[[Configure Java Client to Use Web Client for Uploading Attachments]]
*[[Control the Request Areas Displayed to the End Users]]
*[[Count Ticket Reopens]]
*[[Increasing Default Field Size]]
*[[List Tickets ORDER BY Group]]
*[[Make a Field Conditionally Required]]
*[[Only Assignee can Close]]
*[[Prevent Close of Requests, Incidents, and Problems if Change Order is Active]]
*[[Prevent Update to Past Activities]]
*[[Priority and Impact Default to Empty]]
*[[Remove SLA Violation from Employee View]]
*[[Separate Prefixes for Requests, Incidents, and Problems]]
*[[Set Defaults on Manual Notify]]
*[[Simplified Child Creation]]

----
<div align='center'>To make corrections or additions to this article, select the ''edit'' tab above. 
To discuss or ask questions about this article, select the ''discussion'' tab above.</div>

Add Log Entry When a Property Value Changes on a Ticket

2008-03-28T20:32:03Z

Svetazk:

This article provides instructions for adding entries to the [[Activity Log]] when a property value changes on a ticket.
The steps involved are creating a new [[Activity Notification]], adding [[Site-Defined Trigger|Site-Defined Triggers]], and writing SPEL code for functions used by the the triggers.

== Step 1. Create the Activity Notification ==
Create a new Activity Notification, “Property Update” in USD Web Client.
It can be done by copying an existing Activity Notification, "Field Update" via File | Copy menu option.
Use the code "PROP" for the new activity. This code will be used in the SPEL code when specifying log type:
<source lang="text">alg.type = "PROP";
chgalg.type = "PROP";
issalg.type = "PROP";</source>

== Step 2. Create the spell file ==
Create a spel file prop_log.spl in $NX_ROOT\site\mods\majic folder.
Note: if you change the name of the spel file, change the name of the dummy function in the beginning of the spel file accordingly

<source lang="javascript">
// Dummy function, just so RCS Id is embedded in compiled spell file...
string prp_log_spl_RCSID() { return "@(#)$Id: prp_log.spl,v 1.00 2007/21/0 21:54:25 lauke01 Exp $"; }

// Request property
cr_prp::zlog_value_change(...)
{
string ME;
ME = "cr_prp::zlog_value_change";

string prp_persid, cr_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
cr_persid = argv[6];
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "cr", "dob_by_persid", 0, cr_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object alg;
send_wait( 0, top_object(), "call_attr", "alg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new alg for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}

alg = msg[0];
alg.type = "PROP"; // Code that identifies "Property Update" Activity Notification
alg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
alg.time_spent = "00:00:00";
alg.call_req_id = cr_persid;
alg.analyst = log_agt;
alg.system_time = (int)now();
alg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

// Change Order property
prp::zlog_value_change(...)
{
string ME;
ME = "prp::zlog_value_change";

string prp_persid, chg_id, chg_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
chg_id = argv[6];
chg_persid = format("chg:%s",chg_id);
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "chg", "dob_by_persid", 0, chg_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object chgalg;
send_wait( 0, top_object(), "call_attr", "chgalg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new chgalg for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

chgalg = msg[0];
chgalg.type = "PROP"; // Code that identifies "Property Update" Activity Notification
chgalg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
chgalg.time_spent = "00:00:00";
chgalg.change_id = chg_id;
chgalg.analyst = log_agt;
chgalg.system_time = (int)now();
chgalg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

// Issue property
iss_prp::zlog_value_change(...)
{
string ME;
ME = "iss_prp::zlog_value_change";

string prp_persid, iss_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
iss_persid = argv[6];
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "iss", "dob_by_persid", 0, iss_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object issalg;
send_wait( 0, top_object(), "call_attr", "issalg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new issalg for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}

issalg = msg[0];
issalg.type = "PROP"; // Code that identifies "Property Update" Activity Notification
issalg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
issalg.time_spent = "00:00:00";
issalg.issue_id = iss_persid;
issalg.analyst = log_agt;
issalg.system_time = (int)now();
issalg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

</source>

== Step 3. Add the triggers ==
Using Schema Designer tool in Web Screen Painter, add the following site-defined triggers:

Table cr_prp (request property):
<source lang="text">POST_CI zlog_value_change(persistent_id,owning_cr,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

Table iss_prp (issue property):
<source lang="text">POST_CI zlog_value_change(persistent_id,owning_iss,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

Table prpr (change property):
<source lang="text">POST_CI zlog_value_change(persistent_id,object_id,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

== Step 4. Publish the Schema changes ==

Add Log Entry When a Property Value Changes on a Ticket

2008-03-28T20:31:15Z

Svetazk: /* Step 2. Create the spell file */

This article provides instructions for adding entries to the [[Activity Log]] when a property value changes on a ticket.
The steps involved are creating a new [[Activity Notification]], adding [[Site-Defined Trigger|Site-Defined Triggers]], and writing SPEL code for functions used by the the triggers.

== Step 1. Create the Activity Notification ==
Create a new Activity Notification, “Property Update” in USD Web Client.
It can be done by copying an existing Activity Notification, "Field Update" via File | Copy menu option.
Use the code "PROP" for the new activity. This code will be used in the SPEL code when specifying log type:
<source lang="text">alg.type = "PROP";
chgalg.type = "PROP";
issalg.type = "PROP";</source>

== Step 2. Create the spell file ==
Create a spel file prop_log.spl in $NX_ROOT\site\mods\majic folder.
Note: if you change the name of the spel file, change the name of the dummy function in the beginning of the spel file accordingly

<source lang="javascript">
// Dummy function, just so RCS Id is embedded in compiled spell file...
string prp_log_spl_RCSID() { return "@(#)$Id: prp_log.spl,v 1.00 2007/21/0 21:54:25 lauke01 Exp $"; }

// Request property
cr_prp::zlog_value_change(...)
{
string ME;
ME = "cr_prp::zlog_value_change";

string prp_persid, cr_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
cr_persid = argv[6];
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "cr", "dob_by_persid", 0, cr_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object alg;
send_wait( 0, top_object(), "call_attr", "alg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new alg for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}

alg = msg[0];
alg.type = "PROP"; // Code that identifies "Property Update" Activity Notification
alg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
alg.time_spent = "00:00:00";
alg.call_req_id = cr_persid;
alg.analyst = log_agt;
alg.system_time = (int)now();
alg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

// Change Order property
prp::zlog_value_change(...)
{
string ME;
ME = "prp::zlog_value_change";

string prp_persid, chg_id, chg_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
chg_id = argv[6];
chg_persid = format("chg:%s",chg_id);
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "chg", "dob_by_persid", 0, chg_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object chgalg;
send_wait( 0, top_object(), "call_attr", "chgalg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new chgalg for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

chgalg = msg[0];
chgalg.type = "PROP";
chgalg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
chgalg.time_spent = "00:00:00";
chgalg.change_id = chg_id;
chgalg.analyst = log_agt;
chgalg.system_time = (int)now();
chgalg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

// Issue property
iss_prp::zlog_value_change(...)
{
string ME;
ME = "iss_prp::zlog_value_change";

string prp_persid, iss_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
iss_persid = argv[6];
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "iss", "dob_by_persid", 0, iss_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object issalg;
send_wait( 0, top_object(), "call_attr", "issalg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new issalg for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}

issalg = msg[0];
issalg.type = "PROP";
issalg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
issalg.time_spent = "00:00:00";
issalg.issue_id = iss_persid;
issalg.analyst = log_agt;
issalg.system_time = (int)now();
issalg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

</source>

== Step 3. Add the triggers ==
Using Schema Designer tool in Web Screen Painter, add the following site-defined triggers:

Table cr_prp (request property):
<source lang="text">POST_CI zlog_value_change(persistent_id,owning_cr,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

Table iss_prp (issue property):
<source lang="text">POST_CI zlog_value_change(persistent_id,owning_iss,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

Table prpr (change property):
<source lang="text">POST_CI zlog_value_change(persistent_id,object_id,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

== Step 4. Publish the Schema changes ==

Add Log Entry When a Property Value Changes on a Ticket

2008-03-28T20:29:49Z

Svetazk: /* Step 1. Create the Activity Notification */

This article provides instructions for adding entries to the [[Activity Log]] when a property value changes on a ticket.
The steps involved are creating a new [[Activity Notification]], adding [[Site-Defined Trigger|Site-Defined Triggers]], and writing SPEL code for functions used by the the triggers.

== Step 1. Create the Activity Notification ==
Create a new Activity Notification, “Property Update” in USD Web Client.
It can be done by copying an existing Activity Notification, "Field Update" via File | Copy menu option.
Use the code "PROP" for the new activity. This code will be used in the SPEL code when specifying log type:
<source lang="text">alg.type = "PROP";
chgalg.type = "PROP";
issalg.type = "PROP";</source>

== Step 2. Create the spell file ==
Create a spel file prop_log.spl in $NX_ROOT\site\mods\majic folder.
Note: if you change the name of the spel file, change the name of the dummy function in the beginning of the spel file accordingly

<source lang="javascript">
// Dummy function, just so RCS Id is embedded in compiled spell file...
string prp_log_spl_RCSID() { return "@(#)$Id: prp_log.spl,v 1.00 2007/21/0 21:54:25 lauke01 Exp $"; }

// Request property
cr_prp::zlog_value_change(...)
{
string ME;
ME = "cr_prp::zlog_value_change";

string prp_persid, cr_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
cr_persid = argv[6];
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "cr", "dob_by_persid", 0, cr_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object alg;
send_wait( 0, top_object(), "call_attr", "alg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new alg for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}

alg = msg[0];
alg.type = "PROP";
alg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
alg.time_spent = "00:00:00";
alg.call_req_id = cr_persid;
alg.analyst = log_agt;
alg.system_time = (int)now();
alg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

// Change Order property
prp::zlog_value_change(...)
{
string ME;
ME = "prp::zlog_value_change";

string prp_persid, chg_id, chg_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
chg_id = argv[6];
chg_persid = format("chg:%s",chg_id);
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "chg", "dob_by_persid", 0, chg_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object chgalg;
send_wait( 0, top_object(), "call_attr", "chgalg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new chgalg for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

chgalg = msg[0];
chgalg.type = "PROP";
chgalg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
chgalg.time_spent = "00:00:00";
chgalg.change_id = chg_id;
chgalg.analyst = log_agt;
chgalg.system_time = (int)now();
chgalg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

// Issue property
iss_prp::zlog_value_change(...)
{
string ME;
ME = "iss_prp::zlog_value_change";

string prp_persid, iss_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
iss_persid = argv[6];
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "iss", "dob_by_persid", 0, iss_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object issalg;
send_wait( 0, top_object(), "call_attr", "issalg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new issalg for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}

issalg = msg[0];
issalg.type = "PROP";
issalg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
issalg.time_spent = "00:00:00";
issalg.issue_id = iss_persid;
issalg.analyst = log_agt;
issalg.system_time = (int)now();
issalg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

</source>

== Step 3. Add the triggers ==
Using Schema Designer tool in Web Screen Painter, add the following site-defined triggers:

Table cr_prp (request property):
<source lang="text">POST_CI zlog_value_change(persistent_id,owning_cr,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

Table iss_prp (issue property):
<source lang="text">POST_CI zlog_value_change(persistent_id,owning_iss,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

Table prpr (change property):
<source lang="text">POST_CI zlog_value_change(persistent_id,object_id,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

== Step 4. Publish the Schema changes ==

Add Log Entry When a Property Value Changes on a Ticket

2008-03-28T20:23:17Z

Svetazk: /* Step 2. Create the spell file */

This article provides instructions for adding entries to the [[Activity Log]] when a property value changes on a ticket.
The steps involved are creating a new [[Activity Notification]], adding [[Site-Defined Trigger|Site-Defined Triggers]], and writing SPEL code for functions used by the the triggers.

== Step 1. Create the Activity Notification ==
Create a new Activity Notification, “Property Update” in USD Web Client.
It can be done by copying an existing Activity Notification, "Field Update" via File | Copy menu option.
Use the code "PROP" for the new activity.

== Step 2. Create the spell file ==
Create a spel file prop_log.spl in $NX_ROOT\site\mods\majic folder.
Note: if you change the name of the spel file, change the name of the dummy function in the beginning of the spel file accordingly

<source lang="javascript">
// Dummy function, just so RCS Id is embedded in compiled spell file...
string prp_log_spl_RCSID() { return "@(#)$Id: prp_log.spl,v 1.00 2007/21/0 21:54:25 lauke01 Exp $"; }

// Request property
cr_prp::zlog_value_change(...)
{
string ME;
ME = "cr_prp::zlog_value_change";

string prp_persid, cr_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
cr_persid = argv[6];
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "cr", "dob_by_persid", 0, cr_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object alg;
send_wait( 0, top_object(), "call_attr", "alg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new alg for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}

alg = msg[0];
alg.type = "PROP";
alg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
alg.time_spent = "00:00:00";
alg.call_req_id = cr_persid;
alg.analyst = log_agt;
alg.system_time = (int)now();
alg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

// Change Order property
prp::zlog_value_change(...)
{
string ME;
ME = "prp::zlog_value_change";

string prp_persid, chg_id, chg_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
chg_id = argv[6];
chg_persid = format("chg:%s",chg_id);
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "chg", "dob_by_persid", 0, chg_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object chgalg;
send_wait( 0, top_object(), "call_attr", "chgalg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new chgalg for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

chgalg = msg[0];
chgalg.type = "PROP";
chgalg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
chgalg.time_spent = "00:00:00";
chgalg.change_id = chg_id;
chgalg.analyst = log_agt;
chgalg.system_time = (int)now();
chgalg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

// Issue property
iss_prp::zlog_value_change(...)
{
string ME;
ME = "iss_prp::zlog_value_change";

string prp_persid, iss_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
iss_persid = argv[6];
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "iss", "dob_by_persid", 0, iss_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object issalg;
send_wait( 0, top_object(), "call_attr", "issalg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new issalg for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}

issalg = msg[0];
issalg.type = "PROP";
issalg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
issalg.time_spent = "00:00:00";
issalg.issue_id = iss_persid;
issalg.analyst = log_agt;
issalg.system_time = (int)now();
issalg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

</source>

== Step 3. Add the triggers ==
Using Schema Designer tool in Web Screen Painter, add the following site-defined triggers:

Table cr_prp (request property):
<source lang="text">POST_CI zlog_value_change(persistent_id,owning_cr,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

Table iss_prp (issue property):
<source lang="text">POST_CI zlog_value_change(persistent_id,owning_iss,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

Table prpr (change property):
<source lang="text">POST_CI zlog_value_change(persistent_id,object_id,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

== Step 4. Publish the Schema changes ==

Add Log Entry When a Property Value Changes on a Ticket

2008-03-28T20:19:21Z

Svetazk: /* Step 2. Create the spell file */

This article provides instructions for adding entries to the [[Activity Log]] when a property value changes on a ticket.
The steps involved are creating a new [[Activity Notification]], adding [[Site-Defined Trigger|Site-Defined Triggers]], and writing SPEL code for functions used by the the triggers.

== Step 1. Create the Activity Notification ==
Create a new Activity Notification, “Property Update” in USD Web Client.
It can be done by copying an existing Activity Notification, "Field Update" via File | Copy menu option.
Use the code "PROP" for the new activity.

== Step 2. Write the spell code ==
Create a spel file prop_log.spl in $NX_ROOT\site\mods\majic folder.
Note: if you change the name of the spel file, change the name of the dummy function in the beginning of the spel file accordingly

<source lang="javascript">
// Dummy function, just so RCS Id is embedded in compiled spell file...
string prp_log_spl_RCSID() { return "@(#)$Id: prp_log.spl,v 1.00 2007/21/0 21:54:25 lauke01 Exp $"; }

// Trigger for request property: (cr_prp): POST_CI zlog_value_change(persistent_id,owning_cr,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );
cr_prp::zlog_value_change(...)
{
string ME;
ME = "cr_prp::zlog_value_change";

string prp_persid, cr_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
cr_persid = argv[6];
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "cr", "dob_by_persid", 0, cr_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object alg;
send_wait( 0, top_object(), "call_attr", "alg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new alg for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
return;
}

alg = msg[0];
alg.type = "PROP";
alg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
alg.time_spent = "00:00:00";
alg.call_req_id = cr_persid;
alg.analyst = log_agt;
alg.system_time = (int)now();
alg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for cr=%s property=%s: %s", ME, cr_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

// Trigger for Change Order property: (prp): POST_CI zlog_value_change(persistent_id,object_id,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );

prp::zlog_value_change(...)
{
string ME;
ME = "prp::zlog_value_change";

string prp_persid, chg_id, chg_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
chg_id = argv[6];
chg_persid = format("chg:%s",chg_id);
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

// wrong syntax below
//send_wait(0, top_object(), "call_attr", "chg", "dob_by_id", 0, chg_id);

send_wait(0, top_object(), "call_attr", "chg", "dob_by_persid", 0, chg_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object chgalg;
send_wait( 0, top_object(), "call_attr", "chgalg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new chgalg for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
return;
}

chgalg = msg[0];
chgalg.type = "PROP";
chgalg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
chgalg.time_spent = "00:00:00";
chgalg.change_id = chg_id;
chgalg.analyst = log_agt;
chgalg.system_time = (int)now();
chgalg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for chg=%s property=%s: %s", ME, chg_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

// Trigger for issue property: (iss_prp): POST_CI zlog_value_change(persistent_id,owning_iss,value,label,sequence) FILTER(EVENT("UPDATE") && value {} );

iss_prp::zlog_value_change(...)
{
string ME;
ME = "iss_prp::zlog_value_change";

string prp_persid, iss_persid, old_val, new_val, zzlabel, zzsequence;

prp_persid = argv[3];
iss_persid = argv[6];
old_val = argv[8];
new_val = argv[9];
zzlabel = argv[12];
zzsequence = argv[15];

send_wait(0, top_object(), "call_attr", "iss", "dob_by_persid", 0, iss_persid);
if (msg_error()) {
logf (ERROR, "%s: could not get dob for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
object dob;
dob = msg[0];

send_wait(0, top_object(), "get_co_group");
if (msg_error()) {
logf (ERROR, "%s: could not get group leader for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
object group_leader;
group_leader = msg[0];

send_wait(0, group_leader, "checkout", dob);
if (msg_error() && msg[0] != "NO") {
logf(ERROR, "%s: checkout failed for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}

send_wait(0, dob, "call_attr", "log_agent", "get_val");
if (msg_error()) {
logf (ERROR, "%s: could not get log agent for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}
uuid log_agt;
log_agt = msg[0];

object issalg;
send_wait( 0, top_object(), "call_attr", "issalg", "get_new_dob", NULL, NULL, group_leader);
if (msg_error()) {
logf (ERROR, "%s: could not get new issalg for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
return;
}

issalg = msg[0];
issalg.type = "PROP";
issalg.description = format("FIELD='property' LABEL='%s' SEQUENCE='%s' OLD='%s' NEW='%s'", zzlabel,zzsequence,old_val,new_val);
issalg.time_spent = "00:00:00";
issalg.issue_id = iss_persid;
issalg.analyst = log_agt;
issalg.system_time = (int)now();
issalg.last_mod_dt = (int)now();

send_wait(0, group_leader, "checkin");
if (msg_error()) {
logf(ERROR, "%s: checkin failed for iss=%s property=%s: %s", ME, iss_persid, zzsequence, msg[0]);
send_wait(0, group_leader, "uncheck");
return;
}
}

</source>

== Step 3. Add the triggers ==
Using Schema Designer tool in Web Screen Painter, add the following site-defined triggers:

Table cr_prp (request property):
<source lang="text">POST_CI zlog_value_change(persistent_id,owning_cr,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

Table iss_prp (issue property):
<source lang="text">POST_CI zlog_value_change(persistent_id,owning_iss,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

Table prpr (change property):
<source lang="text">POST_CI zlog_value_change(persistent_id,object_id,value,label,sequence) 1050 FILTER(EVENT("UPDATE") && value {} );</source>

== Step 4. Publish the Schema changes ==

Add Log Entry When a Property Value Changes on a Ticket

2008-03-28T20:14:07Z

Svetazk:

Add Log Entry When a Property Value Changes on a Ticket

2008-03-28T20:13:27Z

Svetazk: /* Step 2. Write the spell code */

Add Log Entry When a Property Value Changes on a Ticket

2008-03-28T20:11:21Z

Svetazk: /* Step 3. Add the triggers */

Add Log Entry When a Property Value Changes on a Ticket

2008-03-28T20:10:38Z

Svetazk: /* Step 3. Add the triggers */

Add Log Entry When a Property Value Changes on a Ticket

2008-03-28T20:09:32Z

Svetazk:

Add Log Entry When a Property Value Changes on a Ticket

2008-03-28T20:05:08Z

Svetazk: /* Step 3. Add the triggers */

Add Log Entry When a Property Value Changes on a Ticket

2008-03-28T20:03:36Z

Svetazk: /* Step 3. Add the triggers */

Add Log Entry When a Property Value Changes on a Ticket

2008-03-28T19:56:11Z

Svetazk:

Add Log Entry When a Property Value Changes on a Ticket

2008-03-27T15:35:45Z

Svetazk: