Hi,
Currently using Studio and Orchestrator v24.10. Working in library projects, the option to disable from publish a workflow in the project is not available.
We create ‘scratch’ workflow(s) to test UI elements typically, with activities that use them, before we create activity components themselves
Test Cases for activity components we create are automatically excluded from publish, the option to ‘Set as publishable’ is available in the context menu, below ‘Remove Test Data’.
The ‘Set as publishable’ option is not available for workflows, so the ‘scratch’ functions appear as an activity in the published library.
Has this option been added in in a later version of Studio?
Thanks
@stevewakley
Can you confirm Which license do you have? Make sure you have unattended robot. Then only you can able to publish your project.
Please check and let me know if it works
@stevewakley
Check if you have Make Private option. This is the option makes the non-required flows hidden from the library.
Hi @Yedukondalu_Aregala, the issue is not publishing the project - I need an developer license for that - it’s this specific option for publishing (or rather not) including workflows in the published library.
Hi @ashok.karale, thanks, I’ll try that, thanks.
Ashok is right, Make Private is the one you want and it is there in 24.10. Right click the workflow and set it to private, and it stops being exposed as an activity in the published library while staying in the project, so your scratch flows still work for testing
The reason you could not find an equivalent of Set as publishable is that libraries handle this differently from test cases. Test cases use that publishable toggle, but for normal workflows it is the public or private state that decides what becomes an activity for whoever consumes the library. Anything public turns into an activity, anything private is hidden from the consumer but can still be invoked internally by your other workflows
One thing to keep in mind.. private does not strip the workflow out of the package, it just hides it from the activity list. If you want those scratch flows gone from the build completely you would move them out of the project or delete them before publishing. But if you only care that they stop showing up as activities, Make Private does exactly that
Thanks. It is a bit confusing that libraries would not implement both set as private and set as not publishable.
If you had common workflows in the project executed by the activity that you didn’t want to be visible as activities in their own right, then setting private makes sense.
If you had something you just didn’t want publishing in the package at all - like test cases for the activities, scratch functions, then to set as not publishable would be better. It would have the advantage of keeping the size of the published library package to a minimum.
