Solution Engineering227 tasks
Design Solution Architecture
A user gets a written architecture: a phased plan, a recommendation document or a gap analysis that stakeholders can review before anyone builds anything. Part of the Solution Engineering overview.
Method
How MeshMesh does it
- Explores the customer's org and situation first. In one case it queried org metadata while exploring, and several queries failed on wrong field names.
- Drafts a phased plan. One example is an Experience Cloud customer portal plan covering the site, Knowledge, guest access, pages, Flow automation, security and testing. Another is a blueprint covering journey mapping, a canonical data model, integration patterns and analytics KPIs.
- For RFP-style questions, compares the options and recommends one. In one case it compared Web-to-Lead, a marketing platform form and a custom intake object, and recommended the custom intake object as the system of record.
- Covers data and attribution concerns, such as permanent original-source retention, UTM and page-level attribution and identity resolution. Security topics come up often, especially Salesforce Shield and the Einstein Trust Layer.
- Hands over the plan for review before anything is built; none of the samples built anything in an org.
The written design often continues in Document Technical Solution Designs.
Products
Products and features it works with
Bars show how many of this capability's tasks touched each product.
- 1MuleSoft62 tasks
- 2Public Sector Solutions8 tasks
- 3Informatica6 tasks
- 4MuleSoft Anypoint PlatformMuleSoft4 tasks
- 5MuleSoft for Flow: IntegrationMuleSoft3 tasks
- 6MuleSoft Omni GatewayMuleSoft3 tasks
- 7Customer Identity and Access ManagementSalesforce Platform1 tasks
- 8Data ImportSalesforce Platform1 tasks
- 9MuleSoft RPAMuleSoft1 tasks