Archive for May, 2010

Abydos extensions for Remedy SRM and ITSM 7.

May 22nd, 2010

Information which may interest you…

Webinar: Simplified data capture, graphical decision trees, advanced process logic and more extensions for Remedy SRM and ITSM 7.

Thursday 27th May 12:00-12:45pm ET. Register Now

Abydos are pleased to annouce that we will be holding a webinar on how to extend your SRM and ITSM 7 applications without customisations, templates or advanced forms on Thursday 27th May at 12:00 noon Eastern Time.

If you have ever needed to make changes to your SRM or ITSM 7 applications you will be aware of the difficulty of customising them to meet your needs without changing the out-of-the-box applications.

Abydos Designer provides an alternative to customisations, advanced interface forms and templates by allowing administrators to define their business rules using a graphical process design environment without the need for a Remedy server.

The value-add that Abydos Designer provides that you wont find in SRM or ITSM 7 includes:

  • End-end graphical process design – Abydos Designer allows you to create proccesses for your application using a graphical drag-and-drop environment without the need for a Remedy server.
  • Process Wizard for Remedy users – Use the process Wizard to guide Remedy users through the process steps, reducing the need for application training.
  • Process Tracker for Remedy users – Allows Remedy users to view graphically exactly where they are in the current process.
  • Release Management – Automated generation of version-stamped SRM/ITSM processes including simple import/export between servers and rollback capability without the need for any Remedy customisation.
  • Import of processes from other BPM tools – For customers using other BPM tools such as Lombardi or Savvion, simply import the process definitions into Abydos Designer to use with your Remedy application.
  • Generation of application tasks from SRM – Allows SRM administrators to control the generation of related tasks for Incident, Problem, Change or Work Orders from a Service Request without the need for any customisation.
  • Process Reporting – Provides Flashboard-based view for managers on the status of all processes in play with indication of group assignment levels and process bottlenecks.

    Webinar Information

    To join us for the live webinar on Thursday 27th May at 12:00 Noon Eastern, click on this link to register: Register Now

    Contact Information

    For further information, please contact Abydos at

    USA Toll Free: 866 635 4358
    Europe: +44-1582-400127,

  • Abydos is a limited company, registered in the UK, Company Registration number: 4299654.
    Abydos respects your privacy. If you would prefer not to receive Abydos newsletters or webinar information, please click here

    How to write workflow to auto generate Message Numbers

    May 21st, 2010

    As posted on BMCDN by Adam


    This is quick guide on how to write workflow which auto generates message numbers for the message action in Active Links and Filters.

    The advantage is that if a message pops up, it very easy to track it back to the workflow item that triggered it. Also makes writing documentation easier

    The Process:

    (I keep all this workflow in the development environment, and don’t move it to live)

    1. Create view forms of database tables

    • actlink
    • actlink_message
    • filter
    • filter_message

    2. Create a new form that will store

    • Message Text
    • Message Number
    • Active Link ID
    • Filter ID
    • Active Link Name
    • Filter Name
    • New Message Number

    3. Create Escalations on actlink_message and filter_message to populate new form (I run every 1 hour)

    4. Workfow to get the active link name from activelink and from filter tables

    5. Workflow to auto generate a new message number

    (I used for active links – Request ID + 10,000

    For filters – Request ID + 20,000)

    6. Push fields back to filter_message and actlink_message if the old message number was 10,000, updating the message number with the new value)

    7. When I create new workflow that has a message, I leave the number at 10,000 (default value) and let the escalation auto assign a number.

    (developed on ARS 7.1)


    All credits to Adam Buteux

    %d bloggers like this: