Multiple Models | One Page

Sachinsourav02
Sachinsourav02
in User Experience

We have multiple models, Model A is where user inputs the data, Model B is where the submitted data would eventually sit. Model B receives data from Model A via an action.

So once input is done as a user can i press a button (from model B) to technically import data from Model A to Model B.

Can we have the action in one page where the input is also done or any workaround on this ?

Tagged:

Best Answer

  • AjayM
    AjayM
    Answer ✓

    Since linking a page to multiple models needs users to be trained to be conscious of the model that page is tied to everytime, I'd rather recommend to separate model B actions into a different page. It'll be a cleaner UX that way.

    image.png

    Cheers!

Answers

  • Dikshant
    Dikshant

    Since Input is in Model A and Action will be in Model B. Hence you cant' do it from Same UI.

    You can link the page with 2 models. In One Model you Input the Data. In Other Model you can run the action to load the Data from Model A to Model B.

  • JMVasicek
    JMVasicek

    I agree with @AjayM, given the current constraints for multi-model I would recommend separating into two pages.

    While it's technically possible to link to incompatible models to the same page and toggle between the two, there is some strange behavior for any cards, etc. that are linked to the other model.

    (For example, module/grid A tied to Model A displays oddly when toggled to Model B)

  • Sachinsourav02
    Sachinsourav02

    @AjayM @JMVasicek @Dikshant

    Thanks for your responses. A quick check, would it then be feasible to create an export and using cloudworks link it to Model B.

    To use Ajay's example, have an input screen for Model A and then cloud works action that pushes data from Model A into Model B ?

  • AjayM
    AjayM

    You can leverage cloudworks for (automated) integration purpose, but probably not required in this context. When user enters data in pageA (that is linked to Model A), why not instruct him/her to navigate to pageB (that is linked to Model B) to run the import action?

    My recommendation was only to avoid linking same page to multiple models, and keep them independent.

  • Sachinsourav02
    Sachinsourav02

    @AjayM

    Not just the automated part, in cloudworks we have that "make it available for User Experience" was thinking on those lines to potentially resolve this issue. Maybe a context: we have not decided if Input users/Submitters will have access to model B, if no then we are checking for alternatives.

  • Dikshant
    Dikshant

    @Sachinsourav02 - I think that's a great idea. Try it out if that job is available in Model A or is it only available in Model B. If it work, then that's a great alternative approach using cloud works.

Categories