Refresh Customer Info Before Saving the Ticket - Revision history

Gityerfix: Reverted edits by Agegeleruvy (Talk); changed back to last version by Gityerfix

2010-11-30T05:24:06Z

Reverted edits by Agegeleruvy (Talk); changed back to last version by Gityerfix

Show changes

Agegeleruvy at 03:04, 24 November 2010

2010-11-24T03:04:10Z

Show changes

Gityerfix at 18:40, 8 August 2008

2008-08-08T18:40:08Z

Gityerfix: /* View the Complete Code */

2008-08-08T18:39:06Z

‎View the Complete Code

Gityerfix at 18:35, 8 August 2008

2008-08-08T18:35:32Z

Gityerfix: Refresh customer info before saving the ticket moved to Refresh Customer Info Before Saving the Ticket: Renamed for consistency.

2008-08-08T18:33:23Z

Refresh customer info before saving the ticket moved to Refresh Customer Info Before Saving the Ticket: Renamed for consistency.

Svetazk at 17:48, 8 August 2008

2008-08-08T17:48:14Z

Svetazk at 17:34, 8 August 2008

2008-08-08T17:34:01Z

Svetazk at 17:33, 8 August 2008

2008-08-08T17:33:16Z

Svetazk at 17:32, 8 August 2008

2008-08-08T17:32:22Z

@@ Line 36: / Line 36: @@
 </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 ==

@@ Line 39: / Line 39: @@
 == View the Complete Code ==
-Coming soon
+[[Media:customer_refresh.zip|Click Here]] to download the complete code.
 == Customization Steps ==

@@ Line 1: / Line 1: @@
 __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.

@@ Line 27: / Line 27: @@
 </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 ==

@@ Line 34: / Line 34: @@
 <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">
+</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:

← Older revision	Revision as of 18:33, 8 August 2008
(No difference)

@@ Line 82: / Line 82: @@
       zcustomerChanged(form_name, base_name, lname, fname, mname, cntID, caller_type);
+    }
-</source">
+</source>
 === Step 4. Add the following java script code before function backfill_cnt_event() ===
 <source lang="javascript">

@@ Line 17: / Line 17: @@
 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:
-. Service contract check (upd_workframe("GET_SVC_CONTRACT"..) - out of the box behavior)
+<BR>1. Service contract check (upd_workframe("GET_SVC_CONTRACT"..) - out of the box behavior)
-. Location lookup
+<BR>2. Location lookup
-. Phone lookup
+<BR>3. Phone lookup
-So I had to “chain” them: location callback function triggers phone callback, and phone callback triggers Service contract check.
+<BR>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 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
-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.
+== Customization Steps ==
+=== Step 1. Add customer location and phone ===
-Here are the customization steps.
+Note that Ids are important here - they will be used by the callback functions to refresh the fields.
+<source lang="javascript">
-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>
+<source lang="javascript">
-Step 2. Modify function backfill_cnt_event() as follows.
+=== 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 )
@@ Line 70: / Line 74: @@
+    }
+}
-Step 3. Add the following code at the end of backfill_cnt_event():
+=== 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);
+    }
+</source">
-Step 4. Add the following java script code before function backfill_cnt_event().
+=== Step 4. Add the following java script code before function backfill_cnt_event() ===
 var zcurrCustID="";
@@ Line 148: / Line 155: @@
+   }
+}