Hi Everyone, I am stucked with one of the most important use case of

Hi Everyone,

I am stucked with one of the most important use case of my application. My objective is that users latest present in users array process variable must only see the process information which I am posting on tempo. If any user is added from that array then along with the previous users , those newly added users must also see the info on tempo now. And if any user(s) are removed, then those removed users(s) should no longer be able to access or see the info of that process instance on tempo.On whole, users present latest in that user array process variable must only see the info on tempo and no one else.

In order to do, I created one parent group('X') of my application. Now, whenever a new instance of process is spawned, using Identity Management Smart service, I create a subgroup('X1') of that Parent Group('X') and then add or remove users in this subgroup('X1') accordingly and then pass 'X1' to the viewers group of Post feed to tempo sma...

OriginalPostID-62228

OriginalPostID-62228

  Discussion posts and replies are publicly visible

Parents
  • ...rt service.
    This works fine for me and my required functionality works fine, However when I go through the Best Practices of Creating Custom Groups,somewhere it states, that one should avoid creating too many custom groups until and unless required to a greater extent. So, By following the above stated approach, my use case works fine, but it will create number of custom groups equal to the number of instances spawned by the process, ie, groups created are directly proportional to the number of instances spawned.In my application, I am expecting around 10 instances to be created daily.

    Therefore in order to achieve my use case, is there any other way around keeping in mind all the best practices.
    Looking forward for your valuable suggestions,

    Thanks in advance
    Siddharth.
Reply
  • ...rt service.
    This works fine for me and my required functionality works fine, However when I go through the Best Practices of Creating Custom Groups,somewhere it states, that one should avoid creating too many custom groups until and unless required to a greater extent. So, By following the above stated approach, my use case works fine, but it will create number of custom groups equal to the number of instances spawned by the process, ie, groups created are directly proportional to the number of instances spawned.In my application, I am expecting around 10 instances to be created daily.

    Therefore in order to achieve my use case, is there any other way around keeping in mind all the best practices.
    Looking forward for your valuable suggestions,

    Thanks in advance
    Siddharth.
Children
No Data