Skip navigation
Share This:

Question: Why and when will status of service target be updated to 'Invalid'?
============================================================
There are five filters that do a Set Fields action on the SLM:Measurement form to update the MeasurementStatus field on the SLM:Measurement form to 'Invalid'.  These filters will fire when the Run If qualification is met and three of these filters have a message generated to the user when the update occurs.  The message identifies the condition causing the update to 'Invalid'.


++++++++++++++++++
#1
SLM:Measurement:AvailDoneUpdateMeasurementStatusInvalid

     Run If
    ( 'GoalTypes' = "Availability") AND ( 'MeasurementStatus' = "Attached") AND ( 'MeasurementDone' = "Yes") AND ( 'TR.MeasurementDone' != 'DB.MeasurementDone')

     NOTE:

     Essentially, this condition will occur when measurement of a service target completes when a service target is in 'Attached' status.


#2
SLM:Measurement:ReqSetMeasurementStatusToInvIfRefEndGoalforReqBasedSVTsLTNow

     Run If
    ( 'GoalTypes' = "Request-Based") AND ( 'MeasurementStatus' != "Invalid") AND ( 'TR.MeasurementStatus' = "In Process") AND ( 'UseGoalAsDefinedOnTheAppFormSel' = "Use Goal defined on the Application Form") AND ( 'ReferenceEndGoalforRequestBasedSVTsFieldValue' !=  $ NULL $ ) AND ( 'ReferenceEndGoalforRequestBasedSVTsFieldValue' < $ TIMESTAMP $)

 

    * * * Message * * *
    'Reference End Goal for Request-Based SVTs' field in Application Form is less than the current time, it will make the Measurement record invalid


#3
SLM:Measurement:ReqSetMeasurementStatusToInvalidIfEmptyOverallStartTime

     Run If
    ( 'GoalTypes' = "Request-Based") AND ( 'MeasurementStatus' != "Invalid") AND ( 'TR.MeasurementStatus' = "In Process") AND ( 'OverallStartTime' =  $ NULL $ )

 

    * * * Message * * *
    Empty Start Time field in Application Form will make the Meaurement record invalid


#4
SLM:Measurement:ReqSetMeasurementStatusToInvalidIfEmptyRefGoalforReqBasedSVTsFV

     Run If
    ( 'GoalTypes' = "Request-Based") AND ( 'MeasurementStatus' != "Invalid") AND ( 'TR.MeasurementStatus' = "In Process") AND ( 'UseGoalAsDefinedOnTheAppFormSel' = "Use Goal defined on the Application Form") AND ( 'ReferenceTimeGoalforRequestBasedSVTsFieldValue' =  $ NULL $ ) AND ( 'ReferenceEndGoalforRequestBasedSVTsFieldValue' =  $ NULL $ )

 

    * * * Message * * *
    Empty Reference Goal field in Application Form will make the Measurement record invalid


#5
SLM:ServiceTarget:Deleted:Request-Based
     'GoalTypes' = "Request-Based"

     NOTE:
     This filter is called from a filter guide SLM:ServiceTarget:DeleteGuide which fires with execution of the SLM:ServiceTarget:DeletedCALLGUIDE filter.  This filter fires with delete action on SLM:ServiceTarget form.
++++++++++++++++++

 

Identifying the sequence which results in update of service target to 'Invalid' status will require careful review of logs with output containing workflow results in execution of the above filters.

 

 

BR,Pratap

Share This:
How to add fields from the application forms  to the OverviewConsole?


 

NOTE: Attempting to sort a newly-added column in the Mid-tier client may fail and/or yield an ARERR 311.

____________________________________________________________________________________________

How to add fields from the application forms  to the OverviewConsole?

The Overview Console Table is populated using a plugin. The plugin returns records from forms that are defined the SHR:ARDBC_OverviewConsoleTemplate form.  The Plugin will look at the Form Guid in this form, and search that form. For example you will see the following 8 records in the SHR:ARDBC_OverviewConsoleTemplate:

 

 

FORM NAME

FORM GUID

TMS:Task

TMSTASK

HPD:Helpdesk

MAINHELPDESK

PBM:Solution Database

MAINKNOWLEDGEDATABAE

PBM:Known Error

MAINKNOWNERROR

PBM:Problem Investigation

MAIONPROBLEM

CHG:Infrastructure Change

MAINCHANGE

AST:PurchaseRequisition

ASTPUREREQUISITION

AST:CI Unavialabilty

ASTCIUNAVIALBLITY

 

If you are logged into the RUT as appadmin for example, the plugin will search the above forms to find the records that are assigned to appadmin and populate the OverviewConsole similar to how the SHR:Consolidated list worked. 

 

But how are the fields mapped from the forms to the OverviewConsole , this is done via the SHR:ARDBC fields form. Here you will see mapping for field from the backend forms to the Vendor form hence populating the form. Form example if you would like  have more information in the Overview console,  for instance the First Name*+  field from the HPD:Helpdesk form.

 

The database id for this field is  1000000019 (in HPD:Helpdesk). This field already exists in the forms:

 

SHR:ARDBC_OverviewConsoleTemplate

SHR:ARDBC_OverviewConsole

 

so we do not need to create it again ( you can map any fieldID the database id do not have to match ,as long the database length is sufficient). But for this example, the database ID are matching.

 

To create a mapping for the  HPD:Helpdesk form. Open the SHR:ARDBCFields form in new mode and use the following values:

 

FieldID: 1000000019

