Abdelaziz, If you are familiar with standard OO Programming, you know about methods. A method accepts x inputs, and provides y outputs. Think of the service action in the same light. Build up a series of filters that do a function you need done, have them fire on the 'Service' event. Then build an AL that calls a service action and provides the necessary inputs, and maps the outputs to where you need.
Viola, you have a service action. Think of it as a way to create code modules that can be called repeatedly throughout your application and always provide the right input, always getting the right output. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Mohamed Abdelaziz Sent: Friday, April 22, 2011 11:13 AM To: [email protected] Subject: Service Action Type ** Can you please provide a detailed definition with scenarios on the user of Service Action Type. (I. E. The use of input mappings, output mapping and Request ID) The user guide does not seem to provide a clear and detailed definition. Thanks, Moe _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
