Status Update: Recently Archived Community Content is Now Restored

Employee Center Additional Details tab is blank for Change Request approval Variable Summarizer

NarasimhaRC
Tera Contributor

3 weeks ago

Hello Community,

I configured an Additional details tab for Change Request approvals in Employee Center My Tasks.

The tab is visible, but the Change Request information is not displayed. I need to show fields such as Change Number, Short Description, Type, Risk, Assignment Group, Planned Dates, Implementation Plan, Test Plan, Backout Plan, and Business Justification.

What is the recommended way to populate Change Request fields in the Additional details tab? Should I use a Variable Summarizer, UI Macro, or custom widget?

 

Thank you.

0 Helpfuls
  • 293 Views
1 REPLY 1

Vikram Reddy
Tera Guru

3 weeks ago

Hi @NarasimhaRC,

 

The tab renders blank because Variable Summarizer only reads catalog item variables, and a Change Request approval has no variable pool to summarize, so it has nothing to show. For a task table like change_request the tab needs to be driven by To-Do Configuration, not the summarizer.

Employee Center > Administration > To-Dos Configuration
  To-Do: Approvals
    Task Configuration
      Name: Change Request
      Reference table: change_request
      Common info fields: number,short_description,type,risk
      Detail fields: assignment_group,start_date,end_date,
                     implementation_plan,test_plan,backout_plan,
                     justification
    Tab Configuration (related list)
      Tab name: Additional details

That chain of records (sn_hr_sp_todos_config, Task Configuration, Tab Configuration) is the supported, no-code path for pulling task fields into the approval to-do, and it's what actually resolves against change_request instead of a variable set. One thing to watch: the out of box hrm_todos_page rendering doesn't reliably attach labels to fields outside the common info set, so Detail fields like Risk, Implementation Plan, Test Plan and Backout Plan can show up without a visible label next to the value. If that's not acceptable for your rollout, a small custom widget bound to the same Task Configuration is the fallback, not a UI Macro, since UI Macros don't participate in this config chain at all.

References

 

Thank you,
Vikram Karety
Octigo Solutions INC

0 Helpfuls