Why Migrate to Web PD Now?
- March 26, 2019
- 0 Comments
Speaker 1: Thanks for joining us today. Today we were talking about an important topic in the IBM digital process automation space, specifically. This is the migration from the clip space designer to the web PD. Tell me, first of all, why do I have to migrate.
Speaker 2: Well, historically the eclipse-based designer put a lot of unnecessary requirements, or a lot of requirements on the developers in terms of the machines, and OS that they had to have. At some company’s required new rules to be made in order to support the deployment of that. It’s very complex. A web based designer, you have your web browser, you go right in. You log in, and you’re immediately authoring. It’s much quicker, it’s much easier for people to use.
Speaker 2: With the eight dot six release of IBM BPM, IBM announced that while they are supporting the desktop designer with the current release, it is now deprecated. Which means, in the next few years, you’re going to see the support for that drop off, and a push towards the web based designer. We really want to embrace that, and move into that before we’re forced into it. We should start thinking about getting to there.
Speaker 1: You talked about the business benefits of the install being easier, when you’re using a web designer. But, what other business benefits are coming from this migration?
Speaker 2: Well, the benefit I’ve heard the most about is that the end users perceive the new coaches that came out with eight dot six, and the web based designer, as being significantly more responsive than the classic coaches that we had before. That’s primarily due to the adoption of more sophisticated, modern approaches to the authorizing, such that we’re doing asynchronous communication, so that data is loading just in time, as the users need it, as opposed to the old paradigm where all the data had to be marshaled in advance, before we started rendering the UI.
Speaker 1: When I make this switch to the web process designer, I’m going to have a faster install, and faster end user coaches. I feel like that’s a win for the developer, and a win for the end user.
Speaker 2: I agree. It’s the right way to go. It unlocks a lot of potential. When people start talking about citizen developer, when you had to do a complex install in order for anybody to get into the authorizing environment, that’s an automatic barrier to your ability to do that. This unlocks that potential for you as well, in addition to the other benefits.
Speaker 1: Well, thanks for sitting down with us today and talking about migrating to the web process designer. You can find out more videos like this on our channel when you subscribe.