home.social

#use-case — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #use-case, aggregated by home.social.

fetched live
  1. @patrickcmiller

    Well, at least that shut up all the muppets saying there is no #usecase for the always rong #Ai

    #hackers are happy

  2. Spatial Signals [podcast]
    --
    americaview.podbean.com/ <-- shared podcast entry page
    --
    americaview.substack.com/ <-- shared Spatial Signals Substack page
    --
    [note that I am not associated with this podcast in any way, and this post should not be considered an endorsement]
    “Spatial Signals is a podcast about remote sensing, GIS, and geospatial technologies - but more importantly, it’s a podcast about the people who use and apply them. This podcast is sponsored by AmericaView, the national remote sensing network dedicated to empowering Earth Observation…”
    #SpatialSignals #AmericaView #Geospatial #RemoteSensing #GIS #spatial #mapping #GeoAI #OpenSource #podcast #remotesensing #earthobservation #spatialprofessionals #SMEs #socialmedia #GISgeeks #usecase #publicgood #spatialanalysis #spatiotemporal #model #modeling
    @SpatialSignals | @Youngstown State University | @AmericaView

  3. UseCase или как описывать бизнес-процессы в коде

    UseCase - как организовать своё приложение с точки зрения бизнес-процессов, чтобы не погрязнуть в хаосе сервисов, контроллеров и разрозненной логики. Узнать как это

    habr.com/ru/articles/1012988/

    #usecase #application #domain #arhitectura #бизнеспроцессы #бизнеспроцесс #архитектура #бэкенд #php #laravel

  4. Beyond the URL Button: The Salesforce Request Approval Lightning Component

    Are you finding that as your company grows, the complexity of your approval workflows grows along with it? What once might have been a simple sign-off from a single manager can quickly transform into a multi-step process involving input from multiple departments, stakeholders, and even external partners. This complexity often leads to delays, inefficiencies, and frustration as approvals get stuck in bottlenecks or lost in email chains.

    Salesforce’s free Flow Approval Processes, built on Flow Orchestrator, automate even the most intricate workflows. A previous post explored launching these Autolaunched Approval Orchestrations via a custom URL button. Today, we are taking that functionality a massive step forward. We will explore the new Request Approval Lightning component and its tie-in to autolaunched flow functionality. This component expands automation by allowing dynamic user inputs directly from the record page.

    The Foundation: Autolaunched Flow Approvals

    Before diving into the new component, let’s quickly recap how autolaunched flow approvals function. When you build an autolaunched approval process, you are essentially building an autolaunched automation that can be executed on demand, very similar to an autolaunched Orchestration or flow. However, the traditional method of launching Salesforce automations (the quick action button) has strict limitations. Quick actions can only be used to add an active screen flow to the page layout; orchestrations are simply not supported. Furthermore, quick actions do not allow you to pass additional input parameter values into your automation beyond the standard recordId.

    Because of these limitations, the standard workaround has been to build an autolaunched Approval Orchestration and assign it to a custom URL button on the page layout. For example, a common use case is to escalate a case to a queue of level 2 experts when a second opinion is required. By appending variables to the custom URL, such as ?recordId={!Case.Id}&submitter={!$User.Id}&retURL={!Case.Id}, administrators could successfully pass the necessary parameters to kick off the orchestration. While highly effective, this URL button method is a bit rigid. It automatically submits the record based on predefined flow logic without giving the submitter much runtime flexibility.

    Enter the Request Approval Lightning Component

    This is where the new Request Approval component completely changes the game. Instead of relying on a custom URL button to trigger your background orchestration, you can now add a native, user-friendly interface directly to your Lightning record pages. This component bridges the gap between the UI of a screen flow and the processing power of an autolaunched orchestration.

    To utilize this feature, you must first design, test, and activate an autolaunched flow approval process. Once your flow is ready, you can simply open the record page where you want to place the component. Click the gear icon on the navigation bar, and select Edit Page to open the Lightning App Builder. From the Components tab, search for “Request” and drag the Request Approval component directly onto the layout.

    Straightforward Setup

    You can customize the title of the component to display user-friendly text at run time. Then search for and select your active, autolaunched flow approval process to run whenever the user clicks the “Start” button. You can also assign a specific label to identify the associated flow approval process to your users.

    Expanding the Use Case: What Can Be Added?

    So, how exactly does this new component expand the capabilities of your autolaunched flow use cases? The true power of the Request Approval component lies in its ability to gather critical, dynamic inputs directly from the submitter at the exact moment of submission. When using the old custom URL button method, the approver destination (such as the Level 2 expert queue) was hardcoded into the flow steps. With the new component, you can dramatically increase the flexibility of your processes through two main enhancements:

    Dynamic Approver Selection

    The component allows you to require submitters to actively select an approver before the flow runs. To enable this, you must configure your underlying autolaunched flow approval process to assign one or more approval steps to a specific resource named firstApprover. In the Lightning App Builder, you then select the Require submitter to select an approver setting.

    It is critical to ensure your flow is properly configured to accept this input. Consider whether the flow approval process you selected assigns one or more steps to the firstApprover resource. If it does, you must select this requirement on the component to prevent the flow approval process from failing when a submitter attempts to use it. This means a single autolaunched flow can now be routed to entirely different managers, departments, or external stakeholders on the fly.

    Submission Comments

    Another massive expansion of your use case is the ability to capture submission comments. Often, an approver needs context as to why a record is being submitted. The Request Approval component shows an Approval Request Comments field by default. This exposes optional submitter comments directly to the approvers via the submissionComments resource.

    If your business process dictates that comments are unnecessary, or if you want to streamline the UI to prevent the submitter from adding comments about a submission, you easily have the option to select Hide submitter comments within the component configuration. These comments are stored cleanly in the new data model under the Approval Submissions object, specifically within the Comments field, making them accessible via queries if you wish to display them in custom approver screen flows.

    The Impact on Your Org’s Architecture

    By tying the Request Approval component to your autolaunched orchestrations, you unlock a highly scalable and flexible architecture. You no longer need to build dozens of slightly different flows for different queues or approvers. Instead, you can rely on a single autolaunched flow that dynamically adapts based on the firstApprover and submissionComments variables passed from the component.

    This ties seamlessly into the broader Flow Approval Process ecosystem. Once submitted, the process still leverages the brand-new UI and audit trail, including the Approvals Lightning app, Approval Submissions, and Approval Work Items. The orchestration sequences stages and steps behind the scenes. It potentially triggers automated background steps like updating records or sending notifications without requiring further user interaction. Approvers still receive their email notifications with links to the Work Guide, and they can still reply directly to the emails with keywords like “Approve” or “Reject” to complete their action. Furthermore, administrators must still remember to add the Flow Orchestration Work Guide component to the record page. It approvers have a centralized interface to actually interact with the assigned approval step.

    It is important no note that this component allows the user to recall the approval process once it is started.

    Conclusion

    The Request Approval component takes the Autolaunched Flow Approval Process and makes it more dynamic and user-centric. By moving away from static URL buttons and embracing this native Lightning component, administrators can empower their users to select appropriate approvers and provide vital context through comments. All while leveraging the free, robust automation engine of Salesforce Flow Orchestrator.

    Whether you are routing cases to level 2 experts or managing multi-million dollar contracts, this functionality ensures your approval workflows are as efficient, user-friendly as possible. Save and activate your record page layout, exit the Lightning App Builder, and watch your new approval processes in action.

    [youtube youtube.com/watch?v=8AlAsH7qb6]

    Explore related content:

    How to Build Custom Flow Approval Submission Related Lists

    Start Autolaunched Flow Approvals From A Button

    Supercharge Your Approvals with Salesforce Flow Approval Processes

    #FlowApprovals #HowTo #LightningComponent #Salesforce #SalesforceAdmins #SalesforceDevelopers #SalesforceTutorial #useCase
  5. (Open) Webinar - Introduction to ML/DL Theory - Explore the foundational theory behind Machine Learning (ML) and Deep Learning (DL) in a geospatial context
    --
    events.teams.microsoft.com/eve <-- shared webina registration
    --
    H/T Eric Loubier | DG, Canada Centre for Mapping and Earth Observation
    “🌎 GeoAI Webinar Series
    March 5, 2026 (11:00 am–3:00 pm ET)
    Module #1: Introduction to ML/DL Theory
    • Explore the foundational theory behind Machine Learning (ML) and Deep Learning (DL) in a geospatial context…”
    #webinar #open #free #GeoAI #UNGGIM #ArtificialIntelligence #Geospatial #Webinar #Canada #Americas #eLearning #onlinelearning #AI #NorthAmerica #Algorithms #Architectures #ML #DL #GIS #spatial #mapping #machinelearning #deeplearning #usecase #workflow #spatialdata #remotesensing

  6. Nice To Be 'Back In The Data Trenches' Directly
    --
    usgs.gov/3d-hydrography-program <-- shared U.S. Geological Survey (USGS) #3DHP home page
    --
    I don't get to be here that often (and that is OK, #ILikeMyJob) - but it is nice to be back working directly with some individual spatial datasets - be it in #QGIS, #ArcGISPro, #PostgreSQL / #PostGIS or wherever...
    #GIS #spatial #mapping #water #dataquality #water #hydrography #3DHP #NHD #opendata #USA #MI #reservoirs #dams #pluvial #fluvial #usecase #SQL

  7. The Power Of Using A Story For Better Data Comprehension And Hence Decision Making
    --
    doi.org/10.1080/15228053.2021. <-- shared book review, “Data Story: Explain Data And Inspire Action Through Story”
    --
    [I encountered this excellent graphic from @saurabh Rai, and went and explored the ideas put so succinctly here; I found, well, a technical story overview (link above) to ‘match’; however, this should not be considered an endorsement of this book]
    #data #storytelling #data #comprehension #presentation #story #frameworks #context #setting #dataquality #communication #usecase #robustness #insights #correctness #decisionmaking #narratives #decisions

  8. Changing Winescapes, Europe, With Changing Climate
    --
    threads.com/@simongerman600/po <-- shared Threads post
    --
    euronews.com/green/2025/04/18/ <-- shared technical media article
    --
    H/T @SimonKuestenmacher
    “Many of the European regions that are suitable for wine-growing in 2025 weren't so in 1960. Rising temperatures will continue to shift these growing regions…”
    [not the asterik, and how that applies to other European wine producing regions]
    --
    “… As climate change affects rainfall and temperatures continue to rise, experts predict that regions as far north as Yorkshire in the UK could become premier wine producers by the end of the century…. “
    #GIS #spatial #mapping #temperature #wine #winescape #Europe #climatechange #production #winegrowing #rainfall #precipitation #drought #pluvial #extremeweather #cartography #usecase #economics #agriculture #metrics #HuglinIndex #remotesensing #Copernicus

  9. A ‘Waylaid' Teaching Diorama – USGS “Geology For Land Use”
    --
    For about 3 years, this gorgeous diorama has ‘just’ been sitting in a corner of a (common) hallway.
    I can’t help but wonder its history:
    • What prompted its creation?
    • Who was the artisan (truly!) that created it and used those components and focus?
    • When was it created? (late 1960s as an educated guess????)
    • Why was it seen as useful / in what setting? (as I am sure it was)
    • How was it funded?
    (never mind that I want to claim it for my office, space notwithstanding…)
    #geology #landuse #trainingaid #education #diorama #oldschool #fedscience #fedservice #education #technical #professional #spatial #landform #geomorphology #usecase #appliedscience #geoscience #USGS
    @USGS

  10. We are proud to share that the Sketch Map Tool was strategically used in Cali, Colombia

    In Cali, the project worked with the communities of Pance and Comuna 18, encouraging participatory mapping that puts citizens at the heart of risk analysis. By combining technical skills with local knowledge, the team identified environmental conditions, hazards, resources, and safe evacuation routes for emergencies.

    🔍 Read More: buff.ly/ibg7zF6
    #SketchMapTool #CaliCo #UseCase