cancel
Showing results for 
Search instead for 
Did you mean: 

"Diaflows" Allow a Dialog Process to target multiple records in a view. (Like a workflow process)

Author Name: Scott Sewell

I have several times needed to set few values at run-time (like I can with a dialog process) - and then execute that against multiple 'targets' (like I can with a workflow.)

The current limitation of a Dialog Process means that I can only run it against a single record - if I need to run against multiple records, I need to create a workflow and then it isn't flexible.

Status: Planned

Hello -

Thanks for the feedback and example use case of dialogs.  We will take this feedback item to see how we could potentially make this scenario easier/possible in a future release.

Thanks,

Brandon

Comments
Level: Powered On
Status changed to: Planned

Hello -

Thanks for the feedback and example use case of dialogs.  We will take this feedback item to see how we could potentially make this scenario easier/possible in a future release.

Thanks,

Brandon

Level: Powered On
I have a couple of cases where I need the user to be able to create a slew of simplistic connector records – for multiple records in one operation – I could do that with a workflow, but I need to be able to feed a couple of options at run-time. (e.g. Create a record that links a contact to a selected publication and include a specific subscription period on the link record). -
Level: Powered On
Yes, I love freedom & puppies 😉
Level: Powered On
I've met this scenario for several different implementations, which require the ability to take simple user input, and apply this to multiple records. Currently the only solution is to develop a web resource (or, historically, an ASP .Net extension) to take the input, but the facility to run a dialog against multiple records would avoid the need for custom development. I recognise that this would incur limitations in the capability of a multi-target dialog - for instance anything related to the user input (i.e. the Page and Query steps) would not be able to use dynamic values - but I think that would be outweighed by the benefits. I'd suggest that a dialog could have an attribute that controls whether it allows multiple target records, so the above limitations wouldn't apply to dialogs aimed at a single target. There's also the performance consideration that dialogs currently run synchronously, and that might be an issue if they were run against up to 250 selected records. One solution could be for the dialog to be split into a user interface stage that ran once, synchronously, followed by non-UI stages that run asynchronously per target record. An alternative could be for workflows to be permitted to accept Input Parameters, and have the dialog pass data to child workflows (one instance per selected record)
Level: Powered On
Great suggestion!
Level: Powered On
Some of the use-cases where I needed this could be solved by granting bulk-edit permissions to all users. However bulk-edit is /too/ all-powerful to enable for the general population. I need the control of determining what entity/fields could be updated in bulk. As a result, I would like to manage this through a dialog (which in this scenario is really closer to a ‘parameterized-workflow’ since I don't expect a multiple-step / branch logic dialog would be needed.).
Level: Powered On
Level: Powered On
Thank you for your suggestion. We are considering this functionality for a future release of CRM.
Level: Powered On
This is still an unexplainable gap - when is the next update to Dialogs/Workflows on the roadmap?
Level: Power Up

Please replace the UI.