If you follow the existing implementation, it's not more dynamic now than if you manually enter all the values in a drop-down list, because that's really how it's implemented. Any time you want to add or change a value to the existing list, you both need to add it to the config form, and add it to the hidden status reason field, which is a selection field. If you fail to add a value to the selection field, you can't use it. It will show up in the menu, but it won't save.
I would recommend not trying to implement it the same way that ITSM does it. Instead, figure out the essentials of the menu qualification, adapt it for your new form, and drop the hidden status reason field. Don't copy over the workflow related to setting the hidden status reason field. If you display the visible status reason character field as a drop down list, then you won't have people entering invalid values in the field. Lyle From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Robert Fults Sent: Saturday, March 06, 2010 7:39 AM To: [email protected] Subject: Re: Reusing the Status Reason field ** Yes, I just copied the fields to a different form, didn't alter IM at all. I looked at the SYS:Status Reason Menu Items form, and I am still trying to figure out why the menu won't load. If I load a different menu it works, but is missing some of the items I need from the Incident form. I could load the values into a drop-down list manually, but it wouldn't be very dynamic that way. -Rob ________________________________ From: Thad K Esser [[email protected]] Sent: Friday, March 05, 2010 1:48 PM Subject: Re: Reusing the Status Reason field ** 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]<mailto:[email protected]> http://uts.fiu.edu<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"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
