Abstractness here… I created a complex screen that does a lot of MRP type things with a button click. It works as designed, but as you could imagine, it takes a long time to process. There is a desire now to click that same button and be able to close the application and let it process on its own. The application itself has an error log already, so I’m not worried about that.
However, I am worried as the solution was built for the client side. This solution uses grids to get the right pieces of data, as well as, BAQs etc. We do not have (sadly) Functions Maintenance. To get this thing to run on the server side, I’m imagining it would be a lot of work, but I wanted to ask. I assume a lot of things would have to be rebuilt. I also assume it’d have to be built using BPMs and BPMs only as Functions Maintenance isn’t an option. How would you go about this?
If you want this to run server side then, the logical step is to build this process into an Advanced UBAQ. You can do everything functions do, plus a bit more.
This is a great question! The problem is, this thing can take a loooong time to process as it creates hundreds of Jobs. The other problem is users want this to process at the end of the day, and they need to take their laptops home after it’s done. I thought about the UDTable route too. The more I think of this, the more I believe this feature will be time-consuming to create I have to use what the user entered/selected, and I have to have it process on the server side. So this has created a hybrid-conundrum.
Hahaha, I like it! Funny thing is, the idea of setting up a dummy terminal to run this process is another idea that’s been kicked around. Definitely the easiest solution.
You can use widgets to create the jobs if that’s your thing. UBAQs use the same designer as BPMs.
Create the UBAQ and then to run it, use the Export BAQ Process which would submit it to the agent and the code would run server side. Your users could submit the process and then go home.
This all sounds fascinating, thank you everyone. Lots to ponder here. Just to be sure I understand, the user would update a checkbox field for each row they want to process in the dbd. They would then save those checkbox selections via a UBAQ. I would then create another another UBAQ that creates the jobs etc. that queries using the checkboxes checked in the previous step. The user, after checking their selections and saving, would then use the BAQ Export Process screen to run the UBAQ that creates the jobs. All they’d have to do is select the UBAQ and click Submit and they’re doing cartwheels all the way home
I have to use what the user entered/selected, and I have to have it process on the server side. So this has created a hybrid-conundrum.