add a script that opens the application and have it run after the .pkg installs.

you need to have a postinstall script added to your pkg that launches the app.

You can do this within Composer before you create the .pkg file, I will attach image below.

Another way is use "Files and Processes" of a policy to call the app.
That saves you from re-downloading it and give you flexibility on re-using the app.

Thanks all! Got it.

I'm guessing the board is having a hiccup of sorts. I just received 8 notifications that Matt_Roy93's post was marked as an answer.

@Mauricio I just had this idea for a similar case. I need to run a command after a package is installed. I can't use postinstall within the package, as it is signed.
My question is, is the "execute command" always run after packages/script are processed?

@hansjoerg.watzl If you upload a script that you want to run and scope it in the same policy it will always run after the packages step.

However if you modify the package or use composer to create a metapackage with a postinstall that installs the original package and then runs a command that works too. I use this frequently to bundle SAP and its prerequisites into a singular package for deployment

@hansjoerg.watzl 'Files and Processes' is the last thing to run in a policy.
You could also add scripts before or after packages (as mentioned by drtaru) to create the policy flow.
Here an example of an Adobe policy we use for the self-service.

I hope this helps!

Thanks, yes I tried it with "Files and Processes" and can confirm, that it was executed as last.
I knew I could also use a script (with After setting), but as it's only a short command, I don't want to create a script just for this simple command.
And now it works too ;-)