Professional Documents
Culture Documents
BMC.com > All Places > Products > BMC Remedy AR System > Documents
Created by Vincent RIEDWEG on 06-Jun-2013 09:17. Last modified by Vincent RIEDWEG on 16-Jul-2013 09:19.
Hi all,
I have seen too often some people always asking about Filter Phase and how it works.
This is actually very well documented here https://docs.bmc.com/docs/display/ars81/Filter+processing+in+BMC+Remedy+AR+System+server .
This document objectives are not to explain again that documentation, but just giving some tech tips that you should know if you want to play with
Filter Phase.
Time to play
Let's take the following scenario: From a staging form, we want to create CI Unavailability record that record to an incident.
In that scenario, to be able to create the relationships, we must retrieve some information from the CI Unavailability record first. So the
database transaction must be committed.
There are different ways to design and build that. Let's talk about 3 different ways.
I take my gun to hunt butterflies
KWWSVFRPPXQLWLHVEPFFRPGRFV'2&
3OD\LQJZLWK)LOWHU3KDVH_%0&&RPPXQLWLHV
I am a lemming
I am a player
KWWSVFRPPXQLWLHVEPFFRPGRFV'2&
3OD\LQJZLWK)LOWHU3KDVH_%0&&RPPXQLWLHV
With that method, it's quite difficult to debug as the record in the stagging form it deleted just after the creation. There is no escalation and the
relationship's records are created immediately.
Quick summary
If you prefer the "I take my gun to hunt butterflies" method, search on eBay for a new brain. Then have a look on the documentation and
reread all the documentation closely.
If you prefer the "I am a lemming" method, I am pretty sure you looks like an old school man or you are not a player. You can just try and adopt
the "I am a player" method. I am pretty sure you will enjoy it.
If you prefer and use the "I am a player" method, you are a winner as you already know all you need to know on Filter Phase.
1786Views Categories: Best Practices, Developer Guides, Tips and Techniques Tags: ars, arsystem, best, practices
(3 ratings)
4 Comments
KWWSVFRPPXQLWLHVEPFFRPGRFV'2&
3OD\LQJZLWK)LOWHU3KDVH_%0&&RPPXQLWLHV
Good one. To add on, probably playing safe is a good option. After 7th step, 8th step is to Push to duplicate staging form "Staging Form2"
with matching Ids to copy the staging form data for record purpose.
-remedyloganalyzer.com
RLA,
For a real design if it's required, for sure. That's just some examples to illustrate the Filter Phase. And if it helps someone having a
better understanding of how Filter Phase works, I win. For that illustration, there is no added value, from my point of view,
having a use case "I am a paranoiac player".
I have decided to write this short document because that's some design tips that I can see too rarely if I am not in charge of the
design.
Vincent,
Vincent, I like your documentation here...i wanted to offer a 4th option that steps 'out of the box' a bit, but if you can live with that, then it's
an options.
"I'll take a break, then come back and finish this later"
- I have in the past written a command line client that is called on submit. This command line client logs into the Remedy server and
performs an update on the record post-submit...so, basically your 3 approaches are 'how do I wait for this data to be available before I
create the other records....so this process does a fire/forget run process, that has a built in 'pause' because of the need to start the
command line, but you can build in whatever delay you need within the program...then do a setEntry call which does the same thing as the
Escalation....but 'quicker' than an escalation, without the 'polling'
LJ, I like your option. Indeed, if we can achieve a requirement without doing anything, I choose that one and take a coffee.
That's quite the same approach, from a Filter Phase perspective, than "I am a player". But with your tool can you read some
information that are required from the previously created record before creating the other request? I already know that with API's I
can do it for sure.
The cons of your solution it that a login / logout call made to the AR System server consumes more resources.
Copyright 2005-2015 BMC Software, Inc. Use of this site signifies your acceptance of BMC's Terms of Use, Privacy Policy and Cookie Notice.
BMC, BMC Software, the BMC logos, and other BMC marks are trademarks or registered trademarks of BMC Software, Inc. in the U.S. and/or certain
other countries.
Manage Cookies
KWWSVFRPPXQLWLHVEPFFRPGRFV'2&