{"id":1844,"date":"2022-07-06T14:32:28","date_gmt":"2022-07-06T14:32:28","guid":{"rendered":"https:\/\/logicbuilder.integroscrm.com\/help\/?page_id=1844"},"modified":"2022-07-14T09:27:24","modified_gmt":"2022-07-14T09:27:24","slug":"teams","status":"publish","type":"page","link":"https:\/\/logicbuilder.integroscrm.com\/help\/teams\/","title":{"rendered":"Teams"},"content":{"rendered":"\n

Release date: 2022-02-19<\/span><\/p>\n\n\n\n

New operators for manipulating teams for Records<\/b><\/span><\/p>\n\n\n\n

There are a bunch of new operators that allow you to read, add or remove teams for records.<\/p>\n\n\n\n

Get Entity Teams <\/b><\/p>\n\n\n\n

Now you can get all Teams that are assigned to the record with an operator Get Entity Teams<\/span><\/strong>. Useful to check whether there is a particular Team set for the record.<\/p>\n\n\n\n

Just provide entity<\/span><\/em> and as output there is an Array<\/span> of all Teams assigned to the record:<\/p>\n\n\n

\"\"<\/a><\/p>\n\n\n

Several notes that apply to the following operators of Teams manipulating:<\/p>\n\n\n\n

  1. In Sugar each teamset for record consists of two components: team_id as Primary Team and team_set_id as all other teams. New operators work with team_set_id only. See chapter Manipulating Primary Team<\/a> to find out how to work with team_id aka Primary Team. <\/li>
  2. The recommended approach is to use new operators on After Save flowcharts than on Before Save.<\/li>
  3. Do not use Save Entity<\/span><\/strong> to preserve team changes. Each of the new operators applies team changes itself.<\/li>
  4. Despite any changes that might be applied with new operators, the standard Sugar logic, which ensures access of Assigned User to a record, works. Let\u2019s say that you created flowcharts and because of its execution a teamset for the record do not contain any Team, to which an Assigned user belongs. In this case, standard Sugar behavior adds Assigned Users\u2019 Private Team.<\/li><\/ol>\n\n\n\n

    Add Teams<\/b><\/p>\n\n\n\n

    It does what it says \u2013 adds Team or several Teams to the record.<\/p>\n\n\n\n

    To add one Team simply provide an ID of a Team to add an entity<\/span><\/em> for which Team(s) must be added:<\/p>\n\n\n

    \"\"<\/a><\/p>\n\n\n

    As a result of the flowchart execution team West is added to the set of teams of Account Record.<\/em><\/p>\n\n\n\n

    To add several Teams, provide an Array<\/span> of Team IDs or Collection<\/span> of Team IDs add and entity for which Team(s) must be added:<\/p>\n\n\n

    \"\"<\/a><\/p>\n\n\n

    As a result of the flowchart execution two teams West and Poland are added to the set of teams of Account Record.<\/em><\/p>\n\n\n

    <\/a><\/p>\n\n\n

    Remove Teams<\/b><\/p>\n\n\n\n

    Conversely to the operator Add Teams<\/span><\/strong>, this operator removes Team or Teams from the record.<\/p>\n\n\n\n

    It works in the same way as Add Teams<\/span><\/strong> \u2013 it expects entity<\/span><\/em> from which Teams should be removed and Collection<\/span>, Array<\/span>, or one Team ID to be removed:<\/p>\n\n\n

    \"\"<\/a><\/p>\n\n\n

    Set Entity Teams<\/b><\/p>\n\n\n\n

    Completely overrides team_set_id with the teams provided in the input. In the same way as the previous two operators, this one expects an entity<\/span><\/em> where Teams must be changed and Array<\/span>, Collection<\/span>, or one team ID that must be set as team_set_id.<\/p>\n\n\n

    \"\"<\/a><\/p>\n

    <\/a><\/p>\n\n\n

    Manipulating Primary Team<\/b><\/p>\n\n\n\n

    As mentioned above, new operators of Teams manipulation work only with team_set_id. However, sometimes you will have to consider Primary Team (or team_id) in your flowcharts as well.<\/p>\n\n\n\n

    You can work with a Primary Team as with the usual field in Logic Builder using Get<\/span><\/strong>\/Set Entity Attributes<\/span><\/strong> on Before Save<\/u>.<\/p>\n\n\n\n

    For example, when it is needed to remove a Team based on conditions and you do not know where this Team was set \u2013 as Primary or not, this challenge could be addressed with two flowcharts: <\/p>\n\n\n\n