Hi lokesh, I am assuming that you have configued a new status reason fr a change status from the Sys:Menu items .Now,you are getting the error while saving the request using this new change status reason.If you check the logs you will find that whatever you select in the status reason that value gets set in the status reason drop-down field(hidden field) where u need to configure your new status reason value.The error was coming as your new value is not configured in this status reason dropdown hidden field which gets saved when you save your change request instead of status reason menu display only field which is visible on the change request form.Please check the exact name of the field status reason in the log ,i don't remember the exact name.
Regards, Prashant Gupta On Mon, Jul 22, 2013 at 2:31 PM, Lokesh Jayaraman <lokeshjayara...@gmail.com > wrote: > ** > Hi Kiran, > > I have compared the workflow between OOB change reason and newly added > change reason. Everything looks same but approval logs shows error "Value > does not fallen with limit" but not sure which form , I have receiving > error. > > > On Mon, Jul 22, 2013 at 2:14 PM, Kiran Patil <kiranpatil....@gmail.com>wrote: > >> ** >> Hi Lokesh, >> >> OOB workflow does work for OOB change reason field. You need to make sure >> OOB workflow also works for new attribute you have created for change >> reason field. >> Enable server side log and find out workflow use change reason field to >> initiate approval process and make sure same workflow understand new >> attribute. >> >> You may need to add same attribute to approval and change join from to >> carry same value further, check server side log for more details. >> >> Regards >> Kiran >> >> >> >> On Mon, Jul 22, 2013 at 12:33 PM, Lokesh Jayaraman < >> lokeshjayara...@gmail.com> wrote: >> >>> ** >>> >>> >>> I am having issues when I add new change reason value in infrastructure >>> change related forms. When I select the new change reason , the CRQ should >>> move forward to Scheduled status from Draft. >>> >>> I have created a new process flow where the CRQ moves forward from Draft >>> to Scheduled for No Impact changes and associated the new process flow to >>> the Approval process config form. In approval process config form I have >>> defined a record. >>> >>> In change template form when I have a old value in the Change Reason >>> field say as "Maintenance" and try to create a CRQ, it works as expected. >>> However When I have the new value in the Change reason field and create a >>> CRQ but the CR is not moving from draft to Scheduled. >>> >>> Please any suggestions... >>> >>> Regards, >>> Lokesh Jayaraman >>> 9566066338 >>> >>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> >> >> >> >> -- >> *Regards* >> * >> **Kiran Patil* >> *Cognizant Technology Solutions* >> *Pune, India* >> *Mob No: +91 989 037 7125 >> * >> _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > > > -- > Lokesh Jayaraman > 9566066338 > “இறைவன் மனிதனுக்குச் சொன்னது *கீதை*, > மனிதன் இறைவனுக்குச் சொன்னது *திருவாசகம*், > மனிதன் மனிதனுக்குச் சொன்னது *திருக்குறள*்” > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
