Now Assist Extract Information from Document
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello,
Has anybody recently used "Now Assist Extract Information from Document".
I'm trying to extract information from document. To be more precise, invoice where it is generating a document task. But Source record is coming as empty because of which no mapping of data is taking place.
Anybody faced something similar?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @ritik-rajen
May you use this tool as alternative
This helps other users find accurate and useful information more easily
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @ritik-rajen ,
Yes, this behavior usually means that the Document Task is being created without being associated with the original Invoice record.
The Source Record is important because the OOB Extract Values process uses it to determine which record should receive the extracted values.
I would troubleshoot this in the following order.
1. Verify the Use Case Target Table
Open:
Now Assist Admin > Skills
-> Platform
-> Extract information from documents
-> Edit
-> Open your Invoice use case
Verify that Target table is populated with the table containing the original Invoice record.
For example:
Invoice
-> <your invoice table>
The Target Table must be configured before using the OOB integration/mapping functionality.
2. Verify the Process Task integration
On the same use case, check the Integration configuration.
You should normally have:
Process Task
-> Creates and processes the Document Task
and:
Extract Values
-> Copies the extracted values back to the source/target record
If Process Task was created manually or the generated Flow was modified, check the Flow in Workflow Studio.
The expected architecture is:
Invoice record created/updated
-> Attachment exists on Invoice
-> Process Task Flow
-> Document Task created
-> Source Record = Invoice record
-> Document processed
-> Document Task = Done
-> Extract Values Flow
-> Update Invoice fields
The attachment should normally be attached to the Invoice/source record, not independently uploaded to the Document Task.
3. Check the generated Process Task Flow
Open the Flow generated from the Process Task integration.
The trigger should be based on the Target Table configured for the use case.
For example:
Trigger:
Invoice record created/updated
Then inspect the Document Intelligence action that creates/processes the Document Task.
Make sure the current Invoice record from the Flow trigger is being passed as the source/target record.
Conceptually:
Source Record
-> Trigger - Invoice Record
Use Case
-> Your Invoice extraction use case
If only an Attachment sys_id is being supplied and the source Invoice record is not passed, the Document Task can be created but Source Record can remain empty.
That would explain exactly what you are seeing.
4. Check how the Document Task was created
If you manually create a Document Task and upload the invoice directly to that Document Task, Source Record does not automatically become your Invoice record.
For testing from an existing Invoice record, the attachment should be on that Invoice and the Document Task should be created through the Process Task integration.
ServiceNow specifically supports linking a Document Task to another record using Source Record so the attachment on that record can be processed.
5. Verify field mappings
After Source Record is populated, verify each extraction field has:
Target Table:
Invoice table
Target Field:
Corresponding Invoice field
For example:
Invoice Number
-> Invoice.number
Invoice Date
-> Invoice.invoice_date
Total Amount
-> Invoice.total_amount
If Source Record is populated but Target Field mappings are missing, extraction may succeed but nothing will be written back.
6. Verify the Extract Values integration
Make sure the Extract Values Flow is:
Active = true
The flow should run after the Document Task reaches:
Status = Done
It then uses the Source Record together with the Target Field mappings to update the Invoice.
7. If this is an OOB Accounts Payable Invoice flow
If you are using the Accounts Payable Operations / Invoice Processing content pack, I would not directly update sys_di_task or add a Business Rule to populate Source Record.
Compare your Flow with the OOB Process Task / Extract Values flows first.
If the OOB flow was copied, verify that the copied flow still contains:
- Correct use case
- Correct Invoice target table
- Correct source record data pill
- Correct extraction field mappings
A copied use case or copied Flow with an old/missing use-case reference is a common place to look.
8. Security check
If Source Record is populated but mapping still does not occur, check:
- Target table Can read
- Target table Can update
- ACLs
- Cross-scope access
- Application Access
The OOB Extract Values Flow updates the target record like any other GlideRecord-based process, so normal platform security still applies.
Recommended test:
Create one Invoice record manually
-> Attach one invoice PDF
-> Trigger Process Task
-> Open the generated Document Task
Before proceeding further, verify:
Source Record = your Invoice
If Source Record is empty at this point, stop troubleshooting the field mappings. The issue is in the Process Task Flow/input configuration.
Once Source Record is populated correctly:
Document Task = Done
-> Extract Values
-> Invoice fields should be updated according to the mappings.
So the first thing I would fix is not the extraction mapping itself. I would trace the generated Process Task Flow and verify that the original Invoice record is passed when the Document Task is created.
Official references:
Set up a Now Assist Document Intelligence use case:
https://www.servicenow.com/docs/r/intelligent-experiences/now-assist-in-document-intelligence/set-up...
Integrate Document Intelligence with a workflow:
https://www.servicenow.com/docs/r/intelligent-experiences/document-intelligence/configure-integratio...
ServiceNow Employee example - Document Intelligence with Flow Designer:
https://www.servicenow.com/community/intelligence-ml-articles/using-document-intelligence-with-nbsp-...
Hope this helps!
If this response helped, please mark it as Helpful.
If it resolves your issue, please Accept it as Solution.
Kind Regards,
Abhishek Pal
