You create a <CurrentUser> node in your DOM. Recommend using <CurrentUser name="" email="" alias=""/>. You will probalby want to do the same for your user list .xml file. The user would select the next person from a drop-down list (or you could get more complex and link everyone together so it can auto-route), and then you would set the current user to the person they selected. You would need to have rules to copy the name/email/alias from the selected person to the CurrentUser fields. The form gets saved or published and an email is sent to the next person to open the form.
You can set up Open Rules (Tools | Form Options) to prevent people from getting into the form (i.e. change views or exit) if they are not the current user.
You need the alias for the Role assignment, the email for sending an email, and the name for the drop-down list.
You sre jumping into some pretty complex stuff here. Don't expect to understand it and get it all right over night!
--
Greg Collins [InfoPath MVP]
Please visit:
http://www.InfoPathDev.com
Greg,
Thanks for the code example. Just one more question. So let say that I put
the domain\login for user in a XML fil. How would I set it to a buttton so
that when the user clicks on it, it will go to a specific person. Let say
that I'm working on the expense report sample. When I click on the submit
button which I put into the form, I want it to be able to go to my Manager.
Now my manager approves and clicks on the submit button, I want it to go to
HR so that they can view it, and send it to Accounting.
Do I just do the same as what you provided in the example, but set the
button to execute that xml file? Please advise.
Also thanks for all the help. I'm really new to this, and appreciate all
the help and efforts you have put into this.
Greg Collins said:
Create an XML file, Users.xml:
<Users>
<User>Domain\login1</User>
<User>Domain\login2</User>
..etc...
</Users>
Add this XML file as a secondary data source (Tools menu)
Create a User Role and have it look up in the Users data source.
If a user's alias is listed in the XML file they will be identified in the role.
You can also do an XML file that takes into account roles:
<Roles>
<Role name="Role1">
<User>Domain\login1</User>
<User>Domain\login2</User>
..etc...
</Role>
<Role name="Role2">
<User>Domain\login1</User>
<User>Domain\login3</User>
..etc...
</Role
</Roles>
Notice login1 is in both roles.
--
Greg Collins [InfoPath MVP]
Please visit:
http://www.InfoPathDev.com
Greg,
Can you point me to an example. I'm fairly new to Infopath and don't know
where to begin. I have been doing some readings on designs and stuf, but
have no clue on programming. Please direct me to a website or provide me
with an example to look at. Thanks.
Greg Collins said:
One option you can use is an XML file loaded as a secondary data source. You would need to store at minimum their network alias, i.e. DOMAIN\login.
You can point the User Roles to that list.
--
Greg Collins [InfoPath MVP]
Please visit:
http://www.InfoPathDev.com
Greg,
I've posted earlier regarding to work flow routing. You say that I can do
this within Infopath. You said that as long as I have a list and have the
assignedto, I should be able to do this. I'm fairly new to Infopath
scripting. Do you know where I make the list of people so that when a user
clicks submit it will know who to send the form to? Also where would I put
this list? And where can I go to assign the form to?
Thanks for you help.
