Here are my notes from when we added SLM Status of Incidents to the Overview Console.
o On SHR:ARDBC_OverviewConsoleTemplate add a new field with the same properties as the SLM Status field on the HPD:Help Desk Form. "zhub_SLM Status" (Public permissions) o On SHR:ARDBC_OverviewConsole add a new field with the same properties as the SLM Status field on the HPD:Help Desk Form and the same ID as the SHR:ARDBC_OverviewConsoleTemplate field added above. "zhub_SLM Status" (Public permissions) o On SHR:Overview Console create a new column for the new field created above "zhub_col_SLM Status" (Public permissions) o Create an entry on the SHR:ARDBCfields form to map the Field ID of the SLM Status field on the HPD:Help Desk form to the field ID of the new zhub_SLM Status on the vendor form. Set the FormGUID of the entry to "MAINHELPDESK". o Kill arpluggin for it to restart. Maybe you can compare what you did to that. Ken. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Steve Kallestad Sent: Wednesday, June 12, 2013 11:49 PM To: [email protected] Subject: Re: Adding status reason column to overview console ** I just took a peek at a 7.6.4 environment and it's already mapped there as well. Look for multiple records in SHR:ARDBCFields where MAINHELPDESK/1000000150 is mapped and slim it down to the one provided out of the box. Then try adding in the field "ConsolidatedStatusReason" into your table and see if it's not populated for you already. If it's still not populating a server restart couldn't hurt and you definitely need to flush the MT cache. In the thick client clearing the arf/arv files is always good too. Sounds to me like you've done everything right except maybe running into an already-mapped field. On Wed, Jun 12, 2013 at 7:48 PM, Robert Gajic <[email protected]<mailto:[email protected]>> wrote: ** Yeah I have taken a sql log and it is being queried (and no errors) T2067.C1,C1000000000,C7,C1000000164,C179,C230000009,C301626500,C1000000217,C1000000218,C1000000163,C3,C1000000161,C1000000150 FROM T2067 WHERE (((T2067.C230000009 = 'MAINCHANGE') AND ((T2067.C1000000427 = 'SGP000000000391') OR (T2067.C1000000427 = 'SGP000000000017') OR (T2067.C1000000427 = 'SGP000000000993') OR (T2067.C1000000427 = 'SGP000000000029') OR (T2067.C1000000427 = 'SGP000000000186') OR (T2067.C1000000427 = 'SGP000000000026') OR (T2067.C1000000427 = 'SGP000000000025')) AND (T2067.C1000000001 = 'Australian Taxation Office') AND ((T2067.C7 = 1) OR (T2067.C7 = 2) OR (T2067.C7 = 3) OR (T2067.C7 = 4) OR (T2067.C7 = 5) OR (T2067.C7 = 6) OR (T2067.C7 = 7) OR (T2067.C7 = 8) OR (T2067.C7 = 9))) OR ((T2067.C230000009 = 'MAINHELPDESK') AND ((T2067.C1000000079 = 'SGP000000000391') OR (T2067.C1000000079 = 'SGP000000000017') OR (T2067.C1000000079 = 'SGP000000000993') OR (T2067.C1000000079 = 'SGP000000000029') OR (T2067.C1000000079 = 'SGP000000000186') OR (T2067.C1000000079 = 'SGP000000000026') OR (T2067.C1000000079 = 'SGP000000000025')) AND (T2067.C1000000001 = ................ From: Robert Gajic Sent: Thursday, 13 June 2013 10:37 AM To: '[email protected]<mailto:[email protected]>' Subject: Adding status reason column to overview console Hi Guys, I have read articles in developer communities etc on how to do this but am still having trouble. This will be long winded but hopefully I can get some help on how to add status reason to overview console (incident to start with). We are running with 7.6.03 (no patch) sql database on windows. 1. Ensure that status reason exists on template form ( I went with Help Desk Status_Reason with field ID of 1000000150 2. Add if not there, a record on the ARDBC Fields form for the mapping 3. Added column for status reason (I added both consolidated status reason and status reason as I was experimenting with both and made sure permissions were given 4. Killed plugin and eventually restarted arservice but nothing turns up under status reason. Any thoughts would be very much appreciated! Robert Gajic ESMC Remedy Developer Lockheed Martin Australia Level 2, 53 Wentworth Avenue Kingston ACT 2604 Australia P.O. Box 6003 Kingston ACT 2604 Australia E-mail: [email protected]<mailto:[email protected]> ________________________________ This message is intended only for the use of the intended recipient(s) If you are not an intended recipient, you are hereby notified that any use, dissemination, disclosure or copying of this communication is strictly prohibited. If you have received this communication in error please destroy all copies of this message and its attachments and notify the sender immediately _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ ****************************************************************************** This email and any files transmitted with it are confidential and intended solely for the addressee. If you have received this email in error please notify the system manager. Subject to local law, communications (including traffic data) with Hubbell may be monitored by our systems [or a third party's systems on our behalf] for the purposes of security and the assessment of internal compliance with Hubbell policies. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
