Change Reportevent in Conditional Actions when calling another Action
AnsweredHello,
while using the Conditional-Action in a Reportconfiguration we are facing an issue that the Reportevent-Parameter $[REPORT_EVENT] is given by the first time, the conditional action is called.
The Conditional Action is set to either print or email the document depending on fields in the BP-Masterdata. However - the conditional action is only in column Print and therefore the parameter $[REPORT_EVENT] is always "Print".
The issue we are facing here is, that our customers are using pictures and set footers, when generating a PDF or Mail but they don't need this, when printing, as there is already a paper having these things in the printer.
What we do is depending on the $[REPORT_EVENT] suppress these elements.
The problem is, as mentioned above, that the reportevent is always the same, when calling a Conditional Action.
We can create a workaround by calling either print or preview using a macro in the client itself for single-delivery, but we do also want to use this in mass-delivery and there it does not work and the customer would have to run the massdelivery twice (1x for mailing and 1x for printing).
It would be very convenient if in the conditional action there was actually a third column besides the result and the executed action, which let us change the $[REPORT_EVENT].
-
Thank you for your request. It has been scheduled for review by the development team that will get back to you should there be questions.
(Please note that as we are user-driven we can't guarantee that your request will be met unless it gets many votes and/or fit the product vision)
Read more about the Feature Request process here
[Internal Id: 138207]
Please sign in to leave a comment.
Comments
1 comment