Start Job activity with parameters

I think would be very useful if we could have a property to send input parameters when using this activity, since API support it, should be easy to implement and give a lot more use for this activity.

Hi @bcorrea,
Thank you for your suggestion. I added it to our internal ideas tracker for our team to consider.

3 Likes

@Pablito,

I want to add something more .
We often use log message activity in project to keep the track of process flow. My suggestion is , can’t we add/create log activity to each activity as optional parameter where if user wants can provide so that there won’t be much need extra log message activity like we already have similar things for AddDelayBefore and AddDealyAfter for lots of activity .

Ahtesham

2 Likes

Hi @md.ahtesham,
Please post it in separate Idea post :slight_smile:

@Corneliu_Niculite

1 Like

Hello,

was this idea already applied ?

Regards,
Diogo Nunes

2 Likes

Hi @NunesDio,
Not yet :slight_smile:

1 Like

Hello,

When does this idea come into effect? This would be very useful @Pablito

1 Like

Hi @M.Onur,
Welcome to the Community!
This feedback is now on the next step of review. It’s hard to say when exactly it will be provided as it’s not a simple process. More information about how it works:

1 Like

Is this idea already applied ?

Regards,
Nagendra

Hi @nagendra.g,
This idea is already on our roadmap for one of the future releases.

Using arguments with the Start Job activity would be AWESOME, please fix asap :slight_smile:

@Pablito, feel free to chime in if I’m missing something substantial here, but I’ve been able to use the “Start Job and Get Reference” activity from the UiPath.Persistence.Activities package without actually enabling persistence in the project settings - and this allows for arguments to be passed in.

Hi,
Could share some more details?

Hi Pawel,

See attached for some screenshots and an example video (only 30 seconds - very quick). You can verify in ~10 minutes (5 if you already have bots set up in a sandbox UiPath instance)

start_job_and_get_ref.zip (2.6 MB)

Thanks for sharing this.
Sorry for my confusion but I needed to double-check this. Yes, we can call it a workaround but for enterprise customers, we need to have a clear view of the installed packages and have a purpose for those. In this case, the basic Start Job activity is the part of System packages that don’t require any additional dependencies and our goal is to make it have similar usefulness. One of the upcoming updates should fix this.

Agree wholeheartedly that this should be a part of System packages. IME most enterprise customers are okay as long as the package is an official UiPath one, but explaining that the particular package is needed for a workaround is certainly not ideal. In most cases queue triggers are the proper solution to these scenarios in enterprise cases.

Glad to hear the update will happen in an upcoming version - but as the last discussion around this was 18+ months ago I figured the workaround was worth a share.

1 Like