the .xml is only going to provide filter information. It will not provided
"new columns" (per the subject of this thread) or "new tables" per your
original post.

Also, since you are using Kix, you could probably ask via someone who
provides Kix support.

Did you take a look at the link you provided?
http://forums.otterhub.org/viewtopic.php?f=53&t=6351#p25546
As a workaround, please use at least 2 QueueIDs or 2 Queues as search
attributes (even if they are the same):


On Wed, Jul 10, 2013 at 9:15 AM, Darshak Modi <darshak.m...@elitecore.com>wrote:

> I tried as below , but error is , I even tried Queues two times by seeing
> forum . Any suggestion ?
> http://forums.otterhub.org/**viewtopic.php?f=53&t=6351<http://forums.otterhub.org/viewtopic.php?f=53&t=6351>
>
> Can't use an undefined value as an ARRAY reference at
> /opt/otrs/KIXCore/Kernel/**System/SysConfig.pm line 1779.
>
> <ConfigItem Name="DashboardBackend###0600-**Paid" Required="0" Valid="1">
>         <Description Translatable="1">Parameters for the dashboard backend
> of the ticket pending reminder overview of the agent interface. "Limit" is
> the number of entries shown by default. "Group" is used to restrict the
> access to the plugin (e. g. Group: admin;group1;group2;). "Default"
> determines if the plugin is enabled by default or if the user needs to
> enable it manually. "CacheTTLLocal" is the cache time in minutes for the
> plugin.</Description>
>         <Group>Ticket</Group>
> <SubGroup>Frontend::Agent::**Dashboard</SubGroup>
>         <Setting>
>             <Hash>
>                 <Item Key="Module">Kernel::Output::**
> HTML::DashboardTicketGeneric</**Item>
>                 <Item Key="Title">Paid Orders</Item>
>                 <Item Key="Description">All open tickets, these tickets
> have already been worked on, but need a response</Item>
>                 <Item Key="Attributes">Queues=**MTWINS;</Item>
>                 <Item Key="Filter">All</Item>
>                 <Item Key="Time">Age</Item>
>                 <Item Key="Limit">10</Item>
>                 <Item Key="Permission">rw</Item>
>                 <Item Key="Block">ContentLarge</**Item>
>                 <Item Key="Group">MTWINS</Item>
>                 <Item Key="Default">1</Item>
>                 <Item Key="CacheTTLLocal">0.5</Item>
>             </Hash>
>
>         </Setting>
> </ConfigItem>
>
> Darshak Modi | Telecom Practices
> Office: 079-26405600 | +91-9909008245
> Skype: darshakamodi
>
> On 10-07-2013 PM 06:31, Gerald Young wrote:
>
>> If you have tried it and were not successful, you'd be asking a different
>> question.
>> If you have tried it and it was successful, you would not be asking the
>> question.
>>
>>
>>
>> On Wed, Jul 10, 2013 at 8:50 AM, Darshak Modi 
>> <darshak.m...@elitecore.com<mailto:
>> darshak.modi@**elitecore.com <darshak.m...@elitecore.com>>> wrote:
>>
>>     Can I not achieve using the xml config ? Like below sample, can I
>>     add another block/xml
>>     See the link
>>     
>> http://blog.otrs.org/2010/09/**26/keep-an-eye-on-certain-**customers/<http://blog.otrs.org/2010/09/26/keep-an-eye-on-certain-customers/>
>>     As per document, I can have count/array/hash also.
>>
>>
>>     <ConfigItem
>>     Name="Ticket::Frontend::**AgentTicketEscalationView###**
>> SortBy::Default"
>>     Required="1" Valid="1">
>>             <Description Translatable="1">Defines the default ticket
>>     attribute for ticket sorting in the escalation view of the agent
>>     interface.</Description>
>>             <Group>Ticket</Group>
>>     <SubGroup>Frontend::Agent::**Ticket::ViewEscalation</**SubGroup>
>>             <Setting>
>>                 <Option SelectedID="EscalationTime">
>>                     <Item Key="Age">Age</Item>
>>                     <Item Key="Ticket">Ticket</Item>
>>                     <Item Key="Subject">Subject</Item>
>>                     <Item Key="Queue">Queue</Item>
>>                     <Item Key="Priority">Priority</Item>
>>                     <Item Key="EscalationTime">**EscalationTime</Item>
>>                 </Option>
>>             </Setting>
>>         </ConfigItem>
>>
>>
>>     Darshak Modi | Telecom Practices
>>     Office: 079-26405600 | +91-9909008245
>>     Skype: darshakamodi
>>
>>     On 10-07-2013 PM 05:30, Gerald Young wrote:
>>
>>
>>         0130 is just a number. It is used for sort order.
>>         Agent and queue are fields added to the dtl. I posted a link
>>         yesterday on this list.
>>
>>         Calculated fields (count) require programming.
>>
>>         On Jul 10, 2013 1:13 AM, "Darshak Modi"
>>         <darshak.m...@elitecore.com
>>         <mailto:darshak.modi@**elitecore.com <darshak.m...@elitecore.com>
>> >
>>         <mailto:darshak.modi@**elitecore.com <darshak.m...@elitecore.com>
>>
>>         <mailto:darshak.modi@**elitecore.com <darshak.m...@elitecore.com>>>>
>> wrote:
>>
>>             Hello,
>>             I want to add some tables like
>>             AgentName/Owner, OpenCount, CloseCount,
>>             And
>>             QueueNane, OpenCount, CloseCount, I checked the xml files and
>>             understood that we can do by creating xml in Files.
>>             However  I did not understood what this means , waht this 0130
>>             means? And how to get/customize for my requirement.
>>
>>
>>
>>             DashboardBackend###*0130*-**TicketOpen
>>
>>
>>             --     Darshak Modi | Telecom Practices
>>             Office: 079-26405600 |+91-9909008245  <tel:%2B91-9909008245>
>>
>>             Skype: darshakamodi
>>
>>
>>                    ------------------------------**
>> ------------------------------**---------
>>             OTRS mailing list: otrs - Webpage: http://otrs.org/
>>             Archive: 
>> http://lists.otrs.org/**pipermail/otrs<http://lists.otrs.org/pipermail/otrs>
>>             To unsubscribe: 
>> http://lists.otrs.org/cgi-bin/**listinfo/otrs<http://lists.otrs.org/cgi-bin/listinfo/otrs>
>>
>>
>>
>>         ------------------------------**------------------------------**
>> ---------
>>         OTRS mailing list: otrs - Webpage: http://otrs.org/
>>         Archive: 
>> http://lists.otrs.org/**pipermail/otrs<http://lists.otrs.org/pipermail/otrs>
>>         To unsubscribe: 
>> http://lists.otrs.org/cgi-bin/**listinfo/otrs<http://lists.otrs.org/cgi-bin/listinfo/otrs>
>>
>>
>>     ------------------------------**------------------------------**
>> ---------
>>     OTRS mailing list: otrs - Webpage: http://otrs.org/
>>     Archive: 
>> http://lists.otrs.org/**pipermail/otrs<http://lists.otrs.org/pipermail/otrs>
>>     To unsubscribe: 
>> http://lists.otrs.org/cgi-bin/**listinfo/otrs<http://lists.otrs.org/cgi-bin/listinfo/otrs>
>>
>>
>>
>>
>> ------------------------------**------------------------------**---------
>> OTRS mailing list: otrs - Webpage: http://otrs.org/
>> Archive: 
>> http://lists.otrs.org/**pipermail/otrs<http://lists.otrs.org/pipermail/otrs>
>> To unsubscribe: 
>> http://lists.otrs.org/cgi-bin/**listinfo/otrs<http://lists.otrs.org/cgi-bin/listinfo/otrs>
>>
>
> ------------------------------**------------------------------**---------
> OTRS mailing list: otrs - Webpage: http://otrs.org/
> Archive: 
> http://lists.otrs.org/**pipermail/otrs<http://lists.otrs.org/pipermail/otrs>
> To unsubscribe: 
> http://lists.otrs.org/cgi-bin/**listinfo/otrs<http://lists.otrs.org/cgi-bin/listinfo/otrs>
>
---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Reply via email to