Attribute type "first event" and "last event"

(1) Share

Report

Posted on by Argent

Hi Community,

After a recent update, the atribute type list for imported process mining data has been updated.

Specifically "Case level attribute" becomes "Case level attribute (first event)" and "Case level attribute (last event)".

I could not find Microsoft Learn documentations explaining the differences between the two.

Any help would be appreciated 🙂

Categories:

Process mining

I have the same question (0)

All responses (4)

Answers (2)

Verified answer

christianhalbig Microsoft Employee on at

Like (1)

Report

Hi @Argent. I have (had) the same question. And this is what I think: As Case Level Attributes should be the same over all events (in the same case), you would need to select, which value it should take (from the first event, or from the last).
Simplified example:
Case No Activity Order Type
0 Invoice Entry 5
0 Approve Invoice 5
0 Payment 5
1 Invoice Entry 6
1 Approve Invoice 6
1 Payment 7

Order Type should be the same over all cases. But maybe sometimes it's not. So you can choose in the drop-down if it should take the value from the first or the last event in case the values are different. If it varies often, then you should consider selecting Event Level Attribute.

As I said, I don't know for sure. But it kinda makes sense to me.

Was this reply helpful? Yes No
Verified answer

JK_msft Microsoft Employee on at

Like (1)

Report

Hi @Argent,

sorry for missing documentation for this new feature. I will submit the request for adding it.

The logic is that you can't always ensure at the input that all events within the case have the same value of the case-level attribute. It may happen that the value of the case-level attribute is available only in the first event or in the last one. According to this setting, we then decide whether to take the value of the case-level attribute from the first or last event. If it is already ensured at the input that all events within the case have the same value of the case-level attribute, then it does not matter which of the options is selected.

Here is an example where Price (case-level attribute) is the same for all events (top table) or is determined according to the first (right table) or last event (left table). In all three cases, the result is the same despite other input data.

Was this reply helpful? Yes No
Argent 19 on at

Like (0)

Report

Thanks for the thoughts! It turned out to be correct 🙂

Was this reply helpful? Yes No
Argent 19 on at

Like (0)

Report

Very clear explanation. Thank you!

Was this reply helpful? Yes No