# Advice on HTTP-Task (or other tasks) parametrization among environtments

**URL:** <https://forum.flowable.org/t/advice-on-http-task-or-other-tasks-parametrization-among-environtments/1371>\
**Category:** Flowable Engine\
**Created:** [December 27, 2017, 3:37pm UTC](https://forum.flowable.org/t/advice-on-http-task-or-other-tasks-parametrization-among-environtments/1371 "2017-12-27T15:37:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jespriu](https://avatars.discourse-cdn.com/v4/letter/j/dfb087/32.png) [@jespriu](https://forum.flowable.org/u/jespriu)\
**Post date:** [December 27, 2017, 3:37pm UTC](https://forum.flowable.org/t/advice-on-http-task-or-other-tasks-parametrization-among-environtments/1371/1 "2017-12-27T15:37:53Z")

</div>

Hi all,  
This may have been aswered, but any good practice to paremetrize flowable objects among environments?  
In particular, I’m trying to come up with a good practice to parametrize the URL endpoints of my HttpTasks among different environments (stage, dev, Prod, …)…any ideas?

Best regards.

---

<div class="post-metadata">

**Author:** ![joram](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/joram/32/26_2.png) [@joram](https://forum.flowable.org/u/joram)\
**Post date:** [December 29, 2017, 4:10pm UTC](https://forum.flowable.org/t/advice-on-http-task-or-other-tasks-parametrization-among-environtments/1371/2 "2017-12-29T16:10:05Z")

</div>

All fields of the http behaviour are Expressions. So you could use something like ${yourRegistry.lookupSomething(‘someUrl’)} for example.

---

<div class="post-metadata">

**Author:** ![jespriu](https://avatars.discourse-cdn.com/v4/letter/j/dfb087/32.png) [@jespriu](https://forum.flowable.org/u/jespriu)\
**Post date:** [February 20, 2018, 5:38pm UTC](https://forum.flowable.org/t/advice-on-http-task-or-other-tasks-parametrization-among-environtments/1371/3 "2018-02-20T17:38:46Z")

</div>

Hi, sorry for the delay answering.  
No really sure what this “youregistry” could be.

What I need is somekind of parameters to be easily changed between environtment. I dont want to really in URLs as they can change between envs.

Do you know any example or BPMN object able to “load” variables/parameters from something attached to the flowable? For example:

- Any object or snippet to load from a config table in the same flowable schema
- OR, object or snippet to load from a XML / YML or so in the flowable-rest directory
- Or something similar?

Thanks!

---

<div class="post-metadata">

**Author:** ![joram](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.flowable.org/joram/32/26_2.png) [@joram](https://forum.flowable.org/u/joram)\
**Post date:** [February 28, 2018, 12:20pm UTC](https://forum.flowable.org/t/advice-on-http-task-or-other-tasks-parametrization-among-environtments/1371/4 "2018-02-28T12:20:42Z")

</div>

> [@jespriu](#):
>
> No really sure what this “youregistry” could be.

In this example, it’s a (Spring) bean, which could behind the scenes do a call to whatever registry system yu have.

> [@jespriu](#):
>
> What I need is somekind of parameters to be easily changed between environtment. I dont want to really in URLs as they can change between envs.

Instead of then using ‘someUrl’ in the example above, use ‘someId’.

> [@jespriu](#):
>
> Do you know any example or BPMN object able to “load” variables/parameters from something attached to the flowable

There’s nothing out of the box, but a simple service tasks should be able to do that trick.