Settles a contradiction by recording a fix, archiving an article, or having the editor rewrite the articles.
`method` says how, with an optional `note`: <list type="bullet"><item>`MARK_FIXED` (the default) — the person already fixed the articles; nothing is written. It becomes RESOLVED, and while the articles read the same later runs do not raise it again.</item><item>`ARCHIVE` with `documentId` — the article is out of date as a whole. It is archived at once and leaves search at the next publish; the contradiction becomes RESOLVED.</item><item>`ALIGN_TO_SIDE` with `documentId` — that article is right. The base's editor rewrites each other article that takes a side on what it says, to agree with it. Refused with 400 when no other article does.</item><item>`ADD_CONDITION` with `condition` — each is right depending on it. The editor adds it to every article that takes a side.</item></list> The editor's rewrites run in the background: the contradiction becomes RESOLVING, each rewritten article keeps serving what it says now, and each rewrite is held for review in Suggested changes. Once every rewrite is decided it becomes RESOLVED if each article was rewritten and approved or already said the chosen answer (`nothingToChange`), and OPEN again otherwise, with what the editor did with each article in `corrections`. Refused with 400 when the base's editor cannot run, and 409 when it is no longer open.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The knowledge base id.
uuidThe contradiction id.
uuidThe tenant identifier
How to settle it, and an optional note.
Why, in the person's words — what they fixed, or why the articles do not actually disagree. Optional.
How: MARK_FIXED (the default — the person already fixed it), ALIGN_TO_SIDE, ADD_CONDITION or ARCHIVE.
"UNSPECIFIED" | "MARK_FIXED" | "ALIGN_TO_SIDE" | "ADD_CONDITION" | "ARCHIVE"For ALIGN_TO_SIDE, the article that is right; for ARCHIVE, the article that is out of date.
uuidFor ADD_CONDITION, what both articles' being right depends on — "if the supplier card names a channel".
Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/knowledgeBases/497f6eca-6276-4993-bfeb-53cbbbba6f08/contradictions/497f6eca-6276-4993-bfeb-53cbbbba6f08:resolve" \ -H "Content-Type: application/json" \ -d '{}'{
"id": "00000000-0000-0000-0000-000000000000",
"knowledgeBaseId": "00000000-0000-0000-0000-000000000000",
"origin": "FACT_CHECK",
"title": "string",
"points": [
{
"about": "string",
"sides": []
}
],
"documents": [
{
"documentId": "00000000-0000-0000-0000-000000000000",
"title": "string",
"sectionTitle": "string",
"status": "DRAFT",
"changedSince": false
}
],
"changedSince": false,
"status": "OPEN",
"resolution": "BY_PERSON",
"resolutionNote": "string",
"resolvedBy": "string",
"resolvedAt": 0,
"chosenDocumentId": "00000000-0000-0000-0000-000000000000",
"condition": "string",
"resolutionRequestedAt": 0,
"resolutionCompletedAt": 0,
"corrections": [
{
"documentId": "00000000-0000-0000-0000-000000000000",
"documentTitle": "string",
"outcome": "APPLIED",
"reason": "string",
"nothingToChange": false,
"executionRecordId": "00000000-0000-0000-0000-000000000000",
"review": "WAITING"
}
],
"runId": "00000000-0000-0000-0000-000000000000",
"executionRecordId": "00000000-0000-0000-0000-000000000000",
"firstSeenAt": 0,
"lastSeenAt": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}