Anne,

I've included a snippet I stored on my computer. I believe I took it from a
KB article but I can not find that anymore:
------------------
*Adding a field to the overview console table in ITSM7*

The Overview Console Table is populated using a plugin. The plugin returns
records from forms that are defined the SHR:ARDBC_OverviewConsoleTemplate
form. The Plugin will look at the Form Guid in this form, and search that
form. For example you will see the following 8 records in the
SHR:ARDBC_OverviewConsoleTemplate:


 FORM NAME                 FORM GUID
----------------------------------------------
TMS:Task                  TMSTASK
HPD:Helpdesk              MAINHELPDESK
PBM:Solution Database     MAINKNOWLEDGEDATABAE
PBM:Known Error           MAINKNOWNERROR
PBM:Problem Investigation MAIONPROBLEM
CHG:Infrastructure Change MAINCHANGE
AST:PurchaseRequisition   ASTPUREREQUISITION
AST:CI Unavialabilty      ASTCIUNAVIALBLITY

If you are logged into the WUT as appadmin for example, the plugin will
search the above forms to find the records that are assigned to appadmin and
populate the OverviewConsole similar to how the SHR:Consolidated list
worked.

But how are the fields mapped from the forms to the OverviewConsole , this
is done via the SHR:ARDBC fields form. Here you will see mapping for field
from the backend forms to the Vendor form hence populating the form. Form
example if you would like have more information in the Overview console, for
instance the First Name*+ field from the HPD:Helpdesk form.

The database id for this field is 1000000019 (in HPD:Helpdesk). This field
already exists in the forms:

   - SHR:ARDBC_OverviewConsoleTemplate
   - SHR:ARDBC_OverviewConsole

so we do not need to create it again ( you can map any fieldID the database
id do not have to match, as long the database length is sufficient). But for
this example, the database ID are matching.

To create a mapping for the HPD:Helpdesk form. Open the SHR:ARDBCFields form
in new mode and use the following values:

FieldID:         1000000019
FormGUID:        MAINHELPDESK
Vendor Field ID: 1000000019
Submitter:       ARSystem

Open the SHR:OverviewConsole in the Admin Tool.

   - open the table z2TH_ConsolidateTable1 properties
   - on tab Table/Tree Property
   - Look for First Name under Fields on Form and click Add
   - Double click on the column First Name and add public Permissions
   - Save and close the form.

Restart the plugin or ARServer. Open the OverviewConsole and there should
now be data for the First Name from the Incidents form.
-- 
Met vriendelijke groet / Kind regards
Michiel Beijen
______________________________________________________
MANSOLUTIONS
Energieweg 60-62
3771 NA Barneveld
The Netherlands
Tel. +31-(0)612968592
Mail [EMAIL PROTECTED]
Internet http://bsm.mansolutions.nl

On Tue, Feb 26, 2008 at 10:32 AM, Jiri Pospisil <
[EMAIL PROTECTED]> wrote:
> **
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Please Read The Disclaimer At The Bottom Of This Email
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> Anne,
>
> have a look at what data you have in the SHR:ARDBCFields form.
> This form defines data mapping between underlying application forms and
the
> overview console list data.
> It is quite likely that there is no data mapping for the Assignee field.
> You can check this by running search on the SHR:ARDBCFields form for
entries
> where Vendor Field ID equals to 1000000218 (assignee field ID).
> New entries can be added to this form to define mapping for missing
> applications (Incident, Change etc.)
> You then need to restart the plugin process on the server (or the whole
> Remedy server) for changes to take effect.
>
> Hope this helps.
>
> Jiri Pospisil
>
>
> LCH.Clearnet
>
>
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:[EMAIL PROTECTED] Behalf Of Ramey, Anne
> Sent: 25 February 2008 21:47
> To: [email protected]
> Subject: Adding Assignee column to Overview Console
>
> **
>
>
> I am using AR 7.0.1 on Linux with ITSM 7.0.2 Patch 4.  When I try and add
> the "Assignee" column to the Overview console, it is only populated for
> Problems and Known Errors.  The "Assignee Group" is never populated.  I'm
> sure this has something to do with the way SHR:ARDBC_OverviewConsole runs
> it's query.  I would think, since these two fields are on the common area
of
> SHR:ARDBC_OverviewConsole and aren't in the Problem only area or anything
> like that, that they would be populated for any type of request.  Am I way
> off base or might there be a bug in the query?
>
>
>
> Anne Ramey
>
>
>
>  __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
> html___
>
>
*************************************************************************************************

>
>
>
>
>
> This email is intended for the named recipient(s) only. Its contents are
> confidential and may only be retained by the named recipient(s) and may
only
> be copied or disclosed with the consent of LCH.Clearnet Limited. If you
are
> not an intended recipient please delete this e-mail and notify
> [EMAIL PROTECTED]
>
>
>
>
>
> The contents of this email are subject to contract in all cases, and
> LCH.Clearnet Limited makes no contractual commitment save where confirmed
by
> hard copy. LCH.Clearnet Limited accepts no liability, including liability
> for negligence, in respect of any statement in this email.
>
>
>
>
>
> LCH.Clearnet Limited, Registered Office: Aldgate House, 33 Aldgate High
> Street, London EC3N 1EA. Recognised as a Clearing House under the
Financial
> Services & Markets Act 2000. Reg in England No.25932
>
> Telephone: +44 20 7426 7000 Internet: http://www.lchclearnet.com
>
>
>
>
>
>
*************************************************************************************************

>
>
>
>  __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
> html___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to