Aramea RAQL is a new innovative product designed for the BMC Remedy AR System application.
RAQL is the Remedy Advanced Query Language, a language modelled closely on
the familiar syntax of SQL.
RAQL statements of SELECT, INSERT, UPDATE and DELETE are parsed and executed
through the Remedy API and so can access and affect only the data that the
Remedy user login is permitted to.
Aramea RAQL statements can be used to replace the use of SQL which greatly
benefits multi-tenancy environments where use of SQL statements is
particularly dangerous as the Remedy database user has access to all the
data on the Remedy server.
The Aramea RAQL server software provides both a front-end access to execute
statements through the Mid-tier and Remedy User Tool and also a Filter API
Plugin for filter workflow.
Aramea RAQL can also benefit companies where access to the database to run
SQL queries is restricted, particularly for professional services teams.
The Aramea RAQL client software can be used to run statements on any Remedy
Server without the need to install anything on the server.
Ad-hoc join statements can be defined without the need to build join forms.
Aramea RAQL can also be used to facilitate a much more streamlined
implementation of any Remedy integration projects.
The Aramea RAQL Java library allows you to interact with the data on the
Remedy server through just a couple of lines of code, thereby reducing time
and cost when developing integration software.
The power and flexibility of Aramea RAQL allows for many uses, whether you
need to simply replace your SQL statements to protect data or you have an
integration project.
Here are some examples of statements to highlight some of what can be
achieved using RAQL:
Creation of a new Task within a Change Request
This example shows that by using RAQL you can create a task for a Change
Request with a single statement by using information from the Task Template
and the Change itself joined to provide the data for the INSERT statement
INSERT INTO TMS:Task
(TemplateID, TaskName, Summary, "Location Company", RootRequestMode,
RootRequestName,
RootRequestInstanceID)
VALUES
(SELECT T.InstanceId, T.TaskName, T.Summary, 'Calbro Services', 'Real',
C."Infrastructure Change ID",
C.InstanceId
FROM TMS:TaskTemplate T, "CHG:Infrastructure Change" C
WHERE T.Summary = 'Standard Update of CMDB'
AND C."Infrastructure Change ID" = 'CRQ000000000001')
As this is not SQL but RAQL the relevant workflow will be triggered for
Submit filters when the statement is executed.
Extracting all attachments from Incident Work Logs
This example shows the use of a special RAQL function used to extract all
the attachments, again in one simple statement
SELECT TO_FILE("z2AF Work Log", 'C:\temp\attachments') FROM HPD:WorkLog
More information
Web: www.aramea.co
Email: i...@aramea.co
Sales: sa...@aramea.co
Chris Jones, Director
Email: chris.jo...@aramea.co
Aramea Small logo
Aramea Ltd, 3rd Floor, 207 Regent Street, London W1B 3HH, United Kingdom
www.aramea.co <http://www.aramea.co/>
---
This email is free from viruses and malware because avast! Antivirus protection
is active.
http://www.avast.com
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
<<image001.jpg>>
