<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Salesforce 101 on Medium]]></title>
        <description><![CDATA[Stories by Salesforce 101 on Medium]]></description>
        <link>https://medium.com/@road.to.salesforce?source=rss-ff06d0e9dd32------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*O_HELlxsnzT_6Mv_7WvQQg.png</url>
            <title>Stories by Salesforce 101 on Medium</title>
            <link>https://medium.com/@road.to.salesforce?source=rss-ff06d0e9dd32------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:27:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@road.to.salesforce/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[SF Bank Users Schema]]></title>
            <link>https://medium.com/@road.to.salesforce/sf-bank-users-schema-56e8fa116ca4?source=rss-ff06d0e9dd32------2</link>
            <guid isPermaLink="false">https://medium.com/p/56e8fa116ca4</guid>
            <category><![CDATA[bank-users]]></category>
            <dc:creator><![CDATA[Salesforce 101]]></dc:creator>
            <pubDate>Mon, 21 Sep 2026 11:10:41 GMT</pubDate>
            <atom:updated>2026-09-21T11:10:41.027Z</atom:updated>
            <content:encoded><![CDATA[<p>Here’s the full picture, consolidated into one schema.</p><h3>The User Pool — 4 Categories</h3><h3>1. External users — the bank’s own customers (via Experience Cloud)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*bpKyWkLCQPS5a2rE829Bhg.png" /></figure><h3>2. Internal users — bank employees, inside core Salesforce</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*nuDzAClgjhOXlMHwPdj6bg.png" /></figure><h3>3. Partner users (if applicable, via Partner Community)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*8KIiuAvYGdc2KGIFxt31iA.png" /></figure><h3>4. System/integration users (technical accounts, not human)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/945/1*AdL0cCAzPjepYtugVPdNCA.png" /></figure><h3>Plus — specific to you as a vendor (not the bank itself)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/927/1*2uTW3qw0KxMgN_lABuGgtg.png" /></figure><p><strong>Key distinctions to keep in your design:</strong></p><ul><li><strong>Human vs. system</strong>: personas 1–3 and the vendor row are people (need UX, permissions, journeys); category 4 is service accounts (need security architecture — least privilege, rotation, monitoring, audit trails)</li><li><strong>Whose employee</strong>: bank employee vs. bank customer vs. partner vs. your own company — each has a different trust boundary and licensing model in Salesforce</li><li><strong>License type</strong>: internal users need full/platform Salesforce licenses; external and partner users use Experience Cloud licenses (cheaper, more restricted); integration users often need dedicated API-only licenses or Connected App permission sets</li></ul><p>Want me to turn this into a visual diagram (trust boundaries, data flow between the four categories) so it’s easier to present to stakeholders?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56e8fa116ca4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SLDS 2.0 Migration | Bad Code Sample | Effort & Time-to-Transition Estimation]]></title>
            <link>https://medium.com/@road.to.salesforce/slds-2-0-migration-bad-code-sample-effort-time-to-transition-estimation-80ba5b97f2c4?source=rss-ff06d0e9dd32------2</link>
            <guid isPermaLink="false">https://medium.com/p/80ba5b97f2c4</guid>
            <category><![CDATA[slds-2]]></category>
            <category><![CDATA[cosmos-theme]]></category>
            <category><![CDATA[salesforce-design-system]]></category>
            <category><![CDATA[slds-transition]]></category>
            <category><![CDATA[sld]]></category>
            <dc:creator><![CDATA[Salesforce 101]]></dc:creator>
            <pubDate>Mon, 31 Aug 2026 23:12:25 GMT</pubDate>
            <atom:updated>2026-08-31T23:12:25.463Z</atom:updated>
            <content:encoded><![CDATA[<p>f you want to justify<strong>”higher effort”</strong> for an SLDS 2.0 migration, the best examples are custom components that bypass SLDS tokens and styling hooks by using hardcoded CSS and component overrides. Salesforce specifically highlights transitioning away from legacy styling patterns toward SLDS-supported mechanisms.</p><h3>Example 1: Hard-coded colors (Bad)</h3><pre>&lt;!-- accountCard.html --&gt;<br>&lt;div class=&quot;account-header&quot;&gt;<br>    &lt;h2&gt;{accountName}&lt;/h2&gt;<br>&lt;/div&gt;<br><br>{accountName}<br><br>/* accountCard.css */<br><br>.account-header {<br>background: #1589ee;<br>color: #ffffff;<br>padding: 16px;<br>}</pre><p><strong>Why this increases migration effort</strong></p><ul><li>Color is hardcoded.</li><li>Doesn’t use SLDS styling hooks or design tokens.</li><li>Must be manually reviewed and replaced.</li></ul><h3>Example 2: Overriding Standard SLDS Classes (Bad)</h3><pre>.slds-button_brand {<br>    background-color: red !important;<br>    border-color: red !important;<br>    border-radius: 0 !important;<br>}</pre><h3>Example 3: Custom Button Instead of Lightning Base Component</h3><pre>&lt;button class=&quot;my-custom-button&quot;&gt;<br>    Save<br>&lt;/button&gt;</pre><pre>.my-custom-button {<br>    background: #0176d3;<br>    color: white;<br>    padding: 12px 24px;<br>    border: none;<br>}</pre><p>Instead of:</p><pre>&lt;lightning-button<br>    label=&quot;Save&quot;<br>    variant=&quot;brand&quot;&gt;<br>&lt;/lightning-button&gt;</pre><p><strong>Migration impact</strong></p><ul><li>Every custom button must be assessed.</li><li>Standard Lightning components usually transition with much less effort.</li></ul><h3>Example 4: Deep DOM Overrides (Very Bad)</h3><pre>lightning-card .slds-card__header-title {<br>    font-size: 22px !important;<br>    color: #444 !important;<br>}</pre><p><strong>Migration impact</strong></p><ul><li>Depends on Salesforce’s internal markup.</li><li>Internal structure can change during migrations.</li><li>Common source of regressions.</li></ul><h3>Example 5: Aura Component with Legacy Styling</h3><pre>&lt;aura:component&gt;<br>    &lt;div class=&quot;legacyHeader&quot;&gt;<br>        {!v.title}<br>    &lt;/div&gt;<br>&lt;/aura:component&gt;<br><br>{!v.title}</pre><pre>.THIS .legacyHeader {<br>    background: #f3f3f3;<br>    border-bottom: 2px solid #999;<br>    font-family: Arial;<br>    padding: 20px;<br>}</pre><p><strong>Migration impact</strong></p><ul><li>Aura components often require additional review.</li><li>Hardcoded styling and non-SLDS patterns increase refactoring effort.</li></ul><h3>Suggested wording for your estimation</h3><blockquote><em>The migration effort is expected to increase for components that rely on hard-coded CSS values, direct overrides of SLDS classes, custom-built alternatives to Lightning Base Components, legacy Aura implementations, or styling that depends on Salesforce internal DOM structures. Such components require manual analysis, refactoring, and regression testing to ensure compatibility with SLDS 2.0.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80ba5b97f2c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Essay 1 — Ilayda]]></title>
            <link>https://medium.com/@road.to.salesforce/essay-1-ilayda-90f21264853f?source=rss-ff06d0e9dd32------2</link>
            <guid isPermaLink="false">https://medium.com/p/90f21264853f</guid>
            <dc:creator><![CDATA[Salesforce 101]]></dc:creator>
            <pubDate>Mon, 04 May 2026 20:23:58 GMT</pubDate>
            <atom:updated>2026-05-04T20:23:58.819Z</atom:updated>
            <content:encoded><![CDATA[<h3>Social Media</h3><p>Nowadays, many people use social Media. Almost everyone send a photo, like a video, share a story everyday. Social Media has become an important part of our life. Social Media use is begins between the ages of 8 and 10. young people grow up with internet and social Media. They are doing what they see on social Media. Parents sometimes check in their social Media. In this essay, I will explore the positive effects social Media for young people in two areas of our lives such as learning new things and have a fun day.</p><p>Firstly; young people learn new things on social Media. for example; what’s happening in the world, digits of pi or culture of a country… When they choose what they will want to travel in the world, in that case they can learn where to go, what to eat and where to stay. Social Media is a library for us to use.</p><p>Secondly; daily life can sometimes be boring, young people can usually be tired during the day. They want to sit somewhere in that case, they surf the social Media. they watch video, listen to music in social Media. for instance: I love watch the cats’ video and movie. When I watch its, I feel better.</p><p>In Conclusion; Social Media is quite necessary and important in the world’s everywhere. Social Media has advantages effects on young people. they learn new things and have a fun day thanks to social Media.</p><p>Yapay Zeka yorumlari;</p><h3>1️⃣ Genel İzlenim (Jüri Gözüyle)</h3><p>Bu essay şunu net gösteriyor:</p><p>✅ Konuyu anlıyorsun<br> ✅ Essay yapısını biliyorsun (introduction–body–conclusion)<br> ✅ Fikir üretmekte zorlanmıyorsun<br> ✅ Günlük İngilizce ile kendini ifade edebiliyorsun</p><p>❌ Ancak dil bilgisi ve akademik writing kuralları zayıf<br> ❌ Cümle yapıları Türkçe mantığıyla kurulmuş<br> ❌ Bağlaç, zaman ve çoğul kullanımı sık hata içeriyor</p><blockquote><strong><em>Yani:</em></strong><em> Bu yazı </em>“başlangıç–orta seviye (A2–B1 sınırı)”<em> bir aday profili çiziyor.</em></blockquote><h3>2️⃣ Değerlendirme Kriterlerine Göre Analiz</h3><h3>📌 1. Task Response (Konuya Uygunluk) — ✅ İyi</h3><ul><li>Soruya cevap veriyorsun</li><li>“Positive effects” konusuna sadıksın</li><li>İki ayrı fikir sunuyorsun (learning &amp; fun)</li></ul><p>🔹 <strong>Jüri yorumu:</strong></p><blockquote><em>“The candidate understands the task and addresses it clearly.”</em></blockquote><p>✅ <strong>Artı puan</strong></p><h3>📌 2. Coherence &amp; Cohesion (Düzen — Akış) — ⚠️ Orta</h3><p>Artılar:</p><ul><li>Paragraph yapısı var</li><li>Firstly / Secondly / In conclusion kullanılmış</li></ul><p>Eksiler:</p><ul><li>Noktalama ve büyük harf kullanımı hatalı</li><li>Cümleler bazen birbirine iyi bağlanmıyor</li><li>“In that case” gibi ifadeler fazla tekrar</li></ul><p>🔹 <strong>Jüri yorumu:</strong></p><blockquote><em>“Ideas are organized, but cohesion is weak and mechanical.”</em></blockquote><h3>📌 3. Vocabulary (Kelime Bilgisi) — ⚠️ Orta</h3><p>Olumlu:</p><ul><li>Günlük kelimeler doğru yerde</li><li>Anlaşılır kelime seçimi</li></ul><p>Geliştirilmesi gerekenler:</p><ul><li>Aynı kelimeler çok tekrar ediliyor<br> (social media, learn, things)</li><li>Yanlış kelime kullanımı:</li><li><em>advantages effects</em></li><li><em>have a fun day</em></li><li><em>world’s everywhere</em></li></ul><p>🔹 <strong>Jüri yorumu:</strong></p><blockquote><em>“Vocabulary is limited but generally understandable.”</em></blockquote><h3>📌 4. Grammar (Dil Bilgisi) — ❌ Zayıf (En Kritik Alan)</h3><p>Bu bölüm puanı en çok düşüren kısım.</p><p>🟥 Sık görülen hatalar:</p><ul><li><strong>Özne–yüklem uyumu:</strong><br> <em>Almost everyone send</em> ❌</li><li><strong>Zaman yapıları:</strong><br> <em>Social Media use is begins</em> ❌</li><li><strong>Article kullanımı:</strong><br> <em>use internet</em>, <em>watch video</em> ❌</li><li><strong>Büyük harf / küçük harf:</strong><br> <em>young people</em>, <em>for example</em> ❌</li></ul><p>🔹 <strong>Jüri yorumu:</strong></p><blockquote><em>“Frequent grammatical errors reduce clarity, though meaning is usually clear.”</em></blockquote><h3>3️⃣ Tahmini Sınav Puanı</h3><blockquote><em>🔔 </em><strong><em>Şeffaf olayım:</em></strong><em> Aşağıdaki puan </em>gerçekçi<em> ve </em>öğretici<em>.</em></blockquote><h3>📊 Genel Değerlendirme</h3><ul><li><strong>CEFR seviyesi:</strong> <strong>A2+ / B1‑</strong></li><li><strong>IELTS Writing Task 2 karşılığı:</strong><br> 👉 <strong>Band 4.5–5.0</strong></li></ul><p>🔹 Bu ne demek?</p><ul><li>Geçer ama güçlü değil</li><li>Üniversite / ciddi sınav için <strong>yetersiz</strong></li><li>Gelişim potansiyeli <strong>yüksek</strong></li></ul><h3>4️⃣ Seni En Hızlı Geliştirecek 5 Net Tavsiye</h3><h3>✅ 1. Basit ama doğru cümle kur</h3><p>👉 Uzun cümle kurmaya çalışma.</p><blockquote><em>Short + correct &gt; long + wrong</em></blockquote><h3>✅ 2. Article (a / an / the) çalış</h3><p>Bu essay’de <strong>en çok puan kaybı buradan</strong>.</p><h3>✅ 3. Akademik kalıplar ezberle</h3><p>Örnek:</p><ul><li>One of the main advantages is…</li><li>As a result,</li><li>For example,</li></ul><h3>✅ 4. Türkçe düşünerek yazma</h3><blockquote><em>“In that case” → Türkçe çeviri kokuyor<br> Bunun yerine:</em></blockquote><ul><li>Therefore</li><li>Because of this</li></ul><h3>✅ 5. Her essay’de aynı checklist</h3><p>Yazdıktan sonra şunları kontrol et: ✔ Her cümlede verb var mı?<br> ✔ Third person “-s” var mı?<br> ✔ Cümle büyük harfle başlıyor mu?</p><h3>Son Söz (Samimi Geri Bildirim)</h3><p>Bu yazı <strong>kötü değil</strong>, <strong>ham</strong>.<br> Düzenli çalışmayla <strong>2–3 ayda rahat B1+</strong>,<br> <strong>6 ayda B2</strong> seviyesine çıkabilecek bir temel var.</p><p>Harika, şimdi <strong>öğretici geri bildirim moduna</strong> geçiyoruz.<br> Aşağıda yazını <strong>adım adım</strong>, <strong>cümle cümle</strong> ele alacağım.</p><p>🔹 <strong>Yöntemim:</strong></p><ul><li><strong>Original</strong> → senin cümlen</li><li><strong>Corrected</strong> → sınavda puan kazandıran hali</li><li><strong>Why?</strong> → <em>neden böyle olması gerekiyor</em> (kısa + net)</li></ul><blockquote><em>Amaç: </em><strong><em>aynı hatayı tekrar etmemen</em></strong><em><br> Ezber değil, </em>mantık<em> öğreneceksin.</em></blockquote><h3>🟦 INTRODUCTION (Giriş Paragrafı)</h3><h3>1️⃣</h3><p><strong>Original:</strong></p><blockquote><em>Nowadays, many people use social Media.</em></blockquote><p>✅ <strong>Corrected:</strong></p><blockquote><em>Nowadays, many people use social media.</em></blockquote><p>🧠 <strong>Why?</strong></p><ul><li><em>Social media</em> <strong>özel isim değil</strong> → büyük harf kullanılmaz<br> ✅ Bu tür hatalar küçük ama <strong>sürekli puan düşürür</strong></li></ul><h3>2️⃣</h3><p><strong>Original:</strong></p><blockquote><em>Almost everyone send a photo, like a video, share a story everyday.</em></blockquote><p>✅ <strong>Corrected:</strong></p><blockquote><em>Almost everyone sends a photo, likes a video, and shares a story every day.</em></blockquote><p>🧠 <strong>Why?</strong></p><ul><li><em>Everyone</em> → <strong>3rd person singular</strong> → s şart</li><li><em>everyday</em> ❌ (sıfat)</li><li><em>every day</em> ✅ (zaman ifadesi)</li></ul><p>📌 <strong>ALTIN KURAL:</strong></p><blockquote><em>everyone / someone / nobody → </em><strong><em>verb + s</em></strong></blockquote><h3>3️</h3><p><strong>Original:</strong></p><blockquote><em>Social Media use is begins between the ages of 8 and 10.</em></blockquote><p>✅ <strong>Corrected:</strong></p><blockquote><em>Social media use begins between the ages of 8 and 10.</em></blockquote><p>🧠 <strong>Why?</strong></p><ul><li>is + begins ❌ → <strong>çift yüklem hatası</strong></li><li>Basit gerçek → <strong>Present Simple</strong></li></ul><h3>4️⃣</h3><p><strong>Original:</strong></p><blockquote><em>young people grow up with internet and social Media.</em></blockquote><p>✅ <strong>Corrected:</strong></p><blockquote><em>Young people grow up with the internet and social media.</em></blockquote><p>🧠 <strong>Why?</strong></p><ul><li>Cümle <strong>büyük harfle başlar</strong></li><li><em>the internet</em> → sabit kullanım</li></ul><h3>5️</h3><p><strong>Original:</strong></p><blockquote><em>In this essay, I will explore the positive effects social Media for young people…</em></blockquote><p>✅ <strong>Corrected:</strong></p><blockquote><em>In this essay, I will explore the positive effects of social media on young people</em></blockquote><p>🧠 <strong>Why?</strong></p><ul><li><em>effects OF something</em></li><li><em>effects ON someone</em></li></ul><p>📌 <strong>Sınav fav:</strong></p><blockquote><em>effects </em><strong><em>of</em></strong><em> X </em><strong><em>on</em></strong><em> Y</em></blockquote><h3>🟦 BODY PARAGRAPH 1 (Learning)</h3><h3>6️⃣</h3><p><strong>Original:</strong></p><blockquote><em>Firstly; young people learn new things on social Media.</em></blockquote><p>✅ <strong>Corrected:</strong></p><blockquote><em>Firstly, young people learn new things on social media.</em></blockquote><p>🧠 <strong>Why?</strong></p><ul><li>Essay’de ; ❌</li><li>Firstly, ✅</li></ul><h3>7️⃣</h3><p><strong>Original:</strong></p><blockquote><em>for example; what’s happening in the world…</em></blockquote><p>✅ <strong>Corrected:</strong></p><blockquote><em>For example, they can learn what is happening in the world…</em></blockquote><p>🧠 <strong>Why?</strong></p><ul><li>Cümle büyük harf</li><li>Essay’de <strong>tam cümle şart</strong></li></ul><h3>8️⃣</h3><p><strong>Original:</strong></p><blockquote><em>Social Media is a library for us to use.</em></blockquote><p>✅ <strong>Corrected:</strong></p><blockquote><em>Social media is like a library that we can use.</em></blockquote><p>🧠 <strong>Why?</strong></p><ul><li>Benzetme → <strong>like</strong></li><li>Daha akademik ve doğal</li></ul><h3>🟦 BODY PARAGRAPH 2 (Fun)</h3><h3>9️</h3><p><strong>Original:</strong></p><blockquote><em>They want to sit somewhere in that case, they surf the social Media.</em></blockquote><p>✅ <strong>Corrected:</strong></p><blockquote><em>When they want to sit and relax, they surf social media.</em></blockquote><p>🧠 <strong>Why?</strong></p><ul><li><em>in that case</em> → <strong>Türkçe düşünce</strong></li><li>İngilizce sade sever</li></ul><p>📌 <strong>Sınav uyarısı:</strong></p><blockquote><em>Türkçe bağlaç çevirisi = 🚨</em></blockquote><h3>🔟</h3><p><strong>Original:</strong></p><blockquote><em>I love watch the cats’ video and movie.</em></blockquote><p>✅ <strong>Corrected:</strong></p><blockquote><em>I love watching cat videos and movies.</em></blockquote><p>🧠 <strong>Why?</strong></p><ul><li><em>love + verb + ing</em></li><li><em>cats’ video</em> ❌</li><li>Genel kullanım → <strong>cat videos</strong></li></ul><h3>🟦 CONCLUSION</h3><h3>1️⃣1️⃣</h3><p><strong>Original:</strong></p><blockquote><em>Social Media has advantages effects on young people.</em></blockquote><p>✅ <strong>Corrected:</strong></p><blockquote><em>Social media has positive effects on young people.</em></blockquote><p>🧠 <strong>Why?</strong></p><ul><li><em>advantages effects</em> ❌<br> ✅ <em>positive effects</em></li></ul><h3>1️⃣2️⃣</h3><p><strong>Original:</strong></p><blockquote><em>have a fun day thanks to social Media.</em></blockquote><p>✅ <strong>Corrected:</strong></p><blockquote><em>have fun thanks to social media.</em></blockquote><p>🧠 <strong>Why?</strong></p><ul><li><em>have fun</em> → sabit ifade</li><li><em>a fun day</em> = konuşma dili, essay’de zayıf</li></ul><h3>🎯 GENEL GELİŞİM ÖZETİ</h3><h3>En çok puan kaybettiren 3 şey:</h3><ol><li>❌ <strong>Third person -s</strong></li><li>❌ <strong>Article (a / the)</strong></li><li>❌ Türkçe düşünce kalıpları</li></ol><h3>Ama büyük avantajın:</h3><p>✅ Yapıyı biliyorsun<br> ✅ Fikir üretme sorunun yok<br> ✅ Essay korkun yok → bu çok önemli</p><h3>📈 Tahmini yeni puanın</h3><p>Bu düzeltmelerle yazsan:</p><p>🔹 <strong>IELTS Writing:</strong> <strong>5.5–6.0</strong><br> 🔹 <strong>CEFR:</strong> <strong>B1 → B1+</strong></p><h3>🟩 BEN YAZSAYDIM — UPGRADED ESSAY (Band 6–6.5 seviyesi)</h3><h3>The Positive Effects of Social Media on Young People</h3><p>Nowadays, social media plays an important role in people’s daily lives. Many individuals use social media platforms to share photos, watch videos, and communicate with others. As social media use often begins at a young age, it strongly influences how young people think and behave. In this essay, I will discuss the positive effects of social media on young people, focusing on learning new things and entertainment.</p><p>One of the main advantages of social media is that it helps young people learn new information. Through social media, they can easily follow world news, discover interesting facts, and learn about the cultures of different countries. In addition, when young people plan to travel, social media allows them to find information about popular destinations, local food, and accommodation. Therefore, social media can be considered a valuable source of knowledge.</p><p>Another positive effect of social media is entertainment. Daily life can sometimes be stressful or boring, especially for young people who are tired after school or work. In their free time, many young people use social media to relax by watching videos or listening to music. For example, watching funny animal videos can improve their mood and help them feel more positive. As a result, social media can support mental relaxation.</p><p>In conclusion, social media has several positive effects on young people. It helps them gain new knowledge and also provides entertainment in their daily lives. When used in a balanced and responsible way, social media can be a beneficial part of modern life.</p><h3>🟦 ŞİMDİ ASIL ÖĞRETİCİ KISIM: NASIL UPGRADE ETTİM?</h3><p>Aşağıda, senin yazınla benim yazım arasındaki <strong>kritik farkları</strong> açıklıyorum.</p><h3>1️⃣ GİRİŞ PARAGRAFI — Daha Akademik Başlangıç</h3><h3>Sen:</h3><blockquote><em>Nowadays, many people use social Media.</em></blockquote><h3>Ben:</h3><blockquote><em>Nowadays, social media plays an important role in people’s daily lives.</em></blockquote><p>🔑 <strong>Neden?</strong></p><ul><li>“Many people use…” → çok basit, zayıf</li><li>“plays an important role” → <strong>examiner’ın sevdiği kalıp</strong></li></ul><p>✅ <strong>Ezberle:</strong></p><blockquote><em>X plays an important role in modern society.</em></blockquote><h3>2️⃣ TEKRARI AZALTTIM, AKADEMİK KALIPLAR EKLEDİM</h3><h3>Sen çok tekrar ediyorsun:</h3><blockquote><em>Social Media … Social Media … Social Media …</em></blockquote><h3>Ben ne yaptım?</h3><ul><li>social media platforms</li><li>it</li><li>this technology</li></ul><p>📌 <strong>Examiner yorumu:</strong></p><blockquote><em>“Good range of vocabulary with less repetition.”</em></blockquote><h3>3️⃣ “Firstly / Secondly” YERİNE DAHA GÜÇLÜ BAŞLANGIÇLAR</h3><h3>Sen:</h3><blockquote><em>Firstly; young people learn new things…</em></blockquote><h3>Ben:</h3><blockquote><em>One of the main advantages of social media is that…</em></blockquote><p>✅ Bu yapı <strong>B1+ → B2 geçiş kapısıdır</strong></p><h3>4️⃣ TÜRKÇE DÜŞÜNCELERİ İNGİLİZCE MANTIĞA ÇEVDİM</h3><h3>Sen:</h3><blockquote><em>in that case they surf the social Media</em></blockquote><h3>Ben:</h3><blockquote><em>In their free time, many young people use social media to relax</em></blockquote><p>🔑 İngilizce:</p><ul><li><strong>daha az bağlaç</strong></li><li><strong>daha net amaç</strong></li></ul><h3>5️⃣ ÖRNEK VERMEYİ DAHA AKADEMİK YAPTIM</h3><h3>Sen:</h3><blockquote><em>I love watch the cats’ video</em></blockquote><h3>Ben:</h3><blockquote><em>For example, watching funny animal videos can improve their mood</em></blockquote><p>✅ Kişisel örnek → <strong>genelleştirildi</strong> ✅ Duygu → <strong>akademik dille ifade edildi</strong></p><h3>6️⃣ CONCLUSION = PUAN KİLİDİ</h3><p>Ben conclusion’da şunları yaptım:</p><ul><li>Tekrar yok</li><li>Yeni fikir yok</li><li>Güçlü kapanış cümlesi var</li></ul><p>✅ <strong>Examiner checklist tamam</strong></p><h3>📊 SEVİYE KARŞILAŞTIRMASI</h3><p>VersiyonTahmini IELTS WritingSenin orijinal metin4.5–5.0Düzeltmeli hal5.5Benim upgraded essay<strong>6.0–6.5</strong></p><h3>🎯 SEN BU SEVİYEYE NASIL ÇIKARSIN?</h3><h3>3 net kural:</h3><ol><li><strong>Akademik cümle başlangıçları ezberle</strong></li><li><strong>Uzun ama kontrolsüz cümle yazma</strong></li><li><strong>Her essay’de aynı yapı</strong></li></ol><h3>🧠 ESSAY YAZMA KALIPLARI (Sınav Odaklı)</h3><p>Aşağıdaki kalıpları <strong>blok blok</strong> öğren.<br> Her paragraf için <strong>5–6 “altın kalıp”</strong> yeterlidir.</p><h3>🟦 1️⃣ INTRODUCTION (Giriş Paragrafı Kalıpları)</h3><h3>🔹 Genel konuya giriş</h3><p>👉 Bunlardan <strong>birini seç</strong>:</p><blockquote><em>Nowadays, </em><strong><em>X plays an important role</em></strong><em> in modern society.<br> In recent years, </em><strong><em>X has become an important part</em></strong><em> of daily life.<br> Today, many people are influenced by </em><strong><em>X</em></strong><em> in different ways.</em></blockquote><p>📌 Örnek:</p><blockquote><em>Nowadays, social media plays an important role in modern society.</em></blockquote><h3>🔹 Konunun etkisini belirtme</h3><blockquote><em>It has a strong influence on </em><strong><em>X</em></strong><em>.<br> It affects the way people </em><strong><em>think / communicate / live</em></strong><em>.<br> This trend is especially noticeable among </em><strong><em>young people</em></strong><em>.</em></blockquote><h3>🔹 Essay amacını söyleme (VERY IMPORTANT)</h3><p>👉 Examiner burada “tamam” der ✅</p><blockquote><em>In this essay, I will discuss the </em><strong><em>advantages</em></strong><em> of X.<br> In this essay, I will explore the </em><strong><em>effects</em></strong><em> of X on Y.<br> This essay will focus on </em><strong><em>two main aspects</em></strong><em> of X.</em></blockquote><p>📌 Örnek:</p><blockquote><em>In this essay, I will discuss the positive effects of social media on young people.</em></blockquote><h3>✅ INTRODUCTION ŞABLONU (EZBERLE)</h3><blockquote><em>Nowadays, X plays an important role in modern society.<br> It has a significant influence on Y.<br> In this essay, I will discuss the main advantages of X.</em></blockquote><h3>🟦 2️⃣ BODY PARAGRAPH 1 (Fikir 1)</h3><h3>🔹 Paragrafa güçlü giriş (Firstly yerine!)</h3><blockquote><em>One of the main advantages of X is that…<br> One important benefit of X is…<br> One of the most significant effects of X is…</em></blockquote><p>📌 <strong>B1+ → B2 geçiş kalıbı</strong></p><h3>🔹 Açıklama yapma</h3><blockquote><em>This is because…<br> As a result,…<br> This means that…</em></blockquote><h3>🔹 Örnek verme</h3><blockquote><em>For example,…<br> For instance,…<br> One clear example of this is</em></blockquote><p>📌 <strong>Kişisel “I” kullanmadan yazarsan +puan</strong></p><h3>✅ BODY 1 ŞABLONU</h3><blockquote><em>One of the main advantages of X is that …<br> This is because …<br> For example, …</em></blockquote><h3>3️ BODY PARAGRAPH 2 (Fikir 2)</h3><h3>🔹 Geçiş kalıpları</h3><blockquote><em>Another positive effect of X is…<br> In addition to this,…<br> A further benefit of X is…</em></blockquote><p>📌 Examiner akışa bakar → bunlar <strong>çok değerli</strong></p><h3>🔹 Günlük hayata bağlama</h3><blockquote><em>In daily life,…<br> In their free time,…<br> In today’s busy world,…</em></blockquote><h3>✅ BODY 2 ŞABLONU</h3><blockquote><em>Another positive effect of X is …<br> In daily life, this helps people to …<br> As a result, …</em></blockquote><h3>🟦 4️⃣ CONCLUSION (Sonuç Paragrafı)</h3><h3>🔹 Sonuca girerken</h3><blockquote><em>In conclusion,…<br> To sum up,…<br> Overall,…</em></blockquote><h3>🔹 Fikirleri tekrar (aynı cümle değil!)</h3><blockquote><em>X has several positive effects on Y.<br> It helps people to … and also …<br> These advantages make X an important part of modern life.</em></blockquote><h3>🔹 Güçlü kapanış (B2 hissi verir)</h3><blockquote><em>When used in a balanced way, X can be beneficial.<br> Therefore, X should be used responsibly.</em></blockquote><h3>✅ CONCLUSION ŞABLONU</h3><blockquote><em>In conclusion, X has several positive effects on Y.<br> It helps people to … and also …<br> When used responsibly, X can be a valuable part of modern life.</em></blockquote><h3>📌 SINAVDA ASLA YAPMAMAN GEREKENLER</h3><p>❌ “in that case” (Türkçe düşünce)<br> ❌ “I think / I love” (academic essay’de zayıf)<br> ❌ Aşırı uzun cümle<br> ❌ Secondly; (noktalı virgül)</p><h3>🎯 BU KALIPLARLA NE OLUR?</h3><p>Eğer:</p><ul><li>Bu kalıpları <strong>doğru grammar ile</strong></li><li>Basit ama net cümlelerle kullanırsan</li></ul><p>🔺 Writing puanın otomatik olarak <strong>+1 band</strong> artar.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90f21264853f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Salesforce Lightning Platform — 8 Layers]]></title>
            <link>https://medium.com/@road.to.salesforce/salesforce-lightning-platform-8-layers-4a81e399e89a?source=rss-ff06d0e9dd32------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a81e399e89a</guid>
            <category><![CDATA[salesforce-domain]]></category>
            <category><![CDATA[salesforce-architecture]]></category>
            <category><![CDATA[salesforce-layers]]></category>
            <dc:creator><![CDATA[Salesforce 101]]></dc:creator>
            <pubDate>Tue, 28 Apr 2026 15:01:05 GMT</pubDate>
            <atom:updated>2026-04-28T15:01:05.148Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Layered example from bottom (8) → top (1)</strong></p><p>I’ll use <strong>one single business use case</strong> across all layers:</p><blockquote><strong><em>“Show Account summary and allow creating a Contact.”</em></strong></blockquote><h3>8️⃣ Infrastructure Layer</h3><p>💡 <em>You never code this.</em></p><h3>Responsibility</h3><ul><li>Data centers</li><li>Compute</li><li>Storage</li><li>Network</li><li>Disaster recovery</li></ul><p>“Code” (Conceptual, NOT Apex)</p><pre><br>Salesforce Global Infrastructure<br>- Physical data centers<br>- Redundant compute nodes<br>- Encrypted storage<br>- Load balancers</pre><p>✅ This is why Salesforce is <strong>SaaS</strong><br>✅ Tenancy, backups, HA are handled here</p><h3>7️⃣ Metadata &amp; Shared Services Layer</h3><p>💡 <em>Where Salesforce magic lives</em></p><h3>Responsibility</h3><ul><li>Metadata execution</li><li>Multi-tenancy separation</li><li>APIs</li><li>Messaging</li><li>Declarative automation</li></ul><h4>Example Artifacts</h4><pre><br>Object: Account<br>Field: Industry<br>Flow: Account_On_Create<br>API: /services/data/v60.0/sobjects/Account</pre><p>You <strong>define</strong>, Salesforce <strong>executes</strong>.</p><p>✅ Metadata ≠ Data <br>✅ Same engine runs for all customers</p><h3>6️⃣ IAM &amp; App Definition Layer</h3><p>💡 <em>WHO can do WHAT</em></p><h3>Responsibility</h3><ul><li>Authentication</li><li>Authorization</li><li>Identity resolution</li><li>App definitions</li></ul><h4>Examples</h4><pre><br>Profile: Sales User<br>Permission Set: Create_Contacts<br>Sharing Rule: Account visibility<br>App: Sales App</pre><pre><br>IF User has Permission &quot;Create_Contacts&quot;<br>THEN allow Contact creation</pre><p>✅ Enforced <strong>before Apex runs</strong></p><h3>5️⃣ Apex Code Runtime Engine</h3><p>💡 <em>Your server-side execution brain</em></p><h3>Responsibility</h3><ul><li>Compile Apex</li><li>Execute Apex</li><li>Enforce limits</li><li>Transaction control</li></ul><pre><br>public class AccountService {<br>    public static void createContact(Id accountId, String email) {<br>        Contact c = new Contact(<br>            AccountId = accountId,<br>            LastName = &#39;Auto&#39;,<br>            Email = email<br>        );<br>        insert c;<br>    }<br>}</pre><p>✅ Multitenant runtime<br>✅ Governor limits enforced here<br>✅ Executes inside SF data center</p><h3>4️⃣ Lightning Application Layer</h3><p>💡 <em>Business logic + app capabilities</em></p><h3>Responsibility</h3><ul><li>Business process orchestration</li><li>Analytics</li><li>Mobile support</li><li>Localization</li><li>Declarative + Programmatic blend</li></ul><pre><br>Sales App<br>- Includes Accounts<br>- Includes Contacts<br>- Tabs<br>- Utility items<br>- Mobile enabled</pre><p>Flow + Apex working together</p><pre>Flow → calls Apex → returns result → displays message</pre><p>✅ This is <strong>where admins + devs collaborate</strong></p><h3>3️⃣ Lightning Component Layer</h3><p>💡 <em>UI rendered logic (client + server)</em></p><h3>Responsibility</h3><ul><li>UI framework</li><li>Client-side JS</li><li>Server-side Apex calls</li><li>Responsive rendering</li></ul><h3>LWC Example</h3><pre>// accountSummary.js<br>import { LightningElement, api, wire } from &#39;lwc&#39;;<br>import getAccount from &#39;@salesforce/apex/AccountController.getAccount&#39;;<br><br>export default class AccountSummary extends LightningElement {<br>    @api recordId;<br><br>    @wire(getAccount, { accountId: &#39;$recordId&#39; })<br>    account;<br>}</pre><h3>Apex Controller</h3><pre>public with sharing class AccountController {<br>    @AuraEnabled(cacheable=true)<br>    public static Account getAccount(Id accountId) {<br>        return [SELECT Name, Industry FROM Account WHERE Id = :accountId];<br>    }<br>}</pre><p>✅ Decoupled UI<br>✅ Partial execution on browser<br>✅ Optimized server calls</p><h3>2️⃣ Lightning Page Component</h3><p>💡 <em>Composition layer</em></p><h3>Responsibility</h3><ul><li>Arrange components</li><li>Define layout</li><li>Responsive regions</li></ul><h4>Example Page Layout</h4><pre>Account Record Page:<br>- Header: Highlights Panel<br>- Left: Account Summary (LWC)<br>- Right: Related Contacts</pre><p>NO logic here<br> ONLY composition.</p><p>✅ Admin-driven<br>✅ Zero code required</p><h3>1️⃣ Lightning Page</h3><p>💡 <em>Entry point</em></p><h3>Responsibility</h3><ul><li>Page definition</li><li>Navigation target</li></ul><pre>Lightning Record Page: Account<br>Assigned to: Sales App<br>Visible to: Sales Users</pre><p>This is <strong>what users open</strong>.</p><p>✅ Mid-ground between VF &amp; Layouts<br>✅ Fully metadata-driven</p><h3>🔁 Full Layer Traversal (One Click)</h3><pre>User opens Account Page (1)<br>→ Page loads components (2)<br>→ LWC renders UI (3)<br>→ Calls Apex method (5)<br>→ Apex checks permissions (6)<br>→ Reads metadata/object (7)<br>→ Data retrieved from infra (8)<br>→ Response bubbles back up</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/737/1*PZFeAVtXoyCegZ62Fg6L7Q.png" /></figure><h3>✅ Why This Matters Architecturally</h3><ul><li>You <strong>don’t fight the platform</strong></li><li>You place logic in the <strong>correct layer</strong></li></ul><p>You avoid:</p><ul><li>Fat controllers</li><li>Logic in UI</li><li>Security leaks</li></ul><p>You scale <strong>cleanly</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a81e399e89a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Typical Layered Architecture (Apex-friendly)]]></title>
            <link>https://medium.com/@road.to.salesforce/typical-layered-architecture-apex-friendly-9bebbe536cc9?source=rss-ff06d0e9dd32------2</link>
            <guid isPermaLink="false">https://medium.com/p/9bebbe536cc9</guid>
            <category><![CDATA[technology-stack]]></category>
            <category><![CDATA[domains]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[tech-layers]]></category>
            <dc:creator><![CDATA[Salesforce 101]]></dc:creator>
            <pubDate>Tue, 28 Apr 2026 14:36:39 GMT</pubDate>
            <atom:updated>2026-04-28T14:36:39.532Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>UI / API Layer → Aura/LWC Controller, REST Controller <br>Application Layer → Service classes (use cases) <br>Domain Layer → Domain / Business logic <br>Infrastructure Layer → Repository / Selector (SOQL, DML)</blockquote><h3>Why this matters</h3><ul><li><strong>Technology stack is a layer</strong> → Apex + SOQL + Salesforce platform live in <em>infrastructure</em></li><li><strong>Business rules stay stable</strong> even if UI or data access changes</li><li>Easier testing, easier refactoring, less fragile code</li></ul><h3>Example Scenario</h3><blockquote><em>“Create an Account if it doesn’t exist, then create a Contact for it, but only if business rules allow.”</em></blockquote><h3>1️⃣ UI / API Layer (Controller)</h3><p>This layer <strong>knows Salesforce UI</strong>, but <strong>not business logic</strong>.</p><pre><br>public with sharing class AccountContactController {<br><br>    @AuraEnabled<br>    public static Id createAccountWithContact(String accountName, String contactEmail) {<br>        AccountContactService service = new AccountContactService();<br>        return service.createAccountAndContact(accountName, contactEmail);<br>    }<br>}</pre><p>✅ Responsibilities:<br>-Receive input<br>-Return output<br>-<strong>Delegate work</strong></p><p>❌ Must NOT:<br>-Run SOQL<br>-Contain business rules</p><h3>2️⃣ Application Layer (Service)</h3><p>This layer <strong>coordinates the use case</strong>.</p><pre>public with sharing class AccountContactService {<br><br>    public Id createAccountAndContact(String accountName, String contactEmail) {<br>        Account existing = AccountRepository.findByName(accountName);<br><br>        Account account;<br>        if (existing == null) {<br>            account = new Account(Name = accountName);<br>            AccountDomain.validateAccount(account);<br>            AccountRepository.save(account);<br>        } else {<br>            account = existing;<br>        }<br><br>        Contact contact = new Contact(<br>            LastName = &#39;Default&#39;,<br>            Email = contactEmail,<br>            AccountId = account.Id<br>        );<br><br>        ContactDomain.validateContact(contact);<br>        ContactRepository.save(contact);<br><br>        return account.Id;<br>    }<br>}</pre><p>✅ Responsibilities:<br>-Orchestrate workflow<br>-Call domain logic<br>-Call repositories</p><p>❌ Must NOT:<br>-Contain SOQL directly<br>-Know UI details</p><h3>3️⃣ Domain Layer (Business Logic)</h3><p>This is where <strong>rules live</strong>. This layer is <em>technology-agnostic</em>.</p><pre>public class AccountDomain {<br><br>    public static void validateAccount(Account acc) {<br>        if (String.isBlank(acc.Name)) {<br>            throw new IllegalArgumentException(&#39;Account name is required&#39;);<br>        }<br>    }<br>}</pre><pre>public class ContactDomain {<br><br>    public static void validateContact(Contact con) {<br>        if (String.isBlank(con.Email)) {<br>            throw new IllegalArgumentException(&#39;Email is required&#39;);<br>        }<br><br>        if (!con.Email.contains(&#39;@&#39;)) {<br>            throw new IllegalArgumentException(&#39;Invalid email format&#39;);<br>        }<br>    }<br>}</pre><p>✅ Responsibilities:<br>-Business rules<br>-Invariants<br>-Validation</p><p>❌ Must NOT:<br>-Run SOQL<br>-Do DML<br>-Access UI</p><h3>4️⃣ Infrastructure Layer (Repository / Selector)</h3><p>This layer <strong>knows Salesforce data access</strong>.</p><pre>public class AccountRepository {<br><br>    public static Account findByName(String name) {<br>        List&lt;Account&gt; accounts = [<br>            SELECT Id, Name<br>            FROM Account<br>            WHERE Name = :name<br>            LIMIT 1<br>        ];<br>        return accounts.isEmpty() ? null : accounts[0];<br>    }<br><br>    public static void save(Account acc) {<br>        insert acc;<br>    }<br>}</pre><pre>public class ContactRepository {<br><br>    public static void save(Contact con) {<br>        insert con;<br>    }<br>}</pre><p>✅ Responsibilities:<br>-SOQL<br>-DML<br>-Data access strategies</p><p>❌ Must NOT:<br>-Contain business rules<br>-Decide <em>when</em> data should be created</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*OdGkRq6aVwLXkLnJDPHwBw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9bebbe536cc9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[English Practice 02.03.26]]></title>
            <link>https://medium.com/@road.to.salesforce/english-practice-02-03-26-6afc4fb97b14?source=rss-ff06d0e9dd32------2</link>
            <guid isPermaLink="false">https://medium.com/p/6afc4fb97b14</guid>
            <dc:creator><![CDATA[Salesforce 101]]></dc:creator>
            <pubDate>Mon, 02 Mar 2026 13:13:29 GMT</pubDate>
            <atom:updated>2026-03-02T13:13:29.891Z</atom:updated>
            <content:encoded><![CDATA[<h3>test</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*AAy7aH2eEliz3J-fBfnVxw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/802/1*EM3tOSTI14Yeior9QB25nA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*9oVGjxiwl6aqLybQcLwSfQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/885/1*N2HKl-_9nkm7Lp1fEGUx0Q.png" /></figure><h3>Cevaplar</h3><h3>✅ 1) Suzie and John are planning to get married and ________ a lot of children.</h3><p><strong>✔ Doğru cevap: have</strong></p><h3>Açıklama:</h3><p>“Have children” İngilizcede <em>çocuk sahibi olmak</em> anlamına gelen tek doğru collocation’dır.</p><ul><li>❌ bring children → çocukları bir yere getirmek</li><li>❌ get children → anlam bozuk</li><li>❌ make children → çocuk yapmak diye kullanılmaz</li></ul><h3>✅ 2) When Sam was a small child, he ________ spend hours every day…</h3><p><strong>✔ Doğru cevap: would</strong></p><h3>Açıklama:</h3><p>“Would” geçmişte tekrarlanan alışkanlıkları anlatır.</p><ul><li>used = bir durumu da anlatabilir ama burada “would” daha uygundur</li><li>was / should → yanlış</li></ul><h3>✅ 3) increasing volume of ________</h3><p><strong>✔ Doğru cevap: traffic</strong></p><h3>Açıklama:</h3><p>“Volume of traffic” İngilizcede sabit bir kalıptır.</p><ul><li>volume of vehicles / circulation → kullanılmaz</li></ul><h3>✅ 4) it’s been ________ recommended</h3><p><strong>✔ Doğru cevap: highly</strong></p><h3>Açıklama:</h3><p>“Highly recommended” → klasik bir collocation’dır.</p><h3>✅ 5) sent in to restore ________</h3><p><strong>✔ Doğru cevap: order</strong></p><h3>Açıklama:</h3><p>“Restore order” = düzeni sağlamak.<br> Bir kalıp ifadedir.</p><h3>✅ 6) What _______ if you had been in my position?</h3><p><strong>✔ Doğru cevap: would you have done</strong></p><h3>Açıklama:</h3><p>Bu bir <strong>3. tip şart (impossible past)</strong> sorusu:<br> If + past perfect → would have + V3<br> Soru yapısı:<br> 👉 “What would you have done…?”</p><h3>✅ 7) If only you _______ me earlier…</h3><p><strong>✔ Doğru cevap: had told</strong></p><h3>Açıklama:</h3><p>“If only + past perfect” → pişmanlık / keşke.<br> <strong>Keşke daha önce söylemiş olsaydın.</strong></p><h3>✅ 8) tell me when to stop _______.</h3><p><strong>✔ Doğru cevap: pouring</strong></p><h3>Açıklama:</h3><p>“Stop” → her zaman <strong>V‑ing</strong> ister.</p><ul><li>stop pouring = dökmeyi bırak</li><li>stop pour ❌</li></ul><h3>✅ 9) he’ll call as soon as he _______ back.</h3><p><strong>✔ Doğru cevap: gets</strong></p><h3>Açıklama:</h3><p>“As soon as” gibi zaman bağlaçları gelecekle ilgili olsa bile<br> → <strong>gelecek zaman kullanılmaz</strong><br> → <strong>simple present kullanılır</strong></p><p>He’ll call when he gets back. ✔</p><h3>✅ 10) A sandwich? _______ have that gorgeous meringue?</h3><p><strong>✔ Doğru cevap: Wouldn’t you rather</strong></p><h3>Açıklama:</h3><p>“Would rather” = tercih bildirme yapısıdır.</p><h3>✅ 11) Long ________ and continue winning…</h3><p><strong>✔ Doğru cevap: may our team flourish</strong></p><h3>Açıklama:</h3><p>“May + subject + verb” → dilek/temenni yapısı.<br> C1 seviyedir.</p><h3>✅ 12) Why are all these flags _______ put up…?</h3><p><strong>✔ Doğru cevap: to have been</strong></p><h3>Açıklama:</h3><p>Pasif perfect infinitive gerekli:</p><ul><li>to have been put up ✔<br> “having been” → yanlış form<br> “being” → zaman uymaz</li></ul><h3>✅ 13) sleeping ________ on the streets</h3><p><strong>✔ Doğru cevap: rough</strong></p><h3>Açıklama:</h3><p>“Sleep rough” → sokakta / kötü koşullarda uyumak<br> İngilizcede sabit bir deyim.</p><h3>✅ 14) before the rain really ________ .</h3><p><strong>✔ Doğru cevap: sets in</strong></p><h3>Açıklama:</h3><p>“Set in” → kötü bir hava durumunun ciddi şekilde başlaması.</p><h3>✅ 15) residents ________ objected</h3><p><strong>✔ Doğru cevap: strenuously</strong></p><h3>Açıklama:</h3><p>“Strenuously object” → güçlü şekilde karşı çıkmak<br> Doğru collocation budur.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6afc4fb97b14" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lightning Application Technology Layers and Runtime Mentality]]></title>
            <link>https://medium.com/@road.to.salesforce/lightning-application-technology-layers-and-runtime-mentality-7c7fb7ee1d2a?source=rss-ff06d0e9dd32------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c7fb7ee1d2a</guid>
            <category><![CDATA[lightning-runtime]]></category>
            <category><![CDATA[apex-runtime]]></category>
            <category><![CDATA[salesforce-layers]]></category>
            <category><![CDATA[runtime]]></category>
            <category><![CDATA[salesforce-runtime]]></category>
            <dc:creator><![CDATA[Salesforce 101]]></dc:creator>
            <pubDate>Mon, 09 Feb 2026 16:12:04 GMT</pubDate>
            <atom:updated>2026-02-09T16:12:04.126Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZC5kJ2fvcoRl4y2DifVncA.png" /></figure><p>⭐ Why Salesforce doesn’t use a strict “one‑above‑another” model</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/918/1*4Zrqn-cZIVrGOi_hRoLu0w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R01R-04QalPLVPMMFgbYIA.png" /></figure><p>⭐ <strong>1. Lightning Runtime (Client-Side + Platform UI Runtime)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*i_dsEwedXEq5XQuDv4A8qw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/678/1*DsSswM8iR6roilvLRrWxfg.png" /></figure><pre>@wire(getAccount)<br>account;  // Lightning Runtime handles this binding</pre><p>⭐ <strong>2. Apex Runtime (Server-Side Business Logic Engine)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*zL1qdfpL5PmIUGYRE-AMDQ.png" /></figure><pre>public static List&lt;Account&gt; getAccounts() {<br>    return [SELECT Id, Name FROM Account LIMIT 10];<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/1*v6AEf6aJLfklSSHbvgAnsg.png" /></figure><p>⭐ <strong>3. Other Runtimes (for completeness)</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*wS1j5iKHjDpNE2aYaFWgkw.png" /></figure><h3>⭐ Key Differences Explained Simply</h3><h3>🔴 Lightning Runtime = Frontend engine</h3><ul><li>Runs in your browser</li><li>Renders components</li><li>Handles UI state</li><li>Calls Apex/UI API for data</li><li>Cannot access database directly</li></ul><h3>🔵 Apex Runtime = Backend engine</h3><ul><li>Runs on Salesforce servers</li><li>Executes business logic</li><li>Reads/writes database</li><li>Enforces sharing rules</li><li>Enforces governor limits</li></ul><p>They are designed to <strong>never mix</strong>, because frontend and backend must remain isolated for:</p><ul><li>security</li><li>multitenancy</li><li>performance</li><li>stability</li></ul><h3>⭐ How they interact together</h3><p>Example: A user opens an Account record page.</p><h3>Step 1: Lightning Runtime</h3><p>Loads LWC → initializes UI → requests data:</p><pre>@wire(getAccounts) accounts;</pre><h3>Step 2: Apex Runtime</h3><p>Executes the Apex class:</p><ul><li>Runs SOQL</li><li>Applies sharing rules</li><li>Returns sanitized data (no unauthorized fields)</li></ul><h3>Step 3: Lightning Runtime</h3><p>Receives data → renders page → responds to user interactions.</p><h3>⭐ A Practical Analogy</h3><h3>Lightning Runtime = Frontend (React-like engine)</h3><ul><li>Rendering</li><li>UI events</li><li>Routing</li><li>Data binding</li></ul><h3>Apex Runtime = Backend (Java-like engine)</h3><ul><li>Business logic</li><li>Queries</li><li>Database modifications</li><li>Security enforcement</li></ul><p>They communicate via <strong>APIs</strong>, not directly.</p><h3>⭐ Which one is higher in the “layer stack”?</h3><p>Lightning Runtime is <strong>above</strong> Apex Runtime because:</p><pre>Lightning Runtime → calls Apex Runtime → calls Database</pre><p>Lightning is the <strong>client-side orchestrator</strong>.</p><p>Apex is the <strong>server-side executor</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c7fb7ee1d2a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[⭐ What “Artifacts” Mean in the Salesforce Architecture World]]></title>
            <link>https://medium.com/@road.to.salesforce/what-artifacts-mean-in-the-salesforce-architecture-world-d4272503eb56?source=rss-ff06d0e9dd32------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4272503eb56</guid>
            <category><![CDATA[salesforce-architecture]]></category>
            <category><![CDATA[salesforce-architect]]></category>
            <category><![CDATA[art-of-artifacts]]></category>
            <dc:creator><![CDATA[Salesforce 101]]></dc:creator>
            <pubDate>Mon, 19 Jan 2026 15:24:57 GMT</pubDate>
            <atom:updated>2026-01-19T15:24:57.720Z</atom:updated>
            <content:encoded><![CDATA[<p>In <em>Salesforce Architects Handbook</em> (and in general solution architecture), <strong>artifacts</strong> are simply:</p><blockquote><strong><em>Tangible deliverables that architects create to explain, design, document, or validate a Salesforce solution.</em></strong></blockquote><p>They are <strong>not code</strong>, <strong>not features</strong>, and <strong>not technical components</strong> — they are <em>communication tools</em>.</p><p>Artifacts help different teams (stakeholders, developers, admins, business, security, data, QA) understand <strong>what</strong> is being built, <strong>why</strong>, and <strong>how</strong>.</p><p>You can think of artifacts as the <strong>blueprints</strong> of a Salesforce system.</p><h3>⭐ Why Are Artifacts Important?</h3><p>Salesforce architecture is complex:<br> integrations, APIs, data models, sharing rules, license constraints, automations, governance, limits…</p><p>Artifacts help architects:</p><h3>✔ Communicate the solution</h3><p>A good artifact shows <em>“Here is what we are building”</em> in a visual, simple way.</p><h3>✔ Align teams</h3><p>Everyone sees the same picture → fewer misunderstandings.</p><h3>✔ Reduce risk</h3><p>Artifacts catch flaws early (e.g., missing data, unclear integration flow).</p><h3>✔ Speed up development</h3><p>Developers can move faster when architecture is clear.</p><h3>⭐ Common Artifact Types (Salesforce Examples)</h3><p>Here are the most typical artifacts Salesforce architects use:</p><h3>1. System Landscape Diagram</h3><p>Shows all external systems and how they connect to Salesforce.</p><p>Helps answer:</p><ul><li>What talks to Salesforce?</li><li>Through which API?</li><li>In what direction?</li></ul><h3>2. Data Model / ERD (Entity-Relationship Diagram)</h3><p>Shows objects, fields, and relationships.</p><p>Helps answer:</p><ul><li>Where does this data live?</li><li>How do objects relate?</li><li>What is master-detail vs lookup?</li></ul><h3>3. Process Flow / Sequence Diagram</h3><p>Shows how a business or system process moves step-by-step.</p><p>Helps answer:</p><ul><li>What happens first?</li><li>Who triggers the process?</li><li>What automation runs next?</li></ul><h3>4. Integration Specification / API Contract</h3><p>Documents:</p><ul><li>API endpoints</li><li>Payload formats</li><li>Authentication</li><li>Error handling</li></ul><p>Ensures both sides integrate correctly.</p><h3>5. Sharing &amp; Visibility Model</h3><p>Shows:</p><ul><li>Who can see what?</li><li>Role hierarchy?</li><li>Org-wide defaults?</li><li>Sharing rules?</li><li>Territory model?</li></ul><p>Critical for security.</p><h3>6. Environment &amp; Deployment Strategy</h3><p>A map of sandboxes and how changes move to production.</p><h3>7. Governance &amp; Center of Excellence Docs</h3><p>Rules, guidelines, naming conventions, coding standards.</p><h3>8. RACI Matrix</h3><p>Defines <strong>who is Responsible, Accountable, Consulted, Informed</strong> for each area.</p><h3>⭐ What Dipanker Means by “The Art of Artifacts”</h3><p>Dipanker emphasizes that creating artifacts is not just “drawing diagrams.”<br> It’s an <strong>art</strong> because:</p><h3>✔ You must choose the right artifact, not create everything</h3><p>For example, sometimes a simple flow diagram solves more than a 20‑page document.</p><h3>✔ Artifacts must be simple enough for non-technical stakeholders</h3><p>A CEO and a developer need different levels of detail.</p><h3>✔ Artifacts are storytelling tools</h3><p>Your job is to <strong>reveal the architecture</strong>, not hide complexity behind jargon.</p><h3>✔ Good artifacts reduce meetings and eliminate confusion</h3><p>A strong diagram can replace hours of verbal explanations.</p><h3>⭐ A Simple Way to Remember It</h3><p><strong>Artifacts = the architect’s language.</strong></p><p>You use artifacts to <em>speak architecture</em>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4272503eb56" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Biggest Causes of Agent Confusion (Object & Field Level)]]></title>
            <link>https://medium.com/@road.to.salesforce/biggest-causes-of-agent-confusion-object-field-level-2de7c7306347?source=rss-ff06d0e9dd32------2</link>
            <guid isPermaLink="false">https://medium.com/p/2de7c7306347</guid>
            <category><![CDATA[atlas-reasoning-engine]]></category>
            <category><![CDATA[agentforce]]></category>
            <category><![CDATA[aireasoning]]></category>
            <category><![CDATA[agenforce-reasoning]]></category>
            <dc:creator><![CDATA[Salesforce 101]]></dc:creator>
            <pubDate>Tue, 13 Jan 2026 11:31:50 GMT</pubDate>
            <atom:updated>2026-01-13T11:31:50.250Z</atom:updated>
            <content:encoded><![CDATA[<h3>A. Missing or Ambiguous Descriptions</h3><ul><li><strong>Objects without descriptions</strong> → Agent doesn’t know the purpose or relationships.</li><li><strong>Fields with vague names</strong> (e.g., Status, Type, Code) → Multiple meanings across objects.</li><li><strong>No help text</strong> → Agent can’t infer constraints or usage.</li></ul><h3>B. Overloaded or Inconsistent Naming</h3><ul><li>Same label used for different semantics (e.g., “Stage” on Opportunity vs. Case).</li><li>API names that don’t match business meaning (e.g., CustomField1).</li></ul><h3>C. Lack of Relationship Clarity</h3><ul><li>No documentation of key lookups (e.g., which field links Order to Account).</li><li>Multiple identifiers (Order Number vs. External ID) without explanation.</li></ul><h3>D. Hidden Requiredness</h3><ul><li>Validation rules enforce requirements not visible in metadata → Agent tries to create/update without mandatory fields.</li></ul><h3>E. Picklist Chaos</h3><ul><li>Unclear picklist values (e.g., “Closed” vs. “Closed — Won”).</li><li>No descriptions for what each value means.</li></ul><h3>F. Formula &amp; Derived Fields</h3><ul><li>Agent tries to set formula fields because it doesn’t know they’re read-only.</li></ul><h3>2) How to Fix (Best Practices for Descriptions &amp; Metadata Hygiene)</h3><h3>Object Level</h3><ul><li><strong>Description format:</strong></li></ul><pre>Purpose: [What this object represents]<br>Primary Identifier: [Field name]<br>Key Relationships: [Lookup fields and related objects]<br>Usage Notes: [When/why records are created]</pre><p>Example:</p><pre>Purpose: Represents a customer order in B2B commerce.<br>Primary Identifier: OrderNumber (External ID)<br>Key Relationships: AccountId → Account; OpportunityId → Opportunity<br>Usage Notes: Created when an order is confirmed in ERP.</pre><h3>Field Level</h3><ul><li><strong>Help Text format</strong>:</li></ul><pre>Meaning: [Business definition]<br>Constraints: [Length, format, requiredness]<br>Example: [Sample value]</pre><p>Example:</p><pre>Meaning: Unique external order reference from ERP.<br>Constraints: Alphanumeric, max 20 chars, required on create.<br>Example: ORD-2024-00123</pre><p>For <strong>Picklists</strong>:</p><ul><li>Add <strong>value-level meaning</strong> in help text or documentation.</li><li>Example</li></ul><pre>Status: Indicates lifecycle stage.<br>Values:<br>  - Draft: Order not yet confirmed.<br>  - Confirmed: Order accepted by ERP.<br>  - Shipped: Order dispatched.</pre><h3>General Rules</h3><ul><li>Avoid generic names like CustomField1; use semantic names.</li><li>Document <strong>read-only fields</strong> (formula, roll-up) in help text: “Calculated from [Field X], do not set manually.”</li><li>Ensure <strong>Required</strong> flag matches business rules; if validation adds extra requirements, mention them in help text.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2de7c7306347" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[️Salesforce Session Settings — Tüm Ayarların Detaylı Açıklaması]]></title>
            <link>https://medium.com/@road.to.salesforce/%EF%B8%8Fsalesforce-session-settings-t%C3%BCm-ayarlar%C4%B1n-detayl%C4%B1-a%C3%A7%C4%B1klamas%C4%B1-e151d1187257?source=rss-ff06d0e9dd32------2</link>
            <guid isPermaLink="false">https://medium.com/p/e151d1187257</guid>
            <category><![CDATA[config-session]]></category>
            <category><![CDATA[org-session-settings]]></category>
            <category><![CDATA[salesforce-session]]></category>
            <category><![CDATA[session-settings]]></category>
            <dc:creator><![CDATA[Salesforce 101]]></dc:creator>
            <pubDate>Thu, 18 Dec 2025 10:25:53 GMT</pubDate>
            <atom:updated>2025-12-18T10:25:53.042Z</atom:updated>
            <content:encoded><![CDATA[<h3>🛡️Salesforce Session Settings — Tüm Ayarların Detaylı Açıklaması</h3><h3>🔶 1. Session Timeout</h3><h3>Timeout Value</h3><p>Kullanıcının ne kadar süre <strong>hareketsiz kalınca otomatik olarak sistemden atılacağını</strong> belirler.<br> • 15 dakika — 24 saat arası seçilebilir. <br> • Güvenlik için genellikle 15–30 dakika önerilir. <a href="https://help.salesforce.com/s/articleView?id=xcloud.admin_sessions.htm&amp;language=en_US&amp;type=5">[help.salesforce.com]</a></p><h3>Disable session timeout warning popup</h3><p>Bu seçenek kapalıysa, kullanıcıya <em>“Oturum sona eriyor devam etmek ister misiniz?”</em> popup’ı çıkar.<br> Açarsan popup görünmez, süre dolar dolmaz logout.</p><h3>Force logout on session timeout</h3><p>Süre dolduğunda kullanıcı <strong>anında çıkarılır</strong>.<br> Ek bir doğrulama veya devam etme izni verilmez. Güvenlik seviyesi yükselir. <a href="https://vortexifysync.com/understanding-session-settings-in-salesforce-a-complete-guide/">[vortexifysync.com]</a></p><h3>🔶 2. Session Settings</h3><h3>Lock sessions to the IP address from which they originated</h3><p>Oturumun sadece başladığı <strong>IP adresinde geçerli olmasını</strong> sağlar.<br> • Session hijacking’e karşı güçlü koruma.<br> • Ancak kullanıcı Wi-Fi → mobil internet gibi ağ değiştirirse oturum düşer. <a href="https://vortexifysync.com/understanding-session-settings-in-salesforce-a-complete-guide/">[vortexifysync.com]</a></p><h3>Lock sessions to the domain in which they were first used</h3><p>Session sadece <strong>ilk login olunan Salesforce domaininde</strong> çalışır.<br> Phishing ve domain manipulation saldırılarını engeller. <a href="https://vortexifysync.com/understanding-session-settings-in-salesforce-a-complete-guide/">[vortexifysync.com]</a></p><h3>Terminate all of a user’s sessions when an admin resets password</h3><p>Admin şifre resetlediğinde kullanıcının tüm aktif session’ları kapatılır.</p><h3>Force relogin after Login-As-User</h3><p>Admin bir kullanıcı olarak login olduktan sonra, çıkınca admin’in yeniden login olması zorlanır.</p><h3>Require HttpOnly attribute</h3><p>Session cookie’lerine <strong>JavaScript erişimini engeller</strong>.<br> XSS saldırılarına karşı önemli koruma.</p><h3>Use POST requests for cross-domain sessions</h3><p>Cross-domain oturumlar sadece <strong>POST</strong> request ile çalışır.<br> GET ile session taşımayı engelleyerek güvenliği artırır.</p><h3>Enforce login IP ranges on every request</h3><p>Profile’da IP aralığı tanımlıysa, sadece login sırasında değil <strong>her request’te</strong> doğrulanır.</p><h3>Use session token instead of session cookie (Lightning embed)</h3><p>Lightning uygulamasını başka bir sitede embed ediyorsan, session cookie yerine <strong>token</strong> kullanır.<br> Bu, cross-domain embedding güvenliğini artırır.</p><h3>🔶 3. Caching</h3><h3>Enable caching and autocomplete on login page</h3><p>Login ekranında autocomplete ve caching açar (kullanıcı deneyimi için).</p><h3>Enable secure and persistent browser caching</h3><p>Lightning performansını artırır; güvenli içerikler cache’lenir. <a href="https://help.salesforce.com/s/articleView?id=xcloud.admin_sessions.htm&amp;language=en_US&amp;type=5">[help.salesforce.com]</a></p><h3>Enable user switching</h3><p>Bir tarayıcıda login ekranında kullanıcı değişimini (switch user) aktif eder.</p><h3>Remember me until logout</h3><p>Remember Me seçeneği logout edilene kadar geçerli olur.</p><h3>Enable CDN for Lightning Component framework</h3><p>Lightning bileşenlerini Salesforce CDN üzerinden yükler → <strong>performans artışı</strong>.</p><h3>🔶 4. Identity Verification</h3><p>Bu ayarlar ayrı sayfaya taşındı. Buradan yönlendirir.<br> (MFA, Lightning Login vb.) <a href="https://help.salesforce.com/s/articleView?id=xcloud.admin_sessions.htm&amp;language=en_US&amp;type=5">[help.salesforce.com]</a></p><h3>🔶 5. Lightning Login</h3><h3>Allow Lightning Login</h3><p>Kullanıcıların telefonla parola girmeden (biometric approval) giriş yapmasını sağlar.</p><h3>Allow only for users with permission</h3><p>Sadece yetki verilen kullanıcılar kullanabilir.</p><h3>🔶 6. Clickjack Protection</h3><p>Clickjacking saldırılarına karşı korur:<br> <strong>Salesforce sayfalarının iframeler içinde embed edilmesini sınırlar.</strong><br> <a href="https://www.greytrix.com/blogs/salesforce/2025/09/02/clickjack-protection-in-salesforce-why-your-iframe-wont-load/">[greytrix.com]</a>, <a href="https://support.phoneburner.com/hc/en-us/articles/36411367773844-ClickJack-Protection-and-Trusted-Domains-in-Salesforce">[support.ph…burner.com]</a></p><p>İki ana kategori vardır:</p><h3>✔ Setup sayfaları</h3><h3>✔ Non-setup Salesforce sayfaları</h3><h3>✔ Visualforce (header’lı)</h3><h3>✔ Visualforce (header’sız)</h3><p>Güvenlik seviyesi yüksek olarak tutulması önerilir.<br> Eğer bir uygulama iframe içinden çalışmıyorsa <strong>Trusted Domains</strong> eklemen gerekir.</p><h3>🔶 7. Trusted Domains for Inline Frames</h3><p>İframe içinde görüntülenmesine izin verilen domain listesi.<br> Eklediğin her domain, belirli bir frame türü için izin alır:<br> • VisualforcePages<br> • Surveys<br> • Lightning Out<br> • Disclosure &amp; Compliance Hub</p><p>Örnek (senin ekranındaki gibi):</p><pre>https://nyk--c.eu27.visual.force.com   → VisualforcePages<br>https://nyk.lightning.force.com        → VisualforcePages</pre><h3>🔶 8. Cross-Site Request Forgery (CSRF) Protection</h3><p>CSRF saldırılarına karşı GET ve POST isteklerini doğrular.<br> Hem GET hem POST’u aktif etmen önerilir. <a href="https://help.salesforce.com/s/articleView?id=xcloud.admin_sessions.htm&amp;language=en_US&amp;type=5">[help.salesforce.com]</a></p><h3>🔶 9. Content Security Policy (CSP) Protection</h3><p>Salesforce sayfalarının başka içerikler tarafından manipüle edilmesini engeller.</p><h3>Enable Stricter CSP</h3><p>Daha katı CSP başlıkları ekler; harici kaynaklara izin azalır.</p><h3>Override IE Email Template Restriction</h3><p>Eski bir ayar, IE11‘deki e-mail template erişim sorunları için (artık pek gereksiz).</p><h3>🔶 10. Lightning Locker API Version — API 65.0</h3><p>Locker Service güvenlik katmanının API versiyonunu belirler.<br> Yüksek API → daha sıkı güvenlik. <a href="https://help.salesforce.com/s/articleView?id=xcloud.admin_sessions.htm&amp;language=en_US&amp;type=5">[help.salesforce.com]</a></p><h3>🔶 11. Lightning Web Security</h3><p>LWC ve Aura bileşenlerini <strong>tarayıcı izolasyonu</strong> ile korur.<br> Yeni sistem → Locker’dan daha güvenli ve hızlı. <a href="https://help.salesforce.com/s/articleView?id=xcloud.admin_sessions.htm&amp;language=en_US&amp;type=5">[help.salesforce.com]</a></p><h3>🔶 12. Content Sniffing Protection</h3><p>Tarayıcıların <strong>dosya türünü yanlış yorumlayıp</strong> XSS açığı yaratmasını engeller.</p><h3>🔶 13. Referrer URL Protection</h3><p>HTTP header <strong>Referrer-Policy</strong> seçilir.<br> Senin ekranında:<br> strict-origin-when-cross-origin<br> Bu seçenek hassas URL bilgilerini sızdırmayı engeller.</p><h3>🔶 14. External Redirections</h3><p>Salesforce’un <strong>güvenilmeyen URL’lere redirect</strong> edip etmeyeceği.<br> Seninkinde: <strong>Always</strong> → her dış URL’ye yönlendirmeye izin var.<br> (Güvenlik için genelde stricter seçilir.)</p><h3>🔶 15. Visualforce Cross-Origin Security Headers</h3><p>COOP / COEP / CSP ayarları:<br> Modern tarayıcılarda cross-origin saldırılarını engeller.</p><h3>🔶 16. Browser Feature Permissions</h3><p>Kamera, mikrofon vb. tarayıcı API’lerine <strong>hangi sayfaların erişebileceğini</strong> kontrol eder.<br> Seninkinde:<br> • Camera → Trusted URLs Only<br> • Microphone → Trusted URLs Only</p><h3>🔶 17. Session Security Levels</h3><p>Session’ları <strong>Standard</strong> ve <strong>High Assurance</strong> olarak ayırır.<br> Amaç:<br> • MFA / SSO / Delegated Auth gibi security levels ile oturum sınıflandırmak.<br> • Bazı işlemler için High Assurance şart koşabilirsin.</p><h3>🔶 18. Logout Page Settings</h3><p>Kullanıcı logout olduğunda yönlendirilecek URL.</p><h3>Store the redirect logout URL locally</h3><p>Tarayıcıya kaydedip hızlı yönlendirme yapar.</p><h3>🔶 19. New User Welcome Email Settings</h3><p>Yeni kullanıcıya gönderilen welcome e-mail linkinin geçerlilik süresi.</p><h3>🔶 20. Aura Action Settings</h3><h3>Disable new Aura boxcar mechanism</h3><p>Aura framework’te XHR isteklerini <strong>batching</strong> yapan mekanizmayı kapatır.<br> (Yavaşlatabilir, ama debugging için bazen gerekir.)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e151d1187257" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>