Hi, Its not a bug. We have seen a case where because of change in the input length of a field it was providing a wrong value.
HTH -- Regards, Dhanshree Vyom Labs Pvt. Ltd. BSM Solutions & Services || ITIL Consulting & Training Email: i...@vyomlabs.com || Web Site: www.vyomlabs.com Follow Vyom Labs http://twitter.com/#!/vyomlabs || http://www.linkedin.com/company/vyom-labs -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Eric Roys Sent: Friday, August 17, 2012 8:51 AM To: arslist@ARSLIST.ORG Subject: Service action Peculiarity Has anyone come across a peculiarity with the filter Service action where-in what is mapped is not what is received on the other end? ARS7.6.4 sp2 The particulars... Filter Service Input Mapping: inChar000 (536870913) = $host$ //source field id (536870913) inChar001 (536870914) = "People" //source field id (hardcoded) inChar002 (536870915) = "Used by" //source field id (hardcoded) inChar003 (536870916) = $corpid$ //source field id (536870915) Source values at time of call say: inChar000 (536870913) = vm04 inChar001 (536870914) = People inChar002 (536870915) = Used by inChar003 (536870916) = 4712258 Receiving says (and passes wrong value - see inChar003)... <FLTR> <TID: 0000003824> <RPC ID: 0000035856> <Queue: Fast > <Client-RPC: 390620 > <USER: jtkirk > <Overlay-Group: 1 > --> service action input <FLTR> <TID: 0000003824> <RPC ID: 0000035856> <Queue: Fast > <Client-RPC: 390620 > <USER: jtkirk > <Overlay-Group: 1 > inChar000 (536870913) = vm04 <FLTR> <TID: 0000003824> <RPC ID: 0000035856> <Queue: Fast > <Client-RPC: 390620 > <USER: jtkirk > <Overlay-Group: 1 > inChar001 (536870914) = People <FLTR> <TID: 0000003824> <RPC ID: 0000035856> <Queue: Fast > <Client-RPC: 390620 > <USER: jtkirk > <Overlay-Group: 1 > inChar002 (536870915) = Used by <FLTR> <TID: 0000003824> <RPC ID: 0000035856> <Queue: Fast > <Client-RPC: 390620 > <USER: jtkirk > <Overlay-Group: 1 > inChar003 (536870916) = Used by Change Service Input mapping to use new field/id as: inChar000 (536870913) = $host$ //source field id (536870913) inChar001 (536870914) = "People" //source field id (hardcoded) inChar002 (536870915) = "Used by" //source field id (hardcoded) inChar003 (536870916) = $corpid1$ //source field id (536870929) => new field/id not in field id set on destination form Use same Source Values as previously noted. Receiving now says (and works properly)... <FLTR> <TID: 0000003824> <RPC ID: 0000036444> <Queue: Fast > <Client-RPC: 390620 > <USER: jtkirk > <Overlay-Group: 1 > --> service action input <FLTR> <TID: 0000003824> <RPC ID: 0000036444> <Queue: Fast > <Client-RPC: 390620 > <USER: jtkirk > <Overlay-Group: 1 > inChar000 (536870913) = vm04 <FLTR> <TID: 0000003824> <RPC ID: 0000036444> <Queue: Fast > <Client-RPC: 390620 > <USER: jtkirk > <Overlay-Group: 1 > inChar001 (536870914) = People <FLTR> <TID: 0000003824> <RPC ID: 0000036444> <Queue: Fast > <Client-RPC: 390620 > <USER: jtkirk > <Overlay-Group: 1 > inChar002 (536870915) = Used by <FLTR> <TID: 0000003824> <RPC ID: 0000036444> <Queue: Fast > <Client-RPC: 390620 > <USER: jtkirk > <Overlay-Group: 1 > inChar003 (536870916) = 4712258 Thoughts? Bug? Enhancement? As designed? Thanks, Eric Roys Seamless Technologies CONFIDENTIALITY NOTICE: This email communication is intended only for the personal and confidential use of the recipient(s) designated above and may contain information which is subject to Federal and/or State privacy laws. In the event that you are not the intended recipient or the agent of the intended recipient, you are hereby notified that any review, disclosure, or use of the information contained herein is strictly prohibited. Do not copy or use the information contained within this communication, or allow it to be read, copied or utilized in any manner by any other person(s). If you have received this communication in error, please notify the sender immediately, either by response e-mail or by phone, and permanently delete the original e-mail, any attachment(s), and copies. ____________________________________________________________________________ ___ 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"
