I'm confused about one thing here. When configuring the data stream, how come you didn't select AEP as a service? I thought that's what you had to do to enable the AEP service like CJA, RTCP and AJO?
99% of work is definitely not in just creating empty default schemas and dropping an unconfigured default dataelement into the websdk action. Jim just shows the process, skipping through the actual data massaging. Which is great. Jim, thanks for doing it. There's a huge lack of vids like this one, showing very brief practical howto. You get my like for sure. Maybe it would be useful to take another 5 minutes to show how this can be a hell of a process for the folks who are new to the job, but that's cool. The actual work is the painful mapping of the existing DL and custom code to every evar/prop/event/whatever, rewriting the logic in many places. Moving your doplugins into appropriate places or the websdk callback. The bill can be in hundreds of thousands after the company neglected their tech debt for a decade or two and now wants someone to suddenly refactor their ancient spaghetti code.
One thing I hate is any unemployed Launch Developer can only watch these type of videos but never get hands-on training, which is the most important. The classes Adobe offers are fine but I personally need a sandbox beyond training that I can practice in!
We love to see it Jim. Now go faster!
Awesome Jim, Thank you 👍
Great idea for a video. Well done!
Love it. Had to watch it on 0.75.
Fantastic Jim, thank you!
Outstanding
I'm confused about one thing here. When configuring the data stream, how come you didn't select AEP as a service? I thought that's what you had to do to enable the AEP service like CJA, RTCP and AJO?
Thx for the video. So how do services companies getaway with charging hundreds of thousands of dollars to get this setup for clients?
If you give me hundreds of thousands of dollars I'll tell you how!
99% of work is definitely not in just creating empty default schemas and dropping an unconfigured default dataelement into the websdk action. Jim just shows the process, skipping through the actual data massaging. Which is great. Jim, thanks for doing it. There's a huge lack of vids like this one, showing very brief practical howto. You get my like for sure. Maybe it would be useful to take another 5 minutes to show how this can be a hell of a process for the folks who are new to the job, but that's cool.
The actual work is the painful mapping of the existing DL and custom code to every evar/prop/event/whatever, rewriting the logic in many places. Moving your doplugins into appropriate places or the websdk callback. The bill can be in hundreds of thousands after the company neglected their tech debt for a decade or two and now wants someone to suddenly refactor their ancient spaghetti code.
One thing I hate is any unemployed Launch Developer can only watch these type of videos but never get hands-on training, which is the most important. The classes Adobe offers are fine but I personally need a sandbox beyond training that I can practice in!
I love this...LOL Speed run of Web SDK > CJA. *shakes head* LOL Did you register this with the speed run wiki? I'd bet you'd top the leader board. :D
Haha, I wish there was one!
Welp, I didn't add the AEP service to the Datastream.
welp, testing wasn't the part of the speed run :)