yes it is.
You will just need to add an extension to IncidentDetail based on your category.
If you are On-Premise, please note that there are currently two open bugs:
- IncidentDetails are not working correctly when using any other than English locale (Hotfix available for 2015.2.2+)
- IncidentDetails are not working correctly for Incidents created by mail (to be fixed in 2016.2)
Florian - something strange has happened. I tried following the instructions, which did allow me to create an additional details tab, but wouldn't trigger it to populate automatically. - I hate to click a "new detail", or something like that, for the detail form to appear. In testing, I removed the extension from the child forms list, and lost the ability to create new incidents. Have you seen that before? The new incident button just doesn't appear on the toolbar in list or form view, and I can't bring it back:
It shows up in the list, and I've tried rearranging the order to no avail.
1 of 1 people found this helpful
please check your grid view. For some reasons you are missing the form view under "On request to create new object show".
It should look like this:
Can you still see the "New Incident"-Button when you are in an existing Incident (so basically in a form view)?
You definetely don't need to click on "new detail".
You only need to ensure the following options are set (example: "Account Lockout"):
The IncidentDetail form has to be set:
The Incident Category needs to have the same name (case sensitive, space allowed) as the IncidentDetail object.
(I don't get why they didn't use toLowerCase() to avoid case sensitivity..):
Hm, not sure what happened here.
Can you create an additional formView and assign this form as navigation view and switch back to the original formView?
Are you on 2016.1 or 2015.2?
Thanks for the suggestions, Florian We actually had HEAT revert the DB (it's a test environment so nothing of real value was lost). Sorry I can't report what the resolution was, I would have loved to know how I broke it!
Thanks for this Florian, was trying all kinds of ways with triggers and fields to get these detail screens to appear until I read this post and realised that you have to make the name of the category and the extended object the same.
Further suggestions for Ivanti Service Manager (Formerly HEAT Service Management) would be:
a) Get something in the Help file about this........
b) Have an easier way of mapping Categories to the detail screens so that the same detail screen can be used for different Categories.