If you liked this, you'll want to know how to write safe queries: kzitem.info/news/bejne/uK6p4JeFbJN8g3o And check out my other Flow Designer videos: kzitem.info/door/PLkQDoKoP0MAOMa7o_B8_hhtzoXMA7ZQaJ
@arumugamofcl
10 ай бұрын
This is good. We can make code more DRY by moving to script include and then use that inside action. So other parts also can use it.
@arnoudkooi
Жыл бұрын
Nice one Rob. Your sub count in the outro deserves an update :)!
@2PaweL
Жыл бұрын
+1
@AkashPanigrahi-q6f
8 ай бұрын
Please upload update previous records script action
@robertthedukefedoruk5607
8 ай бұрын
I'm not sure what you mean.
@ricksharp426
11 ай бұрын
Hey Robert.....your Action works great.......but we want to automate and not pick a scheduled job. Can I hard code the SchedJob Name in the Input as a variable? I am using a Flow to go get some files from an SFTP endpoint, and then run the Action to run the SchedJob, that is a Data source to Transform and Update sys_user table. Make sense sir?
@robertthedukefedoruk5607
11 ай бұрын
I wouldn't make a custom action to run Scheduled Job if I was just going to hard code the scheduled job. The purpose of the Flow Action is to be re-usable across multiple intents. The example you're giving is just one of many possible intents. Hopefully I'm catching your drift. If not, DM me on linkedIn and I'll see what I can do for you.
Пікірлер: 9