Adds Team or several Teams to the record.
- In Sugar each teamset for record consists of two components: team_id as Primary Team and team_set_id as all other teams. Add Teams works with team_set_id only.
- The recommended approach is to use Add Teams on After Save flowcharts than on Before Save.
- Do not use Save Entity to preserve team changes. Add Teams applies team changes itself.
- Despite any changes that might be applied with Add Teams, the standard Sugar logic, which ensures access of Assigned User to a record, works. Let’s say that you created flowcharts and because of its execution teamset for the record do not contain any Team, to which an Assigned user belongs. In this case, standard Sugar behavior adds Assigned Users’ Private Team.
inputs:
entity – input the entity for which new team must be added
- Required: yes
team ids array – input an array or collection of Teams IDs or only one Team ID which must be added to the record.
- Required: yes
outputs:
entity – the entity with the newly added team(s)
As a result of the flowchart execution team West is added to the set of teams of Account Record.
As a result of the flowchart execution two teams West and Poland are added to the set of teams of Account Record.
I need to update an entity and change teams; how should I do this?
In one After Save flowchart.
If you add (or remove) Teams and then update the record, any other flowchart that works on team change (for example, if you have implemented logic of teams inheriting from Account to related records) will be triggered.
Otherwise – firstly, update the record, then update the Team – other flowcharts that work on team change won’t be triggered.
