In this section we will create the application rules to manage our submissions. Our application rules will allow those who are part of the IT department to edit the submission while restrict others to view only permission.
Users who create application rules must have the Application Developer permission. Rather than check this privilege on the user's User Information Form (UIF), it is recommended that you create a group named Application Developers and check that privilege on that group then assign your conference creators to that group.
It is never good practice to allow anyone to edit messages in a conference. This is a potential security issue that is beyond the scope of this tutorial. Just trust me. To get around this, we can use an application rule that will turn a submitted message into a Document and then we can allow our moderators to edit documents.
For efficiency purposes, FirstClass does not know about any fields on a form unless they are touched by the client. Since the status field has not been touched, the server does not know it exists, so when we send a message to our conference, the icon is not displayed in the conference list. We can fix this problem by using an application rule to punch in the default value of our icon field (1017) on both the form (object) and in the list (item). We can modify the Change to Document rule to add these actions.
We will set permissions so that only the IT Department can edit the form, but we must first check the hidden checkbox that will make the IT Dept Only group editable. We do this by adding one more line to our receive rule by setting the value of field 1016 to 1 in the form (Set in Object)
When the work order is completed, you can have a reply automatically sent back to the person who submitted the request. This will only be initiated if the status field (Field 1014) is set to value 2 (completed)