The customer is able to enable and configure the connection to the MAtrix42 infrastructure by entering security credentials (most likely a connection string) into the FireScope tenant. The result would be an SDDM UI!

TODO:

• Consider if multiple Matrix42 systems needs to be addressable

Description:

LIS Online Update is using new web-server

• Previous URI: https://support.update4u.de/LIS/LISUpdateService.svc

• New URI: https://lis.matrix42.com/LIS/LISUpdateService.svc

Also changing URL for License Library!

Acceptance:

1. LIS Update is using new webserver

2. LIS Library access is using new webserver

API extension to create tickets like it is currently in place for incidents (create.incident).

Minimum requirements need to be covered:

• User

• Subject

• Description

• Category (optional if not provided Ticket Default)

• Impact (optional if not provided Category default)

• Urgency (optional if not provided Category default)

• Role (optional if not provided Ticket Default)

• SLA (optional if not provided Ticket Default)

• Entry By (optional)

• Reported Asset (optional)

• Reported Service (optional)

• Classification (optional, if not provided -> Ticket)

Ideally, the extension is marked public.

Acceptance criteria

• API extension available and documented

• Tickets with direct classification to 'Incident' or 'Service Request' can be created

• If attribute values are not provided defaults will be used

• Extension supports

  • User

  • Subject

  • Description

  • Category (optional if not provided Ticket Default)

  • Impact (optional if not provided Category default)

  • Urgency (optional if not provided Category default)

  • Role (optional if not provided Ticket Default)

  • SLA (optional if not provided Ticket Default)

  • Entry By (optional)

  • Reported Asset (optional)

  • Reported Service (optional)

  • Classification (optional, if not provided -> Ticket)

A more intuitive dependency map is available for both assets and services and is based on the KeyLines map plugin.

Matrix42 ESM is able to consume ServiceBus events using the ServiceBus adapter (Nuget). Assets and Services will be created/updated based on ServiceBus messages.

Acceptance criteria

• Assets are created using the ServiceBus

• Assets are updated using the ServiceBus

• Services are created using the ServiceBus

• Services are updated using the ServiceBus

• Ticket (classified as Incident) is created using the ServiceBus

• Ticket (classified as Incident) is updated using the ServiceBus

• Dependencies are created using the ServiceBus

• Dependencies are updated using the ServiceBus

Mock-up

Doesn't apply