AIF's and adding default values
Hi, I've just joined the list today after scanning the archives, so apologies if this has been covered before - I've read related threads that I could find. Basically we have created an AIF for users to submit/create Incidents via the Request Entry Portal. When the AIF opens, it doesn't apply the default values which we have specified for both Impact and Urgency. So I've read through what I can find in various places and have now done the following, as it seems you have to do this via Active Links. We have an Active Link which populates the AIF with various values from the CTM:People form and these all appear to work. I've now added two further additions to the Set Fields section: 1) Drop-Down Field1 = "4-Minor/Localized" 2) Drop-Down Field2 = "4-Low" These equate to the Impact and Urgency fields. Should this work, or am I missing something obvious? Thanks -- Mike ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: AIF's and adding default values
Mike, using an active link to populate the defualts should work. i had to create workflow to do that even though i had defaults set in in AIF forms. Tami Palacky Remedy Developer Dev Technology On Mar 1, 8:54 am, Michael Burton wrote: > Hi, > > I've just joined the list today after scanning the archives, so apologies if > this has been covered before - I've read related threads that I could find. > > Basically we have created an AIF for users to submit/create Incidents via the > Request Entry Portal. > > When the AIF opens, it doesn't apply the default values which we have > specified for both Impact and Urgency. So I've read through what I can find > in various places and have now done the following, as it seems you have to do > this via Active Links. > > We have an Active Link which populates the AIF with various values from the > CTM:People form and these all appear to work. I've now added two further > additions to the Set Fields section: > > 1) Drop-Down Field1 = "4-Minor/Localized" > 2) Drop-Down Field2 = "4-Low" > > These equate to the Impact and Urgency fields. > > Should this work, or am I missing something obvious? > > Thanks > > -- > Mike > > ___ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > attend wwrug11www.wwrug.comARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: AIF's and adding default values
It did indeed work, but we now have a new problem. When you open the AIF, the Impact and Urgency boxes have some default values, yet if you submit the form, the values are not passed and the REQ errors as if the values are not there. However if you 're-select' the values, the REQ works correctly and a incident is raised. Most odd. Will keep digging. Cheers - Mike > Date: Fri, 4 Mar 2011 11:46:15 -0800 > From: tpala...@gmail.com > Subject: Re: AIF's and adding default values > To: arslist@ARSLIST.ORG > > Mike, > > using an active link to populate the defualts should work. i had to > create workflow to do that even though i had defaults set in in AIF > forms. > > Tami Palacky > Remedy Developer > Dev Technology > > > On Mar 1, 8:54 am, Michael Burton > wrote: > > Hi, > > > > I've just joined the list today after scanning the archives, so apologies > > if this has been covered before - I've read related threads that I could > > find. > > > > Basically we have created an AIF for users to submit/create Incidents via > > the Request Entry Portal. > > > > When the AIF opens, it doesn't apply the default values which we have > > specified for both Impact and Urgency. So I've read through what I can find > > in various places and have now done the following, as it seems you have to > > do this via Active Links. > > > > We have an Active Link which populates the AIF with various values from the > > CTM:People form and these all appear to work. I've now added two further > > additions to the Set Fields section: > > > > 1) Drop-Down Field1 = "4-Minor/Localized" > > 2) Drop-Down Field2 = "4-Low" > > > > These equate to the Impact and Urgency fields. > > > > Should this work, or am I missing something obvious? > > > > Thanks > > > > -- > > Mike > > > > ___ > > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org > > attend wwrug11www.wwrug.comARSList: "Where the Answers Are" > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: AIF's and adding default values
Hi Mike, Check if There is activelink on menu select of Impact and Urgency which set the value of fields that are mapped to impact and urgency. In that case you want to populate those fields as well on window open of AIF Enjoy troubleshooting :) Regards Vinay Vermani On Fri, Mar 4, 2011 at 2:55 PM, Michael Burton wrote: > ** > It did indeed work, but we now have a new problem. > > When you open the AIF, the Impact and Urgency boxes have some default > values, yet if you submit the form, the values are not passed and the REQ > errors as if the values are not there. > > However if you 're-select' the values, the REQ works correctly and a > incident is raised. > > Most odd. > > Will keep digging. > > Cheers > > - > Mike > > > Date: Fri, 4 Mar 2011 11:46:15 -0800 > > From: tpala...@gmail.com > > Subjec_attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
