Functionality of Generated Documents that are Recrawled

You can upload the document to the source system, allowing customers to review, update if needed, and send it back to the data store on your Aisera GenAI platform. During recrawl, the updated content from the source system will override the corresponding generated documents.

The following table describes possible use cases

Use Cases	Impact when the published document is crawled back.
Case 1: Generated Documents Uploaded to Aisera Only	Since the source system lacks the generated document (as it was not published to SOR but only exists in Aisera), recrawling from the source system has no impact, and no document will be overridden.
Case 2: Document Exists in Both Aisera and SOR	When a document exists in both systems, any updates made in the source system and recrawled will override the corresponding document in SOR → Knowledge and the Knowledge Generation page. To help identify Aisera-generated documents that have been recrawled, a label is provided for these documents. Tabs where recrawled Aisera-generated documents are labeled: SOR: Knowledge Details page Content Generation: Knowledge Generation → Knowledge Details page Content Generation: Knowledge Generation → Similar Documents
Case 3: Document Uploaded Only to SOR	Since the generated document is stored in SOR and later crawled into Aisera, the version in the Knowledge Generation page will be overridden. However, as the document does not exist in SOR → Knowledge within Aisera, there is no further impact. The label for recrawled Aisera-generated documents will be visible on the Generated Document page as mentioned above.
Case 4: Document Exists Only in the Knowledge Generation Page	As the document has not been published, recrawling has no impact.