Feed

Object name in the permission set is showing as Job Applications however in the object manager it is shown as Job Application so is it reason of the error? if so then how can i solve this? 

We have implemented an Agentforce use case where an employee/user can request details of a Case by providing a Case Number. 

The implementation uses the following components:

• Agentforce Agent
• Agent Action
• Apex class
• Lightning Types
• LWC component rendered as the Agentforce response/output

The same implementation is working successfully in our Employee Agentforce Agent. However, when we implement the exact same configuration in a Service Agentforce Agent

, the LWC does not render. 

Expected Behavior :-

When the user asks for Case details:

1. The Agent asks the user to provide the Case Number.
2. The user provides the Case Number.
3. The Agent Action invokes the Apex class.
4. Apex retrieves the Case details.
5. The response is passed through the configured Lightning Type.
6. The LWC should render the Case details in the Agentforce conversation.

This complete flow works as expected in the Employee Agent. 

Actual Behavior

1. The same flow has been configured in the Service Agent, but the LWC output is not rendered.
2. The Agent Action/Apex execution and configuration appear to be the same, but the LWC UI is not displayed in the Service Agent.
3. There is no clear error being displayed that indicates why the LWC rendering is failing.

Configuration

The following components are the same in both agents:

• Same Apex class
• Same LWC
• Same Lightning Type configuration
• Same Agent Action
• Same Agent User/permissions
• Same input/output structure
• Same Case retrieval logic
• Same LWC configuration
• Same agent instrcutions.

For the Lightning Type/LWC configuration, we have included the supported rendering types, including:

• enhancedWebChat
• lightningDesktopGenAi

This was done so that the LWC can be rendered across the required Agentforce environments, including Agentforce Builder, Salesforce UI, and Experience Cloud/community scenarios.

Important Difference 

The primary difference between the two implementations is the type of Agentforce agent:

Working:

• Employee Agentforce Agent

Not Working:

• Service Agentforce Agent

All other major implementation components are identical. 

Troubleshooting Performed

We have already verified the following:

• Apex class is assigned and accessible.
• LWC is assigned/configured correctly.
• Agent Action is configured in both agents.
• Lightning Types are configured in both agents.
• Same input/output types are being used.
• Same user/permissions are being used.
• The same Apex implementation works successfully with the Employee Agent.
• The same LWC successfully renders when used with the Employee Agent.
• The Service Agent has the same relevant components/configuration.
• No obvious Apex or LWC error is displayed when the Service Agent attempts to return the response.

Because the exact same implementation works with the Employee Agent, we suspect that there may be a difference in the Service Agent runtime, supported LWC rendering capabilities, Lightning Type handling, or Service Agent-specific configuration/limitations. 

Could you please help us determine:

1. Is LWC rendering through Agentforce Agent Actions and Lightning Types fully supported for Service Agents?
2. Are there any differences between Employee Agent and Service Agent runtimes that affect LWC output rendering?
3. Are enhancedWebChat and lightningDesktopGenAi supported for LWC rendering in Service Agents?
4. Are there any additional configuration, permissions, metadata, or settings required specifically for Service Agents to render an LWC output?
5. Is there any Service Agent-specific limitation related to rendering custom LWC components from Agent Actions?
6. Could there be a difference in how Service Agents process the Lightning Type output compared with Employee Agents?
7. Is there any known issue or limitation with LWC rendering in Service Agentforce in the current Salesforce release?
8. If this functionality is supported, could you please advise what logs/debugging steps we should follow to identify why the LWC is not being rendered? 
    

Note: In the Service Agentforce, Case details are successfully retrieved and displayed as plain text in both the Enhanced Web Chat channel on the Experience Cloud site and Agentforce Builder. However, the Case details are not being rendered in the LWC form.
In comparison, the Employee Agentforce successfully renders the LWC with the Case details in both the Enhanced Web Chat channel and Agentforce Builder.

I'm trying to add a related list of Branch Units to the Locations page and it is not one of the options in the dropdown