Stored Procedures

Stored procedures are programs precompiled by Alemba® that can be used to configure your system. You can view a list of them and activate the ones you want to use.

Managing Stored Procedures

Before you start

You must have System Set Up selected in the Admin tab of your General Access security role.

1. Select the Menu button, then Admin, then select System Administration.

   The System Administration window appears.

2. In the Explorer pane, expand System, then select Stored Procedures. The Stored Procedures window appears. Select the required stored procedure(s), by selecting the checkbox next to the name(s):

Within IPK, you can select from the following call management procedures:
New Call	When a new call is logged, default values are entered in the Call Number and Call Reference fields on the Call Details window.
Allocate Config Item Ref	Assigns specific configuration item prefixes to certain configuration items, depending on the Analyst who enters the item into the database.
Config Item Description	If the Analyst does not specify a configuration item description in the Description field of the Call Details window, this allows a default description
Custom Config Item, User, Organization, Location, Call, Service	Selecting the relevant option enables more fields when configuring a Call Details window in the ASM Designer.
Validate External	Runs when a call is forwarded externally to check that it has the required information stored against it.
Post Update	Runs against a call as soon as it is logged, deferred or forwarded, and the information entered into the database
Build Forums	Can be called before or after a forum is built to modify the forum, add Analysts to it, and so on
Within Request, you can select from the following request management procedures:
Request Partition	Used to override partition allocation to requests
Updating a Request	Used to modify request data, start another stored procedure, or send an email, when the request is saved
Within Task, you can select from the following task management procedures:
Task/Approval Partition	Tasks and approvals inherit the partition allocated from the request to which they are linked. This procedure is called to do more complex partition allocation
Updating a Task/Approval	Used to modify task or approval data, start another stored procedure, or send an email, when the request is saved
Task/Approval Rules	Can be used to build dependency rules
Within SLM, you can select from the following Service Level Management procedures
Calculate Escalation Recipient	Used to identify the Analysts who are to receive an alarm in their escalated calls list and an email (if configured)
Find Agreement	Overwrites the core functionality that identifies the Agreement (such as, SLA, OLA and UC) for a call, task or request. It is called after an item (call, task, or request) is inserted or updated. Select to run the procedure is run.
Calculate Escalation Target Time	Used to overwrite the escalation matrix or working hours and holidays of an agreement when the agreement is selected
Calculate Escalation Period	Used to calculate the escalation time (in minutes)
Within Self Service Portal, you can select from the following Service Level Management procedures:
Self Service Portal Log Call	Can be used to perform form validation on a call logged on the Portal
Self Service Portal Log Request	Can be used to perform form validation on a request logged on the Portal
Self Service Portal Self Administration	Enables configuration of the registration information that a User records on the Portal.
Within Messaging, you can select from the following procedures:
Incoming Email Update	Allows a call logged on a compatible email system to be closed (in addition to being logged). Also provides support for custom email messages being sent to compatible email systems
Incoming Email Update 2	Enables updating email messages being sent to compatible email systems
Reply Email	Can be used to configure an email received by an Analyst to modify its content or to forward it to another Analyst, etc
Sending Email	Changes the format of the email message sent when a call is forwarded or escalated
Sending Pager	Changes the format of the pager message sent when a call is forwarded or escalated
Format Message Template, Format Pager Template	Can be used to configure the process by which email and pager messages are formatted
Override MMA URL	Enables specification of a custom MMA URL, to be used in place of the default MMA URL generated by the system
Repeat Reminders	Can be used to override reminder events or perform additional database actions
Within IPK Rules, you can select from the following procedures:
Find Rule	Can be used to bypass the core functionality that identifies the IPK rules applying to a particular call or configuration item. It is called any time an IPK rule may be applied, such as when a call is deferred, forwarded or closed.
Match Rule	Run when a matching IPK rule is found, and can be then used to stop the rule matching, or change the rule found.
Workflow Update	Can be used to change the templates of forums associated with a particular workflow phase. Any parameters within this stored procedure may be returned to alter the behavior of the ASM Core application. It is run both before and after the phrase is added or updated to the database.
Apply Rule	Used to add further functionality to IPK rules. It is executed both before and after an IPK rule is applied
Within Availability, you can select from the following procedures:
Outage Update	Used to perform various database functions, including sending an email or storing data in an alternate source. It is called when an outage is updated, inserted, called back or closed.
Outage Link	Used to perform standard database functions, such as updating various tables and records. It is called both before and after an outage link is inserted.
Outage Downtime	Used to override the standard ASM Core procedures to calculate outage downtime. It is called whenever availability downtime is calculated, including when a configuration item’s availability performance is calculated, an outage is inserted or updated, the application checks for an outage breach, or an event is created.
Within Miscellaneous, you can select from the following procedures:
Login	Called after a failed or successful login, and can then be used to write records to any log file or table that may be required.
Log Out	Called when an Analyst logs out or is logged out by ASM Core. It can then be used to write records to any log file or table that may be required.
Federated CMDB Update	Used before or after integrating with a directory server, and can be used, for example, to update the imported Analysts, or link them to Users or organizations.