- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2017 09:59 AM
We recently discovered that tasks can be added to an incident that has been resolved or closed. To me that is illogical. Since incident_task is a related list, how do I prevent the creation of those new tasks?
Thanks in advance for any suggestions.
John
:{)
Helpful and Correct tags are appreciated and help others to find information faster
Solved! Go to Solution.
- Labels:
-
Incident Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2017 11:59 AM
Please see below screen shot. It is working for me. What is the column name of your incident state(we have state and incident_state columns on incident from . Just curious which one you are using)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2017 02:00 PM
Thanks

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2017 01:36 PM
Can you please add log statement to print parent.state value?
This will help you to troubleshoot issue.
Regards,
Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2017 01:58 PM
Thank you Sachin. I added two lines:
gs.warn("In List control");
gs.warn("state is " + parent.state);
if (parent.state == 6 || parent.state == 7) ...
I'm in the dev instance so I figured warnings would be easier to find. I went to the logs and found nothing.
While I'm far from the most experienced user, I've been on the platform long enough to know how to write log statements and find the results. I've opened a HI ticket because there are too many things "not right".
Best regards,
John
:{)
Helpful and Correct tags are appreciated and help others to find information faster
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2017 01:55 PM
Hi Sachin,
Sorry for the delay in getting back. I was on a call with SN support about the missing --None--. It turns out the first option had a value of NULL_OVERRIDE which was killing the --None-- option. Once that got fixed, things started working as I want, even without checking the No new button box!
Thanks again for all your help.
John
:{)
Helpful and Correct tags are appreciated and help others to find information faster