New and Changed Objects in Document Generation and Contracts

Do more with these new and changed Document Generation and Contracts objects.

Store requirements for specific use cases, such as associating an LLM model with a template for extracting contract details
Use the new AdditionalUseCaseInput field on the existing ContextUseCaseMapping object.
Specify the mode of document extraction
Use the new ExtractionMode field on the existing ContractExtractionResult object.
Specify the Document AI configuration used to extract documents in bulk
Use the new DocumentAIConfiguration field on the existing ContractExtractionResult object.
Store the unique identifier of the Document AI job that generated the extraction result
Use the new DocumentAIJobIdentifier field on the existing ContractExtractionResult object.
Store the unique identifier of the source document in a connected external repository
Use the new SourceDocumentIdentifier field on the existing ContractExtractionResult object.
Identify the sequence number of a sub-batch within a larger batch extraction job
Use the new SubBatchJobSequence field on the existing ContractExtractionResult object.
Localize date, time, currency, and text formats in generated documents
Use the new IsLocalizationEnabled field on the existing DocumentGenerationProcess object.
Route document generation through Large File Size infrastructure

Use the new ShouldUseLargeFileSizeProc field on the existing DocumentGenerationProcess object.

Generate an update table of contents for your document
Use the new IsTocUpdateRequired field on the existing DocumentGenerationProcess object.