So the key to making this work and being able to update either record is a good relationship. Here is an example from cloning a change (just because I have already written it).
- Create a new field on change object as Link Field
- Add a new relationship to change object relating to change object:
3. Add newly created field to change form (put it somewhere sensible to your change layout)
- Add clone object quick action to change
You relationship is now built and the objects created by the clone action, your workflow and then update either of them using run for child quick actions and you don't need to try and do any search and link.
Let me know if you get suck.
Thanks for the suggestion. I am running into an error getting the parent updated.
Unknown NodeKind: SubExpression.
I am in the Child article. My workflow has a task that when completed would call the QuickAction "Publish Article".
"Publish Article" should mark that new version Published, then locate the related article and run the QA "Archive Knowledge Article" to mark it Archived.
Here is my QA. (I took out the Published part to keep things simple and keep my article in Draft status until the archive part is working.)
This is an ErrorMessage article but I was hoping to build the QA at the FRS_Knowledge level and not maintain a copy for each article type. Is this where I have gone wrong?