3.1.5 AgentTicketPhone: Dynamic Field by field name-RESOLVED

Moderator: crythias

Locked
kruegerM
Znuny expert
Posts: 213
Joined: 02 Dec 2010, 16:53
Znuny Version: 6.0.29
Real Name: Marc
Company: National Jewish Health
Location: Denver, CO

3.1.5 AgentTicketPhone: Dynamic Field by field name-RESOLVED

Post by kruegerM »

I just migrated from 3.1.3 to 3.1.5 (and ITSM 3.1.3) to get statistics working, but it's caused a crash in my create ticket (New Phone) page. We have all the dynamic fields listed individually using the syntax:

<!-- dtl:block:DynamicField_TicketFreeText1 -->
<div class="Row Row_DynamicField_$QData{"Name"}">
$Data{"Label"}
<div class="Field">
$Data{"Field"}
</div>
<div class="Clear"></div>
</div>
<!-- dtl:block:DynamicField_TicketFreeText1 -->

... etc

In 3.1.5 when I submit the form, the dynamic fields the 'create' page remains, but the dynamic fields are blanked. If I use generic listing:

<!-- dtl:block:DynamicField -->
<div class="Row Row_DynamicField_$QData{"Name"}">
$Data{"Label"}
<div class="Field">
$Data{"Field"}
</div>
<div class="Clear"></div>
</div>
<!-- dtl:block:DynamicField -->

it works fine.

as a side note - Impact (FreeText14) isn't showing up on the form either.....
Last edited by kruegerM on 29 May 2012, 23:29, edited 1 time in total.
kruegerM
Znuny expert
Posts: 213
Joined: 02 Dec 2010, 16:53
Znuny Version: 6.0.29
Real Name: Marc
Company: National Jewish Health
Location: Denver, CO

Re: 3.1.5 AgentTicketPhone: Dynamic Field by field name

Post by kruegerM »

I've run the 3.1.3 to 3.1.5 migration a couple of times now (thank goodness for dev systems and VM snapshots!)
The 'break' in our AgentTicketPhone operation comes after the application of ITSM 3.1.3.
The core file works, but when I comment out the 'generic' dynamic field section and add our individual ones, it no longer creates tickets.
kruegerM
Znuny expert
Posts: 213
Joined: 02 Dec 2010, 16:53
Znuny Version: 6.0.29
Real Name: Marc
Company: National Jewish Health
Location: Denver, CO

Re: 3.1.5 AgentTicketPhone: Dynamic Field by field name-RESO

Post by kruegerM »

ok - found it. kinda wierd but found it.
if you have valid Dynamic Fields and you are listing fields individually - you must include ALL valid Dynamic Fields even if they are not shown on the form being used (i.e, viewNewPhone). So the choice is either list them, or make them invalid.

I'm not sure why it operates this way - but at least here it is...
Locked