Rules Engine: Make a Dataset as Global to use in multiple bionic rules?
Nag, are you saying using the same dataset in multiple rules across the org without writing it multiple times? I vote for it and would like to call it as a reusable data set. It reduces a lot of effort and time to re-write whenever required.
Thanks for posting this. One problem in this approach would be, if you had a source as another dataset then the field mappings will go for a toss and it will take as much effort as to map each field to the new input dataset. This will only work when you have a fetch task that fetches from MDA or SFDC. Does it sound like a huge limitation or you are good with fetch tasks alone?
Just giving a thought , can we have a clone option in Setup actions ,
Example : Rule is having more actions(under setup actions) , which are only differed by filter conditions, instead of creating all action items we can re-use them ..
Example : Rule is having more actions(under setup actions) , which are only differed by filter conditions, instead of creating all action items we can re-use them ..
I love this point Sundar - "This will only work when you have a fetch task that fetches from MDA or SFDC. Does it sound like a huge limitation or you are good with fetch tasks alone?"
If we can start with a fetch task that really helps a lot in most of the current cases that we deal today.
But one more thought on the same lines, just in case if its a doable solution, how are we going to deal such reusable "fetch" tasks with relationships?
If we can start with a fetch task that really helps a lot in most of the current cases that we deal today.
But one more thought on the same lines, just in case if its a doable solution, how are we going to deal such reusable "fetch" tasks with relationships?
Reply
Login to the community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.