Hi Joshua - I can't see the functionality being updated to be honest, I think it's slated for retirement. However feel free to make your case here
https://community.blueprism.com/participate/ideation-homeTo add to Shikar's advice, there are options to avoid sending duplicate emails. One is to enable only one machine to send emails, and have the others add an item to a queue that will instruct the email machine to send a message. That design could be a SPOF though.
Another option would be to have all machines capable of emailing, but provide them with a way to detect that a duplicate notification has already been sent. You could probably achieve this with an environment lock (to ensure email handling is never done by more than one machine) and a record of sent emails (either the Sent Items folder of a shared account, or a BP work queue) to use as a look-up.
------------------------------
John Carter
Professional Services
Blue Prism
------------------------------
Original Message:
Sent: 08-12-2022 06:46
From: Joshua Kingsley
Subject: Data Exposure - Statistic
Hi @John Carter,
Thanks for your explanation. Do you think the feature can slightly be modified to make it useful now?
Currently, I don't think we have a feature to pass some information across different sessions of a process; since Environmental variables cannot be modified during runtime & Session variables won't work across different sessions.
For example, if a Process is running on multiple machines and incase a notification to be sent to Business people, I want the bot to send email only once. If we run the process on 3 different machines, 3 same emails are being sent now. That is the case if we increase more machines.
Thanks
Joshua
------------------------------
Joshua Kingsley
RPA Developer
Infosys
Asia/Kolkata
Original Message:
Sent: 11-15-2021 09:52
From: John Carter
Subject: Data Exposure - Statistic
@Gary Chan and @MuraliKrishna Kodi - after checking with the engineering team it seems by coincidence they were thinking about retiring this exposure type anyway. However the worry is that somebody somewhere is still using it, so it's always a tough call to remove functionality and probably why it's been left in since v1.
I also had a play to remind myself how it worked, and I was wrong to say statistics are persisted between sessions. It's just a means of recording the current value of a data item within the context of one session. The UI in System>Audit>Statistics is pretty much a display of the BPAStatistics table, and as such of very little practical use.
------------------------------
John Carter
Professional Services
Blue Prism
Original Message:
Sent: 11-14-2021 16:17
From: MuraliKrishna Kodi
Subject: Data Exposure - Statistic
Thanks John for the clarification, even i was confused around it often.
------------------------------
MuraliKrishna
Senior Consultant - Automation Developer
Original Message:
Sent: 11-08-2021 11:14
From: John Carter
Subject: Data Exposure - Statistic
Hi Gary - that feature is a relic from BP v1 that should probably be retired, so please ignore it. I'll make a request for it to be retired - I suspect it's been left in for backwards compatibility but I'd be amazed if anyone is using it. The idea predates work queues and was intended as a way to persist data item values between sessions, almost like an updatable environment variable.
------------------------------
John Carter
Professional Services
Blue Prism
Original Message:
Sent: 11-04-2021 08:00
From: Gary Chan
Subject: Data Exposure - Statistic
Hi, when I choose 'Statistic - Store the contents of this data item in the database for reporting purpose' in Data Item Exposure, how and where can I retrieve the data value from database? Thanks.
------------------------------
Gary Chan
------------------------------