Browser Forms

Re: Hi.....its about Info-path form..!

Clay Fox — Tue, 26 Feb 2008 06:51:53 GMT

Have you decided on a method for identifying the form user?

If you have a Status field then the conditional formating would be

status is blank and UserID is not equal to approver ID

check "hide" the section

Then on submit one of the actions would be to set status to Submitted or whatever right before the submit to Sharepoint and the close of the form.

Re: Hi.....its about Info-path form..!

ahjie1989 — Tue, 26 Feb 2008 06:41:41 GMT

yeah..right

this is part i dont know...

You put the buttons in a section and then add conditional formatting to the section to hide if not the approver

there isnt much option at conditional formatting ..

is it possible that you give me the option for it...?

thanks

Re: Hi.....its about Info-path form..!

Clay Fox — Tue, 26 Feb 2008 06:35:06 GMT

Yes that is what I have described.

You put the buttons in a section and then add conditional formatting to the section to hide if not the approver.

And it sounds like you will have a field that will contain the status and you want to promote this field to SharePoint.

Re: Hi.....its about Info-path form..!

ahjie1989 — Tue, 26 Feb 2008 06:30:34 GMT

what i mean is that

example: i create a leave form...example : with 2 user (Worker, Approver)

-Leave Form with 3 buttons ("Submit, Approve, Reject")

Submit button will be viewable to all, as for Approve Buttons / Reject Buttons, it will be only be viewable by Approver

then i upload it on the server, when a worker is to apply leave form that form,

Worker wont be able to see the Approve Buttons / Reject Buttons"Hidden", after Worker submit it...

When the Approver login in to Approve / Reject, he can only see the Approve Buttons / Reject Buttons "Shown"....

upon clicking the Approve Buttons / Reject Buttons, the Columns Display will update the Status ...

is it possible to create this type of form...?

thanks

with regards

Re: Hi.....its about Info-path form..!

Clay Fox — Tue, 26 Feb 2008 05:49:23 GMT

I guess I do not understand.

You build a smart form that can track each step of the process and then you pass it around.

User A opens new form.

Form is blank so form accepts input into the form fields.

Form stores detials of the user and looks up the manager.

Upon Submit it is validated and email data connection sends the form to manager, and also saves to a central location.

Manager recieves email opens it.

Form in Open rules checks state and user. State is submitted and user matches manager ID saved in form so the manager can see the fields and the buttons to approve or reject.

Each button submits to central location, and emails a response back to the requestor or possibly to the next approver.

Etc.

Re: Hi.....its about Info-path form..!

ahjie1989 — Tue, 26 Feb 2008 05:25:30 GMT

nai....its not about the connection....

i just want to know whats the steps for the form....

how to do it..?

thanks

with regards..

Re: Hi.....its about Info-path form..!

Clay Fox — Tue, 26 Feb 2008 04:04:21 GMT

You set up the data connections for email submit as you would normally.

You setup SharePoint for email.

In a browser based form the server emails rather than the client so having Outlook is not neccessary.I would store the requestor, approver, manager, etc in your form and their email addresses.

Then you can use these fields for the email submit.

Re: Hi.....its about Info-path form..!

ahjie1989 — Tue, 26 Feb 2008 04:01:57 GMT

hii....

is it possible that you teach me step by step....

or can you send me a sample copy...

by the way..i'm not running Microsoft Outlook...i'm just using Form Server 2007...

hope to hear from you soon...

thanks

Re: Hi.....its about Info-path form..!

Clay Fox — Tue, 26 Feb 2008 03:49:22 GMT

What you describe can be done in one InfoPath view without any coding, just use rules and conditional formating to show the correct items and buttons.

Typically you want to identify each form user and the form state so that you have the ability for the logic to determine the appropriate contents.

I typically use an Active Directory Web Service to IDentify the user and retrieve their email address, and other information. The same web service allows me to lookup the approvers email (Manager, etc).

Then also have a field that stores the state of the form.

So if it is open and blank, it is new and for the requester.

If State is pending or for approval then validate the form user is who it is assigned to for approval and display the approval buttons.

Etc if you need an additional step or if you want to reject and resubmit.

Re: Hi.....its about Info-path form..!

ahjie1989 — Tue, 26 Feb 2008 03:41:22 GMT

cool...thanks for the reply....

so is it under three state workflow or just the codeing with the form....?

Re: Hi.....its about Info-path form..!

Clay Fox — Tue, 26 Feb 2008 03:38:33 GMT

Welcome to the forum.

Yes, this is possible and a very common scenario.

Re: Hi.....its about Info-path form..!

ahjie1989 — Tue, 26 Feb 2008 03:27:54 GMT

is it possible...?

Hi.....its about Info-path form..!

ahjie1989 — Tue, 26 Feb 2008 02:35:23 GMT

Hi.....its about Info-path form..!

err....i'm just wondering if i can create a form with workflow..

it will be like this...

A form with 3 Button..."Submit", will be hidden to approver...

( Approve", "Reject)will be hidden to Requester, viewable by Approver and Manager,

Requester - Fill in form,click on Submit Button"

Approver - Write in Comment and Reject / Approver Form...(Approve", "Reject) will be show, "Submit" will be hide again...