{"id":1920,"date":"2022-07-08T14:23:03","date_gmt":"2022-07-08T14:23:03","guid":{"rendered":"https:\/\/logicbuilder.integroscrm.com\/help\/?page_id=1920"},"modified":"2022-07-14T08:57:09","modified_gmt":"2022-07-14T08:57:09","slug":"flowcharts-calls","status":"publish","type":"page","link":"https:\/\/logicbuilder.integroscrm.com\/help\/flowcharts-calls\/","title":{"rendered":"Flowcharts’ Calls"},"content":{"rendered":"\n

Release date: 2021-06-12<\/span><\/p>\n\n\n\n

Possibility to call a Flowchart from another Flowchart<\/b><\/span><\/p>\n\n\n\n

 New operator Call Service<\/span><\/strong> allows calling a flowchart from the other flowchart:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Select Service from the dropdown and provide Service Parameters with data.  The flowchart implementing this service will be called and provide the result which can be used further in this flowchart.<\/p>\n\n\n\n

Prior to calling the Service, please perform the following steps:<\/p>\n\n\n\n

  1. LB Services<\/strong> Extension must be deployed on Sugar Instance. Find and download here<\/a> LB Services Extension version that corresponds to your Sugar version.<\/li>
  2. Service must be registered in Sugar – it must be a record in LB Service module with specified System Name<\/em> and service Arguments<\/em>.<\/li>
  3. Flowchart that implements Service must be deployed.<\/li><\/ol>\n\n\n\n

    Such a flowchart starts with On Service Call<\/span><\/strong> and describes what should happen when Service is called. When a result is expected (data in result<\/em> port in Call Service operator), this result must be set with operator Set Service Result<\/span><\/strong> in the flowchart that implements Service:<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    Example of usage<\/strong><\/p>\n\n\n\n

    Let\u2019s say there are a bunch of flowcharts with the same steps to create a Task. Instead of performing the same steps in each flowchart, it is possible to create the Service and then re-use it.<\/p>\n\n\n\n

    1. Register Service in Sugar.<\/li><\/ol>\n\n\n\n

       For this, just create a record in LB Services module and provide arguments that are needed to be filled to create Task:<\/p>\n\n\n\n

      \"\"<\/figure>\n\n\n\n

      N.B. Each time you add a new Service into Sugar it is needed to update the Metadata in the Logic Builder to work with the newly added Service.<\/em><\/p>\n\n\n\n

      1. Create a Flowchart starting from On Service Call<\/span><\/strong> to create a Task using parameters that will be input in the Service. In a result<\/em> input the Task ID.<\/li><\/ol>\n\n\n

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

        1. Deploy the flowchart into Sugar. Now you can use created Service in other flowcharts, e.g when Case with Type Product is added:<\/li><\/ol>\n\n\n

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

          Also, it is possible to link the Task to other entities using result<\/span><\/em> output port from the Call Service<\/span><\/strong>:<\/p>\n\n\n

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

          New Validation Possibilities<\/b><\/span><\/p>\n\n\n\n

          Operator Throw Exception<\/span><\/strong> allows addressing the challenges of data validation. For example, when data comes through API to Sugar from an external system \u2013 prior to applying changes or saving a record you could implement additional rules, and return an error when rules are violated. <\/p>\n\n\n\n

          Throw Exception result is also seen in interface to users.<\/p>\n\n\n\n

          \"\"<\/figure>\n\n\n\n

          N.B. <\/strong>For validation rules, use error code 422<\/p>\n\n\n\n

          Example of usage<\/strong><\/p>\n\n\n\n

          Let\u2019s say that Quotes with \u201cDiscount Amount\u201d more than 20% must be approved by Manager. To implement this rule, a Quote must not be moved forward prior to the approval either by a user or by API request.<\/p>\n\n\n\n

           So the flowchart which implements all sets of checks ends with Throw Exception when conditions aren\u2019t met:<\/p>\n\n\n

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

           As a result, when criteria of the rule is violated, a user sees the following error in the interface:<\/p>\n\n\n\n

          \"\"<\/figure>\n\n\n\n

           External Clients get the following error in the API response:<\/p>\n\n\n

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

          Possibility to round numbers<\/b><\/span><\/p>\n\n\n\n

          Operator Round<\/span><\/strong> allows rounding a value to specified precision (number of digits after the decimal point):<\/p>\n\n\n\n

          \"\"<\/figure>\n\n\n\n

          Precision<\/strong>:<\/p>\n\n\n\n