Hi,
We’ve had this occur in the past. In our case it was caused
by user entries still being present in the User form, even though the same
person is/was set to offline or delete on the people form. A good example was
the Service Desk, which typically has a higher turnover of staff than other
Hi,
According to me no need to change the user to Non-support we can use the
arreload.exe utility for this.
Location of file arrelaod.exe is: C:\Program Files\BMC Software\ARSystem
(Your installation directory)
The arreload utility executes the BMC Remedy AR System interface that
enables you
We had the same issue in our 7.6.03 environment, and there is an article
on the support site that discusses the fix. Here are the details from the
article for 7.5. The 7.6.03 fix resolved the issue for us. Hope this
helps.
On From CTM:SupportGroupAssocPeopleLookUp and
Form
A Funny Case Of Kiss And A Slap - must read it
A HR Manager, His Assistant, An Old Woman And Her Young Daughter Are
Traveling In A Train And During The Course Of Time Get Themselves
Introduced To Each Other And Become Temporary Friends...
The Train Goes Through A Tunnel And It Gets Completely
My recommendation would be to do a run process. Like everyone else is
saying, the best way to run an escalation is to use a form just for
escalations. One record per escalation. That way you have a small amount
of records for it to walk over. Then use a filter to perform the work.
When you
I will have the position details soon but if you are interested please contact
me via email be first in line. The position will be onsite, long term, needs AR
development and design prefer strong exp with upgrades esp v 7.x to 8. Thanks
all - ch...@cm-ug.com
I have data coming from two different data sources for different CI Types.
(Ex: Computersystems in DataSet A,
IPAddresses in DataSetB).
So I need to create relationships between them and eventually reconcile
them into production dataset.
No issues with CIs because they can be in different
Easiest way to think about relationships is to think about them as CI's also.
The cleanest thing for you to do would be to push the data from
Dataset A and B into a new Dataset C. From there, create your
relationships and then reconcile it into your prod Dataset.
Sent from my iPhone
On Aug 16,
When you set up the reconciliation jobs you can adjust the weight of the
attributes that exist so that, for example, one dataset provides the name and
the other provides the IP address. The key is to set up each dataset so that
the attribute that makes them common exists in both datasets.
Ok, this is one way of doing it.
I was trying to avoid this method if possible to prevent from
reduplicating the data again into datasetC which will eventually impact the
BMC_BaseElement query performance if the CI count is huge.
Else instead of having two datasets A,B , I could directly bring
This works if IPAddress is an attribute of ComputerSystem.(1-1)
But if it is 1-Many then I need to create a relationship CIs between
ComputerSystem and IPAddress.
Note:I am using ComputerSystem, IP Address scenario as a hypothetical
example.
ComputerSystem is in DataSet A, and IP Address is in
You cannot do relationships across Datasets, each one is unique.
-Original Message-
From: patchsk vamsi...@gmail.com
To: arslist arslist@ARSLIST.ORG
Sent: Fri, Aug 16, 2013 2:25 pm
Subject: Re: CIs in two different datasets, creating relationships and
reconciling into Asset dataset
At least not out of the box.
- Original Message -
From: Roger Justice rjust2...@aol.com
To: arslist@ARSLIST.ORG
Sent: Friday, August 16, 2013 3:04:08 PM
Subject: Re: CIs in two different datasets, creating relationships and
reconciling into Asset dataset
** You cannot do relationships
There is no problem creating relationships between CIs in different
datasets.
The relationship itself is, of course, in one dataset and a recon job for
that dataset will process it.
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On
14 matches
Mail list logo
