Thank you for the wonderful video. Other than being able to run this from multiple entities, is there any other advantage to using this over a Business Rule to check and assign values?
Different end goal and different implementation mechanism. Business rules can be implemented as a javascript or as a workflow depending on scope. Business rules are triggered while custom action is effectively an extension to the API (specifically, Execute method) that can be called from anywhere.
Hi Derek, I know this was a long time ago, but I have a question. You used a String input argument rather than an Option Set. Are you able to expand on why Option Sets are difficult to work with in Actions please?
The primary reason is that for optionsets (Choice :) you need to pass integer. That may or may not make sense and you'd need to keep the mapping somewhere.
Thank you for the wonderful video. Other than being able to run this from multiple entities, is there any other advantage to using this over a Business Rule to check and assign values?
Different end goal and different implementation mechanism. Business rules can be implemented as a javascript or as a workflow depending on scope. Business rules are triggered while custom action is effectively an extension to the API (specifically, Execute method) that can be called from anywhere.
Hi Derek, I know this was a long time ago, but I have a question. You used a String input argument rather than an Option Set. Are you able to expand on why Option Sets are difficult to work with in Actions please?
The primary reason is that for optionsets (Choice :) you need to pass integer. That may or may not make sense and you'd need to keep the mapping somewhere.
Really a helpful video
thankyou for the guideline :)
Nice video.
As I know this is a OOB Action but not custom action.
Why not use a business rule for this? Much easier to configure.