Segregating End-Users in Decipher

[stepher]

Good Afternoon, All,

So, we are in the final stages before our first Decipher process goes into Production.  We are still deciding whether end-users would do data verification in Decipher or manage the outcomes after Blue Prism has evaluated the returns.  That topic is covered elsewhere, and not really the point here. 

We have decided to set up a few users in our pre-Production instance of Decipher, to let me them get first-hand experience with the Data Verification process.  These users are being set up using the combination of the default 'Data Verfication' and 'Reporting' roles.  So far, so good.

The problem, as I currently see it, is that an end-user given access to the Data Verification section has access to ALL of the batches that hold up waiting for verification.  As everything will be focused on the one project, this is not an issue at the moment.  But that may not be true for the next project.  For example, the current project is looking at Purchasing Confirmations (email equivalents of the EDI-855 and -856 transactions).  The next project may be looking at patient insurance confirmations.

Admittedly, I may be missing something, but I do not see a way to limit an end-user's access by Batch or Document type.  I am curious if anyone else has come across this and if/how you may have resolved it.

Thanks so much,
Red

------------------------------
Robert "Red" Stephens
Application Developer, RPA
Sutter Health
Sacramento, CA
------------------------------

[BenLyons · Accepted solution]

Hi Red,

Great to see you're making progress towards production!

So let me confirm I understand the question. You're looking to separate your documents which are owned by different business teams, so for example someone in Finance can't view an HR document and vice versa?

If so you can create user groups to reflect this and then add the respective users.

Then in Batch Type you can assign them to the respective groups (you must also include the user running the Decipher clients, by default this is generaluser).

One caveat here is that if these users have access to the reporting tab, they will be able to view each others data in the Field History report. Currently there is no segregation available on the report tab.

That being said I'm working on a report you can run from Blue Prism, due to be release along side 2.2 (though it should work with 1.2 if you have the separate reporting database). And we're aiming to get these updates in the product for 2.3.

Let me know if I've missed the mark or if you have any additional questions.

Thanks

------------------------------
Ben Lyons
Senior Product Specialist - Decipher
Blue Prism
UK based
------------------------------

[stepher]

Thanks Ben,

It has been a while since we set up the document side of things that I did not even think about it.  That make sense, it is just the reverse perspective of what I was expecting.

As a 'By The Way', we are currently on Decipher v2.1 and also have a seaprate reporting database.  I can reach out separately to see about trialing the report.

Thanks so much,
Red

------------------------------
Robert "Red" Stephens
Application Developer, RPA
Sutter Health
Sacramento, CA
------------------------------

[BenLyons]

Hi Red,

No problem. Reach out through the usual channels and we can see if there's anything more we can do to help.

Thanks

------------------------------
Ben Lyons
Senior Product Specialist - Decipher
Blue Prism
UK based
------------------------------