Data Entry Design Pattern using MVIS

Are there any examples written in Flask or other tool that uses REST to
communicate with Universe using MVIS to do data entry? A customer
demographics app for example. What is a good design pattern to support the
session and record locking?

Thanks

Hi Karl,

  It is good to hear that you are trying to build a web application using RESTful and MVIS to do data entry. I have written an MV framework that runs on top of MVIS RESTful APIs, conceived specifically to build data entry web applications and OpenAPI compliant APIs, all without the need to  It is inspired and promotes a Microservices architecture by creating a separate MV account, so the web application can be built without disrupting the original (legacy) MV application. As for the web application, the design pattern we chose is an adaptation of the Model-View-Controller design pattern, separating the view logic from the business logic. The web side are pure Javascript libraries, and the server side is pure MV BASIC.

  About user sessions, user are authenticated through Identity Providers, as Okta, Auth0, Azure or Google, and the framework takes care of the user's session handling. As for record locking, as the web application is completely controlled on the MV server side, you use Universe's native locking, but we have created an additional mechanism to handle the situation when two users edit the same record using web forms, allowing writings only if the record version is the latest.

  Please contact me if you want more information,

  Regards,

------------------------------
Enrique Ignacio Murphy
Software Engineer
Aleator Software - RN40 Software
Argentina
------------------------------

Hi Karl,

  It is good to hear that you are trying to build a web application using RESTful and MVIS to do data entry. I have written an MV framework that runs on top of MVIS RESTful APIs, conceived specifically to build data entry web applications and OpenAPI compliant APIs, all without the need to  It is inspired and promotes a Microservices architecture by creating a separate MV account, so the web application can be built without disrupting the original (legacy) MV application. As for the web application, the design pattern we chose is an adaptation of the Model-View-Controller design pattern, separating the view logic from the business logic. The web side are pure Javascript libraries, and the server side is pure MV BASIC.

  About user sessions, user are authenticated through Identity Providers, as Okta, Auth0, Azure or Google, and the framework takes care of the user's session handling. As for record locking, as the web application is completely controlled on the MV server side, you use Universe's native locking, but we have created an additional mechanism to handle the situation when two users edit the same record using web forms, allowing writings only if the record version is the latest.

  Please contact me if you want more information,

  Regards,

------------------------------
Enrique Ignacio Murphy
Software Engineer
Aleator Software - RN40 Software
Argentina
------------------------------

Thank you for that detailed response Enrique - it's pretty much how I had
envisioned this might work.

In order to work like the rest of the application that this will be part of
I will need to implement locking so that when a second user brings up a
record already being edited that it would be "view only".

Thanks again for the input.

Karl

On Wed, Jul 24, 2024 at 10:12 AM Enrique Murphy via Rocket Forum <
Mail@forum.rocketsoftware.com> wrote:

> Hi Karl, It is good to hear that you are trying to build a web application
> using RESTful and MVIS to do data entry. I have written an MV... -posted to
> the "Rocket U2 | UniVerse & UniData" forum
> Invite your colleagues to join the Rocket Forum and grow our expert
> network.
> ------------------------------
> [image: Rocket Software]
> Rocket U2 | UniVerse & UniData
>
> Post New Message Online
>
> Invite your colleagues to join the Rocket Forum and grow our expert
> network. Share this link.
> Re: Data Entry Design Pattern using MVIS
>
> Reply to Group Online
> Reply
> to Group
>
> [image: Enrique Murphy]
>
> Jul 24, 2024 10:11 AM
> Enrique Murphy
>
>
> Hi Karl,
>
> It is good to hear that you are trying to build a web application using
> RESTful and MVIS to do data entry. I have written an MV framework that runs
> on top of MVIS RESTful APIs, conceived specifically to build data entry web
> applications and OpenAPI compliant APIs, all without the need to It is
> inspired and promotes a Microservices architecture by creating a separate
> MV account, so the web application can be built without disrupting the
> original (legacy) MV application. As for the web application, the design
> pattern we chose is an adaptation of the Model-View-Controller design
> pattern, separating the view logic from the business logic. The web side
> are pure Javascript libraries, and the server side is pure MV BASIC.
>
> About user sessions, user are authenticated through Identity Providers,
> as Okta, Auth0, Azure or Google, and the framework takes care of the user's
> session handling. As for record locking, as the web application is
> completely controlled on the MV server side, you use Universe's native
> locking, but we have created an additional mechanism to handle the
> situation when two users edit the same record using web forms, allowing
> writings only if the record version is the latest.
>
> Please contact me if you want more information,
>
> Regards,
>
>
> ------------------------------
> Enrique Ignacio Murphy
> Software Engineer
> Aleator Software - RN40 Software
> Argentina
> ------------------------------
> *Reply to Group Online
> *
> *View Thread
> *
> *Forward
> *
> *Flag as Inappropriate
> *
> *Post New Message Online
> *
>
>