<?xml version="1.0"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>MachForm Community Forums Topic: Forward Form After Admin Update</title>
<link>https://www.machform.com/forums/</link>
<description>MachForm Community Forums Topic: Forward Form After Admin Update</description>
<language>en</language>
<pubDate>Sun, 03 May 2026 23:08:11 +0000</pubDate>

<item>
<title>yuniar on "Forward Form After Admin Update"</title>
<link>https://www.machform.com/forums/topic/forward-form-after-admin-update#post-19286</link>
<pubDate>Thu, 03 Oct 2013 16:58:07 +0000</pubDate>
<dc:creator>yuniar</dc:creator>
<guid isPermaLink="false">19286@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;I'm afraid MachForm doesn't support that kind of functionality. Sorry. That would create a powerful workflow indeed, but it would complicate things for most users.
&#60;/p&#62;</description>
</item>
<item>
<title>eventura on "Forward Form After Admin Update"</title>
<link>https://www.machform.com/forums/topic/forward-form-after-admin-update#post-19268</link>
<pubDate>Mon, 30 Sep 2013 06:01:46 +0000</pubDate>
<dc:creator>eventura</dc:creator>
<guid isPermaLink="false">19268@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;Hi Guys&#60;/p&#62;
&#60;p&#62;In order to facilitate a little more back end workflow, is there a way to autoforward the form to another email address when the form data has been amended. Let me try to explain by example.&#60;/p&#62;
&#60;p&#62;User completed Vacation request form. They get a copy, manager gets a copy.&#60;br /&#62;
Manager logs in and approves request, form now gets sent (together with the manager's authority) to Human Resources / Payroll.&#60;/p&#62;
&#60;p&#62;If you could tie this so that the form gets emailed to an address dependant upon the content of a field then you have a very powerful workflow solution for the &#34;Office Processing&#34; parts of forms.
&#60;/p&#62;</description>
</item>

</channel>
</rss>
