Open Source Document Management System | OpenKM

No, pero podrías importar esos documentos en OpenKM. Sería lo más sencillo.

Saludos.

I suppose this is done because of the task scheduleduling. Keep on mind the the wotkflow engine was not developed by us but only integrated.

Which OpenKM version are you using?

Deployed workflows are listed at Administration > Workflows. If you see an empty list, then there is no deployed workflows or something weird is happening.

Regards.

It's better if you create an assignHandler and programatically get the users from a role.

Best regards.

Nice!

You can also install Tesseract package in Docker this way:
But anyway is's supossed to be already installed in the Docker image. I mean the image located at https://hub.docker.com/r/openkm/openkm-ce

Sorry for the late response.

Great

There was a problem with last upload. Please, try again and tell me if it works.

Regards.

As you can see in the download URL, it is for OpenKM 6.4 but I don't know if it has sense nowadays. There are other ways to achieve the same result. For example you can move the documents to the OpenKM server and import them from the administration.

Regards.

In the server.xml it's configured a PostgreSQL in the same container where OpenKM is installed. If PostgreSQL is in another container you should configure the JDBC URL properly. Also you need to create an "openkm" user and a database called "okmdb". Of course you can choose another user and database...

If you post 5 messages with different questions and issues is a bit difficult to keep an order in this thread. In will only answer the last one.

About the error, is PostgreSQL database installed? Is the "okmdb" database created?

Regards.

If you want to change the database you have to stop OpenKM, change the server.xml, change the OpenKM.cfg and then start OpenKM again. The "hibernate.hbm2ddl=create" configuration property tells OpenKM to create the database. If the database is already created it should be set to "none". I'm pretty s...

This Docker image is configured to use an embedded database and not recommended for production. This is configured this way yo simplify the deployment and configuration. As Docker people recommend, the database server (in this case MySQL) should be launched in another container, managed by Docker Co...