For call Filter from AL you can user Service action. To do this:
in AL you create Service action, where specify "Input Mapping" (fileds, that will be used in Filter qualifications) and "Output Mappings" (fields, that must be returned after was processed in filters ).
And you create Filter, that have in Execution Option value "Service".
For more information you can see "Workflow object guide"... (http://documents.bmc.com/supportu/documents/39/86/183986/183986.pdf)
With best regards,
thanks alex..one more think i would like know..if i want to create service request whic have some custome fields like customer id,name, phone number,record date,payout date,and issue details through web service.which action i should use in filter?
You can use 'set field' action in Filter. At 'Set Field' you should specify in 'Data Source' property value as 'WEB SERVICE'.
Link to documentation:
See page 89 (Decribe about creating a Set-Field in Filter to use Web Service )
thanks for your feedback.but i dont have access to link you have sent me.it would be great if u shared that doc with me by mail..
but i don't know can i or not to share product documentation.
If you have permission to search product documentaion, you can find it from yourself in A-Z List search.
The name of guide is "BMC Remedy Action Request System 7.6.04: Integration Guide"
I don't see where the filter can actually be called.
When I create "Service" in the AL, I can find no place to specify the name of the filter I want to launch.
Its because in the filter you have an "event" (checkbox) that should be named "service" in the "execution options" part. That's how it knows he needs to be fired.
I see a "Service" box under "Execution Options" in the AL.
I also see an "Event" box under"Execution Options" in the Filter.
But I don't see how they are connected.
It looks like the filter can be ran by the user clicking a button, maybe I don't even need the AL?
1 of 1 people found this helpful
In fact the active link will send some kind of "trigger event" (so named service), and the filter will detect this (if you checked service in "execution options") and the filter will fire.
You should just give it a try or see how it's done already in the solution, see there:
The active link "HPD:COI:Init_000_ServiceGetConsoleVariables" is doing a "service" action, in input mapping it sets a field to "GLOBAL_VARIABLES" (or something like that). Look at the form it executes on (don't remember it right now).
Now if you search filters, with primary form as the one from the active link, you'll see several filters like that:
Those filters will fire when the active link fires the service action. The one that will execute its actions is named "HPD:COI:SERVICE_GLOBAL_XXX" (or something like it).
Best way to see it is to open the 15 "HPD:COI:SERVICE_xxx" and see which one tests the "GLOBAL_VARIABLE" string in the run-if qualification. It has a "call guide" action.
So just think Service action in active link as sending a trigger event for a server side workflow, just saying "hey, wake up, there's something to do on the form, server side!".
Input mapping are data the active link "sends" to the filter (server side) and output is the opposite, data that server side workflow sends to "client side" workflow, back.
A bit like an ajax call on a webpage that would call a php page server side and would get some results back.
I still don't understand. Where is the active link do I specify *which* filter is to be fired? Or, where in the filter do I specify which action will cause the filter to launch?
If I need to run a filter, why not just run that filter? Why do something pointless just to trigger a filter?
The acl does not tell which filter to run. The acl sends just a "service" event on the form.
Any filter that "listen" to "service" on this form will react.
As far as the "why"... Well... I don't know... I guess it's the way it works
So where do I tell the filter to listen for this event? In the "Run If Qualification" ?
Do I put something like: Status = "Closed" or something?
I get that the "Service" box needs to be checked.
But, don't I need to tell the Filter specifically *what* event to listen for?
For example, lets suppose, as a trigger event, I set status to closed. Then in the Filter's "Run if Qualifications" I would have to check to see if Status = Closed. Right?