Ralf Peters Posted May 11, 2017 Share Posted May 11, 2017 Hi, we seem to be geting this error the last few days after the 10th may . i have checked the contact it is send to , it exists , the email is send examples are : SR00024863 SR00024852 SR00024837 SR00024835 SR00024834 this is the only BPM that emails a contact .... Thanks Ralf Link to comment Share on other sites More sharing options...
Victor Posted May 11, 2017 Share Posted May 11, 2017 @Ralf Peters I need to have a look at these requests to find out what's going on... please bear with me Link to comment Share on other sites More sharing options...
Victor Posted May 11, 2017 Share Posted May 11, 2017 @Ralf Peters right, so the "nofifyEmailContact" operation is triggered by BP in the context of the user.... in the examples you mentioned the user is a basic user which is missing rights to certain tables... this is why the node fails... ...don't think is a configuration issue, need to check this with our dev team, could be that we not doing something right in Hornbill... meantime I put in place a quick fix, however since I (admin) am not a basic user I am unable to test it fully... would it be possible to ask one the the users that were logging these requests to do a quick test for you/us? I have cleared the error from the requests you mentioned (except from SR00024863, this one seem not to have the error) Link to comment Share on other sites More sharing options...
Ralf Peters Posted May 11, 2017 Author Share Posted May 11, 2017 Hi @Victor thanks for checking that so quickly . SR00024863 was raised by me from an email , interesting so it only effects tickets raised by basic users, which were all working fine prior to the 10th ?? Basic user raised ticket via portal SR00024703 as a working example. i'll get them to try again and let you know Ralf Link to comment Share on other sites More sharing options...
Ralf Peters Posted May 11, 2017 Author Share Posted May 11, 2017 Hi @Victor just put a couple of test tickets through via the portal , they seem to work now , not flagging the error anymore SR00024872 SR00024873 Thanks Ralf Link to comment Share on other sites More sharing options...
Victor Posted May 11, 2017 Share Posted May 11, 2017 @Ralf Peters and I assume the email to contact is also being sent.... ? looking through the logs from 05/05 when SR00024703 was raised to see what was different then... Link to comment Share on other sites More sharing options...
Ralf Peters Posted May 11, 2017 Author Share Posted May 11, 2017 @Victor yes emails were send , it only affected the Data Selection team Service. 98% of all their tickets are raised through the portal by basic users directly, so there should be heaps of examples :). last one working SR00024800 09/05 15:56 first one failing SR00024816 10/05 10:53 Link to comment Share on other sites More sharing options...
Victor Posted May 11, 2017 Share Posted May 11, 2017 @Ralf Peters dev team is looking into this now... almost forgot...if you plan to update SM, please let me know when you do... I might need to put back the fix since it might be overwritten by the update... Link to comment Share on other sites More sharing options...
Victor Posted May 12, 2017 Share Posted May 12, 2017 @Ralf Peters upon further investigation into this, we found the reason why the BP fails in your scenario. Basic uses that would trigger such actions in their context need an additional role "Hornbill Authorised Guest". If you add this role to all basic users, the issue should be permanently fixed... Link to comment Share on other sites More sharing options...
Ralf Peters Posted May 15, 2017 Author Share Posted May 15, 2017 @Victor thanks for the reply , was that restriction implemented on the 9th May ? All tickets prior to that did not fail ( for at least 6 month) , the BPM is the same and had not changed, 98 % of tickets were raised by basic users ?? Ralf Link to comment Share on other sites More sharing options...
Ralf Peters Posted May 15, 2017 Author Share Posted May 15, 2017 @Victor FYI : i have added all basic users to the required role ,so should work now even accross updates . Thanks Ralf Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now