Forum Discussion
Memorable MemberBUG::PIPELINE::TEAMS ACTIVITY::SETTINGS NOT SAVED
So here is what happened now... I opened the pipeline again and upon clicking on each Teams activity and navigating to the settings, all the settings showed up as set yesterday.
Then I did this. I clicked on a Teams activity in the same pipeline that was copy/pasted from another pipeline (and that pipeline what copy/pasted from another workspace--I forgot to mention this yesterday). So, when I click on this Teams activity, none of the settings show up as they are in that other workspace pipeline. That's fine.
But then, if I click back on the Teams activity that was created within the pipeline I am currently working on, and whose settings just showed up as I had set them yesterday, now they show up as not set, like this:
So I think this is a client Javascript issue. Because like I said above, when I re-opened the pipeline today, the settings were all there as when I had set them yesterday. And now, after switching the focus back and forth between 2 Team activities (one natively created within the current pipeline, and one copy/pasted from another pipeline from another worskpace)) the settings appear gone again. I suspect after I save the pipeline, close it, and re-open it later, the settings will show as set properly again.
Memorable MemberWhat happens if you leave the pipeline design surface without closing the pipeline and go back to the workspace and open another pipeline, for example? And then navigate back to the first pipeline and go to the Teams activity settings? Do they still load automatically as you configured them?
Yes I tried that just now Element115
There is no issue. The settings are same as before.
- Element115
OK then the only factor left is the length of time I do not log out from Fabric and leave everything open. In your case, I guess that since you use it for testing, you log in and out the same day, flushing everything.
Hey Element115
Even I do not log out from Fabric. It has been logged in from Day 1. I never logged out.
Please try again and let me know.- Element115
So here is what happened now... I opened the pipeline again and upon clicking on each Teams activity and navigating to the settings, all the settings showed up as set yesterday.
Then I did this. I clicked on a Teams activity in the same pipeline that was copy/pasted from another pipeline (and that pipeline what copy/pasted from another workspace--I forgot to mention this yesterday). So, when I click on this Teams activity, none of the settings show up as they are in that other workspace pipeline. That's fine.
But then, if I click back on the Teams activity that was created within the pipeline I am currently working on, and whose settings just showed up as I had set them yesterday, now they show up as not set, like this:
So I think this is a client Javascript issue. Because like I said above, when I re-opened the pipeline today, the settings were all there as when I had set them yesterday. And now, after switching the focus back and forth between 2 Team activities (one natively created within the current pipeline, and one copy/pasted from another pipeline from another worskpace)) the settings appear gone again. I suspect after I save the pipeline, close it, and re-open it later, the settings will show as set properly again.