Pages:
Actions
  • #1 by Magestik on 05 Oct 2017
  • Hi

    I would like to report the following bug that happens in the Trigger Editor:

    1) Create a new MFT file. Add a Block. Add a new Trigger with a single action "set user variable". Set Value as [bm_backid] for instance.
    2) Copy the trigger using the "Copy" button within the trigger.
    3) Create a second MFT file. Add a Block. Paste Trigger.
    4) The last square bracket is gone at the Value field. Only [bm_backid remains.

    Can you please check?

    Thanks
  • #2 by rubold on 05 Oct 2017
  • Avoid using square brackets around variable names.  I don't understand why you've done that.  
  • #3 by Magestik on 06 Oct 2017
  • When you need to mix text and variables you have to use square brackets. Same behavior happens with "send text to mobile" or "send email" actions.

    Refer to page 93 of the Manual where there is an example just like that: Last amount won: [last_pl]
  • #4 by Magestik on 10 Oct 2017
  • @MarkV and @mcbee:

    Can you please test this behavior and report a bug if applicable?

    Thanks
  • #5 by MarkV on 10 Oct 2017
  • Hi
    I've tested this and can confirm a right square bracket "]" will be lost from the input fields in a trigger copy and paste procedure as you describe. I will raise a support ticket for this.

    I would also mention rubold is correct with regard to not using square brackets in the set user variable trigger action, if you use square brackets for setting user variables they may not parse correctly. Please see the attached screenshot where:
    user variable mv1 is set as value [market_volume]
    user variable mv2 is set as value market_volume
    and the resulting formula

    you are quite right though for using square brackets for variables in the text of the trigger actions write to file, email, text etc.  
  • #6 by Oxa (WellDoneSoft) on 17 Oct 2017
  • Hello and thanks everyone for help!

    It's been a hectic time here lately, so apologies for the delay in my response.

    I do confirm this bug and also would like to let you know that it will be fixed in the next software update which is scheduled for Thursday, October 19.
  • #7 by Magestik on 21 Oct 2017
  • Thanks guys!

    Much appreciated
  • #8 by Oxa (WellDoneSoft) on 22 Oct 2017
  • Should be fixed now:

    Version 8.5.1.2
  • #9 by Magestik on 29 Oct 2017
  • I have tested the new version and it's fixed.

    Thanks for fixing it so quickly!
Pages:
Actions