Thank you for waiting.
Some of the places where you can find the absolute URLs are:
1. Post content/body
2. Custom fields where the URL of internal or external pages, Images, or files have been used.
3. Content saved in the widget areas.
4. WordPress settings/options table, where active theme and all active plugins (and not just Toolset) may have saved absolute URLs. The URLs in the database table can often be in a serialized form too.
As for the Toolset's audio, embedded media, file, image, and URL type custom fields, storing the relative path URLs won't work, as they expect the absolute URLs.
So, in short, for safer migration, relying on the use of relative paths won't be enough and you'll have to incorporate some sort of "search & replace" in your workflow, when working with a website with separate staging and production environments.
Additional tip: In your content/body and widget areas ( or anywhere where you have to add manual links), a better alternative to using relative paths is the use of Toolset shortcodes, to dynamically generate the URLs.
For example, to add a homepage link, you can use the "wpv-bloginfo" shortcode:
( ref: https://toolset.com/documentation/programmer-reference/views/views-shortcodes/#wpv-bloginfo )
<a href="[wpv-bloginfo show='url']">Home</a>
Likewise, to show a link to the website's "Contact Us" page, with ID "5", you can use the "wpv-post-url" shortcode:
( ref: https://toolset.com/documentation/programmer-reference/views/views-shortcodes/#wpv-post-url )
<a href="[wpv-post-url item='2']">Contact Us</a>
I hope this helps.