Re: Infopath using button options

donstephen — Mon, 26 Jan 2015 06:41:30 GMT

Hi Jassie,

I believe all the above mentioned actions are possible.

1. SharePoint Designer workflow allows you to trigger a workflow based on a certain field's data - i.e Status

2. Same thing as the first one. If that status field is equal to, let's say Approved, then you can trigger the workflow based on that field.

3. Modifying a SharePoint list will require you to use code such as CAML. Here you would need to identify the ID of the items you wish to update or modify. You may want to check out qRules' SubmitToSharePointList command if you prefer to avoid writing code.

4. Cancel may be as simple as closing the form, or you could use the blankem technique from this thread, or re-query the last form (which would require a bit of logic to set up).

I hope I was clear enough.

Regards,

Infopath using button options

jassie — Sat, 24 Jan 2015 18:56:14 GMT

In my first project using InfoPath/SharePoint 2013, I have a request for the following
buttons from a user:
1. 'Save' button where changes are 'saved' but they are not submitted to the workflow yet.
2. 'Submit' button where all changes have been made and the data entered into custom list is submitted
to a workflow to the process is approved or rejected.
3. 'Modify' button where updates to the original custom list have been made.
4. 'Cancel' button where any data that is entered is 'not saved' or is just lost.

In InfoPath Designer 2013, there are options to create your own buttons, there are
the default buttons that are generated by SharePoint 2013, and there is the possibility
of creating several InfoPath 2013 forms to accomodate all the buttons required.

Thus can you tell me if one of my optiions I listed above will work and/or can you tell me
what option you are aware of that would work well? Once you pick an option, would you tell
how to setup the option you are suggesting?

General

Re: Infopath using button options

Infopath using button options