Feature to update the Environmental variable

[PradeepPadashet]

Requesting to enhance the product feature by adding the capability of update the environmental variable ( Well aware of Credentials::Set actions from internal object ) but set environmental variable actions would be most benedictory for the developer community.

[HarshitRawat]

sounds like a good idea but it can have ramifications
For ex- If any process changes an env var used by many other processes , there is a risk that other processes would be affected and it would be a catastrophe . Risk would outweight the small benefit in my opinion

[stepher]

Glad I looked back for this one.

I understand the risk that @Harshit Rawat speaks of, and I have been thinking about it. Perhaps this could be a separate class of Environmental Variables. Or perhaps this could be managed like Credentials where only certain processes would have access to the specific variable. Initial setup would be a pain, but it would minimize said risk.

[Neel1]

If you are set up on Blue Prism API , then following API calls can be done to update env variable.

1. Fetch EV ID from API call Get /api/v7/environmentvariables. You can apply filter for any particular EV.

2. If required, You can check the reference of EV using below call to see how many process it impact. if not go to point 3.

get /api/v7/environmentvariables/{environmentVariableId}/references

3. Update the value of EV by using Patch call

patch /api/v7/environmentvariables/{environmentVariableId}

Body need to be passed in sample format for changing the value of EV.

[
{
"op": "replace",
"path": "/value",
"value": "rpa123"
}
]

[ChrisRPA]

@Neel1 thats an interesting solution. I'll be testing this out in our sandbox.

Thanks for your input 

[Neel1]

Let me know if you need any help @ChrisRPA