Recreating request functions in scoped application

[chrisn_]

Hello everyone,

I have a lot of business units in my organization looking to have their own scoped application with a catalog and requests. My big question is, how to functionally accomplish this? In global there is the REQ, RITM and sc_task tables, but there is also a variable table out there where all the variables are stored and then sourced for those individual requests. How can I recreate or utilize this functionality for a scoped app? The way I have in the past I created a request table, a task table, and then record producers which created records with flows that worked on them but the variables of the record producers were just getting dumped into a description field. The only way I know how to get closer to the way global request works is to create the columns on the request table, but that doesn't seem right? That would mean I would have to write UI policies to control what shows and doesn't for each request process. Am I just missing something obvious or is it this complicated?

[SanjivMeher]

You have to create you catalog item/record producer in the scoped App is the obvious answer. For ex, for security response, all our catalog items are created in security response scope.

If you want to use record producer, you dont always need to dump the variables to description as well. There is a variables formatter, which you can add and utilize on the form. We have added a formatter to our security request form, and agents can see what options the user selected....

[Andrew G]

Have you determined a solution for your question? I'm also interested.