Document work started from the assistant¶
HiveAI can help prepare a document-work result or direct you to a protected upload, viewer or signing experience. These are different activities, with different evidence of completion. Returning to the conversation does not by itself mean that a record was updated or a workflow task finished.
The shared document services implement these capabilities. The complete assistant journey, protected navigation and connected frontend are still being verified. This guide explains the supported meanings and recovery rules; it does not introduce a new screen sequence. Use the owning work area's verified guide for its controls and final result.
Record a document-work result¶
The assistant integration supports three kinds of completed document work:
| Result | What is recorded | What to check |
|---|---|---|
| Review | The result of a document review | The intended document version, review evidence and actual completion time |
| Processing | The result of document processing | The processed artifact, its version and evidence of the work performed |
| Release | The result of a document release | The released artifact and evidence supporting the recorded result |
These records use the same underlying completed-work capabilities described in document outcomes. Recording a review is not automatically a workflow approval. Recording a release is not proof that a recipient received a file. A signature or upload is also a separate operation.
A proposed result needs a clear work context, result, evidence reference, document reference and version, and start and completion times. Optional information can include a due time, quality assessment or a correction linked to an earlier result. Use actual evidence; a proposal is not evidence that the work happened. Raw file contents and signature material belong in the protected document experience, not in the result description.
The service prepares a short-lived review of the proposed result against the current document-work state. Its preview lasts five minutes, but access or approval may expire earlier. A preview does not save the result or guarantee that all business rules will pass. If the work changes or access is removed, obtain a fresh review through the supported journey.
Before accepting a proposed action, check the organization, intended work, document version, result and evidence. After execution, read the actual returned outcome and confirm the saved result in its owning work area. An action whose processing is finished may still report that the requested change was unavailable. Reporting recovery explains why a saved result and its appearance in downstream reporting may happen at different times.
Continue in a protected document experience¶
A protected handoff gives the application a limited opportunity to continue the selected operation outside the conversation. The shared preparation expires after ten minutes; permissions or the underlying document session may end access earlier. Stay in the same organization and use your own identity and selected document version.
| Activity | What the shared return can establish | What still needs confirmation |
|---|---|---|
| Upload | The selected upload reached the returned state | Whether a usable file was finalized and then attached or consumed by the business action |
| View | A matching, unexpired viewing session exists for you and that version | Whether delivery and display succeeded; it does not establish that you read or approved the document |
| Sign | A matching sealed signature artifact is associated with the signable session | Whether the owning record or workflow accepted and applied that artifact |
An upload can change state because you discarded it. A successful return check must therefore be interpreted together with its actual result; it is not a general “upload complete” signal. A separate finalized-file check is stronger, but the owning business action still needs to accept the file.
For the detailed boundaries, see upload and viewing, attachment and consumption, and signing. Those guides explain why staged files, attached files, signed artifacts and completed business work are distinct.
Recover without repeating completed work¶
| Situation | Next step |
|---|---|
| The proposal expired or the work changed | Review the current work and obtain a fresh proposal through the supported action |
| Permission was removed | Ask the appropriate administrator to check current access before continuing |
| The protected handoff expired | Return to the owning work area and check the original operation before starting another |
| The file operation succeeded but returning to the conversation failed | Preserve its document or operation reference and confirm the saved source result |
| Upload was discarded | Treat the returned state as discarded; begin another upload only when the business task still requires one |
| Signing returned but the record is unchanged | Check the source's signing or submission status; a staged signature alone does not complete the task |
| The action is pending or its result is unknown | Keep the original operation reference and let the supported recovery or support process reconcile it |
| The action reports unavailable | Read the reason; verify whether any source result was saved before making a new attempt |
Do not repeat an upload, signature or completed-work action solely because the conversation did not receive a response. Give support the organization, work item, document/version, operation reference, time and visible result. Do not send session credentials or signature material as troubleshooting evidence.
Managers and executives should measure the business result separately from assistant activity. A prepared proposal, a return to the conversation, a live viewer and a completed source task are different milestones. Support should preserve that distinction when explaining progress or resolving uncertain outcomes. Initial reader review and the connected assistant walkthrough remain pending.