Can a user update their request after submitted?

[Gemma Jacobs]

Hi everyone, 

Can I get advice and suggestions on a requirement we received I'm not sure how to move forward with. 

We need the following to take place using flow designer:

-submitter will submit a request

-The request is then reviewed.

-If determined a business case is needed; then the request needs to go back to the submitter to populate additional fields

I know I can show and hide additional fields with ui policies but I'm not sure how a request can be edited after it is already submitted. 

I've tried creating 2 catalog items also, but I'm not sure how to link those together to one request.

Has anyone else had a requirement like this or any ideas on how to achieve this? 

Thanks so much for any feedback you have

Gemma

[Community Alums]

Hi @Gemma Jacobs ,

You can inform your customer it's not good practice to allow end users edit what they submitted since the workflow for that catalog item must have already triggered and change in variable information might confused the approvers.

For example :

Lets say as soon as request is submitted the approval is triggered with already submitted values so approver also approve/reject the approval based on already filled in data not based on modified values. modified values might confuse the approvers.

[Gemma Jacobs]

@Community Alums Thank you for the feedback and guidance. I agree it probably isn't the best approach...especially since we do not have a developer right now.  Can you provide a suggestion I can offer to them instead? 

[Community Alums]

Hi @Gemma Jacobs 

There is no way of editing a request by submitter after submission. Instead you can create a support ticket associating to this request and can ask the submitter to populate additional information on the ticket and then copy this information to the request via BR or Flow.

If my answer resolves your query then, please mark it as helpful and correct answer !!
Sharath Allam

[HAMDI Oussema]

Hi @Gemma Jacobs ,

I suggest creating a record producer named "Modify Request." This would allow you to maintain a list of your existing requests.

When you select a request, an on-change event could load all the data from the existing record, enabling the end user to make the necessary changes and submit a new request. During the submission of the new request, the previous one would be marked as "Closed" and "Skipped."