It would be great if JObject was an available asset type in Orchestrator. While it is possible to serialize the JObject into a string and add it as a string asset, it would be even more efficient and user friendly to have a JObject editor of some sort to add and edit JObject assets directly in Orchestrator.
Based on the asset type jobject what may be a use
you mean to say all the values for asset must be in config
You should be able to Stringify any JSON object you want to store as an orchestrator asset and store it as a string.
Thank you for your suggestion. I added it to our internal ideas tracker for our team to consider.
It would get too complicated if we allow storing multiple data types in orchestrator. Like we have pleans to allow searching by metadata. But then we will need to search in strings and in jobjects too.
I feel it is too little value brought by this… and too much work.