Jump to content

Corrupt request


m.vandun
 Share

Recommended Posts

Hi,

Sometimes (we had a few already) a request is created and it seems to have gotten corrupted. These request do not have a timeline and also no activities are created. It seems, that for some reason the BPM is not being recognized. I've checked all our services, but all are configured with a working BPM.

5891e59547f5b_2017-02-0114_39_45-(3)IN00002929-Hornbill.thumb.png.ef5c9b120d101de6c218d42a681b44b1.png

Any ideas?

Regards,

Mark

Link to comment
Share on other sites

Is the call being logged by hitting the "Raise New" button without using it as a dropdown menu and selecting "Raise New" --> "Incident" for example?

If so, the default Business Process will be followed which may not even be set by default. I believe the relevant setting is app.requests.defaultBPMProcess.incident

Link to comment
Share on other sites

If you hit "Raise New" you've not actually selected a service, so that never gets triggered.

I've put a simple Start -> Select Service -> End process in place as the default; as soon as you do so it jumps to the correct ProCap/Process for the selected Service/Catalog item.

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...