{"id":678,"date":"2022-12-06T22:19:00","date_gmt":"2022-12-07T04:19:00","guid":{"rendered":"https:\/\/blog.felineflock.com\/?p=678"},"modified":"2024-01-03T22:29:48","modified_gmt":"2024-01-04T04:29:48","slug":"chatgpts-blend-of-tech-and-humor-a-new-approach-to-salesforce-triggers","status":"publish","type":"post","link":"https:\/\/blog.felineflock.com\/index.php\/2022\/12\/06\/chatgpts-blend-of-tech-and-humor-a-new-approach-to-salesforce-triggers\/","title":{"rendered":"ChatGPT’s Blend of Tech and Humor: A New Approach to Salesforce Triggers"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

ChatGPT is a prototype artificial intelligence chatbot designed by OpenAI to understand natural human language and generate written text that closely resembles human writing.<\/p>\n\n\n\n

I’ve played with ChatGPT for a little while to create a Salesforce trigger and will tell the results but, first, the routine it gave me when I’ve asked “Write a Seinfeld routine about Salesforce triggers.<\/strong>“<\/p>\n\n\n\n

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

Then I’ve asked ChatGPT: “Please write a Salesforce trigger that notifies case team members of any new Case Feed post.<\/strong>“<\/p>\n\n\n\n

Below was the response followed by ChatGPT’s very nice explanation: “This trigger will be executed whenever a new Case Feed post is created. It will first query the CaseTeamMember object to retrieve the case team members for the case associated with the post, and will store their user IDs in a set. It will then use these user IDs to query the User object and create a map of users. Finally, it will create an email message for each new Case Feed post, setting the recipients to the case team members, and will send the messages using the Messaging.sendEmail<\/strong> method.”<\/p>\n\n\n\n

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

As you can see, the code is well-formatted and commented out, however it will NOT work properly:<\/p>\n\n\n\n

    \n
  1. the trigger is missing the opening {, which ended up in the bottom of the code<\/li>\n\n\n\n
  2. it runs a query on CaseTeamMember inside the first loop<\/li>\n\n\n\n
  3. it uses “stream() .map(user -> user.Email) .collect(Collectors.toList())” which is not Apex and uses what seems like an undeclared variable “Collectors”.<\/li>\n<\/ol>\n\n\n\n

    Then I’ve tried again giving further details: “Please write a Salesforce trigger in Apex that notifies case team members of any new Case Feed post and avoid queries inside loops.”<\/p>\n\n\n\n

    The response: <\/p>\n\n\n\n

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

    It did respect the best practice of not placing a query inside a loop, but, otherwise, it had almost the same flaws:<\/p>\n\n\n\n

      \n
    1. the trigger is missing the opening {, which ended up in the bottom of the code<\/li>\n\n\n\n
    2. instead of collecting the case ids (parentId) it collected the post ids and added an unnecessary query on Case\/CaseFeed<\/li>\n\n\n\n
    3. again it used “stream() … .collect()” (non-Apex).<\/li>\n<\/ol>\n\n\n\n

      So I’ve made a third attempt with more details: “Please write a Salesforce Case Feed trigger in Apex that collects the parent case ids and uses it to retrieve the Case Team Member emails, then notifies each case team member about the Case Feed post. Avoid queries inside loops. Avoid stream() and collect() methods.” resulted in:<\/p>\n\n\n\n

        \n
      1. it still collected the post ids instead of parent ids<\/li>\n\n\n\n
      2. unnecessary nested queries<\/li>\n\n\n\n
      3. missed some query optimizations<\/li>\n<\/ol>\n\n\n\n

        Fourth try: “Please write a Salesforce Case Feed trigger in Apex that collects the ParentIds and use them to retrieve the Case Team Member emails from the CaseTeamMember object, then notifies each case team member about the Case Feed post. Avoid queries inside loops. Avoid stream() and collect() methods. Avoid nested queries.”<\/p>\n\n\n\n

        It did figure out the part of querying the User object to collect the email addresses but the resulting code became more incomplete and looking worse than before. It included another query inside a loop. It was as if ChatGPT just started to give up! \ud83e\udd37\ud83c\udffd\u2642\ufe0f<\/p>\n\n\n\n

        I will try a more “baby-steps approach” later.<\/p>\n\n\n\n

        Then, since ChatGPT seems to shine at fiction writing, I’ve asked: “Write a dialogue that Lamar Davis would say in GTA 5 about Salesforce flows<\/strong>.”<\/p>\n\n\n\n

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

        Lamar: “Yo, have you seen those Salesforce flows? They’re like a bunch of little automation scripts, all connected together in one big flowy thing. You can use them to automate all kinds of processes, like creating records, updating fields, and sending notifications. It’s like a whole other level of hustling, right there in your Salesforce org.”<\/p>\n\n\n\n

        That does resemble Lamar, maybe after getting some Trailhead badges.<\/p>\n\n\n\n

        Then I’ve tried another Seinfeld routine: “Write a Seinfeld routine about Salesforce flows<\/strong>.”<\/p>\n\n\n\n

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

        Amusing! I would like to see what results others got!<\/p>\n","protected":false},"excerpt":{"rendered":"

        ChatGPT is a prototype artificial intelligence chatbot designed by OpenAI to understand natural human language and generate written text that closely resembles human writing. I’ve played with ChatGPT for a little while to create a Salesforce trigger and will tell the results but, first, the routine it gave me when I’ve asked “Write a Seinfeld […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-678","post","type-post","status-publish","format-standard","hentry","category-blog"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/posts\/678","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/comments?post=678"}],"version-history":[{"count":1,"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/posts\/678\/revisions"}],"predecessor-version":[{"id":690,"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/posts\/678\/revisions\/690"}],"wp:attachment":[{"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/media?parent=678"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/categories?post=678"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.felineflock.com\/index.php\/wp-json\/wp\/v2\/tags?post=678"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}