Dan Munns Posted April 30, 2018 Share Posted April 30, 2018 Hi, We have suddenly started getting this error on calls logged today. The BPM is not set to add the request to any board and a restart of the BPM fixed it. Can someone have a look at this please as this is starting to become a pain. Link to comment Share on other sites More sharing options...
James Ainsworth Posted April 30, 2018 Share Posted April 30, 2018 Hi Dan, Just to confirm that in your BPM that has the error, you have not included any nodes for Boards? Whether that be adding, moving, or removing? Regards, James Link to comment Share on other sites More sharing options...
Victor Posted April 30, 2018 Share Posted April 30, 2018 2 hours ago, Dan Munns said: The BPM is not set to add the request to any board You sure? Check "service-desk---additional-access" process, in first stage (don't know the name)... aren't there any "Add to Board" nodes? I assume there is, as there is no way (that I know of) that flowcode is invoked otherwise... The error is this: You need the right 'app.a.manageBoards' to perform this entity operation No entirely sure why "manage boards" right is needed though... 2 hours ago, Dan Munns said: restart of the BPM fixed it because the restart is done in your user context and you do have the above right... Link to comment Share on other sites More sharing options...
Dan Munns Posted April 30, 2018 Author Share Posted April 30, 2018 @Victor @James Ainsworth apologies, you are correct. The request was an emergency request and as such it tried to add it to our Emergency Requests board. This has not happened before though, and emergency requests are usually added to the board normally with no errors. Has there been a recent change with permissions have been changed around boards? I have noticed that there are closed calls on the board as well, but I have a node to remove them from the board if they are on it (decision node to remove from Emergency Requests board if the relevant PC question has been answered as 'Yes'). Some of these go back to the 3000s for reference numbers (we are currently on 13803) is there anyway I can remove these automatically or will it have to be manual? Link to comment Share on other sites More sharing options...
James Ainsworth Posted April 30, 2018 Share Posted April 30, 2018 Hi Dan, Out of curiosity, the requests where you see this error, do you know if they were they raised automatically using the routing rules? I don't believe that there is a way that you can currently remove a group of requests from a Board. We have some plans around this but nothing that will be there to help in the short term. Regards, James Link to comment Share on other sites More sharing options...
Dan Munns Posted May 1, 2018 Author Share Posted May 1, 2018 @James Ainsworth the request was logged via the service portal Link to comment Share on other sites More sharing options...
James Ainsworth Posted May 1, 2018 Share Posted May 1, 2018 Hi Dan, There has been a new release of the platform (Hornbill ESP Build Number: 2913). This will be applied automatically to your instance. I'm not aware of any particular fixes directly related to the error that you have posted, within the build, but I would be interested if you are still getting the error message after this has been applied. Regards, James Link to comment Share on other sites More sharing options...
Dan Munns Posted May 2, 2018 Author Share Posted May 2, 2018 Hi @James Ainsworth we have had another instance of this error this morning. SR00013909. Link to comment Share on other sites More sharing options...
James Ainsworth Posted May 2, 2018 Share Posted May 2, 2018 Hi Dan, I don't have access to your system so unfortunately I'm unable to access the mentioned request. Can you confirm that the Platform build 2913 or greater had been applied when this latest occurrence took place? This will depend on you maintenance window when the update is applied. Regards, James Link to comment Share on other sites More sharing options...
Dan Munns Posted May 3, 2018 Author Share Posted May 3, 2018 Hi @James Ainsworth I have had a brain failure and cant remember where to find the version for the platform. The error has happened again though with a ticket logged at 21:05 last night. (SR00013942) Any chance someone who has access can have a look? @Victor maybe? Link to comment Share on other sites More sharing options...
Dan Munns Posted May 3, 2018 Author Share Posted May 3, 2018 Three more logged this morning with the error: SR*13961 SR*13959 SR*13956 Link to comment Share on other sites More sharing options...
Victor Posted May 3, 2018 Share Posted May 3, 2018 @Dan Munns I'll have a look. The desk is particularly busy at this time, may I ask, if is rather urgent to raise a support request with us so you can have resolution targets on this issue? Otherwise I can't make definitive promises on when I can look at this other than ASAP Link to comment Share on other sites More sharing options...
Dan Munns Posted May 3, 2018 Author Share Posted May 3, 2018 @Victor raised under IN00151170 Link to comment Share on other sites More sharing options...
James Ainsworth Posted May 3, 2018 Share Posted May 3, 2018 Hi Dan, You have possibly already had answers to some of you questions above from Hornbill Support on the raised incident, but just wanted to follow through in any case. The version of the platform and all other installed apps can be found by selecting the 'About' option under the Profile Menu in the top right of the Hornbill tool bar. I had forgotten to mention previously about checking the version of Service Manager, but I can see that you applied the latest update today. Hopefully that has cleared up this particular issue. Regards, James 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