Issues with Dynamic Fields

Jignesh Kakka (jkakka)

20 Mar 2013 20 Mar '13

4:33 a.m.

While creating ticket, we pass Dynamic fields as name-value pair. But while getting ticket we receive dynamicFields as DynamicField_FieldName. Cant this behavior be changed to having Name Value pair even while getting the ticket. The reason wh I want in this way is , let's say if we add or remove a dynamic field from System, then it may not require code change if we maintain as name-value pair I was assuming that this may happen in OTRS 3.2 . But it also applies same logic while getting tickets Thanks, Jignesh

Attachments:

attachment.html (text/html — 2.3 KB)

Show replies by date

Michiel Beijen

20 Mar 20 Mar

10:34 a.m.

Hi, On Wed, Mar 20, 2013 at 5:33 AM, Jignesh Kakka (jkakka) wrote:

...

While creating ticket, we pass Dynamic fields as name-value pair. But while getting ticket we receive dynamicFields as DynamicField_FieldName.** **

Cant this behavior be changed to having Name Value pair even while getting the ticket. ****

The reason wh I want in this way is , let’s say if we add or remove a dynamic field from System, then it may not require code change if we maintain as name-value pair****

I was assuming that this may happen in OTRS 3.2 . But it also applies same logic while getting tickets

Can you explain the use case you have for this? What code would you now write that can be different if OTRS behaviour would change? -- Mike

Jignesh Kakka (jkakka)

3:21 p.m.

Hi Michiel, Let’s say we add a dynamic field called ticket_source in OTRS. Now while creating the ticket , there is no problem. But while getting the ticket, I have to modify my application source code to get/read this new Dynamic field from the response. Had it been name-value pair, it would have got populated in my map automatically. Thanks, Jignesh From: dev-bounces@otrs.org [mailto:dev-bounces@otrs.org] On Behalf Of Michiel Beijen Sent: Wednesday, March 20, 2013 4:05 PM To: Development community of OTRS Subject: Re: [dev] Issues with Dynamic Fields Hi, On Wed, Mar 20, 2013 at 5:33 AM, Jignesh Kakka (jkakka) mailto:jkakka@cisco.com> wrote: While creating ticket, we pass Dynamic fields as name-value pair. But while getting ticket we receive dynamicFields as DynamicField_FieldName. Cant this behavior be changed to having Name Value pair even while getting the ticket. The reason wh I want in this way is , let’s say if we add or remove a dynamic field from System, then it may not require code change if we maintain as name-value pair I was assuming that this may happen in OTRS 3.2 . But it also applies same logic while getting tickets Can you explain the use case you have for this? What code would you now write that can be different if OTRS behaviour would change? -- Mike

Michiel Beijen

4:03 p.m.

Hi, On Wed, Mar 20, 2013 at 4:21 PM, Jignesh Kakka (jkakka) wrote:

...

Let’s say we add a dynamic field called ticket_source in OTRS. ****

Now while creating the ticket , there is no problem.****

But while getting the ticket, I have to modify my application source code to get/read this new Dynamic field from the response.****

Had it been name-value pair, it would have got populated in my map automatically.****

**

I still don't understand. How do you read the values? Can't you just read values from Dynamicfield_whatever as well? --' Mike

Carlos Rodríguez

4:10 p.m.

Hi Jignesh, I see, but I think is extremely easy to remove the "DyamicField_" prefix using a simple Regular Expression (for substitution), you can use it everywhere in your code even if the prefix is not there. On the other hand, we have this prefix is some parts of the code in several files, because a Dynamic Field can be named as Priority, StateID, Owner, ResponsibleID, TicketNumber, etc. if you call TicketGet from the TicketObject and you don't have the "DynamicField_" Prefix in the Dynamic Fields it will be totally a mess. and it will be worst, if you for example update the ticket based on the results of a TicketGet (without the prefixes). So IMHO I don't see many complications in having the prefix, but a lot of problems if we don't. Please think about it. ((enjoy)) Carlos Rodríguez On Mar 20, 2013, at 9:21 AM, "Jignesh Kakka (jkakka)" wrote:

...

Hi Michiel,

Let’s say we add a dynamic field called ticket_source in OTRS. Now while creating the ticket , there is no problem. But while getting the ticket, I have to modify my application source code to get/read this new Dynamic field from the response. Had it been name-value pair, it would have got populated in my map automatically.

Thanks, Jignesh

From: dev-bounces@otrs.org [mailto:dev-bounces@otrs.org] On Behalf Of Michiel Beijen Sent: Wednesday, March 20, 2013 4:05 PM To: Development community of OTRS Subject: Re: [dev] Issues with Dynamic Fields

Hi,

On Wed, Mar 20, 2013 at 5:33 AM, Jignesh Kakka (jkakka) wrote: While creating ticket, we pass Dynamic fields as name-value pair. But while getting ticket we receive dynamicFields as DynamicField_FieldName. Cant this behavior be changed to having Name Value pair even while getting the ticket. The reason wh I want in this way is , let’s say if we add or remove a dynamic field from System, then it may not require code change if we maintain as name-value pair I was assuming that this may happen in OTRS 3.2 . But it also applies same logic while getting tickets

Can you explain the use case you have for this? What code would you now write that can be different if OTRS behaviour would change?

-- Mike

_______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

4533

Age (days ago)

4533

Last active (days ago)

List overview

Download

4 comments

3 participants

participants (3)

Carlos Rodríguez
Jignesh Kakka (jkakka)
Michiel Beijen