Skip to main content

​
Deploying & Rejecting Drafts

Once you have iteratively edited and tested your Analysis Field Draft and are confident in its performance, you need to take a final action: either Deploy the changes to make them live or Reject the draft if it’s no longer needed or incorrect. These actions are typically performed from the Draft Editor page (/settings/analysis/drafts/[id]).

​
Deploying a Draft

Deploying promotes the prompts (Instructions, Rubric, Directions, etc.) from your draft version to become the new live version of the Analysis Field (or the specific Configuration Link override, if the draft was created at that level).
  1. Ensure Thorough Testing: Confirm that your draft performs accurately and as expected across a representative set of test interactions (Testing Drafts).
  2. Navigate to the Draft: Open the specific draft version you want to deploy.
  3. Click “Deploy Changes”: Locate and click the “Deploy Changes” button (or similar).
  4. Confirmation (if any): You might be asked to confirm the deployment.
  5. Backend Process: Fabius updates the live field/link with the content from your draft and typically updates the draft’s status to Deployed. The field’s overall version number likely increments.
Impact of Deployment:
  • Immediate Effect: All subsequent analyses run by configurations using this field (or specific link) will now use the newly deployed prompts.
  • No Retroactive Change: Deployment does not re-analyze past interactions. Results generated using previous versions remain unchanged.
  • Draft Archival: The deployed draft usually becomes read-only or archived. To make further changes, you’ll need to create a new draft based on the now-live version.

​
Rejecting (Archiving) a Draft

If a draft is experimental, incorrect, superseded by another draft, or no longer needed, you should reject it to keep your workspace clean.
  1. Navigate to the Draft: Open the specific draft version you want to reject.
  2. Click “Reject Draft”: Locate and click the “Reject Draft” or “Archive Draft” button.
  3. Confirmation (if any): Confirm the rejection.
  4. Backend Process: Fabius updates the draft’s status to Rejected.
Impact of Rejection:
  • No Effect on Live Prompts: Rejecting a draft has no impact on the currently live Analysis Field or Configuration Link prompts.
  • Archival: The draft is typically hidden from default views but may be accessible in a history or archive section. It cannot be deployed.
Regularly review and reject outdated or unnecessary “In Progress” drafts to maintain clarity in your field management.
Deploying and rejecting drafts are the final steps in the iterative development cycle for your analysis logic, ensuring changes are controlled, tested, and managed effectively. Next: Learn about adding advanced context: Using Knowledge Documents | Using Custom Fields