Section 6 · Productivity and Collaboration · 10% of exam
6.4 AppExchange, packages, AgentExchange, and Flow awareness
Exam objective
Identify AppExchange use cases and understand managed and unmanaged packages, publisher considerations, AgentExchange prompts, and Flow awareness. AppExchange helps organizations discover Salesforce apps and components for needs that may be met by existing products. Evaluate publisher trust, supported Salesforce versions, permissions requested, data handling, reviews, maintenance, and fit with the org before installation.
Managed packages are distributed and maintained by a publisher with package controls and upgrade paths. Unmanaged packages provide components without the same publisher-managed upgrade model and are often used to distribute sample or starting components. Understand what will be installed and how updates or modifications are handled.
AgentExchange extends discovery to agent-related assets such as prompts or actions. Flow may be part of an installed solution or may be the appropriate native automation tool. Review package contents and permissions, and test the feature in a safe environment before broad rollout.
Additional concepts
Review a package before installation
Check publisher information, supported capabilities, requested permissions, compatibility, update approach, and data handling. A managed package is publisher-controlled and has managed upgrade behavior; unmanaged components can be modified locally but do not follow the same publisher-managed upgrade path.
Treat agent and Flow assets as governed components
AgentExchange can provide agent-related assets such as prompts. Flows may be included in a package or may be a native way to meet the requirement. Review dependencies, permissions, and behavior in a safe environment before exposing an installed component to users.
A business wants a scheduling capability not available in its current configuration. Compare AppExchange options, review publisher and security details, test installation in a sandbox, and confirm whether a native Flow can meet the requirement more simply.
Key takeaways
- Assess fit, publisher trust, data access, and lifecycle before installing.
- Managed and unmanaged packages differ in publisher control and upgrade behavior.
- Review AgentExchange assets and Flow dependencies as part of solution governance.
