How to add 'Properties' to a Package?

Recently upgraded to platform version 22.10.x

We can see that Packages have a ‘Properties’ attribute on Orchestrator, but our question is - how do we add Properties to a Package?

1 Like

Hi @cshan - You can add properties to a published package while creating a Process in Orchestrator. Kindly check the below screenshot

Please check below link for more info

https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/organizing-resources-with-tags

Hey @ushu

Are you sure that’s how it works?

I added properties to a Process using the Package named “DummyDelayProcess”, but the Package did not inherit or show the property I added to the Process.

Also, in the link you provided, there is a section which implies Package properties are added in Studio. I am unable to figure out where to add these. https://docs.uipath.com/orchestrator/standalone/2023.4/user-guide/organizing-resources-with-tags#taggable-objects

Hi @cshan - Properties tag let the developers to search for the items relevant to them. Check highlighted points from the below screenshot

According to the documentation, viewing the object with a specific properties, can be done with below steps

  • Go to Tenant, click on Search Tenant

  • There, you can see your process with the configured properties. Not only that you can search for the properties you’ve configured at the process level, that shows all items those were related to the properties

  • Also, you can do the search the processes based on the configured properties. This way it helps the developer to get all the matched items

I don’t see any screenshot referring to Studio. Please let me know if I’m doing wrong

Hey ushu,

You are focusing on “Processes”, but my question is related to “Packages”, that is why your answer is not correct.

Posting the answer to hopefully help out other visitors to the thread.

After some guesswork and experimenting I have found that using the format ‘key:value’ (eg. ‘Application:Excel’) in either Project Settings or Publish menus in Studio will push to the ‘Properties’ of the Package in Orchestrator:


You don’t add properties to packages.

Packages contain code - either processes or libraries. You add properties as arguments to either a process or library (custom activities), and then they show up in Orchestrator for you to be able to pass values into the process directly, or via trigger (or via activity properties if it’s a library).

That’s something entirely different than what people think of when you say properties. Those are just tags for informational purposes, they don’t actually do anything. Properties are also the input values you fill in for activities/processes.

Hi Paul, it’s unfortunate that the word ‘Property’ is a bit ambiguous, but I think the screenshot in my initial post made it clear which type I was referring to?

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.