Is Resolved date editable trough WebUI?

Hello.

I’m using RT 4.2.10 and RTIR 3.2. I’ve developped my own extension and I’ve included the ‘Resolved’ date at the end of the EditDates.

<&|/l&>Closed:\ <& /Elements/SelectDate, menu_prefix => 'Resolved', current => 0 &> (<% $TicketObj->ResolvedObj->AsString %>)

The field shows well and a proper date is selectable, but when you try to save changes, the view stays on the edit form without commiting anything.

If I try to do ‘$ticket->SetResolved( $date->ISO )’ from the perl API, it works well.

Looking at the RT sources I’ve seen in Ticket.pm a couple of subs called ‘_OverlayAccessible’ and ‘_CoreAccessible’. The former seems to show that ‘Resolved’ is not writable, but the latter shows that it is. Does this mean that ‘_OverlayAccessible’ refers to through WebUI and hence it is not editable from there?

Thanks in advance.

Best regards.

Iñaki de Eguía Díez
Desarrollador - Entornos Abiertos
inaki.deeguia@csa.esmailto:inaki.deeguia@csa.es

En cumplimiento de la Ley Orgánica 15/1999, de 13 de diciembre, de Protección de Datos de Carácter Personal, los datos personales reflejados en este documento se incluirán en una base de datos informatizada de titularidad de Centro Regional de Servicios Avanzados, S.A. Dicha base de datos se encuentra inscrita en el Registro General de Protección de Datos conforme a lo dispuesto en la legislación vigente y cumpliendo todas las medidas de seguridad del Real Decreto 994/1999, de 11 de junio, de medidas de seguridad de los ficheros automatizados que contengan datos de carácter personal. Asimismo, el cliente dispone en todo momento de los derechos de información, acceso, rectificación, cancelación y oposición, que podrá ejercitar por escrito mediante carta dirigida al Responsable de Seguridad, en la siguiente dirección: C/ López Bravo, 1. 09001 Burgos (España).

Hi I�aki,

The code you have puts it on the screen, but you also need to add
something to commit the incoming value to the DB. If you look in
ModifyDates file, you’ll see a call to ProcessTicketDates. By default
that only handles the core editable RT dates. You need to add some code
to receive the Resolved argument when submitted and update the DB. In
4.2 there’s a callback right before the ProcessTicketDates call, so you
should be able to add the code there.

JimOn 3/29/16 10:19 AM, I�aki de Egu�a D�ez wrote:

Hello.

I’m using RT 4.2.10 and RTIR 3.2. I’ve developped my own extension and
I’ve included the ‘Resolved’ date at the end of the EditDates.

<&|/l&>Closed:\ <& /Elements/SelectDate, menu_prefix => 'Resolved', current => 0 &> (<% $TicketObj->ResolvedObj->AsString %>)

The field shows well and a proper date is selectable, but when you try
to save changes, the view stays on the edit form without commiting anything.

If I try to do ‘$ticket->SetResolved( $date->ISO )’ from the perl API,
it works well.

Looking at the RT sources I’ve seen in Ticket.pm a couple of subs called
’_OverlayAccessible’ and ‘_CoreAccessible’. The former seems to show
that ‘Resolved’ is not writable, but the latter shows that it is. Does
this mean that ‘_OverlayAccessible’ refers to through WebUI and hence it
is not editable from there?

Thanks in advance.

Best regards.

I�aki de Egu�a D�ez
Desarrollador - Entornos Abiertos
inaki.deeguia@csa.es mailto:inaki.deeguia@csa.es

En cumplimiento de la Ley Org�nica 15/1999, de 13 de diciembre, de
Protecci�n de Datos de Car�cter Personal, los datos personales
reflejados en este documento se incluir�n en una base de datos
informatizada de titularidad de Centro Regional de Servicios Avanzados,
S.A. Dicha base de datos se encuentra inscrita en el Registro General de
Protecci�n de Datos conforme a lo dispuesto en la legislaci�n vigente y
cumpliendo todas las medidas de seguridad del Real Decreto 994/1999, de
11 de junio, de medidas de seguridad de los ficheros automatizados que
contengan datos de car�cter personal. Asimismo, el cliente dispone en
todo momento de los derechos de informaci�n, acceso, rectificaci�n,
cancelaci�n y oposici�n, que podr� ejercitar por escrito mediante carta
dirigida al Responsable de Seguridad, en la siguiente direcci�n: C/
L�pez Bravo, 1. 09001 Burgos (Espa�a).


RT 4.4 and RTIR Training Sessions https://bestpractical.com/training

  • Washington DC - May 23 & 24, 2016

Thank you very much, Jim.

I’ll look into it.

Iñaki de Eguía Díez
Desarrollador - Entornos Abiertos
inaki.deeguia@csa.esDe: rt-devel rt-devel-bounces@lists.bestpractical.com en nombre de Jim Brandt jbrandt@bestpractical.com
Enviado: miércoles, 30 de marzo de 2016 19:27
Para: rt-devel@lists.bestpractical.com
Asunto: Re: [rt-devel] Is Resolved date editable trough WebUI?

Hi Iñaki,

The code you have puts it on the screen, but you also need to add
something to commit the incoming value to the DB. If you look in
ModifyDates file, you’ll see a call to ProcessTicketDates. By default
that only handles the core editable RT dates. You need to add some code
to receive the Resolved argument when submitted and update the DB. In
4.2 there’s a callback right before the ProcessTicketDates call, so you
should be able to add the code there.

Jim

Ok. I’ve finally achieved it.

Since I’m using RTIR, the callback to modify is RTIR/Edit.html/AfterProcessing.

Thanks again.

Cheers!

Iñaki de Eguía Díez
Desarrollador - Entornos Abiertos
inaki.deeguia@csa.esDe: rt-devel rt-devel-bounces@lists.bestpractical.com en nombre de Iñaki de Eguía Díez inaki.deeguia@csa.es
Enviado: jueves, 31 de marzo de 2016 10:18
Para: rt-devel@lists.bestpractical.com
Asunto: Re: [rt-devel] Is Resolved date editable trough WebUI?

Thank you very much, Jim.

I’ll look into it.

Iñaki de Eguía Díez
Desarrollador - Entornos Abiertos
inaki.deeguia@csa.es

De: rt-devel rt-devel-bounces@lists.bestpractical.com en nombre de Jim Brandt jbrandt@bestpractical.com
Enviado: miércoles, 30 de marzo de 2016 19:27
Para: rt-devel@lists.bestpractical.com
Asunto: Re: [rt-devel] Is Resolved date editable trough WebUI?

Hi Iñaki,

The code you have puts it on the screen, but you also need to add
something to commit the incoming value to the DB. If you look in
ModifyDates file, you’ll see a call to ProcessTicketDates. By default
that only handles the core editable RT dates. You need to add some code
to receive the Resolved argument when submitted and update the DB. In
4.2 there’s a callback right before the ProcessTicketDates call, so you
should be able to add the code there.

Jim