Integrating Vlocity with Salesforce

An account lands in the org. The name is right. The address is right. The industry step that should have followed, the step the team still does by hand because the vertical process requires it, never starts. The partner calls the account copy a Vlocity integration and closes the ticket. The step is still on a desk. A connector that only copies the account drops the industry steps. That drop is the failure. A diagram with Vlocity on one side and Salesforce on the other, and the account as the only object, is a poster of a finished job that is not finished.

The person who runs the industry step can tell you it did not happen. The account record cannot. If the design stops at the account, the design has chosen the wrong object.

#The app

The app is Salesforce Industries. The record says what Vlocity became, and this page quotes that sentence once: "Vlocity, acquired in 2020, became Salesforce Industries (or Industries Cloud) providing deep, industry-specific solutions."

Industry clouds are the point of the sentence. Deep, industry-specific solutions are what the record claims. It does not claim that an account copy is the solution. A search for a Salesforce Vlocity app is a search for that industry cloud, under the name Salesforce Industries, or Industries Cloud, as the sentence allows. It is not a search for a generic account sync with the old logo in the corner.

The sentence does not name a screen. Do not invent an OmniStudio screen the source does not name. If a proposal needs a screen name to sound precise, and the name is not in the record and not on a screen you have opened in your own org, the name is invention. Take it off. You can say industry step. You cannot say a screen you have not stood in front of.

Open the place the industry work actually happens. If the only place anyone can show you is the account, you have not found the app's work. You have found a record almost every cloud can hold. The industry cloud is the one that still has steps beyond that record. Ask the person who performs the next step to show you where they perform it. That place is the app. A slide of verticals is not.

#The connector

A connector that only copies the account drops the industry steps. The object is the industry step. The account may travel with the step, because the step is about someone. The account is not a substitute for the step. If the call writes the account and stops, the industry work did not integrate. It queued itself onto a person, quietly, and the diagram will still look green.

Name the step in the words the team uses for the work, not in a product screen this page refuses to invent. "The order of the industry checks they run after the account exists" is a honest name if that is the work. A trademarked screen name you found in a different customer's story is not. This page will not supply the screen. Your org, opened, might. If it does not, you still do not get to invent one so the connector has a label.

This page does not name an API, a daily cap, a middleware SKU, a connector product, or a price. The record does not name them. A box between the account and the industry cloud, with a vendor name on it, is a poster unless you can say which step the box carries and what you see when the step does not run. If you cannot, remove the box. The connector is the step running after the account is there, or the step not running. Those are observable. A SKU is not.

Write the sentence. This account, this industry step, ran or did not run. If the sentence has no step, it is the account copy. Decline it even when the copy is accurate. Accuracy on the wrong object is still the drop.

#The architecture

The architecture names Salesforce Industries, the industry step, and the failure when the call writes only the account and the step does not run. The account can be on the picture as the record the step needs. It cannot be the only object. Vlocity can be on the picture as the old name, in a caption, so a searcher recognises the page. It is not a second cloud you connect to in parallel with Industries. The sentence says it became Industries. Draw the current app.

Do not draw a screen you cannot open. A rectangle labelled with an OmniStudio name the source does not use is the invention this page forbids. If your org has a screen, and a named person can open it and show the step, you may put that person's words on the picture. You may not promote a remembered demo into the architecture.

A guide book is not the industry step. People search for a Salesforce Vlocity integration guide book because industry clouds sound large. This page will not invent the book, and it will not invent the screens a book would pretend to list. The picture is finished when the team can point at one step that must run, and at the account copy that is not enough.

Extra industry products do not go on this diagram as decoration. The record says industry-specific solutions, plural in spirit, and does not name your vertical's objects. Name only the step you have seen. A diagram of every industry Salesforce sells is a catalogue of someone else's shelf. It is a poster in your workshop.

#When the call does not land

The failure is an industry step that does not run. The account is present. The step is not. That is the call not landing. Write the account you can find, the step that should have followed, and the time you asked the person who runs the step. A ticket that says the Vlocity sync succeeded, because the account arrived, has celebrated the drop. Reopen it. Success is the step.

Check the system. Did the call land in Salesforce Industries, where the step is performed, or did it land on an account in a place where that step does not exist? An account in the wrong place is a copy, not an integration. Point the next attempt at the industry cloud, and do not call the first copy a phase one. Phase one that drops the step teaches the programme to stop at the account forever.

Then check the object. Was the step named before the call, in words the team recognises? If the design never named it, the call could not land it. The fix is to name the step, not to add a screen from a slide. If the step was named and still did not run, write that. The account being correct does not soften it.

Do not invent an error code, a screen fault, or a retry cap. If the person who runs the step says it did not appear, that sentence is the status. Quote them, with the time. If a screen you have actually opened shows a state, write that state. If you have not opened a screen, do not describe one.

#An integration names three things

An integration exists only when the page can name the system, the object, and what happens when the call fails. A diagram that does not name those three is a poster.

The system is Salesforce Industries. The object is the industry step. The failure is that the step does not run when the call only copies the account. A proposal that cannot name the step is not a Vlocity integration. It is an account interface with a vertical word in the title. Change the title or name the step. Do not proceed on the account alone.

The same test rejects invented screens. Do not invent an OmniStudio screen the source does not name, and do not accept one from a partner who cannot open it in your org. The test rejects a middleware name, a fee, and a daily cap. None of those make the step run. The step runs, or you record that it did not.

Keep the three sentences above any map of systems. You may add a box only when it carries the step or explains the account the step needs. A box that says "orchestration" and does not name the step comes off. Orchestration you cannot point at is a poster word.

#The other two pages

This page is not the implementation page, and it is not the page about what happened. How the industry cloud is designed, and which steps belong in a change, is implementation. That work is on the Vlocity implementation page. The purchase and the rename as history are on what happened to Vlocity. Stay here for the app, the step, the architecture, and the call that writes only the account.

Do not let a successful account copy close an industry design. The copy can be true and still drop the step. This page tells you to notice the drop. The other pages tell you what was bought, and how a real change to the industry work is scoped. Link them. Do not buy a connector SKU to glue the link. This page will not name one, and it will not print a price.

A partner who brings a guide book of screens has brought names this record does not contain. Ask them to sit with the person who runs the next step, and to write the step in that person's words. If they cannot, they are early. If they can, and the step did not run after the account landed, you have the incident. The book is unnecessary. The step is not.

Write the account, the step, and whether the step ran. If you cannot name the step, you are not ready to integrate. Go and watch the work. Then put the step on the diagram and take the account-only arrow off. When the step runs, say so and stop. When it does not, say the call wrote only the account. That sentence is the whole incident. Do not decorate it with a screen you have not opened.

The next account that arrives gets the same test before anyone calls the interface healthy. Ask the person who owns the step whether it ran for this account, not for a sample chosen because it looks tidy. A tidy sample hides the drop. The ordinary account is the one that tells you the call lands. If the ordinary account only produces a record, and the step stays on the desk, the connector is still the account copy. Leave the status at failed until the step runs for that ordinary account, in Salesforce Industries, with the step named in the team's words.