Relationship Between Knowledge Approval Tables

[brendanhamman]

I am attempting to add a related list to my knowledge table form. In the lifecycle of our knowledge articles (we have some that are 7 years old), it may generate dozens of approvals based on our initial approval and renewal workflow. My idea was to add a related list which will show only approvals for active workflow contexts to filter out old, cancelled, or no longer required approval records.

This sounds easy enough, but I just can't find a unique link between my wf_context records and my sysapproval_approver records in order to create the relationship. Each tree of reference fields I go down ends up at a table that is not unique to that context. However, I do know that such a relationship exists: if you cancel an active workflow context, it WILL change all related sysapproval_approver records to "cancelled".

Thanks for your help!

[SanjivMeher]

What happens if you delete the context which is already finished, since you want to keep the active context.

You will always have one active context, which is currently running against the knowledge article. Any old context should be in finished state.

I think, you can do one improvement to the workflow, if you dont want to keep the approval history. You should never end the workflow. You should Rollback in the workflow, so that the existing workflow gets reset when there is a stage change. If you are creating individual workflow context for every change in the article, you wont have control on it.

I am not sure if there is a link between the approval and workflow context. For example, if you associate multiple workflow to one workflow, and both creates their corresponding approvals, and you approve one of them, may trigger both workflow as approved. But I will check and let you know, if I find anything.

[Goran WitchDoc]

Hi Brendan,

Have you thought about activation the versioning for Knowledge? I think this will help you a lot on what you are doing and will solve this automatically, since you only see approval records for the specific version etc.

[brendanhamman]

Good idea, thanks for the response. I can see the benefits of versioning, but this may be a better feature for more "mature" knowledge bases, as it is introducing additional steps / complication to our knowledge workflow. We have looked at this in the past, but for our current processes we are satisfied with the audit history and our custom approval workflows. I appreciate the feedback though.