We also thought using PD was going to be quicker and more flexible. In many ways it is. Be careful, last I checked using PD instead of AOT/PDT does not create the SRM:AppInstanceBridge (form name from my memory, didn't verify) that links the SRM:Request to the fulfillment request(s). The status of the SRM:Request will not be updated as the fulfillment request(s) progress as well as Work Info records added on one side (request or fulfillment) will not be visible on the other side.
This is one of those operating as designed defects. Maybe the newly released 8.3.4 fixes this? Jason On Feb 25, 2014 10:08 AM, "Jamie" <[email protected]> wrote: > We are literally just starting out with our development this week, so > we'll see how things go. However, based on my understanding there is no > direct correlation with AIF and Process Designer. Our intentions are not > to use AIFs as well, but you can utilize process designer workflows on just > a regular SRD. I look at the process designer just as a quicker way to > define your process without having to create a bunch of AOTs first. > Everything is done within the single Process Designer tool. > > As I said, we'll see how things go.... :) > > > _______________________________________________________________________________ > 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"
