Automating alert distribution using DAI Agent

[jldum]

Hi there,

I am looking at addressing the following scenario

one alert report to be distributed to user(s)
the report has a select criteria with a one-one relation to user defined to DAI

findings so far:
as developer,
go on report, set the value of the selection criteria , via tool select email/schedule
manually change the e-mail , save

via Administration > General > System > Scheduled delivery
one may see using the form a row level a where field containing values like :

31313130305F3131372626307C5E
31313130305F3132312626307C5E

NB: this has not been scheduled yet for testing

questions:
1. is it the way to go to address this request ?

2. are the values (31313130305F3131372626307C5E, ...) seen in the where field
the corresponding value set for the criteria ?

3. if yes, is there a way to maintain (change) them easily

3. in this approach the report has to be run x time
is there another approach possible with one execution and an email sent at each break ?

Thanks
Regards

JL D

[Carsten Sørensen]

Hi JLD,

In case you want 1 specific report (with a user specific criteria) to be send to a specific user - the way to do this is to define the report (eventually using a @USERID condition) - and save a schedule (logged in) as each individual user. That way the userID will be correctly set during agent execution and the "email To" address would be correct.

The encoded string that you refer to is including the where clause - but it isn't really meant for changing.

If you want to set the reports up for the users - then you can log in as administrator or another user having user maintenance rights and use the "user profile" "run as" to switch to a specific user and set up the schedule for that particular user. Using this methodology you ensure that the report schedule is executed in the right context (in the context of the logged in user) where e.g. @USERID conditions would be resolved correctly.

Best regards,
Carsten

[jldum]

Thanks Carsten.
JL

[jldum]

Hi Carsten,

have been looking at your explanation.
brings some other questions forward

1. where as an Administrator or poweruser do you have access to the 'run as'
(I only found it on a page after I had created a schedule request as Administrator for a report
and this brought me into another online session , for the userid I set in the field)
are there other places ?
is it the 'best practice' for this item/function ?

My current deduction is that 'automation' is primarily a user's own responsibility and not an activity
expected to be administered centrally

2. Is it the same mechanism for the Enterprise version of the product ?

thanks in advance for your answers
Regards

JL D

[Carsten Sørensen]

Hi JL D,

Re. 1: You'll find the RUN AS on the user profile (your name in the bottom toolbar to the right) - you must however be logged in with a user that has RIGHTS to User Maintenance to get that functionality.

Best practices... I think we can improve scheduled report delivery administration - for now it is. I agree that in practice it is the user that decides/should decide whether or not to receive the reports by email - in that light I believe the current functionality however is "best practices" seen from the individual users perspective.

Re. 2: Yes.

Best regards,
Carsten

[admin]

Hi JL,

The Run as function can be found on your user profile. There is a link to the user profile at the bottom tight of the screen (your user name) -clicking the name takes you to the profile from where you can the Run as:



The main focus of the scheduling function in the Server edition, is to let users schedule report delivery to themselves, but it is possible for administrators to override default delivery by editing the SCHDESTINATION value in the Scheduled Delivery interface found in Administration / System / Scheduled Delivery

The enterprise edition can process a Job queue that is similar to the list of scheduled reports, but can deliver data dumps as well (and html and optionally PDFs etc). The job queue is a table that is typically populated by an external application.

Best regards

Bo