Feed

#Trailhead Challenges

The challenge ask to create tree internal cases with specific product, stakeholder and object field, but this asked to add detailed recommendations. In this case this challenge doesn't mentioned where you can add your recommendations, in this case i used Subject, Description and Comments fields but I received the follow error message.  

Challenge Not yet complete... here's what's wrong: 

We can't find an internal case record using the proper use case of Agentforce field generation. 

My only extra consideration was use Internal IT case record type. 

@lwc

#Trailhead Challenges

Hello, I created two new rollups that have recently gone missing in production. They are still present in the sandbox I originally built in before deployment. Is there an audit trail available that could highlight actions done, similar to the Salesforce one? 

The ask here is for the subscription terms to be at the product level instead of just one place at the contract that then governs all the products. 

USe Case #1: 

As we are reviewing the processes surrounding post-install Routine Scheduled Changes (simple MACs) and Managed Scheduled Changes (complex reconfigurations and moves), there is a desire to use the amendment process any time a location already exists. This way all services(products) for a location would be contained within one contract and not spread out over multiple locations. 

The challenge with being able to adhere to this direction is that amendments always apply the existing contract term to any added services.(?) 

So, if a customer has a contract that installed products A, B and C on a 3-year term and they then want to reconfigure from A to D but do not want the new services on a 3-year term, but a 1-year term, a new quote would be required for the new service. 

So, the user would need to amend the existing contract, creating an amendment opportunity/quote to terminate the A and also create a new opportunity/quote to install the D. Not only does this become disjointed for Account Managers to manage but once the new services are installed, the B and C would still reside on the original contract while the D would now reside on a newly created contract (contract #2). This too will add challenges when trying to handle future amendments for that customer's Account location. 

Use Case #2 

'SPECIAL' is a new product that will only be sold on a one-year term. This means if the customer is ordering additional services for which they would like on a longer term, Sales must create two independent opportunities/quotes to sell the combined services. 

Bonjour, 

Je voudrais créer une action "en masse" sur le champ "consigner un appel" dans l'objet "compte", j'ai 152 comptes à mettre à jour mais je ne sais pas comment faire.  

J'utilise l'assistant d'importation de données, est-ce que je dois créer une colonne spécifique dans mon fichier Excel ou est-ce que ça peut se faire dans Salesforce directement ? 

Let me know if this is possible in #Salesforce CPQ & Billing

The ask here is for the subscription terms to be at the product level instead of just one place at the contract that then governs all the products. 

USe Case #1: 

As we are reviewing the processes surrounding post-install Routine Scheduled Changes (simple MACs) and Managed Scheduled Changes (complex reconfigurations and moves), there is a desire to use the amendment process any time a location already exists. This way all services(products) for a location would be contained within one contract and not spread out over multiple locations. 

The challenge with being able to adhere to this direction is that amendments always apply the existing contract term to any added services.(?) 

So, if a customer has a contract that installed products A, B and C on a 3-year term and they then want to reconfigure from A to D but do not want the new services on a 3-year term, but a 1-year term, a new quote would be required for the new service. 

So, the user would need to amend the existing contract, creating an amendment opportunity/quote to terminate the A and also create a new opportunity/quote to install the D. Not only does this become disjointed for Account Managers to manage but once the new services are installed, the B and C would still reside on the original contract while the D would now reside on a newly created contract (contract #2). This too will add challenges when trying to handle future amendments for that customer's Account location.  

In my use case, I am working on a  project where a guest user will need to submit some data into salesforce and based on that data I will be calling a prompt Template, I gave already the guest user the Prompt Template User. But the response in the backend is null. 

Any blog or videos might be helpful to create the agents.