IT has two request offerings that invoke
two different processes with different targeted delivery time: Request Standard
Software, Request Non-Standard Software.
An end user shouldn't have to know the
difference of the back-end process for the two request offerings, they just
need a Service Catalog item that allows them to request a
software. User selects Request Software in Service Catalog, system displays
a list of standard software for selection.
- If a standard software is selected, system
invokes the Request Standard Software workflow and starts the clock against the
targeted delivery time for this request offering.
- If Other is selected, system will request for
the specific software name, invokes the Request Non-Standard Software
workflow, and starts the clock against the targeted delivery time for this
Is this something HEAT can accommodate, with
If the user wants both
a standard and a non-standard software, can the system do one request offering
to accommodate both, so that the end-user doesn't have to open two tickets?