Currently buttons that call microflows can pass both the current object and a possible parent object from the page to the microflow.
However when a button calls a page, when I use conditional visibility/editability or write XPaths to retrieve data I only have access to the current object and never to the parent object. This leads to a lot of extra dataviews in dataviews, microflows that only open pages and calculated attributes that are only used to pass some data from the parent object. It would be great if [%ParentObject%] would be created and the access to it would no longer be restricted to buttons that call microflows.
Very good idea! I am not sure if ParentObject is the correct term. Would OuterObject be better? ContainingObject?