Skip to main content
B
BrianToussaint19-Tanzanite
19-Tanzanite
July 28, 2015
Solved

Set Up Participants added group as default

  • July 28, 2015
  • 3 replies
  • 1233 views

I'm trying to figure out a couple of things.

  1. How did two groups get added to roles automatically when it wasn't that way before?  Notice that it corresponds with our upgrade to 10.2 from 10.1.
  2. How do I get these two groups from automatically populating?

7-28-2015 2-10-12 PM.jpg

Best answer by BrianToussaint

So I talked to Tech Support because for some reason my test server decided it didn't want to start any workflow routings.  While I had them on the phone for that, I also got this issue settled.  Seems that since I had those roles in my team at the org level it decided to add the groups that were in the teams at the library level.  They had me remove those roles from my team at the org level.  After that it works great.  Now why it changed from my 10.1 to my 10.2 is beyond me but it is working now.

3 replies

Marco Tosin
21-Topaz I
Marco Tosin21-Topaz I
21-Topaz I
July 29, 2015

Brian,

we went on 10.2 from 10.1 two months ago.

I haven't seen the behavior you have described.

Marco
S
satre-21-Visitor
1-Visitor
July 29, 2015

Since, behaviour is change after upgrade and there is no change in Workflow&Lifecycle. you can check below things

1. Team template if group is added to role in team

2. if Approve Role is getting resolved by Context team i.e. same role is exist in Product team and contain groups.

Hope it helps !!

Thanks

Shreyas

B
BrianToussaint19-TanzaniteAuthorAnswer
19-Tanzanite
July 29, 2015

So I talked to Tech Support because for some reason my test server decided it didn't want to start any workflow routings.  While I had them on the phone for that, I also got this issue settled.  Seems that since I had those roles in my team at the org level it decided to add the groups that were in the teams at the library level.  They had me remove those roles from my team at the org level.  After that it works great.  Now why it changed from my 10.1 to my 10.2 is beyond me but it is working now.

Terms & ConditionsCookie settingsAccessibility statement