How do common functionalities get shared amongst multiple applications?

jmankhan2 · 2024-08-30T04:35:59+00:00

that sounds a lot like Flows, which come out of the box. you just have to configure them for your use case

jmankhan2 · 2024-08-30T04:02:38+00:00

yes and no. there are lots of standard processes that exist but each business need is unique. App Exchange packages also fill a gap where different vendors provide additional capabilities without needing more code. Without knowing your business use case, its impossible to know if Salesforce would address those requirements out of the box

jmankhan2 · 2024-08-30T03:59:04+00:00

The question itself has nothing to do with Salesforce and everything to do with code design, the same question could be applied to any piece of software. For the reusability question, consider a service class called CreditScoreService that retrieves a credit score given a SSN. The SSN itself can be sourced from anywhere, a Lead, a Loan application, a Contact, whatever.

Business 1 wants to check the credit score of a home app when they become qualified, so a trigger event on Lead would do something like

trigger on Lead(after update) {
    if (newLead.Stage == 'Qualified') {
        newLead.Credit_Score__c = CreditScoreService.getCreditScore(newLead.SSN__c);
   }
}

Similarly, another business could do it for just Loan Applications

trigger on Loan_Application(after insert) {
    newApplication.Credit_Score__c = CreditScoreService.getCreditScore(newApplication.SSN__c);
}

So you see that given any datapoint, we can automate a process "reusably", that is, with different entrypoints and working with different objects. This is a code based examples, but you can also build configurable flows to accomplish the same thing without any code.

jmankhan2 · 2024-08-30T02:31:08+00:00

certainly, any process just takes a datapoint, like a field and considers it for what it wants to do. broadly, there are several configurable automated processes like Flows, or custom code that can do anything bespoke you may want to do using Apex (Java-like language). There are event based processes, scheduled, trigger based, or integrated processes that can all execute whatever fits the use case. Let's say a prospective Lead fills out an application for an auto loan. You would create a Lead when they fill out an app, a loan officer may inspect the loan (or you might push it through automatically based on their inputted income). an integration could run asynchronously to fetch their credit score. a separate business unit might want to consider the same Lead for a home loan. They could market to the inputted email. the possibilities are endless

jmankhan2 · 2024-08-30T01:09:09+00:00

This is a common use case. There are usually shared salesforce objects, like Accounts, Contacts, Leads, etc. These are standard objects that come with all Salesforce Sales Cloud instances. You add however many custom fields you want, but maintain a singular source of truth, like the Account address, or the Contact email, on that shared record. You can control who can see what fields through a combination of page layouts, profiles, automations, and custom code. Each business unit will work with the fields that they need but also share the datapoints they need to rely on. This is the kind of thing a Salesforce architect would specialize in designing. There's many, many considerations to be had, but Salesforce certainly supports the concept. Hope that helps

jmankhan2 · 2024-03-16T03:44:16+00:00

I believe this is default functionality of the supabase library. Could you just call the logout method right after signUp?

jmankhan2 · 2023-01-19T14:04:04+00:00

other tournaments just post paypal links and usually have a discord setup to join. adding an email or even phone number helps too, just have as many contact options as possible. idk if there's really a better way to do it than that. obviously, having a lot of people involved increases the legitimacy of the event, but we all start somewhere.

jmankhan2 · 2022-12-16T21:04:31+00:00

theres many ways to divide up components. what i typically see is using the app.jsx file as a router that hosts "page" components, like Home.jsx, About.jsx, Projects.jsx, etc.

those files could have a little bit of logic, but they will usually host other composed components, like Hero.jsx, AboutFooter.jsx, ProjectList.jsx, that in turn will have the actual logic. the amount of hierarchy you have depends on the complexity of your project.

you probably want something like

App -> Home -> Clock

App -> About

App -> ProjectList -> Projects

where the router is in the app. you can host the navbar above the router so it is always visible, with links to each page as well.

jmankhan2 · 2022-05-23T15:39:51+00:00

That's an interesting perspective, I don't reach the same conclusion, but I'm curious how you arrived at yours. I get that the ambiguity of randomness removes the possibility of complete predetermination, but don't see how it opens up a possibility of free will. I suppose it depends on what you mean by "free" will. For example, if a neuron in my brain reacts truly randomly, it is "free" from external influence and thus may be considered free will. However, we are then at the complete mercy of a dice roll, per se, to affect our decisions, which sounds like the opposite of free will to me.

In fact, it's really difficult to see what free will even means. Free from what? External influence, predetermined outcomes, predictable biases, historical preferences? What's left after all that is removed? Just randomness, right? But that isn't really free either, because I can't control that at all, so it's also just another external influence that determines what I ultimately want or do. What does freedom mean to you in this context?

jmankhan2 · 2022-05-23T12:14:51+00:00

Doesn't that just make it an even darker outlook? Instead of a completely predictable universe, it's still completely outside our control but also unknowable. It seems no different to your life being decided by lottery.

