I'm looking at creating a new process. I'm thinking I'll have a Request Offering form that may need to be filled in by a couple of different persons - at different times in the process. I'd like to have one form that keeps all information, but may need to have different persons fill it in. I know I can submit a RO and edit it using the Service Request/Parameters/Edit tab, but I don't want to have a non-technical user use this interface. Rather, I'd like to have the process email the person, that needs to fill in additional information, a link to the RO form and have them use that interface to add the info. Is this possible?
So I may have a partial answer...How do I enable or disable "Save for later" in service requests?
So when I enable "Save for later" I can see this request to modify. But for my scenario above, I would have to be able to modify the customer within a workflow so I could "move the form around to other people". Is this possible?
Not 100% sure if this would work, But I would send the link to the second person, the only thing would be that I would ask them for the number of the original request (That would be said on the notification with the link):
You would use always the same request, if they do not include an "Original SR", that one becomes the original, if they include an "Original SR", then in the workflow you can link both requests and use a QuickAction to update the original with the new one's information.
You can also leave some fields out of "Edition" by hiding them if "Original SR" is not empty...
Is pure theory, but should work, let me know if something is not clear and I can expand.
You can grant access to the service request for self service by adding new fields to the Frs_MyItem object and adjusting the security model a sample guide is here: How to show in Self Service Incidents/Service Requests that have been submitted for the User and also Reported by the User
In your process you could grant the new updater the access to the SR and then notify them to update it. The problem is ensuring the workflow can continue once the updates have been made as changes to parameters last time I checked cannot trigger business rules. But you could trigger an update possibly from the SR object.
My current thinking now is to create a business object that gets initially populated by a service catalog/request offering. Then as the process progresses, the business object gets changed/modified and on Save, can trigger workflows and/or quick actions. The SR route seems too complicated and as Alasdair said, changes to parameters don't trigger business rules and workflows.