One generic process for different purposes

We develop a generic process in a package.
From orchestrator we wish to schedule a job upon this process, and each job must use a different database, so I have to pass parameters, or contextualize somehow the job.

Is there a way or a good practice to do such thing?

Example : I have only one robot.
I tried to use environment to contextualize the process. The idea was that in the process, I grab the environment from where the job is launched into, via the API, and if it is environment A, I used conf file A.

But you can’t deploy same process, even the environment is different, if it concerns the same robot.