It would be very useful if I could right click on a record (from a search result) and click on something like "Send To E-Form", and have certain values on the E-Form to be auto populated from matching index values from the record I initiated the E-Form from. For example, a doctor creating a visit note for a patient does not want to re-key all of the patient information into the form during the visit. If the form could be auto populated based on an already existing record, the doctor will only have to fill in the relevant information pertaining to the visit.

This issue has been posted a lot of different ways but nothing has happened with it. I know Docuware has come up with their version of autoindexing and don't seem to understand why so many other softwares have standardize how it is done. You create a odbc connection and assign it to a data entry textbox. When someone keys a value and hits enter, it will populate all the other fields. This is the way it has always been done. This version runs after the fact which doesn't let the person indexing compare the results to the image they are looking at. Anyhow, hopefully this can be added at some point. Especially when indexing a document within a tray.

Der neue Daten-Export steht in der Cloud zur Verfügung, wenn man der Idee folgt in Indexfelder (Insbesondere Table Fields) einen Aufbau nach "Nummer > Bezeichnung" zu wählen, kann das beim Export nicht manipuliert werden. (Nur die Nummer sollte exportiert werden.
D.h. es ist insbesondere bei, auslesen der Table Fields nicht möglich, die erfassten Daten in eine Verarbeitungsfähige csv zu übergeben.
Für Indexfelder kann das umgangen werden, in dem der Eintrag vor dem Export in eine dafür angelegtes Indexfeld geschrieben wird, welches dann exportiert wird.
Da derzeit nicht in Table-Fields geschrieben werden kann, ist es derzeit besonders schädlich, dass nicht wie bspw. im Workflow ein Feldinhalt manipuliert werden kann.
Zudem fehlen noch weitere Formatierungen beim Datum und bei BEtragsfeldern. (Wie Felder vor dem Export manipuliert werden könnten (ähnlich den Arithemtischen Ausdrücken im WF Designer) könnte das Problem evtl. umgangen werden

It's common to reference a Local Data Connector data source and have the Autoindex routine be set to create a data record if there is no matching record. Especially common in verifying a migration to find items that got missed. It's invariable that some docs won't come over, and this is a great way to find them. It's common for these to sometimes be a ton of records(often > 1,000,000). In 7.3 the system will only use 1,000 records from the remote data at a time, even if the query limit in the LDC config file is set to 10,000 rows. This limit causes a huge and unnecessary expenditure of time.

Can we get that restriction removed?

Thanks!

i have noticed that docuware automatically sets the form width on the mobile view by the widest element then stretched all the fields / drop downs etc to fit. problem i have is that people on the mobiles have to scroll sideways on their mobiles to click the drop down and i cant reduce the size of some of the elements causing this as they need to be the size they are for when it is exported as a pdf so it doesnt look funny or out of proportion. is there any wat to customize the mobile view? also if they try landscape view, the keyboard pops up as soon as they click on a drop down blocking most the screen.