We used PD for one specific SRM SRD that could not be done in SRM 7.6.04 because we needed conditional component based on a question's answer. The SRD was built using Process Designer by the time we went live we had upgraded to 8.0. After working with Support to try and figure out why 1) the Work Info records added by the requester in SRM didn't show up in the fulfillment app (and vice versa) along with 2) the fulfillment app was not updating the status in SRM when completed (yeah, we missed those in testing) we found that PD doesn't create the 'SRM:AppInstanceBridge' record that links SRM and a fulfillment app. I know what I am about to say next will shock you.... let's say it together everybody... it was working as designed. You can see in the Communities we were not the only ones to stop using PD (https://communities.bmc.com/message/289470#289470) due to this oversight.
Support did ask why we were using PD and not just using an autofill response. We had overlooked that new feature in 8.0. Once we knew about autofill we recreated the SRD and that was the last time we used PD. Jason On Thu, Jan 22, 2015 at 10:38 AM, Ray Gellenbeck < [email protected]> wrote: > Teri, > > I used it as a standalone when it was Abydos. Pretty good, but tasking > was sometimes an issue. I hate to bag on BMC, but it does appear to be > another case where they tried to just buy sometime and bolt it in with > limited resources and limited success. We never had it work properly at > the last client site that tried to use it. I counsel clients away from it. > > So what are your choices? Well, plunk down thousands more on another 3rd > party solution, adapt to the limitations in the OOTB flow or go custom > development. None of those choices are pretty. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "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"