FormGUID: MAINHELPDESK

Vendor Field ID: 1000000019

Submitter: ARSystem

 

Open the SHR:OverviewConsole in the Admin Tool.

- open the table z2TH_ConsolidateTable1 properties

- on tab Table/Tree Property

- Look for First Name under Fields on Form and click Add

- Double click on the column First Name and add public Permissions

- Save and close the form.

 

Restart the plugin or ARServer.Open the OverviewConsole and there should now be data for the First Name from the Incidents form.

NOTE:  For custom fields that were created on application forms such as HPD:Help Desk, they should be added to the following forms with matching database IDs and at minimum Public (View) permissions:

SHR:ARDBC_OverviewConsoleTemplate

SHR:ARDBC_OverviewConsole

If they do not have any permissions, the columns will display in the Overview Console, but they will not be populated with data.

Share This:

When deleting/importing the job/transformation, here are the steps that need to be followed:

 

1. Delete Entry for the job/transformation from UDM:PermissionInfo form

2. Delete entries for the job/transformation from UDM:ExecutionInstance form

3. Delete entries for the job/transformation from NGIE:Delta

4. Export job/transformation to XML from Spoon Client

5. Delete job/transformation from the Repository using Spoon Client

6. Import job/transformation from step 4 using Spoon Client

Share This:
Share This:

If You are In a Server Group Environment,You are configuring SLM in Server Group



Below Steps you need to follow

 

Log into Admin Server (Primary)

- Open "AR System Server Group Operation Ranking" form.

- Admin Operations and Business Rule Engine should have same rank (Rank 1)

- Go to AR System Administration Console -> General -> Server Information -> Configuration -> Disable Admin operations must be unchecked.

- Check armonitor.cfg/conf file. The line for "slmbrsvc.exe" must be commented out on Secondary server and uncommented on Primary server.

- Check ar.cfg/conf file, the parameter "Business-Rules-Engine-Suspended" should be "F" on Primary and "T" on Secondary server.

- You must restart the Servers for the changes to take effect.

 

Further following steps are necessary for building Service Target in as server group environment:

 

- Login to directly to the Admin Server (NOT through load balancer)

 

- Admin Server should be taken out of the Server Group (optional)

Reason: There is no mandatory requirement to take the primary server out of the server group while building SVTs but building SVTs can have an impact on memory allocation to observer process and, in extreme conditions, that can result in crash of observer if memory reaches maximum size for process in that Operating System.

 

- Dev Cache mode should be enabled

Reason: administrative operations complete faster because the administrative thread doesn't need to copy the cache, and that less memory is used because there is only ever one copy of the cache.

 

- Post building SVT, the Admin Server can be put back in Server Group after disabling Dev Cache mode.


BR,Pratap

Share This:

The Service Level Management application can be integrated with BMC Remedy AR System and BMC applications to meet your specific business needs and process requirements. The information that follows describes how to use BMC SLM with BMC Remedy Incident Management, BMC Remedy Change Management, BMC Remedy Asset Management, and Requester Console or with any Custom Application.

 

 

Below steps need to be performed to integrate the BMC Service Level management with any Custom or OOTB Application.

 

 

Go to the the application administrator console

             then go to the Custom Configuration

              Then  go to the Service Level Management-console

SLA1.pngslm2.png

To know whether the data source is built properly or not..you need to check the SLM logs under DB directory..

 

once it is completed it will create a join form...TMS:Task_SLA

 

 

Once Data Source is built properly...then you need to slm4.png

Then you need to build the target Goal types..

 

 

 

Once this is done ,then you need to do built certain workflow  to show the SLM panel on the application form.

 

 

 

 

 

To display BMC SLM status in custom applications

1 Copy the fields SlmDVF, Details..., and z1D_ButtonSLMImage from the

SLM:Service Request form and place them on your custom form. Align as needed

and make them all visible by default.

 

 

Create a set of Active Links that will execute appropriately for your design. Each

Active Link should consist of the following 2 separate Actions:

  A Set Fields Action that sets SlmDVF as follows:

"action=setvalue"

  A Set Fields Action that sets SlmDVF as follows:

"param1=x"

where x = 0 for Gray/No SVTs Attached image

where x = 1 for Green/Within Service Target image

where x = 2 for Yellow/Service Targets Warning image

where x = 3 for Red/SVT Breached image

 

 

You can also reuse the following existing BMC SLM Active Links in your custom

application:

 

 

  SLM:ServiceRequest:SetIconStatusByCopyingSLMStatusValueGray

  SLM:ServiceRequest:SetIconStatusByCopyingSLMStatusValueGreen

  SLM:ServiceRequest:SetIconStatusByCopyingSLMStatusValueYellow

  SLM:ServiceRequest:SetIconStatusByCopyingSLMStatusValueRed

 

 

 

Change the form name to match the form on which you want these Active Links

to execute, and set the Run If condition to apply to your application.

3 Copy and appropriately name the following Active Links, and set the Primary

Form to the form on which you want them to execute:

 

 

 

  SLM:ServiceRequest:OnClickDetailsDisplayIntegrationDialog

  SLM:ServiceRequest:TrapDVFEventAndDisplayIntegrationDialog

 

 

BR,Pratap



Share This:

Using the "PERFORM-ACTION-SEND-EVENT" you can send an event to remedy opened inside a remedy View.

 

 

PERFORM-ACTION-SEND-EVENT  F600070516 "EventString"

 

 

F600070516:- Database-id is the ,ID of the Remedy View Field.