InfoPath Dev

During my adventure in form creation I have come across something I would like to do but however I am at a loss on how to create this.

I have a form that filters data from a SharePoint list based on previous selections (Dependent Drop Down). The very last selection will ba a list of activities that have to be meet in order to submit the form. Generally there will be three items left but that not what it is limited to.

These activities are added as completed by clicking a button in a repeating table where they are stored with addition data based on each activity.

So in a nut shell as the users completes the activities he or she will open there form from SharePoint and log the data and save the form back to the library.

What i would like to do is once the required activites have been meet it will change to where instead of saving the form to SharePoint I would like a workflow to start for an approval process. From there I would make that view read only to where the approving person will do there thing saving it back to SharePoint. I pretty much know how to do everything except figuring out how to calculate many required activities are needed.

Does anyone have any ideas on how to approach this problem without using code.

Thanks,

Doug

Can't you just use conditional formatting in the button that says what actions to perform based on given criteria?  The workflow part is separate, because that depends on what workflow tool you're using (SPD or Visual Studio).  The workflows themselves have to have logic that says what to do based off some metadata in the form.  For example, when all activities are complete, you can tell the button to set a flag in the form (hidden field) that tells your workflow to perform the approval actions.  The form itself can then have a Rule in the Form Options menu that changes the view automatically to a read-only view (remember to remove buttons from this view).

warrtalon:

Can't you just use conditional formatting in the button that says what actions to perform based on given criteria?  The workflow part is separate, because that depends on what workflow tool you're using (SPD or Visual Studio).  The workflows themselves have to have logic that says what to do based off some metadata in the form.  For example, when all activities are complete, you can tell the button to set a flag in the form (hidden field) that tells your workflow to perform the approval actions.  The form itself can then have a Rule in the Form Options menu that changes the view automatically to a read-only view (remember to remove buttons from this view).

Well I am sure this is where i would do most of the work in the form design. The problems is there are 101 different things in a list that all have different activities assigned to them. So as you choose the items in the drop down list it will filter to what activities are required.

For example if I picked "Value Stream Mapping" as one of the 101 items it would present me three items to choose from that are required for that event. 1. Completed TM203; Focus on the front of the room 2. Completed appropriate (Level 1 Shadowing) 3. Assisted in 2 classes.

I need a way to cross check to see if all items have been completed before allowing the person to submit the form. So the gray area I am trying to figure out is how to get that in to the criteria area.

Doug

If there are 101 different combinations, then it could be a gigantic chore.  You might have to make an extra field for each selection that has a boolean flag (or something similar) that gets set to True once each task is completed for a given selection.  You can then reference this field for each selection via conditions on the button.  This will be a ton of work, but I don't yet have a solution in mind that can handle all 101 combos in a consolidated manner.

warrtalon:

If there are 101 different combinations, then it could be a gigantic chore.  You might have to make an extra field for each selection that has a boolean flag (or something similar) that gets set to True once each task is completed for a given selection.  You can then reference this field for each selection via conditions on the button.  This will be a ton of work, but I don't yet have a solution in mind that can handle all 101 combos in a consolidated manner.

Yea that's my problem because of the large amount of info and finding a way to due this efficiently in InfoPath. Maybe some will chime in with a solution that would work for me.

Doug