Hello community,
Context:
We have an application (eg.: APP Groups) to manage the security for a second application (eg.: APP Application) with all the necessary groups.
Our team have a requirement to allow the user to create a group without having to access the Appian Designer, so we are using the "create a group" smart service (https://docs.appian.com/suite/help/22.1/Create_Group_Smart_Service.html).
Problem:
This smart service works but it doesn't allow us to add the object in the groups application. There is any way to, when creating a group, passing the indication (through smart service or function, for example) that this group is to add to the group application?
We need to be able to move this objects through environments, so they need to live inside this application.
Thank you.
Discussion posts and replies are publicly visible
The way I've seen this done before is to imagine there are two classes of Group. One you can consider to be a group that represents a "service" - that offers up the relevant functionality within your application. This is static and is attached at design-time to the object(s) that you want to expose your your different user communities. The other type of group you can consider to define the role(s) that you want your user communities to have. These can be created a run-time and, to meet your use case, can also be dynamically added to (or removed in the future) from the static groups you've defined. Think of the static groups as power sockets and your dynamic groups as plugs. You can create dynamic groups at run-time and plug them into your static power sockets. The art in this model is in defining the scope of the functionality you want to be able to expose to your user communities.