Modern FOIA Solution – Full Webinar
Modern FOIA Webinar – Demo Only
ARMEDIA FOIA WEBINAR TRANSCRIPT
Matthew Maines: Thanks, James. Alright. So, before we actually get into this, there’s a lot we want to cover for ArkCase FOIA. But I do want to give you kind of a high-level story of what we’re actually going to show today.
We’re going to show a specific use case. That use case is going to be submitting a new request. We’re actually going to send it out the customer today, is going to be myself. We’re going to send it through the web portal and then we’re going to actually see and process it right through the actual different queues in the ArkCase FOIA system.
We’re going to make it very simplistic. It’s going to be all done in this short period of time during the demo, from intake all the way through a release or distribution.
We’re going to show you some of the things that you can do as you process it through the different queues, like redaction. We’ll do the fill step, we’ll probably read acts something and then in the approves that will actually burn it. Once again this is a very simplistic workflow that you’ll see today.
Let’s just think about how you can compound that over days or multiple users and we’ll talk a little bit about that.
So, this is the high-level flow you’re going to see portal all the way through to ArkCase through the service API’s and then we’re actually gonna process it to the workflow and then distribute to the portal.
And we’ll spend a little bit of time on some of the other bells and whistles like the reporting module, to search module and definitely the admin to show you some of the configurations that drives this.
But before we do this actual workflow, let me jump out to the application and let’s go ahead and jump into the application.
So when I log in, I’m actually logging in as my personal user. What you’re going to see here on the screen is my view.
And when I say my view, this is ArkCase handles everything with role-based access control. The login was a manual login, as you can see there, but once again you do have the ability out-of-the-box to do single sign-on so integration with Kerberos SAML, any CAC or PIP authentication that is available out of the box that just needs to be configured.
Today, what you’re seeing here, just from a high level to get you used to what you see on the screen and how the navigation works before we do the actual overall workflow, is you have your navigation, your modules on the left-hand side. Once again, role-based access, so whoever has acts to these modules obviously that role dictates it.
So, I logged in as someone like a supervisor or even just a basic day-to-day analyst. They may only see say the Q’s module in their dashboard. They may not see all these other modules that we’re seeing today.
Also, at the top, you do have global new, we won’t need to create any of these. We’re going to create a request from the actual web portal and automatically will ingest.
But you also do have your simple search that leads in your search module and then your internationalization up at the top. Once again, the landing page is the dashboard page, this is kind of your jumping-off location and we’ll use this as part of the workflow.
So let’s go ahead and get into what that workflow looks like and then we’ll come back to some of these other modules and talk about them after the workflow.
So, as I transition, we’re going to transition over to the sample web portal, and as you can see, here we’re going to go ahead and just submit a FOIA request.
I’m going to say that I want to know the 2016 federal budget. Not all of these fields are mandatory, but as you can see here, there are some that you must you know, you have to enter specifically name and email address that type of thing and we’re going to populate that.
Some of these other fields are obviously configurable whether their meanings are optional.
All the dropdowns are controlled through the admin module which will show up in the look-up tables later.
Once again, this overall view or form, this angular form is also configurable, so once again out-of-the-box it provides some of the main pieces of information that most businesses need to collect from a FOIA perspective.
But once again, this can be configured to meet your requirements. Some of these other fields we’re just going to leave blank. Anything from expedite or how much you’re willing to pay, so on and so forth.
So, I’m going to go ahead and enter in my information and I’m going to submit this request.
So a couple of things are happening at this point. Not only with this ingestion method specifically the web portal, but whether it was email ingestion that creates a request or fax ingestion. We’ve had clients using fax with a drop folder and ingesting.
No matter what option you utilize as it pertains to getting the FOIA request into the system, you ultimately are seeing that were leveraging the open API’s of ArkCase FOIA. And at the same time, when we’re taking this information, not only are we putting it in the actual application persistent in the database, we’re also utilizing Alfresco’s Document Management to store all of the actual files.
When I say the files on creation of a request, we actually take the metadata that’s collected and we create an actual PDF file.
We place all the information in the right location and that becomes your quote to quote request document. So it’s actually in document form and has been being saved out on the Alfresco Document Management section of share which you’ll see a little bit later.
At the same time, we are also taking this through the process. We’re going to leverage the Document Management throughout the process.
That’s going to be channeling all the versioning control and then, when we move to a state of release, we’re actually going to use Alfresco as Records Management, to seamlessly move this document into making it a record and moving it to the file management plan which you’ll see here in just a minute.
So with that being said, we’ve already submitted an actual request.
Let’s go ahead and jump into the Intake Queue. All I did was actually click on the actual bar from the actual widget right there on the home screen. And as you can see here, when I open up 137 (which is request 137), it’s going to populate the information of the 2016 federal budget as you can see here.
Not only are we loading actual data, but we’re also living the actual view of not only the request form, as you can see in the first half but also the acknowledgment letter.
The acknowledgment letter is just a correspondence template that actually populates the information. These are just sampled templates that can be used out-of-the-box. Or can be configured to meet specific requirements or leverage forms that you are ready use.
So once again, tthis acknowledgment letterby default in this in the out-of-the-box FOIA sends an email to the end user. As you can see here, we said we’d send an email. That’s the email of the acknowledgment letter. Okay?
With that being said, let’s talk about some of the information associated to the actual request.
First off, we have the request or information that came in. As an intake person, some of the main things that you’ll have to do is obviously pick a request track. Is it simple, complex, expedite… These are specific things that have to be tracked and said and persisted, so you can report on them on the DOJ reports that we’ll talk about a little bit later and the report module.
Additionally to that, you can add additional information. Maybe that all the populated information wasn’t populated or someone called in and gave additional information – you can actually add that.
You also have the ability to dictate maybe the spelling of the request surname was wrong or the address is wrong, you can update that information, okay?
So once again, to accelerate this due to time, we’re going to go ahead and just move this on in the in the overall path.
But before I do that, I want to point out the buttons at the bottom, that allows me not only to send this maybe over to the whole queue, maybe you’re waiting on something, maybe all the information is not there.
Maybe you need to delete this because it’s a duplicate.
Maybe you need to send this on to maybe the next queue and continue to work on it or you can actually send it on and queue up the next individual request in the queue.
And that’s what that next buttons for.
So for instance, I am an actual person that works all day on the intake. That’s my only job, I process intake and I make sure that moves on into the next queue. I can do that by just basically looking at these individual intakes you like we’re seeing now and populating the information and hitting next. It’ll just queue up the very next request in my intake queue.
But because I’m an admin and we want to see this single request go through the whole process, I actually had the access to complete this.
By hitting this complete button, it’s actually going to update my status and it’s going to actually ask me specifically about my category. So I’m going to go over here and actually show you different views.
So, one of the things that we have to update is the actual category. If the end user populates it which I forgot to do on the web portal, if you populate it here, you’re actually able to see that it’s authentic eighths it gives them metadata. So if we go back into this specific request and go ahead and try to complete this, you’ll see that it actually will move on no problem.
So once I actually open up this request again in the actual intake queue, we’ve already got all the information populated here so I’m going to go ahead and complete this and move this on into the next queue.
Once I complete it you’ll see that the actual status is now moved to In Fulfill. So at any one time the end user, the person that submits the request they can come in and check the status of their request and see where it is in the overall process. If you scroll down 137 is currently in fulfillment, okay?
You’ll see some of the other requests that they’ve actually done in the past and we’ll talk a little bit more about that here shortly.
With that being said, let’s switch gears!
Now we’re no longer taking the intake of this request. We’re actually starting to process or fulfill it. There are many ways to fulfill this request, but we’re going to use the most simplistic way today just due to time.
The folder structure you have within the actual request view. We have a working request folder which is these two documents that automatically get created and stored in the Alfresco Document Management.
You can see them both loaded here. We also have a working folder and a response folder.
The working folder allows you to upload as many documents as you want, whether it is from a network drive.
Maybe you’re searching a system outside of Alfresco.
Maybe you want to search just Alfresco.
There are many different ways to upload documents into your working folder. You even have the ability through the Outlook or the Alfresco Outlook connector. If you have it tied to your Outlook you can actually drop files directly from your email into this folder.
So there’s a lot of different things that you can do if you decide to configure and leverage those.
So let’s go ahead and just look at adding real quickly from my network drive, you’ve got some sample files. I’m going to add four files that cover the 2016 budget. Maybe these are the files that will fulfill this response, okay?
So, once these have been added to the actual folder, the actual folder will actually show you some information – not only the title and what kind of documents, but:
- Who uploaded them,
- Are they’re active,
- They’re not actually records, so they actually can be worked on, and
- What version there are.
Let’s just say that as the person is doing the fulfill, they have to go through each of these documents and make sure that one, they’re in the right document.
So, as you can see or we’re going to go ahead and load just in the tab the document. You can move through the different pages, make sure that everything looks good.
You even can search for keywords, so maybe you’re looking for SSN or something that you may need to redact you do have the ability to do a quick search and then you can redact all matches or redact one and move on.
Or you can do what I’m going to show you now which is just be able to redact a single area. I’ll go in here I’ll go ahead and redact. Once you redact an area this is just what we call an overlay, so we can still be moved around.
But I can actually tag it as a specific exemption code. So let’s just say that due to national security we’ve got to protect this area, okay?
With that being said, you can still add any other types of annotations, at this time. You can add rubber stamps, which are configurable maybe it’s a signature. Maybe it’s a line to underline a section. Maybe it’s a note to the next step in the overall workflow that you want them to look at something. Maybe it’s something you want to note to say that you need litigation to look at it.
Whatever it may be, you can add that right here to the actual physical document.
So we’re going to go ahead and save this. So basically what it’s doing is it’s saving that as the current version, but just an overlay. When we burn this in the next step you’ll see how it version controls the document.
So with that being said, this is a very very simplistic story. This may take hours and hours or days of researching and finding documents. It may take many hours of looking at each of these documents and redacting the key sections out that you need to redact to make it a final document.
Maybe you actually have multiple tasks that need to be sent out to many different users and as you can see, here’s a start basic task. We can fire a task directly from the request and say: “Hey Sally, please go ahead and look for this set of documents.”
Whatever it may be, you can do that very easily. Specifically, if your workflow dictates you having automatic tasks sent out on every single request to a set group for them to do certain pieces of the step of the workflow, through configuration we can change your workflow.
We can use this out-of-the-box workflow we just add some automated tasks that fire, when you hit, say that’s fulfillment queue, whatever it may be. Really depends on your requirements, but ArkCase is flexible in the configuration that it allows.
The Overall Workflow
So with that being said, let’s go ahead and move this on the overall workflow.
We’ve gone through the intake, we populated the basic information, we’ve now done some fulfillment by finding the documents and actually ended up redacting something.
We’re going to go ahead and send it on to be approved, so it can be finalized so it can be burnt and then it can be placed in the actual response order.
As you’ll notice here, we’re still on the same page, I haven’t the roles of admin to complete this and move it on. As you can see here, we’re now in the approval state.
With that being said, I can go in here and I can go ahead and just burn this actual version one. The great thing is here is that I’m accelerating this overall path.
You know, there may be a lot of other things that have to be done by the approver himself. The reality is, he can go back in here and look at the updated document if he wants to look at the updated document – as you can see we are on version two of one. Like I told you earlier when we were redact something, it actually shows the original and then it burns the new version. So it does not affect the original version.
As you can see here, the new 2.0 version has now burned the redaction – you can see the exemption code on top of that.
Not only that, but we also populate and capture all the exemption codes on every single document. The reason we do that is once again for the exemption report the DOJ extension report to give you counts, okay?
So once again, just to summarize we’ve taken something from the intake, we fulfilled it very quickly, we then approved it everything is copacetic, everything is good.
There’s a couple of things you can do at this point.
FOIA out-of-the-box allows for the ability to move this through what we call litigation queue.
When I say litigation I mean like General Counsel or some form of higher supervisor approval. You do not have to send it through this General Counsel queue, you can send it if you decide to check the box with litigation, according to the out-of-the-box workflow, but some specific businesses may need it to go through General Counsel or a request to go through every single day. And if that’s the case, we can actually set the workflow up to do that and you would never have to hit litigation – we just go on through.
We’re now going to go ahead just skip that queue though, due to time purposes and go ahead and move it on in the workflow.
So this is another step in the overall workflow which is as you see here, billing.
The Billing Queue
The billing queue is very specific to depending on what type of payment processor that your specific business wants to use. You may already currently have a payment processor. Maybe your payment process is paid.gov.
We have this demo set up to just mark that, but once again we can integrate with any payment processor. Once again, we just use the RESTful API as to communicate send out invoices, have the invoices paid and then we actually process that automatically by automatically checking the paid check box.
But since this is a demo environment, we don’t have that set up to process payment, we’re going to assume that the actual customer paid their invoice and we have been notified that it’s been paid.
Until it’s been paid, it cannot move out of the billing queue. So, per out-of-the-box rules or configuration rules, it has to stay in the billing queue until it’s paid. Once it’s paid and they can move on to be released in the release queue, okay?
So before we do that I want to show you a couple of things.
Before you move it on to be released you have to move the documents, the final documents you want in the actual response folder so that way that they’re the response documents are delivered.
So I’m going to go ahead and show you that this is a full-fledged Document Management. Which means I can make my own subfolders if I decide I wanted subfolders just so you can see that when we actually submit this out, we will actually deliver each of these documents in the order structure that we have here.
So I’m going to go ahead and move all four of these document. I can either drag and drop like I’m doing, I can do a massive drag and drop, I can copy and paste – I can do a lot of different things associated here. So, if I wanted to go ahead and you know cut this and paste it into that folder. I didn’t have to pull everything over if I didn’t want to pull everything over, but I decided to just go ahead and pull everything into this folder, okay?
So once I’ve done that, once again this can be done at really any process depending on if you want to make this the billing step, maybe you want to make this the approve step, at this point you can do it in many different ways. But let’s go ahead and complete this and have this move on to the final step.
The final step is essentially it’s going to release this.
There’s a couple of things that are happening at this point. We’re taking all the final documents or any documents in the response folder and we’re essentially marking them as records and moving them over to the Records Management plan.
So this is the Alfresco Records Management plan.
Alfresco Records Management
So we’ll work within records managers to set up their file folder structure and actually show you how to basically build out your retention policies and we’ll go from there. And essentially this will be a seamless connection.
Once the actual setup for the RM is done and configured, this will be a seamless connection between ArkCase FOIA and the Records Management file plan.
So before we go out and show you where those documents live in Alfresco, let me show you the end result of that specific request we took through the overall workflow.
So as you can see here, 137 has now been released and we actually can see that the actual request idea is an actual download. And as you can see, you can open up the zip file it did maintain the folder structure we gave it and as you can see, we’ve got all of our different documents that are available to us.
And I can’t remember, I apologize I’m not sure which one that I actually marked, but once again, they would get all the final documents which would be your burn documents. Things along those lines, okay?
I wanted to show you where the end result documents were living. So essentially, the anyone outside of a Records Manager really won’t need to worry so much about where the documents live, that’s going to be a seamless thing.
You’ll notice that in ArkCase everything can be done here in ArkCase, just understand that the underlying repository is the Alfresco DM & RM. And once again, it’s seamless once it’s been configured and set up initially, okay?
So let’s kind of switch gears.
The Request Module
I want to go back into the request module real quick and show you the request you’re working today.
The request module is essentially just a different view of the same request we just processed.
So you may be saying: “Hey, that queue management is really nice but I only have three FOIA folks.” We don’t need to through the queues management or anything like that.
Okay, that’s fine, we have a totally different view for you folks.
You have the ability to use what we call the request module. Essentially the same request. You can do all the same things like:
- Implement the collecting information,
- You can send something through litigation,
- You have all the ability to kind of move through the overall workflow,
right here within this at this location.
So, you can move through the individual steps by completing this ticket and move it in on through. You also have access to the document section, like we talked about earlier.
So here’s all our final documents.
So once again, as you can see or they are marked as records. I do apologize, I couldn’t show you and share, but they are marked as record – this is a seamless thing. Additionally, you can see all the different tasks that maybe have fired out for this specific request, so if we had created a manual Task that you can see it here.
So once again, this is just a different view. You can even see the actual person that submitted this and once again, that ties into the people module and things along those lines.
So once again, there’s a lot of functionality that can be used and just depends on how you want to leverage it. Queues and requests module are essentially the same things just different views for the request.
The Task Module
The tasks module also once again, is where it stores all tasks that are in the system.
So this would be maybe you needed a new global task, you wanted to create a task, maybe I needed to meet with James about something. Maybe I wanted to tie a specific task to an actual request, this is how you can see that it’s linked.
So once again you can process these requests or these tasks at any time.
As you can see, or if I move down to a specific task like the Approval of a Costsheet.
So we talked a little bit earlier in the introduction that you can tie a lot of things to an actual, to an actual request.
So we can track cost and time associated to request, whether it’s mine, Matt the user that’s logged in or maybe James has logged in working on the same request finding documents. He can also charge time and cost. This is just a process in which the individual costsheet goes to the workflow.
So once again, there’s a lot of tasks that will be fired. Any task that is associated to a step of the workflow that will have a process diagram, so you know where in the overall process it is.
Cost and Time Tracking
Jumping down into time and cost.
This is what a costsheet looks like. Each person can create their own costsheet and timesheet and they can actually tie it directly back to a specific request, so I can see how much expense is associated back to this request.
I wanted to jump back to the request and take a look at the request and look at the cost or time associated. I could actually see that information right here within the actual, within the actual request, okay?
Time is the same thing. You can track the hours associated and you can tie the actual hours to an actual charge, charge roll and very quickly I’ll show you by editing the timesheet I can show you what a charge roll looks like.
As you can see here, if I go in here and say I needed an investigator who is looking for something and I spent, they spent two hours on Monday. You can see that it costs three hundred dollars an hour, so this is a configurable value in the actual Admin Module.
So once again, a lot of other bells and whistles where you can track time and cost associated to a specific request.
So let’s switch gears once again.
We are able to now process the request and there are many different ways to process a request, but how do you find your information?
Well, the first way is just our Advanced Search.
The Advanced Search can find the information that we’re looking by using keywords or as you can see, we have type ahead.
And what this is doing is searching across all of the metadata are all the persisted data, but it’s also searching across all the documents that have been OCR’d and indexed, so we are searching full text and on metadata here.
This search result is fully configurable. These are the out-of-the-box columns and the out-of-the-box facets or the categorization, so maybe use one of the singing things been released about the budget. You can see that narrows down that information.
Maybe I wanted to see anything about the, you know, something that’s specifically in the intake you like a narrow it down. Once again, these are all hyperlinks that will actually redirect you out to the location so you can see the detail.
Maybe you were looking for a specific file.
You could actually see that there’s, you know, a way to narrow down by an object type like a file.
Maybe I was looking at a specific document, wanted to download it. I can actually download native format and show you what that looks like very easily.
You can jump out to the viewer, jump out to the parent to get where that document is. There’s a lot of flexibility not only finding the information but then navigating to see the details, okay?
There’s also another way to search.
This is a very focused search. So you can add tags to really any layer of the object.
When I say an object, I mean a request a document, a task, whatever it may be so you can categorize things with tags, so it’ll help you find the information much much more quickly so you can see all of these things have to do with a budget tag.
So if I was to go out to any of these locations, you would see that either the document or the request is tagged. So once again just another way to search, but has the same look and feel. Has the search results and has the facets on the right-hand side.
So I’m going to jump over and show you real quick where the tags live.
As you can see here, this is where the tags live. I can add tags not only on the request level, but I also can add them on the document level.
So it’s pipe ahead, it’s are you going to tell me that it’s already a tag and it’s going to let me add a tag there. So I can add a tag here or I can even go in and add a tag in on a document or something like that, okay?
So once again, very easy you can add multiple tags at anyone time. So if I want to need a Tag1 the new tag maybe I want to Tag2. I got as many tags that want on each individual request or document.
Once again, just another way to categorize things, be able to search and find them.
So let’s jump into the canned reports.
So I’ve got some of the sample reports in here and I’m going to run it for the last couple of days. You do have the ability to leverage all of the out-of-the-box DOJ reports this happens to be one of those samples.
There are 32 DOJ reports that will be available to you out-of-the-box, but you do have the ability through the Admin Report Designer to create your own one-off report.
So we don’t limit you to what we provide, you have the ability to build your own.
So this is just some of the canned reports that you can see, the exempted codes we talked about earlier, and how we categorize those and as you can see here. These are these are laid out after the example of the DOJ reports.
We also have an audit report.
The audit report actually is running against all system audits and manual audits that are actually happening on the front end. So basically anyone that logs in, it basically performs really any type of search or viewing or opening – it will actually log the information here what IP address is coming from.
So just another sample report that’s available to you.
Now, transitioning to Admin.
Admin is really the brains behind the overall system.
Obviously, ArkCase FOIA out-of-the-box will work for pretty much any business. But once you get to the point where you want to start configuring the application to best meet your requirement – whether it’s terminology like labels or drop-down changes or maybe it’s around security.
So security, we talked about. We do offer syncing with Active Directory.
We do provide a single sign-on, but since this is implemented with Active Directory we do have the ability to sync Active Directory groups. But once those are synced we actually have to tie them directly to what we call a Functional Access Control.
The functional access control is the actual role that we talked about – the admin role.
That role is actually tied to many specific privileges. As you can see, are they’ve got a lot of authorized privileges for the Administrator group, but as you go down to the different groups or roles assuming the roles you have different privileges.
Out-of-the-box you can utilize these, you can leverage these, you can tie these roles directly to your groups in Active Directory and you can use the system essentially the first second you have it downloaded.
So, if you decide you want to build this out and modify these roles by editing them or changing the privileges or even creating the own roles, just create the role here in the actual Create Role privilege complete configuration and then tie that functional access new role to the group’s you want to have that access.
You can tie a role to one group or many groups, there’s no restriction there.
Moving on in Security
You also have the ability not only to drill down into privileges, but you also have the ability from a higher level to restrict an entire Module. So for instance, maybe I want to restrict the Subscription Module.
As you can see here we have the Subscription Module available and is actually available to the Role Administrator. That happens to be the action will roll that’s tied to my group. I’m going to go ahead and remove that and as you can see real-time it’s successfully updated, okay?
So basically, anybody that’s utilizing that or as access to that now no longer has access to it, so that’s real-time.
It’s the same way with dashboard configuration and reports.
You do have the ability to control which reports are associated to which group or role I should say.
Additionally, within the configuration, you have things like Label Configuration.
I’ve talked about dropdowns. Maybe you decided immediately that the file types that we’re leveraging request document and audio and video, these are not doc types that you want.
Well, it’s very easy for you to come in here and delete that information.
You can delete it, you can even edit the information. Maybe you want to drag-and-drop the location of where these things are in your actual drop-down.
So you have full control on what is shown in your actual table and what order it is in.
And once again, this is pretty robust, pretty much any drop-down you have in the system is available in this lookup table.
You also have Label Configuration.
So label configuration is extremely robust.
So let’s spend just a minute talking about this.
So this is not only just like navigation labels or table labels, it’s actually down to the individual columns of a table.
So basically, any button or column anything along those lines you’re able to modify the actual label within the actual application.
So out-of-the-box it may work for you, but you may decide you want to change some labels you can go in here and basically click on any label – you can change the label and update it.
If you want to reset to the default, you can reset and then as you move through the different modules you can change these labels freely and easily.
So we put the power into the end-users hand.
So as things change, maybe terminology changes, you do have the ability to update pretty much any label change or lookup drop-down within the application on your own.
Now we’ll train you how to use this. Once again, we’ll be available for support if for some reason you need help utilizing that.
We also allow you to handle your own Logos whether it’s the header Logo at the top left or even a login Logo.
Once again, out-of-the-box, we provide the ArkCase FOIA Logo, but you can update that with your personal Logos.
If you have someone on staff that can handle custom CSS, you can change the look and feel of the overall application. So a lot of things we’re putting it back in the hands of the end-user.
One item that we didn’t talk much about today but was kind of implied was the correspondence templates.
We talked about the Acknowledgement Letter that’s automatically generated and sent out by email.
Well, that is a Correspondence Template – you have the ability to maintain your static correspondence templates and every time they’re used, they populate the information like all the merge, excuse me, merge fields what we call mail merge. You have the ability to build out templates and utilize them as part of your workflow. So maybe they were the acknowledgment letter doesn’t meet the standard text that you want.
We can go into the Correspondence Template, download your template and then update it and upload it right back into the correspondence and maybe, even modify some of the data that you want to be placed on that specific Correspondence Template.
And you would then see the next time that that template is generated either automatically or manually, it would have the new information placed on there the new static template we be used so on and so forth.
And you can build out as many templates as you want here in the Correspondence templary.
We provide quite a few samples, but you can manipulate those.
To Wrap It Up
So outside of that really kind of gives you a high-level idea of the overall process.
I know we rush quickly through the use case, a request coming in from a web portal. Once again, it can come in from many different ingestion places whether it’s an another external system, maybe its back suggestion, email ingest and maybe it’s a snail mail and scanning something in through say Ephesoft. Or some other scanning mechanism that would come right to ArkCase.
You would then take it from the Intake Queue, these are just suggested sample queues out-of-the-box, but they can be configured to other queues that are needed.
I mean, we take it on through essentially to a release point where we actually provide the final documents to the end-user.
At the end of the day, you do have the ability not only to get that information in and process it, but then to search it in many different ways and then control the overall look and feel through your Admin Module.
So hopefully this was beneficial from a very quick perspective and we can go from there.
All right, so I’m going to go ahead and show you one last thing.
I know I mentioned it since we have just an extra minute before we turn it over to Q&A.
This Dashboard I was talking about earlier is specific to my user.
Which means, that I have access to control the Dashboard so I can move things around. I can actually set this Dashboard up anyway that I want, I can remove Dashboards, I can add Dashboards.
Once again, this is high-level information that helps me as the user that logs in see what I’m actually trying to process and what I’m actually trying to do for the day maybe, right here on my Dashboard. Once again, these Dashboard widgets out-of-the-box are available to you, but you can configure your own Dashboard widgets.
Maybe you need specific metadata that you want your supervisor so your higher-up to see every single day, so you can actually use it to jump off the different locations.
As you can see here, I’ve changed my dashboard. As you can see here I jumped to the Intake queue from this widget, maybe I wanted to jump right into a specific request right there from the table, and as you can see it jumps you right into the request so I can see the detailed information.
So, wanted to make sure that you knew that everything in this application is role-based driven.
So I as this user that’s logged in has a lot of control about configuring my look and feel, and what access I have throughout the application to focus it to my specific persona.
So, that’s really the nice thing about ArkCase FOIA.
It provides a lot of configuration right from the Admin front-end to be able to make the users experience what that persona needs and only what that persona needs.
But what that means said I’m going to turn it back over to Lauren for Questions and Answers.