Hello Giridhar. This should be doable in IIQ 8.4, and there are a couple of ways you could approach it depending on whether you need to keep the OK page or not.
If a simple submission message is enough (without the OK page), one option would be to use addLaunchMessage from the Standard Workflow Handler. It is meant for showing messages like “Request was submitted” in the UI without creating another form or approval gate.
<Step action="call:addLaunchMessage" name="Set Submission Message">
<Arg name="message">
<Script>
<Source>
return "Add".equalsIgnoreCase(operation)
? "Add request has been submitted successfully."
: "Remove request has been submitted successfully.";
</Source>
</Script>
</Arg>
<Transition to="End"/>
</Step>
This assumes operation is already available as a workflow variable. (Workflow Library Methods)
If you would like to keep the OK page, it might be worth considering a small launcher workflow structured something like this:
Input Form -> Schedule Processing Workflow -> Informational Form (OK) -> End
The idea here would be to call scheduleWorkflowEvent right after the user submits the input form. That would start the actual processing as a separate, independent workflow. The launcher workflow could then show the conditional Add/Remove message with the OK button. Since the processing workflow would be running on its own, whether the user clicks OK or closes the page would not have any impact on it. (Advanced Workflow Topics)
I would probably suggest staying away from is the QuickLink workflowSuccess attribute. It is tied to the workflow launch itself, and based on community reports, it has been known to show up even when the user exits through Cancel or Back without actually submitting.