BPM, Workflow, and Case

BPM, Workflow, and Case

Come for answers. Stay for best practices. All we’re missing is you.

 View Only
  • 1.  Guidelines to migrate from Brazos UI to standard BAW views?

    Posted Mon March 07, 2022 04:01 AM

    Hi All,

    Are there guidelines or any other step-by-step or general description how to migrate coaches from Brazos UI to standard BAW views? Maybe sombody did make such a migration?

    Any help appreciated,
    Thx,



    ------------------------------
    Laszlo
    ------------------------------


  • 2.  RE: Guidelines to migrate from Brazos UI to standard BAW views?

    Posted Tue March 08, 2022 08:14 AM
    Hi Laszlo - yes there are several ways you might approach this. Depending on your scenario, it might require a mix of automated/scripted migration (from one toolkit to another), and/or runtime support (by making a UI Toolkit controls act like and programmatically "look" like Brazos controls at runtime) and/or rewrite of the UIs to be migrated so they can take advantage of UI Toolkit capabilities that are simply not available with Brazos.
    Which approach you choose mostly depends on project priorities and how you ultimately want to pay off that technical debt. Please PM me if you'd like to discuss further.

    ------------------------------
    Eric Ducos
    ------------------------------



  • 3.  RE: Guidelines to migrate from Brazos UI to standard BAW views?

    Posted Tue March 08, 2022 08:24 AM
    Hi Eric,

    Till now we only know that we have to replace Brazos controls with BAW controls. No further requirements or details. Is there any guideline if know only this?

    thx,

    ------------------------------
    Laszlo
    ------------------------------



  • 4.  RE: Guidelines to migrate from Brazos UI to standard BAW views?

    Posted Tue March 08, 2022 03:05 PM
    Definitely no official guidelines from IBM. The reason there is no direct answer is because Brazos and SPARK UI (the ancestor of the BAW UI toolkit) are philosophically *very* different. This translates to different types of controls, configurability, programmability, etc.

    So again, it depends on your scenario: If you want to move on from Brazos and don't mind some runtime overhead, there's one approach that could be pretty effective and could really limit the impact of the change on your Brazos-dependent application & toolkits. That's a great short term answer, but the technical debt mostly remains (hidden in the runtime adapter layer as a mostly interest-free loan :)). If there are specific benefits you need from the BAW UI Toolkit, then a different approach is needed which also partly depends on your Brazos usage pattern.

    So - no simple guideline. More like a priority-guided decision tree.

    ------------------------------
    Eric Ducos
    ------------------------------



  • 5.  RE: Guidelines to migrate from Brazos UI to standard BAW views?

    Posted Wed March 09, 2022 01:43 AM
    Hi Eric,

    I see. Many thanks!


    ------------------------------
    Laszlo
    ------------------------------



  • 6.  RE: Guidelines to migrate from Brazos UI to standard BAW views?

    Posted Wed March 09, 2022 06:44 AM
    Hi Laszlo,

    Brazos UI, written by BP3, is a library of pre-built UI coach views such as tables, text fields, dropdowns, etc. Brazos was meant to be an accelerator for BPM projects because it helps speed up the implementation of coaches.  Till now, I believe the philosophy of Brazos is to allow building of coaches by configuration rather than by coding. 

    With IBM BPM UI, which is based on SPARK UI, it is rather an opposite methodology to building coach views and coaches. The coach views offer less configuration options but more so on callback functions based on certain events. This means that in order to build a coach with BPM UI, you most likely will have to write some Javascript codes.

    So there you go, with such differences, you will have to plan your migration in which you probably will have to rewrite your existing coach views. You should be better off getting some experienced consultants to do it unless you know what you're doing. 

    Regards
    Thong Huynh

    ------------------------------
    Thong Huynh
    Sydney NSW
    ------------------------------