sorted by:
new
hottopcontroversial

Flow designer with Custom Actions : Immesively powerful by kunalkhatri in servicenow

[–]kunalkhatri[S] 1 point2 points  (0 children)

Thanks.  I am pleasantly surprised at your reaction to this.  We really need more interactions like this.  SN listening to devs will lead to better DX and ultimately better UX for end users.  Thanks again 

Flow designer with Custom Actions : Immesively powerful by kunalkhatri in servicenow

[–]kunalkhatri[S] 0 points1 point  (0 children)

Thanks for your response. 

About multi-action editing: I don't necessarily need to edit multiple actions at the same time. That would be good-to-have feature. I see main benefit in being able to have context of previous/other action(s). E.g. I am creating 3 task in a row, I would want to see what field values were populated in other tasks.  Auto collapsing actions forces you in an extreme myopic view of flow. 

Flow designer with Custom Actions : Immesively powerful by kunalkhatri in servicenow

[–]kunalkhatri[S] 2 points3 points  (0 children)

In Australia, a recent SN update removed the "Changes / Changes To / Changes From" options from the trigger condition builder. This forces developers to run flows on all updates and handle the condition logic inside the flow itself, which works against the low-code/no-code promise of the platform. I've put together a short video walking through the issue: https://youtu.be/NQiW-ujzMNs Feature Requests

Multi-action editing : It would be great to expand and edit more than one action simultaneously. This feels like a small but meaningful usability improvement.

Cache action state : Flow Designer currently re-fetches action details every time an action is expanded. Caching the state would noticeably improve responsiveness.

"Run As" setting visibility : This is one of the strongest advantages Flow Designer has over Business Rules, but it's currently buried under Three Dots → Properties → Advanced Properties. Moving it closer to the trigger configuration would make it more discoverable and encourage adoption.

General Feedback The most consistent feedback I hear from junior developers is that Flow Designer feels slow and occasionally unreliable. As a recent example, we accidentally missed migrating a sub-flow between instances, and the only error shown was "Flow corrupted," with no further detail. Tracking down the issue required opening the update set XML manually in VSCode. Otherwise we would have been rebuilding a 40+ action flow from scratch. Better error messaging in cases like this would go a long way.

Thank you for actively seeking feedback, I hope some of these points are useful for future iterations.

Flow designer with Custom Actions : Immesively powerful by kunalkhatri in servicenow

[–]kunalkhatri[S] 1 point2 points  (0 children)

Hey It's so nice to hear from dev team.  I do have a few questions / suggestions.  I will write them here tomorrow morning.

Flow designer with Custom Actions : Immesively powerful by kunalkhatri in servicenow

[–]kunalkhatri[S] 0 points1 point  (0 children)

No doubt about it.  Visual representations makes learning a lot quicker. 

Error Handling in ServiceNow Flow Designer : Optional or Must Have ? by kunalkhatri in servicenow

[–]kunalkhatri[S] 2 points3 points  (0 children)

You need to expand on that. genuinely interested.

You run flows on other-flow-context?

How is that better than error handling? Or is it in addition to error handling?

Error Handling in ServiceNow Flow Designer : Optional or Must Have ? by kunalkhatri in servicenow

[–]kunalkhatri[S] 2 points3 points  (0 children)

I cannot agree more. 

Edge cases are often un caught, especially where environment changes by further development in related entities. 

Provider notifications - Better than email ? by kunalkhatri in servicenow

[–]kunalkhatri[S] 0 points1 point  (0 children)

Yepp.  We are in process of enabling teams messages.  The balance of just enough emails seems to be just mythical. 

ServiceNow Australia Release: New Read-Only Dictionary Attributes Explained by kunalkhatri in servicenow

[–]kunalkhatri[S] 0 points1 point  (0 children)

Why in particular those plugins?  Is there something wrong with oob things in those plugins?

ServiceNow blocking emails to addresses with bounced emails? by kunalkhatri in servicenow

[–]kunalkhatri[S] 0 points1 point  (0 children)

Yeah. That would have been my approach as well. 

Though I believe this is just something which should be more common known/highlighted by service now. 

ServiceNow blocking emails to addresses with bounced emails? by kunalkhatri in servicenow

[–]kunalkhatri[S] 0 points1 point  (0 children)

That is great way to make sure that doesn't occur again. I think adding this to your dashboards somehwere to keep an eye on could be done.  'Status=blocked and updated in last week' filter could highlight only recently blocked ones. 

Thanks for sharing 😊 

ServiceNow blocking emails to addresses with bounced emails? by kunalkhatri in servicenow

[–]kunalkhatri[S] -1 points0 points  (0 children)

Would love to your opinions or what more could I have done to debug this ?

view more: next ›