Attesting an integration

An integration's own page lists the data that moves between two products: a model, a schedule, an RFI, and so on, each in one direction. We call each of those a data flow. In the portal they are the rows under Data that's shared. The public integration page shows the same rows as types of data, under headings such as "Sends to (other product)". Most of them were recorded by AEC Integrations from public sources. Answering Yes or No on that page is how the company at either end says whether a flow is right.

Answering needs a seat and the Managed plan. A company on Free can see every flow and every answer, but cannot answer. See Your seat and Plans.

In the vendor portal, open one of your products, choose Integrations, then choose the integration from the list. Each integration has its own page, with a Data that's shared section listing every flow.

A row you have not answered yet has two buttons:

• Yes says the flow is right.
• No says it is wrong.

Yes saves at once. If the other company has already said No, choosing Yes instead opens a short form so you can add a note explaining your side. The note is optional there.

No opens a form asking why. Give a reason: it is required, so the other company and AEC Integrations know what to fix. If the direction is wrong, say so there too. Saving records your No and adds a corrected row for you, in one step.

Once you have answered a row, it shows your answer as text, Yes or No, with a Change link beside it. This stops a stray click from changing an answer you meant to keep.

Choose Change to bring back the two buttons for that row. Then choose the other answer, or choose the pressed button again to take back your answer. Press Escape to leave the row as it was. Once you save, the row shows your answer as text again.

If you say No because the direction is wrong, the page records your No on the row and adds the corrected row for you. It shows the two together: the row you said No to, and under it a box headed You submitted a change. The box says what the direction becomes, gives your reason, and says whether the other company has answered the corrected row yet: it has not answered, it agrees, or it disagrees. If it gave a reason, choose the i button beside that line to read it.

The box ends with two links:

• Change opens the reason form again, with your reason and the corrected direction filled in. Edit the reason, pick another direction, or pick another reason for the No.
• Cancel takes back both answers: your Yes on the corrected row and your No on the original. The original row then needs your answer again.

A corrected row you added stays on record after you cancel the change or pick another direction. It shows again as a row with no answer from you. See Current limits.

Your note is not public. Only the company at the other end of the integration and AEC Integrations see it. If your company makes both products, only AEC Integrations sees it.

Several people at your company can hold seats, but your company has one position on each flow. The latest answer from anyone at your company is your company's answer.

You can answer on any integration where one of your products is at an end. An integration that runs through a connector product shows its rows as Not needed: AEC Integrations keeps those up to date, and neither company answers for them.

If a flow is missing, choose the Add data that's shared button above the table. Pick the data type from the list, set the direction, and add a note if it helps. Adding a flow also records your company's Yes on it.

The list of data types is fixed. If what you need is not on it, tell us through the correction route.

The public integration page shows where each flow stands. It shows each company's answer, but never its note. Your company counts once, however many seats it holds. What readers see does not depend on either company's plan. An answer already on record shows the same way whether its company is on Free or Managed.

Where it stands	What the page says
Nobody has confirmed it	Listed by AEC Integrations
One company confirms	Confirmed by (that company)
Both companies confirm	Confirmed by both companies
One confirms and the other says no	Companies disagree
Only "no" answers	Listed by AEC Integrations

A flow reads "Listed by AEC Integrations" until a company confirms it. AEC Integrations' own record is never counted as a vote, so it cannot create a disagreement.

If your company makes the products at both ends, it still has one position. That flow can show "Confirmed by" your company, but not "Confirmed by both companies".

The integration page updates shortly after you answer. Search results catch up on the next nightly update.

The page tells you, on the integration's own page, what your answer sets in motion. In short:

• When you say Yes and the other company has not answered, it is reminded after 14 days.
• When you say No, the other company and AEC Integrations are told. A No does not delete the flow. It stays on the page, shown as the table above describes, until we look at it.
• When the two companies disagree for 7 days, we email both and review the listing.
• When your Yes is 12 months old, we ask you to confirm it again. It does not expire, and the public page shows it as before.

"Confirmed by" and "Confirmed by both companies" mean the companies at the ends of the integration stand behind that data flow. It is a statement by the companies, not a test by AEC Integrations.

• Previous: Your seat.
• Next: Owning an integration.
• Contests and protests, for asking to change an integration's other details.
• How we research and verify listings.