I am back after a long break

Its been an year since I posted in the blog, as I was busy with a complex implementation of Cloud to an enterprise customer. I will try to post few experiences, that I have faced during this time in the coming days along with my regular posts on other areas as well.....

Threads in BMC AR System

Today, we can see a brief info about threads

Threads:

1. Individual data channels between the AR Server and the database
2. Each designed for a specific function
3. Certain functions are more efficient with a properly structured thread.

At the server:

Depending on query type the server chooses which data channel; a backup of any due to channel limits can cause server lag.

Thread Types and usage:

• Fast –used for efficient queries
• List –Used for large data transfers
• Admin –used for Administrative functions
• Private –Individual dedicated threads

About AR System Forms in Database

How to go about a list of forms/fields in Database

In order to do this, you need direct SQL Access:

To get the schemaid for a particular form:

• Select schemaid from arschema where name=‘HPD:HelpDesk’

To get a list of forms and corresponding “T” tables:

• Select name,schemaid from arschema order by name

To get a list of all fields for a schema (e.g., schema 120):

• Select fieldname,fielded from field where schemaid=120

To get a list of all forms and fields:

• Select arschema.name,field.fieldname,field.fieldidfrom arschema,fieldwhere (arschema.schemaid=field.schemaid) order by arschema.name,field.fieldname

Please note that this is a brief note and you can go through the bmc docs for in-depth info about this topic.

Submitter Mode in BMC ITSM

Today, we can see about 'Submitter' Mode in BMC AR System

Submitter Mode:

Two Options:

 Locked: The value of ‘Submitter’ can never change

Changeable: ‘Submitter’ can change

Its Use:

• Ability for the submitter to edit ticket/data they submitted, both in and out of the BMC Remedy applications
• Development workflow that has been designed to accommodate your choice

Please note that this is a brief note and you can go through the bmc docs for in-depth info about this topic.

Discuss about 112 field - Assignee Group

Today I am going to brief about '112' field in BMC AR System

Field 112: The “Assignee Group” Field

                                                         Used to enforce row level permissions

                                                          BMC Remedy permissions are cumulative

                             If “Public”is ever in field 112 everyone will be able to see it

To enforce row level permissions all that is needed is:

                                                               i.      –Add field 112 to a form

                                                             ii.      –Add workflow to push the Group ID of any group that should have access

Please note that this is a brief note and you can go through the bmc docs for in-depth info about this topic.

ServerGroup : Message not in catalog -- message number = -1 (ARERR -1)

ServerGroup : Message not in catalog -- message number = -1 (ARERR -1)

If you are seeing the above error, it may be because the DB server may gone down and up after some time. Check with DB team and also look out for arerror logs. 

Though the DB is back, arserver maynot have re-established the connection with DB properly. Restart of AR Server would help in establishing the connection back.

Read user not able to answer a Survey in SRM:Survey form.

Read user not able to answer a Survey in SRM:Survey form.

When an Incident is closed a Survey is sent to the Requester of the Incident.

If this requester has a read license, then he/she cannot answer the Survey as it gives "You do not have write license" on some fields like z1D_Question1_Rating, z1D_Question2_Rating, User_Action, etc.

Error happens when they submit the survey. We  get logged in and answer survey questions fine. Error happens after completing survey questions, on submit.

You do not have write license (AREE 8932)

You do not have write access to field:

z1D_Question9_Rating (ARERR 330)

What I did to resolve this issue

Remove the "SRM:Survey" form from active link "SRM:SHR:Save_CreateEntryOnForm_Submit" and save.

Flush the cache on your midteir server.

Note: Flushing cache will slow everything up on midtier as all forms and workflow will then have to recache