fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

8.8K
active users

#summer23

0 posts0 participants0 posts today
Helena Jambor 💔 🇮🇱 🇺🇦<p>We were sailing on Plöner See, Schleswig Holstein - a wonderful family sailing course at the Youth Hostel Plön! </p><p><a href="https://vis.social/tags/urbansketching" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>urbansketching</span></a> <a href="https://vis.social/tags/Summer23" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Summer23</span></a> <a href="https://vis.social/tags/watercolour" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>watercolour</span></a> <a href="https://vis.social/tags/Sketch" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sketch</span></a> <a href="https://vis.social/tags/sketchbook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sketchbook</span></a></p>
Helena Jambor 💔 🇮🇱 🇺🇦<p>View of Elbe in Elbsandsteingebirge, Schmilka, terasse of Biohotel Helvetia. </p><p><a href="https://vis.social/tags/urbansketching" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>urbansketching</span></a> <a href="https://vis.social/tags/Summer23" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Summer23</span></a> <a href="https://vis.social/tags/watercolour" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>watercolour</span></a> <a href="https://vis.social/tags/Sketch" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sketch</span></a> <a href="https://vis.social/tags/sketchbook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sketchbook</span></a></p>
Helena Jambor 💔 🇮🇱 🇺🇦<p>Off topic: in summer I keep a sketch-diary - helps me remember the obscure and beautiful. <br>This years book is almost full, so here a few outtakes <a href="https://vis.social/tags/urbansketching" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>urbansketching</span></a> that I liked! </p><p><a href="https://vis.social/tags/Summer23" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Summer23</span></a> <a href="https://vis.social/tags/watercolour" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>watercolour</span></a> <a href="https://vis.social/tags/Sketch" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sketch</span></a> <a href="https://vis.social/tags/sketchbook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sketchbook</span></a></p>
Stoney Takes<p>Little known fact: Page and Mike are on coffee shop tour befriending random baristas along the way <a href="https://heads.social/tags/goodfellas" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>goodfellas</span></a> <a href="https://heads.social/tags/phish" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>phish</span></a> <a href="https://heads.social/tags/summer23" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>summer23</span></a> <a href="https://heads.social/tags/yemsg" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>yemsg</span></a></p>
Bastian Ilso<p>Summer vacation 2023: indoor camping</p><p><a href="https://mastodon.art/tags/camping" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>camping</span></a> <a href="https://mastodon.art/tags/summer23" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>summer23</span></a> <a href="https://mastodon.art/tags/vacation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vacation</span></a></p>
Andy Engin Utkan<p><strong>HTTP Callout in Salesforce Summer 23 – POST – 1/3</strong></p><p>HTTP Callout in Spring 23 got many people excited. The blog post and the video by <a href="https://www.linkedin.com/in/joshdayment/" rel="nofollow noopener" target="_blank">Josh Dayment</a> and I drew quite some attention. We heard one criticism for this functionality: the solution was incomplete without the POST method.</p><p>With Summer 23, the Salesforce Flow Product Team not only moves the GET method to GA, but also gives us the POST method in Beta.</p><p class=""></p> <span class=""></span>🚨 Use case 👇🏼<p></p><p class="">The use case we picked for this demo is based on a real-life client requirement. The client wants to shorten the long URL links before they send them to customers via email or text. Text (SMS) requirement is very important because we cannot hide the long URL behind a short label there since SMS does not support rich text. I don’t have texting set up in my preview Org, therefore, I will demo this using email.</p> <p><strong>The solution consists of many parts. The list is as follows:</strong></p><ul><li>Bit.ly is the service that supports an API with a POST method to shorten URLs. We will need an account with Bit.ly. The good thing is they allow us to use the service for free until we reach a certain number. (1)</li><li>A record-triggered flow with an async path that uses the HTTP callout to Bit.ly to shorten the URL (2)</li><li>A public digital experience (community) site that houses a screen flow to display the critical field values for the Opportunity (3)</li><li>A screen flow that runs at system context without sharing to show the critical Opportunity field values on the community site. (4)</li><li>A simple record-triggered flow to create the long URL on the record (this can also be a formula field) (5)</li><li>A simple record-triggered flow that generates the email with the short link. (6)</li></ul><p>And a few custom fields on the Opportunity object: <em>URL</em> (long) and <em>Short URL</em> text fields and a <em>Short URL Requested</em> checkbox field.</p><p>First, we go to Bit.ly to create a free account. They have API documentation available. However, I cannot say the documentation is very clear. Here is the relevant settings page we need to create the access token for the API.</p><p>*<em>I wiped my values from the screenshot; you will need to copy yours by going to this screen.</em></p><p>We will come back to this later.</p><p>Let’s walk you through the flow that will execute the HTTP Callout.</p><p>Create these custom fields on the Opportunity object:</p><p><em>URL</em> (Text)</p><p><em>Short URL</em> (Text)</p><p><em>Short URL Requested</em> (Checkbox)</p><p>Then create the HTTP callout async record-triggered flow.</p><p><strong>This is how the flow looks after it is completed.</strong></p><p><strong>Set up the start element as follows.</strong></p><p><strong>Build an assignment element to assign field values.</strong></p><p>You will assign the input parameters Bit.ly API needs to the Apex defined variable that the “Create HTTP Callout” builder provides us. Initially, enter a fixed URL here, such as SalesforceBreak.com, until you can get the flow to work without issues.</p><p><strong>Get your group Id from Bit.ly from your browser address bar when you display this screen here.</strong></p><p><strong>The only input parameter that the callout action needs is the Apex defined variable.</strong></p><p><strong>The short URL is again inside an Apex defined variable under 2XX&gt;link.</strong></p><p>We will update this value to the short URL custom field of the Opportunity record.</p><p>But you can do all this after properly creating your HTTP callout action. And that requires a few steps.</p><p>The introduction of HTTP Callout in Salesforce Flow during Spring ’23 generated a lot of excitement, but one key limitation was the absence of the POST method. With Summer ’23, Salesforce not only moved the GET method to General Availability (GA) but also introduced the POST method in Beta, addressing a major user request.</p><p>To demonstrate the real-world application of this new functionality, a use case was chosen based on a client requirement: shortening long URLs before sending them via email or SMS. Since SMS does not support rich text formatting, a short URL is essential to improve readability. Bit.ly’s API, which supports a POST request to generate short links, was used for this purpose.</p><p><a href="https://salesforcebreak.com/2023/06/03/http-callout-in-salesforce-summer-23-post-beta-2-3" rel="nofollow noopener" target="_blank">Please continue to the second post by clicking here.</a></p><p>Explore related content:</p><p><a href="https://salesforcebreak.com/2023/06/03/http-callout-in-salesforce-summer-23-post-beta-2-3" rel="nofollow noopener" target="_blank">Create HTTP Callout – POST 2/3</a></p><p><a href="https://salesforcebreak.com/2023/06/03/http-callout-in-salesforce-summer-23-post-beta-3-3/" rel="nofollow noopener" target="_blank">Create HTTP Callout – POST 3/3</a></p><p><a href="https://salesforcebreak.com/2023/01/10/http-callout-beta-in-salesforce-spring-23/" rel="nofollow noopener" target="_blank">Create HTTP Callout – GET</a></p><p><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://salesforcebreak.com/tag/api/" target="_blank">#API</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://salesforcebreak.com/tag/automation/" target="_blank">#Automation</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://salesforcebreak.com/tag/http-callout/" target="_blank">#HTTPCallout</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://salesforcebreak.com/tag/release/" target="_blank">#Release</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://salesforcebreak.com/tag/salesforce/" target="_blank">#Salesforce</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://salesforcebreak.com/tag/summer23/" target="_blank">#Summer23</a></p>
Andy Engin Utkan<p><strong>HTTP Callout in Salesforce Summer 23 – POST – 3/3</strong></p><p>Welcome to the final installment of our three-part series on configuring Salesforce flows within a community site. In this post, we focus on a flow that utilizes HTTP Callout to fetch and display Opportunity details using a record ID. This setup ensures streamlined access to essential data through a user-friendly interface, all running in the System context without sharing for enhanced security.</p><p>Join us as we walk you through the integration of this flow into your digital experience, emphasizing the role of URL parameter handling and the utilization of HTTP Callout for secure data retrieval. We’ll also demonstrate how to automate email notifications with dynamic links. We value your feedback—please let us know if you need more detailed information on any of the steps!</p><p>Now, you will build the flow you will host on the community (digital experience) site.</p><p>Important note: We will set this flow up to run at the System context without sharing under the <a href="https://help.salesforce.com/s/articleView?id=release-notes.rn_forcecom_flow_fbuilder_flowtype.htm&amp;release=222&amp;type=5" rel="nofollow noopener" target="_blank">Advanced Flow settings</a>.</p><p>This simple flow gets an opportunity using the record Id as input and displays critical field values on the screen. Note that the system builds a decision to handle cases where the recordId input is missing or invalid.</p><p><strong>Here is what the Display Text component looks like in the Screen Element.</strong></p><p>Once you complete your flow and activate it, create a public community (digital experience) site and add your flow to the main page. Several steps must be followed to set up guest user access properly. We will not go into these steps in this post. <em>Comment below if you need a follow-up post with detailed steps, please.</em></p><p>Once you set up your community, you can pass the recordId as a URL parameter to your flow to see the Opportunity record field values on your screen. You see the long URL in the browser address bar below.</p><p><strong>Now, set up a simple record-triggered flow to populate the URL (long URL) field on the Opportunity record. Here is how you do it.</strong></p><p>Now set up another record-triggered flow to send an email with the short URL to the owner of the record.</p><p><strong>Your email action looks like this in Summer 23 (Yay!).</strong></p><p><strong>Your email body text template will look like this.</strong></p><p><strong>Your email will look can be seen in the image below.</strong></p><p>You may think it is silly to shorten the URL by looking at this since we can hide it in an HTML email. That is correct, however, the actual value add is when you need to text (SMS) the link. Short URL looks much better.</p><p><strong>After debugging and activating all your flows, you can create a new Opportunity like the one below.</strong></p><p><em>Hint: Cloning and modifying a few field values work well when testing.</em></p><p><strong>Voila: The system has populated your long URL and short URL, and sent the email to the record owner’s email inbox.</strong></p><p>Enjoy</p><p>Note: These posts were written as a result of a collaboration between Josh Dayment and Andy Engin Utkan. I want to thank Josh Dayment for his relentless efforts and countless trials to get this demo to work.</p><p>Explore related content:</p><p><a href="https://salesforcebreak.com/2023/05/30/http-callout-in-salesforce-summer-23-post-beta-1-3" rel="nofollow noopener" target="_blank">Create HTTP Callout – POST 1/3</a></p><p><a href="https://salesforcebreak.com/2023/06/03/http-callout-in-salesforce-summer-23-post-beta-2-3" rel="nofollow noopener" target="_blank">Create HTTP Callout – POST 2/3</a></p><p><a href="https://salesforcebreak.com/2023/01/10/http-callout-beta-in-salesforce-spring-23/" rel="nofollow noopener" target="_blank">Create HTTP Callout – GET</a></p><p><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://salesforcebreak.com/tag/api/" target="_blank">#API</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://salesforcebreak.com/tag/automation/" target="_blank">#Automation</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://salesforcebreak.com/tag/http-callout/" target="_blank">#HTTPCallout</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://salesforcebreak.com/tag/release/" target="_blank">#Release</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://salesforcebreak.com/tag/salesforce/" target="_blank">#Salesforce</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://salesforcebreak.com/tag/summer23/" target="_blank">#Summer23</a></p>
Chris<p>A Simple but eye-pleasing update to dynamic forms in the <a href="https://fosstodon.org/tags/Salesforce" class="mention hashtag" rel="tag">#<span>Salesforce</span></a> <a href="https://fosstodon.org/tags/Summer23" class="mention hashtag" rel="tag">#<span>Summer23</span></a> pre-release.</p><p>A align fields horizontally checkbox on field sections keeps the fields at the same height, so fields don&#39;t look slightly off due to differences in their size. </p><p><a href="https://fosstodon.org/tags/Summer23TreasureHunt" class="mention hashtag" rel="tag">#<span>Summer23TreasureHunt</span></a></p>
SP Rupert<p>There’s only 209 days until the 4th of July! There’s plenty of time to work on your beach bod.</p><p><a href="https://universeodon.com/tags/4thOfJuly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>4thOfJuly</span></a> <a href="https://universeodon.com/tags/beachbod" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>beachbod</span></a> <a href="https://universeodon.com/tags/summer23" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>summer23</span></a> <a href="https://universeodon.com/tags/vacation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vacation</span></a></p>