search

coolOrangeLabs / powerGateTemplate

powerGate full functional sample ERP integration
MIT License
3 stars 3 forks source link

trigger sync property job in powerEvents directly before the pdf job,… #213

Closed TollJulian closed 2 years ago

TollJulian commented 2 years ago

… with a higher priority

See #68

TollJulian commented 2 years ago

Added a module which triggers the synch property job. Called this function in powerEvents, just before the PDF job is triggered. PDF job Priority 110, Synch Property Priority 100

TollJulian commented 2 years ago

and took note about this in the related wiki site

TollJulian commented 2 years ago

A problem with my solution could be that the customer this way is forced to disable the sync properties job in the Vault administration settings, which would be a significant change in the whole Vault system. On the other hand, according to our support, triggering the job sync job via powerEvents you are more secure that it's processed before the export job. Anyways, this works only if using one single job processor.

@PatrickGrub what do you think about?

PatrickGrub commented 2 years ago

A problem with my solution could be that the customer this way is forced to disable the sync properties job in the Vault administration settings, which would be a significant change in the whole Vault system. On the other hand, according to our support, triggering the job sync job via powerEvents you are more secure that it's processed before the export job. Anyways, this works only if using one single job processor.

@PatrickGrub what do you think about?

@TollJulian Why do you need to disable the sync properties job in the Vault? Why it cannot exist as well? And yes it works only with one JobProcessor, this must be written in the WIKI and also in the code so that a developer reads it when changing or debugging the code.

TollJulian commented 2 years ago

@PatrickGrub if the sync properties job is still enabled in the Vault, it gets triggered twice. Once by Powerevents and once by Vault