The code is missing the part where the association record is created. I guess you have not copied it over, cause it did not work anyway. That is because the OOB solution is pretty tied to how Workspaces work. It expects the submission of the incident to be done from the same page in which the button has been pressed. This is doable in Workspace, because it is a single-page web application, but not so much in UI16: when you press the Create Incident button, the page is re-loaded. No matter whether the UI Action saves the current record or just navigates to a new one. This can be seen in business rule Link interaction to incident on Incident.
There are two solutions to this:
- make the Create Incident UI Action a server environment only UI Action and add code to create the association record (in table interaction_related_record); have a look at UI Action Create Incident on Interaction with Action name "ws_create_incident".
- make the Create Incident UI Action a client UI Action that opens a new Interaction record so that the URL will contain parameters that set the identity of the "source" Interaction. Then create an onAfter insert Business Rule on Incident that checks for those parameters in the transaction's referer HTTP header. Of course it should create the m2m record if the parameters point to an Interaction record.
I have expanded the solution to include everything that is necessary to have two UI16 compatible UI Actions on Interaction: Create Incident and Create Request. Both redirect when pressed, the former to a new Incident record, the latter to the Request Catalog. Upon Saving or Submitting the Incident and Ordering a Catalog Item, the created record is associated with the "source" Interaction.If the Interaction record needs saving when creating an Incident or a Request, the UI Actions prompt the user, save the record if confirmed by the user and redirects one to a new Incident the other to the Catalog.
The solution is and can be imported as an update set. UI Action Create Incident needs one enhancement: right now what field of the Interaction is copied into which field of the Incident is configured by editing a map in it. This should be extracted from the code and replaced perhaps with a property; or other means to store the map outside code. The UI Page can also be enhanced to dynamically load the Interaction record's record class name to support l10n.
Or you can just use it for inspiration. Hope it helps, and have fun! 🙂
