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 * _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
