P
Pedro Innecco
Hi there,
Don't know if Microsoft reads suggestions on this forum, but I have some
InfoPath suggestions for future releases. The idea is to be able to perform
the features outlined below with NO CODING:
1. To allow parameters in the userName() function to return log-in name,
email, firstname, lastname etc. The idea is to fetch such values without the
need of Web services.
2. Allow further flexibility on the toolbar buttons, such as
a) Allowing specific buttons only at specific views. For example, the close
button only at one view, or the save button only at another view.
b) More control over SAVE and CLOSE buttons. For example, not giving the
user the ability to save when closing the form, giving the user the ability
to save but not to specify a file name (save as).
c) Allowing specific buttons based on variables, conditions, etc.
3. Also allowing the user to add buttons on forms for (without coding
always): Saving, Closing. For example, I would like to allow a button called
CLOSE on my form. Wich could ask the user to save the changes or not, but
not allowing the user to specify the filename (no SAVE AS, just SAVE). This
button would only appear on already submited forms (esily done with
variables).
Don't know if Microsoft reads suggestions on this forum, but I have some
InfoPath suggestions for future releases. The idea is to be able to perform
the features outlined below with NO CODING:
1. To allow parameters in the userName() function to return log-in name,
email, firstname, lastname etc. The idea is to fetch such values without the
need of Web services.
2. Allow further flexibility on the toolbar buttons, such as
a) Allowing specific buttons only at specific views. For example, the close
button only at one view, or the save button only at another view.
b) More control over SAVE and CLOSE buttons. For example, not giving the
user the ability to save when closing the form, giving the user the ability
to save but not to specify a file name (save as).
c) Allowing specific buttons based on variables, conditions, etc.
3. Also allowing the user to add buttons on forms for (without coding
always): Saving, Closing. For example, I would like to allow a button called
CLOSE on my form. Wich could ask the user to save the changes or not, but
not allowing the user to specify the filename (no SAVE AS, just SAVE). This
button would only appear on already submited forms (esily done with
variables).