Role Based Subscriptions for Scheduled Jobs

• 

  Ole Dyring

  January 30, 2025 07:46

  Thank you. We appreciate your input.

  The status of this post will be updated as your request is being processed by TARGIT.

  Until then, the post will remain here to gather further interest (more votes) and comments.

  Best regards / Ole

  1
• 

  Marlene Knaup

  February 03, 2025 10:14

  Hi, I think it would also be great if not only one creator could manage their own scheduled jobs but also someone else from the respective department. So far it is only possible to see your own scheduled jobs or all of them from the entire company.

  2
• 

  Amanda Manley

  December 17, 2025 15:46

  Feature Request: report designers can define batch elements when setting up scheduled jobs, but lose this when setting up subscription. Additionally, end users can’t choose which batch element(s) they want when subscribing- so not narrowed down to their user permissions or what they need. For users who work across many divisions or clients, this means the report will have too much data in it, and if we use iteration within the report, the user will get 1 file that contains way more than they need.

  It would be extremely helpful if:

  • Designers could continue defining batch elements as they do today, even when they define a scheduled job as a subscription.

  • When subscribing, users are prompted to select all or only specific batch elements they want to receive

  • The batch elements shown to the user are filtered based on their user permissions-- so the user shouldnt see more elements in that drop down than they would see when the drop down is present on the criteria bar. 

  This would keep ownership of batch logic with the designer, reduce subscription noise, and better align scheduled output with what users actually need without changing report design or security models.

  2
• 

  Ole Dyring

  January 02, 2026 12:51

  Hi Amanda,

  I am not ruling out that we might look into something like your suggestion. However, it kind of clashes with the way outputs from scheduled jobs are working. Let me try to explain.

  Generally, a scheduled job works like this:

  • It produces an output (typically a PDF) at the time when the job is scheduled for. It does this by opening the source document of the scheduled job to query the most recent data before creating the output.
  • The same method is used no matter the delivery method - either by email, to a folder or to a list of subscribed outputs.
  • The effective permissions - at the time of querying the data - is determined by the user setting in the scheduled job itself. I.e. it is not determined by who is receiving the mail, by who is opening a file from a folder, or by who is subscribing to a scheduled job.
  • Batch jobs simply add further criteria to the report before individual sub reports are created - otherwise it follows above rules.

  So, if subscriptions were to adhere to the each potential subscriber's permissions then we would have to produce all potential outputs beforehand to satisfy all potential user permissions - which in many cases would put a huge load on the system's resources. Let alone organizing all these outputs into a permission based structure.

  For now I think the best solution might be to provide a direct link to the TARGIT report itself. The users can then open the report themselves - applying their own user permissions and potential further criteria as they do so - before exporting to PDF, if necessary.

  BR / Ole

  0

Please sign in to leave a comment.