Present automation issue

Josselin Granger shared this question 6 months ago
Completed

Hello,

I'm looking for a workaround to better control ou Present export automation. Maybe I'm missing something.

We have created a present to generate client monthly reporting.

Works great, there is a "site code" filter which allows us to get specific data for each of our site. We now have 150 clients, and it is not possible to manually generate each present.

So what we did was the following :

  • Set a filter for one site
  • Create a broadcast, sent to the person in charge of the site, with the current filters
  • Name the broadcast with the site code

So far, seems great.

a73c5905a4b8ff61f59d1dff1796c874

However,

I have two major issues. The first one is that it is nearly impossible to maintain this config : if someones tell me that he didn't receive the report, here's what my automation looks like :

4b79329766f49e09b1283022b42dd4ec

Good luck finding the one with the problem !! 😭

(we're looking at 150 lines, probably 200 in the next 6 months)

The second issue is that if the data is incorrect, I can't see what the filters values are :

89248bbbdf079e24cf9e411d9581de4e

I tried to look into the API, but didn't find how to trigger the report broadcast.

I would be able to provide all the data (Present UUI, filter values, recipient email), and willing to create a script calling 200 times a report broadcast or even a pdf download, but I didn't find any way to do it.

Does anyone have an idea ?

Replies (8)

photo
1

Hello Josselin

Thank you for reaching out to the Yellowfin support.

This is to keep you informed that we have submitted a Jira task to the Product Team for further review or clarification. As soon as we hear back from them, I will update this case for your visibility. Feel free to let us know if you have any questions or concerns; we would be more than happy to assist you.

Regards

Siddhartha

photo
1

Hello Josselin

Greetings of the day!

Thank you for your patience. Using the web service SENDTOEMAIL, we are able to send multiple emails at once.

a2b00fe2509706544e048843e641531ePlease go through the below link for more information. (https://wiki.yellowfinbi.com/display/yfcurrent/Functional+Report+Services)


This is an example that I tried with the postman that is below.

'<alterationCommand xsi:type="xsd:string"></alterationCommand>'

In the line above we need to put the format for a report that we expect in email. I mean 'TXT', 'DOC', 'DOCX' etc.

Below is the format that I have used to send email successfully with PDF format mentioned,


<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://service.web.mi.hof.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">

<soapenv:Header/>

<soapenv:Body>

<ser:remoteReportCall soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">

<req xsi:type="ser:ReportServiceRequest">

<alterationCommand xsi:type="xsd:string">PDF</alterationCommand>

<loginId xsi:type="xsd:string">admin@yellowfin.com.au</loginId>

<password xsi:type="xsd:string">test</password>

<orgId xsi:type="xsd:int">1</orgId>

<reportId xsi:type="xsd:int">60860</reportId>

<reportOptions xsi:type="ser:ArrayOf_soapenc_string" soapenc:arrayType="xsd:string[]">

<string>tshepisot@test1.com</string>

<string>tshepisot@test2.com</string>

<string>Admin@yellowfin.com.au2</string>

</reportOptions>

<reportRequest xsi:type="xsd:string">SENDTOEMAIL</reportRequest>

</req>

</ser:remoteReportCall>

</soapenv:Body>

</soapenv:Envelope>


Please check the below screenshots for your reference. Is this what you are looking for? Please let us know if anything else comes up that we can help you with.


a75a2f4f3e8a53dd4dd0d8eee30630c6


1d33015af52b5ef7f638f9f8c702dd27



Regards

Siddhartha

photo
1

Hello,

my problem is absolutely not about sending email, my problem is managing my broadcasts. I can't have my team using web services, they won't be able to do that.

Again, my problem is that :

  • I create a brodcast for a report, with say ClientFilter = "Client1", and send it to "Recipient1". I name the broadcast "Report 1"
  • I create a brodcast on the same report, with ClientFilter = "Client2", and send it to "Recipient2". I name the broadcast "Report 2"
  • And so one

In the end I have 100 brodcasts, each one with the client code.

However, when I look at the broadcast schedule, they all have the same name. This makes it impossible to maintain.

Thanks

Regards

photo
1

Hello Josselin

Greetings of the day!

Thank you for the response. I will check this with my wider team and get back to you soon.

Regards

SIddgartha

photo
1

Hello Josselin

Greetings of the day!

I have an update from the product team saying that the schedule management table contains not only tasks for broadcast, which is why there is no column with the recipient. However, we can see if the task was successful and details.
a1a4dfc3b35eb7a98adc659be2e13a79

c21a3faab3b67dabc3d3efb32cf7bc55


In the 'broadcast' section we have a list of tasks with email subjects, where we can specify all needed info and, in such a way, easy to find a needed task. Besides that, we can see there if a task was successful.


a241e72ab68623b40abd6898030066b4



6313184d7168b874f654cbe766612fb2

Please let us know if anything else comes up that we can help you with.

Regards

Siddhartha

photo
1

Hello Josselin

Greetings of the day!

We would like to check, with you if you had the opportunity to read our last response. Request, you to review and let us know if you have any questions or if further assistance is required.

Regards
Siddhartha

photo
1

Hello Josselin

Greetings of the day!

This is a follow-up reminder that 2 days have passed without any activity in this ticket. When there's no activity, it usually means either that you have identified the solution for the reported issue or that the matter is no longer relevant and after 5 days (2 days from now) without any activity, we assume that the ticket can be closed.

If this is not the case, please do reply and let us know how we can be of further assistance, we would be happy to assist.

Regards
Siddhartha

photo
1

Hello Josselin

Greetings for the Day.

This email is to notify you that we believe that you have identified the solution for the reported issue or that this ticket can be resolved for now. Because of age and inactivity, I am going to go ahead and mark this ticket as Completed. However, if you ever want to revisit this or have anything else I can help you with, please let us know, and we will be more than happy to do so.

Regards

Siddhartha

Leave a Comment
 
Attach a file