What does everyone think about the recent Try/Catch changes?
You no longer get a “Catches” block by default when you first add it to the workflow
When you do add a catch, it chooses the System.Exception type by default, which arguably saves a click or two, or does it, since every time you add a new catch, you need to then change that default to something else anyway
They’ve changed the way it renders so you no longer see the topmost sequence name when TRY is collapsed
They’ve removed the variable name for each catch, so you’re expected to just know there’s a local variable automatically created, and you have no ability to change its name
How will the above affect existing automations that may have used custom exception variable names?
Without having seen it, tried it or done anything substantial with it, I say Not
The need to change these trivial constructs every or so version, which forces you to unlearn development habits and change it into something new without having actual significant improvements is just inviting error during development just in the name of ‘change is good’.
As a consultant I work for a variety of clients who for various reasons not always work on latest versions, and changes like these makes it all the more anoying where the IDE is different everywhere.
Sure, if a new feature is actually a new feature and ‘ads’ something of value, sure, I’ll adapt. But the change you describe is, on the surface, just useless cosmetic redesign.
I understand how this is a bit annoying when adding the consecutive catches. The current behaviour is the result of us already adding that initial System.Exception catch by default, which was not the case previously (and already saves you clicks there).
Would the suggestion here be that the behaviuor for adding the consecutive catches would be better if we did not pre-fill it, but instead let you do it right away after it is added?
You can now rename the Try block if you have to though:
I played with the T/C in last release a bit. The function “Surround with Try/Catch ” has some gaps:
you can’t undo it
when applied to an activity you can’t delete the activity from TRY block neither you can add another activity to the TRY block - this is not the case when you add T/C and then add an activity to TRY block
allows delete “Body” of second and any other CATCH block → it leads to a strange behavior when you add an activity instead of the deleted “Body” → you can’t add any other activity to the CATCH block
Anil_G
sonaliaggarwal47
ashokkarale
sharazkm32
Jon_Smith
Bal_Son
Nitesh
Marielle_Timajo_Apay_NCS
adi.mehare
Youri98