Backlog

Next up

In Progress

Done

Main Roadmap

Capture tokens from two different pages is currently impossible.

In Review

Capture tokens from two different pages

Admin

potential value for: Healthcare Monitoring feature integration <img src="https://6a576daeca54028812757a46.featurebase-attachments.com/c/post/6a5f2791e996ccca95a29107/019f83b2-86cc-72bd-a9da-90b2c40c34d0/b64u-MDE5ZjgzYjItODZhYS03M2IzLTkxOGYtMTE3YWFmOTQ4MmU4.png?X-Amz-Expires=3600&amp;X-Amz-Date=20261001T170000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20261001%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=817ce11e3393daebac6c46d125791fa09dff768c581ce112116bea8774ec7585" data-width="100%" data-align="left" alt="" data-featurebase-content-key="6a576daeca54028812757a46/post/6a5f2791e996ccca95a29107/019f83b2-86cc-72bd-a9da-90b2c40c34d0/b64u-MDE5ZjgzYjItODZhYS03M2IzLTkxOGYtMTE3YWFmOTQ4MmU4.png" data-featurebase-content-filename="019f83b2-86aa-73b3-918f-117aaf9482e8">

Expose Services status via pubic API

Is there a way to ensure that only documents that have been poorly recognized end up in QC, while the documents still go through? The background to this is that some documents were not recognized properly in one of our child tenant and now need to be manually trained. We would therefore like to have a filter that allows us to identify which documents were recognized below a certain value. Despite this, the documents should still be processed and the JobRouter processes should not prevent them from being processed. Filtering allows the customer to dive right into Parashift and train these documents.

QC for poor receipts | QC für schlechte Belege

To keep the EV view clean, for example, if not the training option or not for validation is active, the "hide" field should be available.

Field Config: Hide in EV

The tenant search in the menu over "Powered by Parashift" is only case-sensitve. It would be nice to search non-case-sensitive.

Tenant search non-case-sensitive

Hey there The resolution of the outbound PDF are differ from the resolutuion of the inbound. The problem is that parashift turns the pdf to an image and it will converted in an image with 2500 pixel longest side. If you have set the checkox "Generate Output PDF" in the upoad-config it must be so, that the inbound resolution is the same as the outbound, for example 300dpi. Actually this differ and when the result of some docments before and some documents from parashift merge you got an PDF with different page sizes. Thanks &amp; Best regards

PDF resolution: inbound differ on outbound

For admins who are active in many tenants, the list is long and not sorted. Having it sort in alphabetical order would make the list more clear and easier to find a certain tenant. This would be the easiest improvement to implement, I think. Another idea is to be able to make certain tenants "invisible" in the "Personal settings" page, so it would not show in the quick list. Ofcourse users should be able to undo this too and make tenants visible again.

Sort list of tenants in alphabetical order (by default)

It would be helpful if, during training, we could select individual values in each field on a character-by-character basis—for example, using the arrow keys. Is something like this planned?

Selecting values character by character, e.g., using the arrow keys

Sometimes I need to create a new doctype that is variation of a similar existing document type. If I copy the existing one, both are using the same fields. Although I don't want any shared element between those 2 doctypes. I'd love to have a "Copy with new fields" option

Copy and duplicate all fields

Today we need to edit each users permissions individually. It would make editing permissions a lot easier if you could use groups to edit many users at once. Even better if you could push these permissions between tenants.

Use roles / groups to edit user permissions

Add the ability to assign users to teams. Add the option to assign document-types to teams. Members of a specific team shall only be able to see documents assigned to their team. Usage of validation levels shall be possible.

Planned

Validation: Create teams, assign document-types to teams

Support regex pattern in Automatic Agent configuration

Restrict user permission to delete documents

- separation-validation via API - remove/add batches to training

Add more API Request

Partners should be able to integrate only the relevant parts of our validation interface into their interfaces. This would be very valuable for partners.

Parashift AG