Database table for change request "Additional information"

Further to that I would echo the caution from Mostafa Helmy. You do not want to be trawling through that table to try find information in the workflow(s) for a change request. They are variables you have created yourselves anyway elsewhere in the overall request workflow, so you can refer to them in email/SQ/decision/etc. nodes as you will.

Couple of things to bear in mind …

1. These variables in the Additional Information section tend to have been defined as PUBLIC variables, either that or you haven't unchecked the Display Job Variables option in the WF definition (only really relevant during development, once done hide them).
2. Public variables, however, don't obey that setting and WILL be displayed whether you like it or not. Question is - do they need to be public? WF variables will be available for use in a) the WF they are created in and b) any sub-workflow hierarchy created by calling other worfklows. Public variables should only (IMHO) be used when either a) you do want them visible to end users, in which case pick meaningful variable names or b) if they have to persist across sibling WFs, e.g. can only be determined and set in an approval phase WF but must be available in a fulfilment phase WF (and cannot be recreated in that hierarchy).

Hope this helps.