I did some reverse Engineering and it seems, there is no reference (documentkey) to the record.
Instead the link can be found in a JSON object in field inputs of table sys_flow_action_report. I created a Script Include that returns the flow context sys_id based on either a GlideRecord, or the combination of tablename and sys_id.
This I use in a UI Page containing links to the context records. On it's turn the UI page is opened from a UI action.
But how should it look like if not like the Operations view? the stages pretty much give you the full view of the flow since you see it from start to end. Of course perhaps seeing that there is another approval process a head of you. But then again, is this the way the end user should learn how the process for doing X is?
I did some reverse Engineering and it seems, there is no reference (documentkey) to the record.
Instead the link can be found in a JSON object in field inputs of table sys_flow_action_report. I created a Script Include that returns the flow context sys_id based on either a GlideRecord, or the combination of tablename and sys_id.
This I use in a UI Page containing links to the context records. On it's turn the UI page is opened from a UI action.
I couldn't find any records in sys_flow_plan_context_binding table. Do we need enable any properties to create records in this table ? Please help to get the details.
