Alert Activity Bug

Non planifiée

Christopher Wiebke

31 janvier 2019 16:40

I get a valid output in the sandbox, even though workflow says it is an invalid input type

0

• 

  Permanently deleted user

  11 mars 2019 16:30

  The Alert is only expected to accept String values as inputs. You can check this by hovering over the (?) icon next to the Text input. So the warning that a "number input is not valid for this input" is probably correct/expected, but it's confusing that it still works fine in the sandbox or HTML5 viewer.

  For anyone looking to dismiss the error and use a string input, try using a .toString() method. For example, the input for the Alert pictured here could be: =$mileMarkerDropQuery.features.length.ToString()

  Or if you're just checking values for debugging purposes (rather than needing to display them to an end user), you could use the Log activity instead.

  
  

  0
• 

  Permanently deleted user

  11 mars 2019 16:33

  Quick correction to my comment, .toString() is case sensitive, so the example should be:

  =$mileMarkerDropQuery.features.length.toString()

  
  

  Also, I've filed this to our bug tracker #29357 for investigation.

  0
• 

  Permanently deleted user

  2 mars 2020 20:16

  In browser-based viewers, the Alert activity uses Window.alert() which does accept any kind of object. However, we encourage the use of strings here for simplicity.

  0

Vous devez vous connecter pour laisser un commentaire.