We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
Daisy Chain Request Offerings
In this example, each of the requests for ask for the affected user to be identified. In a Daisy Chain that would be entered once then auto-filled in the rest of the requests. This would also allow complex request processes to be broken into smaller module sized requests.
Comments
1. Request Offering Summary Page https://community.cireson.com/discussion/1736/request-offering-summary-page
2. Call a request offering from a link or script that prepopulates some fields. https://community.cireson.com/discussion/226/call-a-request-offering-from-a-link-or-script-that-prepopulates-some-fields#latest
If the summary page were also a confirmation page you could include a link to the next offering and embed the needed info in the link. Then have the subsequent offering auto-fill from there.
The "competitors" product has the option described as:
Chained Service Requests
Chained Service Requests can be used in an activity workflow to provide additional information to a Service Request. The next request in the chain would be completed by a designated person or group after the initial request is created.