Request was created: null
I'm testing new V5.0 new features and when I do a 2 page SR offering on Save I get Request was created: null.
I modified an exiting offering I had before the upgrade. It is strange because it worked fine yesterday when I had everything on one page. Any ideas why it errors out? All other offerings are working fine.
Answers
<a rel="nofollow" target="_blank" href="https://support.cireson.com/KnowledgeBase/View/50#/" title="Link: https://support.cireson.com/KnowledgeBase/View/50#/">Cireson KA #50 - FAQ: Why Are Users Unable to Submit Requests From the Request Offerings in the Cireson Self-Service Portal?</a><br><br>If you've already done all that.... You may need to check that your connectors are syncing your changes in SCSM, you could potentially disable the AD connector(s) then re-enable them and then run them.<br><br>After that, you could check the Cireson Database and ensure it's syncing over the users correctly. You may even end up having to <a href="https://support.cireson.com/KnowledgeBase/View/1142#/" title="Link: https://support.cireson.com/KnowledgeBase/View/1142#/">get the CacheBuilder to rebuild it</a>.<br>
Test to see if an SCSM administrator can create OK using the request offering, then check the template to see what you have set and remove relationships \ pre-set property values till you find the culprit.
Let me know if you need further assistance and we can troubleshoot in a support ticket.
Cheers
Joe
Also check webconsole.log it should have thrown an error in their as to why it failed. Should give us some more clues.
For this one id check webconfig log and see if it has an error about missing permissions for those particular users.
It sounds like a value\relationship on the template is being pre-set that certain users may not have permissions to create, check if you are setting any related items etc on the template. Then slowly strip back the template and test from one of the problem users till you find it.
2016-11-25 09:25:18,503,Commit new threw an exception
I created 10 request offering and all showed the same error.
what I can do?
Has anyone been able to successfully use multiple mapping with those container activities, or is this something that Cireson can easily fix?
In the template a service was added as a related configuration item and end users aren't allowed to add that relationship. The strangest thing is that in version 5 this just worked, so Cireson has changed the way it handles permissions.
So check your templates and check the users permissions.
This should let Users create/modify activities