Re: SRM 2.2 Attachment files
Hugo, That apparently is as designed, since we have seen the same behavior. You will have to create your own workflow to push the attachment over to the Incident work info. Kevin *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Hyunkel v2.0 *Sent:* Monday, January 16, 2012 6:31 PM *To:* arslist@ARSLIST.ORG *Subject:* SRM 2.2 Attachment files ** Hi List; I've found something and I need some clues to get this done. It happens when users attach a file from the Request Entry form (either while creating a New Service Request or updating and existing Service Request) on SRM. The file is seen on the Service Request form, but not in the Incident Management form (Work Info) the text is the same on both entries, but the missing data is the attachment itself. Does anyone had seen this before? Thanks. *Hugo Ruesga* *Software Development Advisor* P Please consider the environment before printing this email *The information contained in and transferred with this electronic message is intended only for the recipient(s) designated above, it is protected by law and it may contain information which is privileged and confidential. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. **Thank you.* _attend WWRUG12 www.wwrug.com ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
Re: SRM 2.2 Attachment files
that is correct, attachments are not part of the workflow that generates the template with SRM requests. the idea is to prevent attachment files to be in more that one place in the database and the reason for the link to view the service request at the top of the tickets. On Jan 17, 9:27 am, Kevin Morgan goofy1...@gmail.com wrote: Hugo, That apparently is as designed, since we have seen the same behavior. You will have to create your own workflow to push the attachment over to the Incident work info. Kevin *From:* Action Request System discussion list(ARSList) [mailto: arsl...@arslist.org] *On Behalf Of *Hyunkel v2.0 *Sent:* Monday, January 16, 2012 6:31 PM *To:* arsl...@arslist.org *Subject:* SRM 2.2 Attachment files ** Hi List; I've found something and I need some clues to get this done. It happens when users attach a file from the Request Entry form (either while creating a New Service Request or updating and existing Service Request) on SRM. The file is seen on the Service Request form, but not in the Incident Management form (Work Info) the text is the same on both entries, but the missing data is the attachment itself. Does anyone had seen this before? Thanks. *Hugo Ruesga* *Software Development Advisor* P Please consider the environment before printing this email *The information contained in and transferred with this electronic message is intended only for the recipient(s) designated above, it is protected by law and it may contain information which is privileged and confidential. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. **Thank you.* _attend WWRUG12www.wwrug.comARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org attend wwrug12www.wwrug12.comARSList: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
Re: SRM 2.2 Attachment files
Thanks for your kind responses I appreciate that. I'll need to built that workflow. Is there any guidance on how to copy those attachments? Or is it possible just move the attachments? Thanks. Hugo Ruesga Software Development Advisor P Please consider the environment before printing this email The information contained in and transferred with this electronic message is intended only for the recipient(s) designated above, it is protected by law and it may contain information which is privileged and confidential. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. Date: Tue, 17 Jan 2012 07:18:39 -0800 From: tpala...@gmail.com Subject: Re: SRM 2.2 Attachment files To: arslist@ARSLIST.ORG that is correct, attachments are not part of the workflow that generates the template with SRM requests. the idea is to prevent attachment files to be in more that one place in the database and the reason for the link to view the service request at the top of the tickets. On Jan 17, 9:27 am, Kevin Morgan goofy1...@gmail.com wrote: Hugo, That apparently is as designed, since we have seen the same behavior. You will have to create your own workflow to push the attachment over to the Incident work info. Kevin *From:* Action Request System discussion list(ARSList) [mailto: arsl...@arslist.org] *On Behalf Of *Hyunkel v2.0 *Sent:* Monday, January 16, 2012 6:31 PM *To:* arsl...@arslist.org *Subject:* SRM 2.2 Attachment files ** Hi List; I've found something and I need some clues to get this done. It happens when users attach a file from the Request Entry form (either while creating a New Service Request or updating and existing Service Request) on SRM. The file is seen on the Service Request form, but not in the Incident Management form (Work Info) the text is the same on both entries, but the missing data is the attachment itself. Does anyone had seen this before? Thanks. *Hugo Ruesga* *Software Development Advisor* P Please consider the environment before printing this email *The information contained in and transferred with this electronic message is intended only for the recipient(s) designated above, it is protected by law and it may contain information which is privileged and confidential. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. **Thank you.* _attend WWRUG12www.wwrug.comARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org attend wwrug12www.wwrug12.comARSList: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
SRM 2.2 Attachment files
Hi List; I've found something and I need some clues to get this done. It happens when users attach a file from the Request Entry form (either while creating a New Service Request or updating and existing Service Request) on SRM. The file is seen on the Service Request form, but not in the Incident Management form (Work Info) the text is the same on both entries, but the missing data is the attachment itself. Does anyone had seen this before? Thanks. Hugo Ruesga Software Development Advisor P Please consider the environment before printing this email The information contained in and transferred with this electronic message is intended only for the recipient(s) designated above, it is protected by law and it may contain information which is privileged and confidential. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
