In the ELSE block, create a new Update issue in Jira action. We can use this to create our IF/ELSE condition.ĭrag the original Create issue in Jira step into the IF block. If no matching issue is found, that list will have a size of 0. The Jira search will return a list of results. This is where having that unique identifier comes in handy: We can accomplish this with an IF/ELSE condition.įirst we need to search for an existing issue in Jira. What we need is a recipe that will create a Jira issue only if it doesn’t already exist, and update an issue if it does exist. If we start the recipe like this, then every time a customer service rep updates a Salesforce case, we will create a brand new issue in Jira. However, this action by itself will not be enough to keep our customer support issue up-to-date across Salesforce and Jira. We can do that by setting the Salesforce case number as a label on the Jira issue. Note that whenever two apps touch the same underlying record, it’s important to have a unique identifier that works in both places. We’ll map the subject and description fields from the Salesforce case to their equivalent fields in Jira. Whenever our recipe picks up a new case in Salesforce, we want to create an equivalent issue in Jira, so let’s create that step. Output tab Use an IF/ELSE condition to choose between creating or updating an issue in Jira If the case is missing a description, we want to prompt the case owner to go back and provide the missing details. Use an IF condition to send incomplete cases back to the ownerįor our technical support team to be able to work on an issue, the details need to be complete. Create the recipeĬreate a new recipe with Salesforce as the triggering app, and select New/updated record in Salesforce as the trigger, and Case as the object. However, the general principles applied below will work, no matter which apps you use in your organization. To follow along exactly with this example, you’ll need active connections to: Determine whether we need to create a new issue in Jira, or update an existing issue.Identify cases that are incomplete, and prompt the case owner to provide the missing information.We’ll use conditional logic to accomplish two tasks in this recipe: Here, we’ll revisit the same use case, but this time we’ll focus on the flow of actions in the recipe, rather than how data is mapped. In a recent post, we used the example of escalating customer support cases from Salesforce to Jira to show how to use Lookup Tables to transform data. To show you how to use these conditions in a recipe, let’s work through an example that includes both types of conditions. How to use IF and IF/ELSE conditions in a recipe IF condition checks if description is present in Salesforce caseĪ “block” of actions that will be executed whenever the condition is true.Ī block of actions that will be executed whenever the condition is false - this is only applicable for IF/ELSE conditions
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |