More types for Orchestrator assets

Feedback Orchestrator
,
1

I know that the concept of assets for Orchestrator is basicly a dictionary itself, but it would still be cool/useful to be able to use a dictionary type as a single argument

1 Like
2

Similar to another idea bellow

Cheers

1 Like
3

I really can’t see how they are similar. A dictionary, being a collection, can use really useful activities like add, remove etc which are much simpler than cycling through the table every time to add a new element or remove an old one

4

They are similar as they both concern extending types of assets you can store on the Orchestrator with multidimensial object.

5

In that sense, yes they are, but taking that into account, now I think I’m missing the point of your answer :sweat_smile:

6

The idea is just to highlight that there is something proposed around, so if someone from product would look around it could consider both in the same time.

That also emphasizes both of them, as they are similar.

Cheers

1 Like
7

I’d second that dictionaries would be really useful as an asset type, my use case is a list of users and teams and I don’t want to have to maintain a config file for it when orchestrator should really be able to hold this.

As it stands, rather than a config file I’ll be using a text asset and converting that in a custom activity. It’s not really as simple as it ought to be!

1 Like