Digital Exchange Community

DX_Community_Banner.png
Expand all | Collapse all

Blue Prism Application Modeller best practice

  • 1.  Blue Prism Application Modeller best practice

    Posted 09-25-2019 12:01

    When working with a bigger application (a ERP system such as SAP or something similar). What is the best practice when setting up the Application Modeller?

    Some like to have a Basic Action object that contains the Application Modellerer. The rest of the objects then inherit that (Using 'Share the Application Model of another object')

    But what if the plan is to ramp up and have several developers using this application? Because right now, only a single developer can edit in the Application Modeller at a time. Is it better separate the Application Modeller for each window?

    --------------------------------------------------
    Disclaimer: This content was auto-posted from Stackoverflow. The original Stackoverflow question is here Stackoverflow Post, posted by Rubiano.


  • 2.  RE: Blue Prism Application Modeller best practice

    Posted 12-20-2019 00:08
    Hi Rubiano,

    The recommended best practice is to create a VBO for each screen within the UI. This allows you to have smaller Application Modeler instances and also allows multiple developers to work at the same time.

    Cheers,

    ------------------------------
    Eric Wilson
    Director, Partner Integrations for Digital Exchange
    Blue Prism
    ------------------------------