Answers to some Human Task Capture outcome Fields duplicated in Timeline updates

[Berto2002]

I am testing a workflow with a node that requires two fields data capture: one date and one multi-line text field:

The output on the timeline is this where the text field output has been duplicated two additional times, showing thrice:

The configuration of the capture is this:

We have a second case of this (i.e. it's a permanent feature). This one captures four data fields and has output 3 lots of answers but interestingly:

 - the first lot of answers are only two of the fields (red)

 - the second and third lot of answers (green and yellow) have a different order...

Thanks in advance for any insight on how this comes about or if it should not...

Rob

PS Rufus is the imaginary testing cat

[Sam P]

@Berto2002 If its the same thing, I have this when different Human Task Capture Outcome Fields have the same Field ID, e.g. field_1 is the output of the first two Outcomes so I always have it duplicated on the timeline, like here for example:

It can be a pain but can also work in your favour sometimes.  If you're referencing the data elsewhere later in the process it usually shows like this from the picker, all those using the same field ID will be selected together automatically:

 

 

[Berto2002]

@Sam P I think you may have found the cause. I do indeed have three outcome buttons and each of those has a date and comments field, each with the same field ID.

I, too, have benefitted from the fact that it enables the references to be consistent. However...

I would like someone at Hornbill to comment on this because no-one would design a system to display duplicate outcomes so I think it is a defect.

[Steve Giller]

If there's a defect here it's allowing different buttons to have the same ID, although now we know that some Customers are doing this, fixing the defect would break existing Workflows and this may prevent it from being addressed.