I have a stream that somehow got itself set as its own flow target -- RTC won't let me delete it
I have a stream that originally had a flow target to another stream
I was asked to remove this flow target
When I did that, the flow target somehow got updated to be itself
I am worried that this is going to cause a horrible problem and want to remove this cycle -- will this cause an endless loop of 'flowing' and blow up the stream ?
I believe I need an admin's help to fix this...
( this is RTC client/server 5.0.1 )
One answer
Although strange, it is almost certainly harmless. There are no algorithms that recurse down the flow relations (these relations are just used to configure the Pending Changes view). For example, you can have stream A be a flow target of stream B, and stream B be a flow target of stream A, so there is nothing problematic with cyclic flow relations.
Comments
HI Geoffrey -- Thanks for the reply and for letting me know that it would not have caused a catastrophe to have a stream flow into itself.
I had tried to delete the flow target via the RTC native windows Client ( version 5.0.1 ) by opening up the stream definition and deleting the flow target. I did not try to remove it via Eclipse. From the RTC Client, It would act like it worked; I would do a save and then see it back again after re-opening. After trying this several times with no luck, I got some help from our RTC admin for this repository and he had success using his administrator credentials to remove the unwanted flow target from the stream.
If this happens again, and you have the time, please submit a defect ... it either should work, or you should get some kind of error message making it clear why this wasn't allowed (such as you not having permission to make this change to that stream).