Lisa,

I didn't know what this setting was so I did a little searching in the 
knowledge base.

I found out that this setting on an Audit form is present for an Audit form of 
type Log and it is the number of
other forms that have targeted this particular Log Audit form for auditing.  
So, if it is set to 5, it should mean
that there are 5 forms out there that have auditing of style log turned on and 
those forms have specified
this form as the form to log their audit records to.

So, this is what the setting is - a reference count of the number of forms that 
are targeting this form with a
log style audit.

It seems to be used to determine that there are forms that are referencing this 
form and if the count gets
down to 0, the system knows that no forms are targeting this form as an Audit 
log form any more.

So, this is an internal, automatically set option used for internal management 
of the auditing environment.  It
is not a setting you should be controlling or worrying about.

So, why the difference????

First, have you turned on auditing for another form targeting this form so that 
now there are 4 forms auditing
to this audit log form instead of 3?  That would be consistent with the number 
being 4 on dev and 3 on staging.

Now, if you have not updated auditing on any form on dev to point to this log 
form, the number should be
consistent between the environments.


If you want to pursue further to see what is connected, I found this query in a 
KB article that allows you to
get the names of all forms that are connected to a given log form.  It is an 
SQL query you would issue to the
database.

> select name Form , enable Enabled from arschema s, schema_audit a where 
> a.form=(select schemaid from arschema where name='TMS:AuditLogSystem') and 
> a.schemaid=s.schemaid order by name

Change the name TMS:Audit...  to the audit log form you are looking for of 
course.

This should show you all the connected items.

If this shows you why things are different, terrific.


Other KB articles had a discussion about the number seeming off.  There was a 
mention of doing a
Refresh Object List action when things are displayed in dev studio to make sure 
all the values are correct.

Since the count is calculated, a restore of an old form definition could bring 
back old values.  The values are
really advisory and informational so the system doesn't force recalculation at 
all times so there is the
possibility that they get out of sync.  the Refresh Object List operation 
should recalculate things.


I know this doesn't necessarily answer your question, but hopefully it provides 
some more information
for you to work with.

Doug Mueller

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Kemes, Lisa A DLA CTR INFORMATION 
OPERATIONS
Sent: Wednesday, April 30, 2014 8:01 AM
To: [email protected]
Subject: Audited from RefCount property on a Form

**
Does anyone know what this property is?  "Audited from RefCount"

It's on the CTR:AuditLogSystem form and I'm doing a migrator diff and the count 
is different from dev to staging.  On Dev it's "4" and on Staging it's "3"

I can't find this property anywhere on any documentation....

Lisa Kemes
Remedy Consultant
Dev Technology Group
DLA Office: (717) 770-6437
Cell Phone: (717) 602-9460
[email protected]<mailto:[email protected]>


_ARSlist: "Where the Answers Are" and have been for 20 years_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to