Hello Oscar,
There are a few ways that variable values can be seen, though I'm not sure which best fits for your use case.
For an API based solution, once a workflow instance has been created, the get workflows API can be used with the returnData value set to 'variables' to retrieve info about variables and their current values.
For a UI based solution, this is more involved as it would require an update to workflow definition files in order to have them expose the variables.
To simply display the values, the instructions field can be used. For example, an "instructions only" type step could be created as the first step in your workflow definition acts as a way to expose relevant variables to the user. The below xml is just a small expandable example that would be included within a step element
<instructions substitution="true">Show variable values: var = ${instance-var}</instructions>

Alternatively, if the goal is the allow the variable values to both be displayed and edited in the UI, the variables could be set to be part of a step.
This will have their current values appear in an editable format in the UI. This would also be included in a step element
<variableValue name="var" scope="instance" noPromptIfSet="false" required="false"/>

Hopefully one of these solutions works for you. Let me know if you have any questions.