Approvers related list - Approving field does not populate

Suzanne H
Giga Guru

Hello Community,

Approvers [sysapproval_approver] related list - Approving [document_id] field does not populate when manually adding approvers to the list (when sys_created_by is not system). See screenshot. The approving [document_id] field autopopulates when an approver is added by workflow. Does anyone know why the field doesn't populate in this scenario?

SuzanneH_1-1677797056506.png

ApprovingA document_id reference field to the record being approved, on any table.

 

11 REPLIES 11

Hi,

If you don't mind, please share what you tried?

 

Saying that it doesn't work and not providing an example doesn't help us help you and in the spirit of helping on these forums, I didn't provide that link and type all that in my last reply if it wouldn't work, haha. A "before" business rule on the approval table that would run on insert to fill in a few fields (if they're empty/blank) by conditionally applying to records associated with catalog items would work as that's a platform feature and a common use case that people use them for.

 

I'd love to help walk through what you've tried and provide some assistance šŸ™‚


Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

AnveshKumar M
Tera Sage
Tera Sage

Hi @Suzanne H ,

The Approval table will have two fields one is Approving and the other Approval for.  The Approving field is populated if the approving record belongs to a table which is not extended from Task table, such as KB Articles, and the Approval for field is populated if the approving record belongs Task type tables, such as Incident, Change, Problem, SR etc.

 

You can add "Approval for" column from the Personalize list so that you know what you are approving, refer the screenshot below for quick guide to personalize the list view.

AnveshKumarM_1-1678433340505.png

 

You can refer this ServiceNow KB article, https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0688375.

 

Thanks,

Anvesh

Thanks,
Anvesh