Pass arguments with change requests?

[ILYA STEIN]

I am creating a framework using a company-built orchestration engine to automate execution of certain standard change requests. Some of these requests my require passing additional information (arguments) to the orchestration engine. Are there any recommendations / best practices on how to do that? I was thinking of utilizing some unused field in change records, but I want a consistent and future-proof solution, not a one-off.
P.S. I realize that the simplest solution would be to have multiple different change templates, but that is not practical in our case, as there are too many minor variations that just don't justify creating so many different templates.

[ILYA STEIN · Accepted solution]

Answering my own question, in case anyone else is interested. I ended up passing the arguments pertinent to change automation in the change record's Tags (sys_tags) field. This makes it easy to parse the arguments while observing conventional format typical for tagging, such as 'Tag1':'value1', 'Tag2':'value2', ...