What does the + suffix at the end of a Studio document name denote?

Question

Question

John Murray · Apr 6, 2016

Here is a screenshot from my 2016.2 FT instance of Studio and Ensemble:

I don't recall having seen the highlighted "+" suffix on document names previously. Who can tell me what it denotes?

I originally posted this in the Field Tests group but it turned out to be a 2016.1 feature that I hadn't previously noticed. So I subsequently moved the post to the Cache group.

Discussion (11)2

Log in or sign up to continue

Timur Safin · Apr 6, 2016

Saved but not compiled.

0 0

score 0 · Answer 1 · 2016-04-06T10:18:00-04:00

Odd then that when I click the Compile button the suffix disappears while compiling but then reappears afterwards, even though the Output tab reports successful compilation.

score 0 · Answer 2 · 2016-04-06T10:23:11-04:00

Timur Safin · Apr 6, 2016

My guess that this sounds like result of some source control hook activity (Deltanji?)...

0 0

score 0 · Answer 3 · 2016-04-06T11:34:36-04:00

No, it even happens when I have no source control class set for the namespace (and have restarted my Studio after confirming that).

score 0 · Answer 4 · 2016-04-07T17:05:29-04:00

Then it is a bug. What is client version and how to reproduce it?

Edit: this i s a bug for classes inherited from Ens.BusinessProcess. We will work on it.

score 0 · Answer 5 · 2016-04-08T04:27:43-04:00

Given that John Willeke reports the "+" feature arrived in 2016.1, is that version of Ensemble also affected by this bug? I don't currently have a 2016.1 Ensemble to test.

score 0 · Answer 6 · 2016-04-08T09:12:39-04:00

Yes to 2016.1. This is server side problem already corrected by MAK4540, not sure to what versions correction will be ported to.

score 0 · Answer 7 · 2016-05-13T09:22:41-04:00

Mark Hanson · May 13, 2016

The MAK4540 fix was approved for porting to 2016.1.1 and all later releases.

0 0

score 0 · Answer 8 · 2017-04-05T09:49:58-04:00

John Murray · Apr 5, 2017

Good to see this indicator behaving reliably now.

0 0

score 0 · Answer 9 · 2016-04-06T10:53:07-04:00

Jon Willeke · Apr 6, 2016

This indicator is new in 2016.1.

0 0

score 3 · Answer 10 · 2016-04-07T22:58:08-04:00

It is a bug due to Ensemble code adding routines to the set of items generated by the class but not setting the timestamp for these. So when we look at all routines generated from this class and verify the timestamps of each one has not changed these are different and so cause the flag showing it is not up to date.

As there is pre-existing code that sets this $$$cCLASSroutines array manually I updated the logic to only verify timestamps that are not "" which should fix this problem. This fix was submitted as MAK4540.