Activating date / time Dynamic Fields via the postmaster filter

[cbruigom]

Hi There,

I am using a regex to look for a date / time string in the body of an incoming mail and then via the post master filter use the [***] to set a date / time dynamic field. If I parse the string to a plain text field it is in the right format i.e 04/30/2015 20:30:00.

What happens however is if I parse it to the dynamic field it doesnt update it. I notice that the fields check box is not activated, could this be the cause? I have tried setting the dynamic field to mandatory and that doesnt help, it still shows as not activated and doesnt have the correct date time stamp.

Any ideas anyone?

I am using OTRS 4.0.5

[cbruigom]

An update on this issue:

If I parse the string to the Follow-up headers then the values are written. In the syslog I now get:

Filter: 'calendar' Set param 'X-OTRS-FollowUp-DynamicField-TicketCalendarStartTime' to '04/30/2015 21:15:00'

I notice before that there were errors in the syslog saying:
Could not update field TicketCalendarEndTime for Ticket ID 160 !

Any ideas why it writes to 'X-OTRS-FollowUp-DynamicField-TicketCalendarStartTime' but not to 'X-OTRS-DynamicField-TicketCalendarStartTime'?

[crythias]

followup is followup.

[cbruigom]

Hey crythias,

Ok so your point is? Any idea how I can update and activate the date / time dynamic field as I am trying to do?

[crythias]

Ok so your point is?

If the entry is a Followup, it will only set the Key/Value with X-OTRS-FollowUp-Key: Value.

If I parse the string to the Follow-up headers then the values are written. In the syslog I now get:

Seems legit.

I'm afraid I don't know what the problem is. If the data is updated, then what's the problem? If the data is not, then syslog is lying. Also make sure you understand the difference between a ticket dynamic field and an Article dynamic field, if there is still such a distinction.

[cbruigom]

I'm afraid I don't know what the problem is. If the data is updated, then what's the problem?

Ok I found this in the admin manual (RTFM)...

And although it is for the pending date it actually shows a different date format to use, when I change to that It writes it. Looks like the format of the date / time through shown on forms must be different to how it is stored....

X-OTRS-State-PendingTime: e. g. 2010-11-20 00:00:00 Sets the pending time of a ticket (you also should sent a pending state via X-OTRS-State). You can specify absolute dates like "2010-11-20 00:00:00" or relative dates, based on the arrival time of the email. Use the form "+ $Number $Unit", where $Unit can be 's' (seconds), 'm' (minutes), 'h' (hours) or 'd' (days). Only one unit can be specified. Examples of valid settings: "+50s" (pending in 50 seconds), "+30m" (30 minutes), "+12d" (12 days). Note that settings like "+1d 12h" are not possible. You can specify "+36h" instead.