Feed

Solution: Using Static Resources

1. Upload Your Icon as a Static Resource
   • Go to Setup → Static Resources → Click New.
   • Upload your logo file (e.g., ayushLogo.png) and provide a Name (e.g., ayushLogo).
   • Click Save.
2. Modify Your Visualforce Page 
   Add the following code to override the default header icon:

<apex:page standardStylesheets="false" showHeader="true">
    <!-- Custom Section Header -->
    <apex:sectionHeader 
        title="Your Application Name" 
        subtitle="Your Subtitle" 
        icon="{!URLFOR($Resource.ayushLogo)}"
    />
    <!-- Rest of your VF page content -->
</apex:page>

Example

<apex:image id="theImage" value="/img/myimage.gif" width="220" height="55"/>
The example above renders the following HTML:
<img id="theImage" src="/img/myimage.gif" width="220" height="55"/>
Resource Example
<apex:image id="theImage" value="{!$Resource.myResourceImage}" width="200" height="200"/>
The example above renders the following HTML:
<img id="theImage" src="<generatedId>/myResourceImage" width="200" height="200"/>
Zip Resource Example
<apex:image url="{!URLFOR($Resource.TestZip, 'images/Bluehills.jpg')}" width="50" height="50" />
The example above renders the following HTML:
<id="theImage" src="[generatedId]/images/Bluehills.jpg" width="50" height="50"/>

Hi @lokesh singh thakur bondili

, 

Thank you for your question! Based on my understanding, you're asking how the CaseId passed to the Agentforce_Service_Agent_new agent can be accessed and utilized within the agent's prompt template or for passing it to a tool. Please correct me if I misunderstood. 

In Agentforce, any variables declared as "Available for output" in an invocable action can be accessed within the Agent Action Builder. Here’s how you can use the CaseId: 

Displaying the CaseId in the Agent Window: In the Agent Action Builder, you can enable the "Show in conversation" option for the CaseId variable. This will display the CaseId directly in the agent window, making it visible to the user. 

Referencing the CaseId in a Prompt Template: To use the CaseId in a prompt template, you can reference it using the variable name. For example, if the variable is named CaseId, you can include it in your prompt like this: "Your case has been created successfully. The Case ID is {{CaseId}}." 

Passing the CaseId to a Tool: If you want to pass the CaseId to a tool or another action, you can map the output variable (CaseId) from the invocable action to the input of the tool or action in the Agent Action Builder. 

For example, let’s say a customer creates a case using the agent. The CaseId generated by the backend action can be returned to the customer as confirmation. Later, if the customer wants to check the status of their case, the agent can prompt them to provide the CaseId as a unique identifier to retrieve the case details. 

I hope this clarifies your question! Let me know if you need further assistance.

Hello @Kawal Kaur

To clone OLIs(OpportunityLineItems) before decomposition based on product attribute conditions, follow this approach: 

1 .Use a Before Insert/Update Trigger on OpportunityLineitem.  

2. Chethe ck product attribute condition in the trigger logic. 

3. Clone logic :Use.clone(false,true) to deep clone the OLI.  

4. Limit clones: Add logic to restrict cloning to a maximum of 7-10 OLIs. 

5 . Insert cloned OLIs before the decomposition logic runs. 

 Refer below sample code- 

if(shouldClone && cloneCount <10){ 

OpportunityLineItem newOLI=oldOLI.clone(false,true); 

newOLI.OpportunityId=oldOLI.OpportunityId; 

toInsert.add(newOLI); 

}