Programmatically creating requests for other users

[ritmo2k]

In the most basic scenario, we create a form with validation that must be satisfied before the requester can submit it.

We have an automated process that notifies users that a series of requests are now available for them to submit.

The current solution sends an email notification with a link to the form. However, this relies on the user addressing the email without forgetting.

Is there a procedure where we can programmatically create requests on behalf of the user with a task that collects the information from the user that they would otherwise populate if they were to create the request themselves?

[Mark Manders]

Trying to improve human behavior through technology is never a good idea. People need to take their own responsibility. You will run the risk that nobody will ever respond to an email, because the system will do it for them. My solution would be to send reminders and make them annoyingly often after an x period of time.

But I understand your requirement. You will need to know for which users it has to be done. But you can utilize a scheduled job (loop through the users) or a flow (look up users and use the 'for each') to create the tasks. Depending on how often and the consistency in the requests, you can make it as dynamic as you need it to be. Define variables for the input, so you can utilize different catalog items/record producers. Or, if that's not necessary, just create the records from the script/flow.

[ritmo2k]

Hi Mark,

For the solution you proposed, since I will know the requester and recipient, is there a model that allows me to create the request in full?

The original problem case I had was that the current request forms use request-level variables and the request form has validation which requires the request to be populated in full before submission.

If I understand your suggestion, those request-level validation requirements can be moved into a task and not prevent the request from being created?