Enterprise Territory Management (ETM) rules on Account are run automatically when creation of an Account. However, they do not run automatically on account update. Out of the box, here are some options available.

Include the checkbox on the layout

                                

Run the ETM rules from settings, setup -> territory models -> pick a territory and run all rules assigned to the territory

  

 

Here are some limitations with running ETM rules automatically

• ETM rules do not run on inline edit
• DML updates from Apex do not run ETM rules

To programmatically run ETM rules on every account update, you could fire off a REST callout to update the account. This will run the ETM rules. Here is a sample code that uses Queueable job to perform this.

Make sure to pass the accountId and any other fields you would like to include in the dataWrapperJson variable.

Here's some sample code demonstrating a basic REST callout from an LWC component using Apex:

LWC component (lwcMyComponent.js):

Explanation:

1. We import necessary modules: LightningElement for the component base, api and track for reactive properties, and getDataFromApex from the Apex wrapper class (replace with your actual class name).

2. The component has two reactive properties: data to store the response from the API and error to handle any errors during the callout.

3. The handleClick method is triggered on a button click or any user interaction.

4. Inside handleClick, we call the getDataFromApex method from the Apex wrapper. This method should handle the actual REST callout logic.

5. The call to getDataFromApex uses .then and .catch for handling successful responses and errors respectively.

6. On success, the response data is stored in the data property.

7. In case of errors, the error object is stored in the error property for handling in the component template (e.g., displaying an error message).

Apex Wrapper Class (apexCalloutWrapper.cls):

Explanation:

1. This Apex class exposes an @AuraEnabled method getDataFromApex accessible from LWC.

2. The method defines the API endpoint URL (replace with your actual URL).

3. It uses the Http class to create an HttpRequest object specifying the URL and HTTP method.

4. The h.send method sends the request and captures the response.

5. On successful response (status code 200), the response body is parsed as JSON and returned as a Map.

6. In case of errors, an AuraHandledException is thrown with details for handling in LWC.

Note:

• Remember to replace the placeholder values (URL, Apex method name) with your specific API details and class name.
• Configure Remote Site Settings in Salesforce to allow access to the external API endpoint.
• This is a basic example. You might need to modify it based on your API requirements (headers, request body, etc.).

There are two main ways to pass parameters between LWC components in Salesforce:

1. Using Public Properties with the @api decorator:

This method is ideal when there's a parent-child relationship between the components. Here's how it works:

• Parent Component:

  1. Define a property in the parent component's JavaScript file.
  2. Mark the property with the @api decorator to make it accessible by the child component.
  3. Assign a value to the property and pass it down to the child component using the component tag.

• Child Component:

  1. Import the parent component.
  2. Access the public property using the parent component's tag followed by a dot notation (e.g., parentComponentName.propertyName).
  3. Use the received value in the child component's logic or template.

Here's an example:

Parent Component (parent.js):

Parent Component (parent.html):

Child Component (child.js):

2. Using Lightning Message Service (LMS) for Non-Parent-Child Communication:

This method is useful when the components don't have a direct parent-child relationship. LMS provides a pub/sub mechanism for components to communicate with each other.

• Publisher Component:

  1. Create a new message channel using new MessageContext(this).
  2. Use the publish method of the message channel to send a message with data.

• Subscriber Component:

  1. Subscribe to the message channel using subscribe method.
  2. Define a callback function to receive messages and handle the data.

Here are some resources for further learning:

• Salesforce Documentation on LWC Properties: https://developer.salesforce.com/docs/platform/lwc/guide/js-props-intro.html
• Salesforce Documentation on Lightning Message Service: https://developer.salesforce.com/docs/component-library/bundle/lightning-message-service

After a user has been deactivated you might notice in the LoginHistory that previously authenticated apps are trying to establish a login resulting in login failure.

This will show up in Scale Center under 'Failed Logins'. To remove these failures you can revoke the apps for these inactive users. You can do this for individual users by going to Setup -> Users -> User Detail -> Oauth Apps -> Revoke

When you have to do this for hundreds of users, it isn't effecient to do this manually. You can run the below script in anonymous apex. To further automate, you might want to schedule this as a batch class to run weekly or daily.