For reference, there is a general doc page dedicated to configuring the My To-dos page here.
If we use Change Request approvals for example, and look at what is populated:
It stands to reason that an approver user might expect more information present on this page before deciding to approve or reject the task. For example, the expected start/end dates, risk, urgency, etc...
There is a dedicated module (given the proper roles) where you can navigate to: Employee Center > Administration > To-dos Configuration. Here you can open a To-dos Configuration [sn_hr_sp_todos_config] type record with some options.
The Detail fields don't really allow for fields on the specific task type (Change) to add things like urgency, risk, etc... but even if this was an option here, this value correlates in the UI on the "hrm_todos_page" page which does not include labels, so it would not be clear what the values appearing represent.
The only other options I see would be:
- Customizing the target widget in the 'To-dos Widget Mappings' Related List
- Utilizing the 'To-do Configuration Details' Related List
I suppose the issue I'm encountering is that the Docs on the Related Lists are not clear, particularly the latter which state, "In the To-dos Configuration Detail list, you can map the source table fields based on the defined conditions."
When actually viewing the "hrm_todos_page" portal page and more specifically the "HRM Todos Summary" widget, the fields mappings are not obvious or apparently displayed, at least with our Change Request example.
So the ultimate question is, is it possible using the dedicated To-dos Configuration module to actually modify the screen with more clear information about what is being approved without customizing the widgets being utilized? It seems like that is the purpose of the Module yet at the same time it's lacking the expected flexibility.
Any clarity or demonstration would be highly appreciated. All that to say, it is understood we can click to the 'ticket' portal page, or use the self-service > my approvals within native UI, but the goal would be actually have a more user-friendly experience straight from this portal page, since the action of approve/deny is presented.
