Dates in custom fields coming through when they shouldn't

[Tina.Lapere]

Hi, 

We've noticed something weird with some dates that we are putting into custom fields.

In the PC we've set 2 date fields to go into custom fields 21 & 23 

 

I've logged a test call like this: 

But when I view the call as an analyst I'm seeing the following:

Even though I didn't complete the last working day field it's putting in the same date as what I've completed in the leaving date field.

I've done a test and put different dates in both and it pull over the correct information.

If I log this via our existing service portal it comes though as expected (no date in the custom_23 field)

Is this a defect?

Thanks

Tina

[Steve Giller]

56 minutes ago, Tina.Lapere said:

Even though I didn't complete the last working day field it's putting in the same date as what I've completed in the leaving date field.

The Last working date has as its label "Last Working Day (if different)"

Without having access to the Workflow I obviously cannot be sure, but that implies that the Workflow will take the Leaving Date and use it as the Last Working Day if the Last Working Day is empty.

[Tina.Lapere]

@Steve Giller This is not something we've setup in the workflow (PC or BPM) and it doesn't happen when I use the existing service.portal. 

It happens before it logs the call to ICT:

This is the Update Request Details node :

This is the last working day setup in the PC

I can't see anything obvious.  And like I said it uses the same PC & BPM when logged through our existing (service) portal and the last working day (if different) is blank.

Thanks

Tina