Workflow

Re: Confirmation screen then approval sent via Notes.

Hilary Stoupa — Tue, 27 Jan 2009 15:59:48 GMT

If your drop down entries are in a secondary data source, you could add an expression box that displays the data node that you are using for your 'display' in the drop down, filtered on the 'value' that was selected in the drop down. If your drop down entries are simply typed into the drop down control, which I think yours are, you won't have that option and I'm afraid will have to end up taking the multiple expression box w/ conditional formatting approach.

Re: Confirmation screen then approval sent via Notes.

riehmc — Mon, 26 Jan 2009 20:41:27 GMT

How do you get a drop-down list box on page 1 to show the display name and not the value on page 2?

0 - Select (default)

1 - Install

2 - Existing

I know that you can use the "install" and "existing" as the value but I have numerous drop-downs that would have to be redone. Is there an easier way to call the display name instead of the value?

Re: Confirmation screen then approval sent via Notes.

Skarn — Sat, 24 Jan 2009 23:51:57 GMT

There's not a much easier way that I'm aware of.

For things like checkboxes, I'd have 2 expression boxes, with a conditional hide on them so only one shows up that matches the checkbox value. e.g. a yes/no checkbox would have two expression boxes, one with 'Yes' as text, and one with 'No' as text, then the 'Yes' one is set with conditional formatting to 'hide' when checkbox is not equal to 'yes' and vice versa for the No.

For text boxes, I used to make the preview up with expression boxes also - but they can't display carriage returns properly sometimes! So I just use textboxes again now, and set them to read only on the preview.

For combo boxes, just use text boxes or expression boxes again.

It takes a bit of time, but it give you the 'locked preview' effect

Re: Confirmation screen then approval sent via Notes.

riehmc — Fri, 23 Jan 2009 19:27:30 GMT

Thanks that was much easier than creating a separate form. I also like your idea on the formMode views but I need some direction on how to set up.

I used text boxes on the second view to pass the data but would rather use another method if you have an easier one in mind.

Re: Confirmation screen then approval sent via Notes.

Skarn — Fri, 23 Jan 2009 06:09:50 GMT

Put another 'view' in your form - View menu -> Manage Views - from the panel on the right on your Infopath window, select 'Add a new view' from the bottom.

It's like another 'page' in your form.

Then, on your first/main page, create a button control - right click it and go to it's properties -> rules tab.

Create a new rule with an action to 'switch view' - and set it to switch to the new second view.

Now you can set up your second view in the formatting you wanted for the 'preview'.

Re: Confirmation screen then approval sent via Notes.

riehmc — Thu, 22 Jan 2009 14:40:05 GMT

What needs to be done to make a "next" button on the "request form.xsn" transfer you to another form called "confirmation screen.xsn". The second form contains the xml from the previous form that can be reviewed before hitting the "submit" button

Re: Confirmation screen then approval sent via Notes.

Skarn — Thu, 22 Jan 2009 09:49:19 GMT

Sorry, I don't understand your second question.

Re: Confirmation screen then approval sent via Notes.

riehmc — Wed, 21 Jan 2009 20:57:30 GMT

This sounds like a plan, can you explain how to start a new form without having to publish both all the time?

Re: Confirmation screen then approval sent via Notes.

Skarn — Wed, 21 Jan 2009 20:46:57 GMT

I gather the submit button isn't actually a 'send via email' button because then the user wouldn't accomplish anything by going back and changing fields, because it is already sent!

Maybe a 'preview' button is what you mean - which you can do by designing a view a bit like a 'print view' which consists of all the fields they need to see on one page in a more 'report' like fashion (just using formatting on the controls, and lock them) - switch to this view when the 'preview' button is pressed, and put your real submit button on this page.

When they push the real submit button, set a hidden field value to something which can tell the form it is at the 'approval' phase - I use 'formMode' and give it a number which indicates where in the 'approval' chain the form is.

Then use Form Open rules to check the value of this field, and switch to a different view -
For your 'supervisor' view, unless they need to change any of the fields, just give them the same 'preview' view you gave the user - except this time make the submit button go to the helpdesk. And if they have limited fields to fill in, put them in a section which is only visible when formMode = 1.

You could even use the exact same view without having to clone it, and put two conditional rules on the submit button, one for when formMode = 0 -> submit to supervisor and one where formMode = 1 -> submit to helpdesk.

Hope this one idea helps you on your way.

Confirmation screen then approval sent via Notes.

riehmc — Wed, 21 Jan 2009 20:29:35 GMT

Can someone help me in creating a confirmation screen to show all the information the customer provided after they hit the submit button? On the confirmation screen it will give the customer the option to go back and edit or "confirm" their request.

Then I have a "gpContactSelector" pulling AD info for the supervisor information. After the customer confirms, I would like to have the request sent via email to the supervisor for approval. Once the supervisor authorizes, the data will then be emailed to a helpdesk to begin processing the request.

My creativity has overstepped my ability. Any help is appreciated.