Another option is to spin off a new form that is a "Question/Answer" form. Have workflow on the "Change" that creates a new record that is "owned" by the target person to answer the question. ( That way field '2' on the Change is not an issue, and you get a one Change to many "Question/Answer" records too.)
-- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 11/30/06, patrick zandi <[EMAIL PROTECTED]> wrote:
** Just looking this over.. Submitter locked mode allows the submitter to update his ticket in Read license mode. The approver already has a Fixed or Floating license. So you could use a Diary field to log the conversation by inputs via Email submission or API or Mid-tier. Create a Question 400 character field, or 2000 for that matter. and Create an Answer Field. If the Question is placed in the field - push to diary, and send email to customer with a URL or Email form. Answer comes into the Answer field and gets pushed to the Diary. Does this fit the License scenario ? They both have access to the Diary and Question and Answer field. The submitter is able to update his information. The approver is able to update the ticket. Just a thought.
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
