Hi Jan,

We ended up creating the data in the import zip format and posted it using the import api end point as you suggested. We considering adding the reload api as you mentioned, but we were worried there might be errors when generating reports simultaneously. Also didn't want to have to roll our own docker image.

Thanks again

Hi thanks for the response.

I want to add on that we also want to have these protection levels without forcing the user to type in any password similar to what was asked here: https://github.com/jsreport/jsreport-pdf-password/issues/1 .

After searching through HummusJS, I came across https://github.com/galkahana/HummusJS/issues/220 .
You can try to set the userPassword to ''.
And set password and ownerPassword to the one you want.

However, in jsreport, I don't see a way to set a userPassword to empty string.

Thanks.

Hi,

I've been looking at https://www.npmjs.com/package/jsreport-pdf-password to add some protection to the pdf we make. I do not understand how to use the protection level as I would expect multiple choices to be selected.

I want our pdfs:
ALLOW high resolution printing (protection level - 13)
ALLOW text access of screen readers (10)
DISALLOW making any changes (4)
DISALLOW copying of text, images and other content (5)
DISALLOW plaintext metadata (6 and 7)
DISALLOW highlighting text on pdf

Please guide me on how this can be achieved.

Thanks.

Hi Jan,
We are thinking to implement a refresh template method on the jsreport server, so that we can call that via the api. Are you okay with that?
Thank.

Hi Jan,

Our use case is that we are generating all the required entities for a pdf on the fly. To reduce the amount of chatter we are generating the entity files and folders ourselves directly into the data folder of jsreport rather than going through the odata API to create entities (assets can contain large images, etc.).

We will be generating these entity files per pdf that we want to generate and the frequency of generation will be client initiated so they can occur frequently and in parallel.

Ideally this will work with a single server and no downtime. We would perhaps have more instances/servers in the future but that would be to alleviate load rather than downtime.

Thanks!

Hi Jan,

Thanks for the quick and detailed response. Unfortunately, we will be running multiple report generating jobs in parallel so restarting the JsReport server is not really an option. It also sounds like that would be quite an expensive option. Currently our work around is to:

1. Create an empty template in the folder
2. Rename the folder to trigger a refresh on the entities
3. Use the OData API to query for the empty template
4. If the empty template is found then the entities are all there

This is a bit hacky so it is undesirable. Ideally there would be some API method to trigger the entities refresh without having to rename the parent folder name and another API method to query the JsReport server status for when it is idle (not in the process of updating entities from an external change).

Thanks again

Hi Jan,

I'm running it in dev so I think syncModification is true by default. It works fine with one template.

The issue is that files seem to get partially detected, so when we are create an entire directory of templates, assets and folders it seems to fail to detect the later files that are created. It's non-deterministic so at best all the files are detected and at worst only assets are detected (as they are the first to be created).

EDIT: This is currently being locally tested on my Windows 10 machine using nodejs

Hello,

We are generating the templates, data and assets in an application external to the jsreport server. The files are generated directly into the data directory specified in

    "fs-store": {
      "dataDirectory": "data",
      "syncModifications": true,
      "sync": {
        "usePolling": true
      }
    }

When the files are generated, the files are not consistently updated and the template that we want to generate a pdf for is undetected by the jsreport server. When we restart the jsreport, the template is detected. Is there a way to force jsreport to rescan all files in the data-directory? We have tried setting usePolling to false and it has not improved anything.

The version we are using is jsreport 2.3.0

Thanks,

Thomas