"Send" button and it's rules - InfoPath Dev
in

InfoPath Dev

"Send" button and it's rules

Last post 04-10-2013 09:00 AM by HHearle. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • 04-08-2013 02:34 AM

    "Send" button and it's rules

    Hi

    I have a form that is made up of several sections. Each section is one seperat form with a "send" button at the bottom. Each section, or form, is sendt to a different e-mail adress. I want to diasable a section after having sent it once so the same user can not send the same form twice.  Please help.

  • 04-08-2013 06:30 AM In reply to

    Re: "Send" button and it's rules

    Hi,

    You just need to have a (hidden) field where you track the "currentStep".

    So, when currentStep=0, you hide some sections and show others.

    The rules increase currentStep to 1.

    Which then allows you to hide some sections and show another.

    And so on.

    Does this make sense?

    Ernesto Machado
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™


  • 04-08-2013 09:54 AM In reply to

    Re: "Send" button and it's rules

    Hmmmmm.....

    I'm afraid not....I'm very new at this.

    Is "currentStep" a rule assigned to a field? How do i  do this?

    Sorry if this is a stupid question.....

  • 04-08-2013 02:06 PM In reply to

    Re: "Send" button and it's rules

    currentStep is just a node in your InfoPath's form schema. It won't ever be displayed on the canvas. You will use it to control conditional formatting in the form, and set the value of currentStep via rules.

    So for example, when a user clicks button1, set a field's value for currentStep=1.

    When a user clicks button2, set a field's value for currentStep=2.

    You can then have 2 sections: one gets hidden when currentStep=1 and the other gets hidden when currentStep=2.

    Hope this helps!

    Ernesto Machado
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™


  • 04-10-2013 09:00 AM In reply to

    Re: "Send" button and it's rules

    ErnestoM's answer is probably better but a simple solution could just be to disable the button itself.  If you create a text box (make it non-visible), and set a rule on the send button to set the text box value to something, then conditional format the send button so that when the text box equals that something, the button is disabled.  Simple!

    I haven't ever tried ErnestoM's way of doing it but I think his way would probably be better in the long run...

Page 1 of 1 (5 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.