@Konrad: "Do you know why is there no activity to update or create assets (or do other interactions with Orchestrator) in studio?
Design choice or just not prioritized yet?
I’m confused cause this must be something everybody needs to do to some extend, but instead have to use workarounds (like API calls or storing the asset on a shared fileserver instead)."
I approve of above post 
Thank you for taking it up ovi!
Isn’t Orchestrator Activity Pack on the roadmap already?
I thought it’s planned for ~2018.
Yes, it is. I added this as a “User story”.
Creating assets through activities won’t be implemented soon since it has a big potential for being abused by creating too many assets. Basically the biggest usecase for programmatically creating assets is to have the workflows create the asset when migrating processes to a different instance, and for this situation we should have a migration tool in 18.2.
Editing/updating assets could be indeed useful though.
Soon to come…and others.
SetCredential
*CredentialName (String)
*Username (String)
*Password (String)
SetAsset
*AssetName (String)
*Value (String, Integer, Bool)
UpdateWindowsCredential
*NewPassword (String)
StartJob
*ProcessName Release Name (String)
*RobotName (String)
OR
*NoOfRobots (Integer)
GetJobs
*ProcessName (String)
*RobotName (String)
States (checkbox - ability to select multiple)
From (DateTime)
To (DateTime)
Top (int)
Skip (int)
Jobs (IEnumerable(Of Jobs) - > Process, Robot, Environment, State, Started, Ended, Source)
StopJob
*JobID
OR
*ProcessName (String)
*RobotName (String)
DeleteQueueItems
*QueueItems(Array(Of QueueItems))
RaiseAlert
*Severity (DropDown - > Info, Success, Warning, Error, Fatal)
*Notification (String)
Nice!
I assume those activities will be reflected in the Audit section in Orchestrator?
@TejusVenkatesh one we discussed