Document Intelligence and Flow Designer able to create two records based on one document

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2023 08:31 AM
Hi All,
We are currently looking to implement Document Intelligence and are wondering if we would be able using Flow Designer and the information from the source table, to create two different records based one document.
We basically get a large PDF document with a lot of information on it send to ServiceNow and need to create these two items:
1. A new case in CSM using some of the information
2. A Consumer record using some user details on the form
Would this be possible?
Thanks in advance.
- Labels:
-
Customer Service Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2023 10:51 AM
Christian, as i'm sure you are aware the easy path for Docintel is a workflow around one task type. I could see a couple of options to support your use case.
1. let's assume the PDF comes in and creates a di_task against one task definition where you define the keys you want for the case and for the consumer record. These values are extracted using DI and are now available in the extracted values table di_extracted_value...from there you can write a flow to grab those values and do what you'd want to do.
2. My guess is you may want the PDF to come in and create a case and if no consumer record you intend to create it from the data on the PDF. In that case you could setup your task definition in a standard way using the case table as target table and processing the case keys and values and even mapping the keys you need to case record to that record, you could then define keys for the consumer record but don't map them just have them as extracted values then use flow designer to hit the extracted values table grab them and create a consumer record.
3. You could the above with 2 task definitions, case is easy....for consumer source table = case target table = consumer.
4. Or option to process in interaction table...create 2 task definitions one for case one for consumer source record is the interaction and they both parse the document...if as I assume you want the consumer record tied to the case you'd need to have a way to know the case you created...
is this helpful?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2023 02:29 AM
Thanks for the reply Brian and for confirming that what I'd hoped we can do is actually possible. I wouldn't have thought of the option#4 as this is exactly what we need. Every time a new PDF form comes in, we need to create a case for it using some of the document details and then also create a consumer record and tie those back to the case.
I'll see how I get on with setting it up 🙂