Some deployments - like Forticlient VPN - might have customers want multiple Profiles.
Currently we need to “re-run” multiple configurations for this to work.
I can create a script that runs seperately, but it would be nice if ImmyBot’s pipeline would allow for “multiple runs” of seperate configurations.
I second this, but I dont think it should be limited to this one thing for sure.
An example, we have 2 clients that have their own inhouse IT. Would be nice if we could setup a task to create their local admin account and create our local admin account (i typically have to copy the task and rename the task to accomplish this…not sure if it was intended to work this way)
same issue with adding a cert via tasks
Yes, this is the Task Template feature that I’ve referred to in other community posts. Just needs more upvotes to get on the roadmap 
got a link to that post? i will certainly upvote it
If it helps anyone else. I sometimes duplicate the built-in tasks and rename them which will apply more than one configuration. I guess ImmyBot sees it as a completely different task at that point rather than the same task with a different configuration. Meraki VPN is a good example.
Just a me-too post. We also end up having to create multiple different tasks to deploy three local accounts.