Separate rendition task from export package job

Creating renditions is a part of an Export Package (to Portal) job.
This is very error sensitive and source of failing package sends.
This results in failed export jobs from which it is hard to recover.
It also does not seem possible to do a good check if renditions are up-to-date (everything is renderen over and aver again).
Please exclude the rendition phase from the Export Package job.

  • Hans van Koelen
  • Aug 5 2021
  • Future consideration
Meridian Server
  • Attach files
  • Admin
    Rudi Pieters commented
    August 12, 2021 06:29

    Clear now, added to the backlog. Thx.

    Attachments Open full size
  • Hans van Koelen commented
    August 10, 2021 13:56

    No, that is the main issue...
    This does not seem to work, all drawings are rendered again (and we know for sure that they are up-to-date).

    Attachments Open full size
  • Admin
    Rudi Pieters commented
    August 10, 2021 13:50

    Under Jobs | <Export Job> | Rendering | Settings (tab) there is an option Use existing rendition (Publish existing renditions if they are up-to-date.) Would that help?

    Attachments Open full size
  • Hans van Koelen commented
    August 06, 2021 06:42

    Yes and no, The rendition part of the job still consumes most of the time.
    Most of the time renditions are up-to-date but when this is not the case, the rendition should be updated. I think I should work as designed, the problem is the trigger for generating the PDF when needed. It triggers always.

    Attachments Open full size
  • Admin
    Rudi Pieters commented
    August 06, 2021 06:33

    In the publish job settings you can deselect all render engines. Does this work in your case?

    Attachments Open full size

Related ideas