Cloudworks process from different model in NUX Page

Options

In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds:

We have one core model with multiple deployed models and so when we create a Cloudworks process, it's one by model deployed. When we add these Cloudworks process in a NUX page, either we put them all in one page and so the user will have to launch the one linked with its model or we create one page by model and it becomes difficult to maintain the pages.

Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)

Either it impacts our page builder to maintain the page or the users see multiple cloudworks in their page which are not relevant

What would your ideal solution be? How would it add value to your current experience?

An idea to solve this problem would be that if a cloudworks process is not linked with the model of the page, it is not displayed

Here is how two cloudworks process linked with two different models are displayed:

Tagged:
3
3 votes

New · Last Updated

Comments

  • samantha20
    edited June 25
    Options

    I advise implementing a filtering mechanism in the NUX platform that ensures only Cloudworks processes linked to the current Wordle Unlimited model of the page are displayed. This approach enhances user experience by displaying only relevant processes and simplifies page maintenance for builders.

Get Started with Idea Exchange


See our Submission Guidelines and Idea Evaluation Criteria, then start posting your own ideas and showing support for others!