Hi .... have started to have a look at joget ... not sure if i am approaching this poblem in the right way ... appreciate if someone could point me in the right direction
From my understanding a user View is essentially treated as an application ... now this seems to work ok for the examples such as a booking application, but how do we use them when we want to 'chain them together'.
Take the example of a fixed asset management system, where i am using it to manage the assets for my clients. So this means that I would probably have:
Now the thing is that after I have selected a client to work on, I would think that I should also be able to jump to the asset view, and work on assets that belong to the client ... otherwise, I would need to exit from the client view, and then open the asset view, and some how tell the view that I am wanting to work on this client.
I have been through the first module in the advanced training. but this appears to focus on the the filtering of data based on the user ... but this is totally different from what I am wanting to do.
Is there some sample/documentation somewhere that tell me how to do this?
Or am I thinking about this in completely the wrong way?
Thanks in advance.
Hi, you could use the Multi Paged Form element. Alternatively, you can also make use of the Userview Key in a separate userview to maintain a reference to a client.
You can have more than one userviews in an app. Maybe one userview for Clients and another for Assets. In your Clients userview, you can add datalist to display the list of assets belong to each client, for example. Maintenance of the asset records are in the Assets userview. Here are some of the Joget features you can use to segregate data in your app:
Powered by a free Atlassian Confluence Open Source Project License granted to Joget Workflow. Evaluate Confluence today.