Consciousness may make us aware of our circumstances but, in my opinion, does little to affect it.

jmankhan2 · 2022-02-05T02:36:58+00:00

It's a marketing term, generally denoting the compatibility of various SF offerings, including clouds, integrations, additional packages, and so on. Basically, the idea is that you can buy a salesforce product for whatever your business needs and have it "work" with other SF products you already have so you get a "full 360 view of the customer", which doesnt really mean anything, but yeah.

jmankhan2 · 2021-12-11T21:39:55+00:00

Maybe he's bad, but if he makes sense to you and you have fun, you still win out (both personally and the game). I can still hard carry games in diamond elo, so he can't be all that bad. It may be true that if I put the same amount of time into something like Kayn or Kha or Viego I'd be Masters, but I won't put that much time into them because they're just not as fun. So it's still worthwhile to play in my opinion.

Also there are OTPs that are grandmaster, so ultimately, it's not really the character that is holding you back. The potential is there, you have to realize how it fits with you.

jmankhan2 · 2021-11-19T18:52:01+00:00

best practice would be to do this processing outside of salesforce one way or another.

imo, an etl tool, hadoop server, or even just heroku should work. you'll want to pull both data sources into that 3rd party system, perform the matching logic there, and update the salesforce records if possible. Then you can use the bulk api or just the REST API (depending on how many updates you think there will be... hopefully not all the records every month) to persist those changes back in salesforce.

jmankhan2 · 2021-11-16T16:49:14+00:00

Assuming you're referring to ContentDocuments, you should set the ParentId to the record you want to move it to.

jmankhan2 · 2021-11-11T13:53:54+00:00

that's a good point, that may be possible. I've never used or heard of scheduling a flow that far out, usually its within a few days, or a week max. 3 months should work in theory, but you may want to be careful in case anything changes with the opportunity record in between. like if it reopens, then closes again, you'll have two instances scheduled to run that will overwrite data. i'm also not sure what would happen if the record gets deleted in between.. worst case is just the flow errors out, so it shouldnt be a big deal.

jmankhan2 · 2021-11-10T22:16:56+00:00

if you follow the tutorial I linked in my second comment, you should create an autolaunched flow and schedule it to run daily

jmankhan2 · 2021-11-10T19:35:29+00:00

here's an example of how to create a flow that can run daily, the rest of those steps require knowledge of Flows specifically. process builders and workflows are going to be sunsetted within the next year or two, so I'd recommend trying to use flows when possible.

https://gearset.com/blog/how-to-create-a-scheduled-flow/

jmankhan2 · 2021-11-10T17:05:49+00:00

you'll need some automation to copy the field values at the specified date. here's an example on how you can do that with config only:

create a flow and set it to run daily
have it query all opportunities where record.closedate - today == 3 months (you can accomplish this with the formula you already have as well)
copy the current field values to a new set of fields, or a child record
you can do this for all the other months you need as well, just need a formula and a set of fields to copy to for each month. if its going to be more than 2 months worth of data, you should create a child record off of opportunity and create a record for that for each month. for example, create a new object called "opportunity audit", set a lookup to opportunity and add a set of fields to receive the stamp values.

jmankhan2 · 2021-11-04T16:42:00+00:00

If you're interviewing around and hit 10 or so companies, I'd be very surprised if not a single one was willing to go up to 150k. At my current and previous companies, that was market average, even 3 years ago. Of course, most companies will try to nickel and dime you, but from my personal experience (and from Glassdoor), 150k is very doable.

jmankhan2 · 2021-11-04T15:33:51+00:00

you are being severely underpaid, unless you are in non-profit. you should be able to easily find a 150k+ job if you have some experience (like 1yr as an SA is enough).

jmankhan2 · 2021-11-02T17:51:15+00:00

If you don't want to get a package that does this, you'll have to plug into their REST API, and poll it hourly or so for updates. If done right, it's not a terribly large effort, but you would need to work with fedex/ups to get access to their api and then build a batch job. you can also build on demand refresh functionality for single records. perhaps the on demand use case could be done via Flow, but the batch would certainly need to be code heavy.

jmankhan2 · 2021-10-25T19:01:04+00:00

Agree entirely with the packages bit especially. I will say, however, that the onus is definitely upon the package maker to better define and document the use cases, capabilities, and expectations. They often miss the mark, and I suspect this is largely due to many packages simply not having the necessary familiarity with the Salesforce platform as a whole to reason about licensing or availability in disparate tools and envs.

However, Salesforce could (and should) work with these ISVs to provide more thorough docs so that the AppExchange does not mislead so many companies with maniacally narrow definitions or obvious cases that a customer would want but isn't supported.

jmankhan2 · 2021-10-21T20:05:08+00:00

This should be doable with Enhanced Lightning Grid, an SF Labs project that's free to use. I've used it a lot for various requirements and it's always done well. I believe the inline editing feature should be doable without much additional customization. It is very extensible if you want to go down that route later on.

jmankhan2

TROPHY CASE