do any of you know a way to send email from the QlikView_gui to an address stored in a variable?
I have implemented in many of my apps an email_button that sends an email to myself (Feedback). The issue is, that address is hard_coded.
I do, however, have that email in a variable as part of a script_code to recognize when the admins (myself and one colleague) are logged on. In that case, several development_relevant objects become visible.
=> I'd like to send the email to whatever address is in that variable' => Then I could also write some code to put varying addresses in that variable.
Up to now it seems that isn't possible, however. I will try using the alarm_function to trigger emails when a specific variable has some value - then the user could just tick a checkbox to have the email sent.
that one is possible - from the GUI, not from the alarm_function.
(I assemble a variable with the keyword > mailto: < and that address (and a semicolon) that I can use in the trigger).
Now the next challenge is varying that.
Since I cannot put any real code into a trigger, I guess I'll either have to use a variable that is populated on the GUI - but that could be troublesome - or I'll have to implement one more way of reloading a block of script, where that variable is filled with the right person and the email is triggered right afterwards.
Alternatively, I could add three or four email_buttons with a hardcoded address each and a visibility_condition ...
That would probably be easier, but the quick_and_easy solution is somewhat less attractive to me ...
I guess in QlikView_Desktop (though the app is running on the server).
We have QlikViewServer and usually, the users access apps in the Browser, but I think that in the Browser, reloading the script (via a button on the GUI) is not possible, which is just about the core function of the whole thing.
The email will open in the locally installed Outlook and not sent immediately - that's how this button works up to now. It opens an email for editing, but it has to be sent manually.
Thinking of that - maybe using the built-in alert_function (triggered manually) would be easier in that it allows you to add a message_text and it is sent automatically.
The only drawback of putting together an > emailing_variable < in the script is that obviously you cannot add the currently active sheet to that - unless you create one such variable for every sheet ... I once developed that as a quick way for the people to send me info if something was wrong and I'd know immediately which chart was not doing what it should - but then,. nobody ever used that anyway ... 😉 Not the only thing that i developed in QlikView to see it being put into a drawer ...
That is the most direct approach - letting the user control the final sending via Outlook. If you want it more directly sent and to multiple recipients at once you could use Windows PowerShell and it could be quite straight forward to send to these recipients from a single variable a comma separated list of recipients....
Yes - going via Windows does seem like the logical thing to do - but I cannot do anything like that for the simple reason that I don't have access to the server ...
I only have access to those few paths where all the QlikView_apps are stored, but I cannot log on to the server or do anything of the sort. QlikView is not part of IT here and it's not supported by IT which is why there is a constant strife going on between the official IT_guys and myself ...
You can send mail via PowerShell equally well from the users Windows - not dependent on the server at all. So it can be just a more automated sending than the Outlook option is. It has the disadvantage that the user might not be able to see in his sent folder in Outlook what was sent for later reference. That depends on how the Outlook and mail-server environment is set up...
I cannot do that, either - there are security_restrictions on every employee's laptop and PC ...
However, the built_in alert_functionality is working fine - but thinking of it, that approach requires a reload of the script to trigger the email to be sent. If the database grows and reloading takes a bit (the machines are not the fastest here), then triggering Outlook might still be faster even if the user has to manually send it.
