I think he's trying to add the status reason functionality to a completely different form, not repurpose its use on Incident.
Robert, have you looked at the "SYS:Status Reason Menu Items" forms. The records there control the values in the display-only version of the menu (and are form-specific) and have to match the attributes of the hidden field.
Thad Esser
Remedy Developer
| From: | Rick Cook <[email protected]> |
| To: | [email protected] |
| Date: | 03/05/2010 10:27 AM |
| Subject: | Re: Reusing the Status Reason field |
| Sent by: | "Action Request System discussion list(ARSList)" <[email protected]> |
**
Do NOT repurpose fields in ITSM. You are only starting to see the reasons why it is a bad idea.
Rick
From: Robert Fults <[email protected]>
Date: Fri, 5 Mar 2010 13:24:13 -0500
To: <[email protected]>
Subject: Reusing the Status Reason field
I posted this over in BMCDN:
I am trying to reuse the status reason field from IM in a form in order to build some dynamic workflow. I copied over the field and verified that the menu was the same. I also copied over the hidden status reason field and duplicated the 2 Active Links (that I could find) that were related to these fields. For some reason I can't get the status reasons to load when I set my status to Pending or Resolved. The ALs were: HPD:SHR:OnDisplay_100_SetTempStatusReason and HPD:SHR:SetStatusReason_100.
What am I missing? Why is it these issues don't exist with other fields like the Assigned Support Group fields?
Any help would be great!
Sincerely,
Robert Fults
Remedy Dev.
Florida International University
Email: [email protected]
http://uts.fiu.edu
_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_
*IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature. *
_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_
