Idea ID: 2758403

Ability to segregate the management of the pricing of user options of an offering

Status : Waiting for Votes
over 1 year ago

Ideally, would like to be able to segregate the management of user option pricing to a specific set of individuals / groups to minimize the service catalog admin's administrative tasks.

  • In reference to the following document link ...  https://docs.microfocus.com/itom/SMAX:2020.02/CatalogCreation

    " Separating catalog offerings into services enables service owners to maintain their respective catalog areas, that is, to have the tools and permissions to create and update offerings related to the services they own. A service owner is the organizational persona in charge of maintaining a service, providing support for that service, and fulfilling service requests against this service. It would stand to reason that this person would be able to define and edit the service and support offerings related to the service. The service owner should be able to:

    1. Define the offerings and how they appear to end users in the Service Portal.
    2. Describe the purpose of the offerings and how to use them. The names and descriptions of the offerings are also used for search matching, so the service owner should be able to include keywords in the descriptions that match what end users search for when looking for this offering.
    3. Specify the audience for the offerings, that is, which end users would be able to see and request the offering in the Service Portal (for example, whether or not the offering is specific to a certain location).
    4. Define a task plan for fulfilling the offering. For example, a local IT help desk manager responsible for distribution and maintenance of personal computers and related equipment would be able to define the process for issuing a laptop for a new employee. The tasks may include checking the stock, ordering a new laptop if none is found in stock, installing the company’s OS image on the laptop, and so on.
    5. Define a form for the offering.

    All of these activities require the person creating and editing the offering to be very familiar with how the service operates "

    Points 1 and 2 are in line with the enhancement; however, 4 and 5 is way too much permission as these will influence how the Request is fulfilled.  If we open this up to the Offering Sponsor, there will never be any standard approach to the fulfillment process … and the support of non-standard workflows will be a nightmare.  Possibly have the ability to restrict the editing of the task plans and forms via permission settings ?

    Point 3 can be grouped with 1 and 2; but realistically, the offering sponsor would not know how to limit the audience; hence its in blue, kinda on the fence on this one.

  • The intent is to enable the customer to update their specific data content of their own catalogue item.   Pricing / drop-down list values / etc.  Items that the Catalogue Admin can tag as “Customer Updatable”

    Self empower the Customer to manage the currency of their own catalogue items without involving the Catalogue  Admin.  As the Catalogue grows, the Catalogue Admin will take longer to delivery “simple data updates”.

  • Can you provide more details on this Idea? What do you mean by segregating management? Do you mean only allowing certain roles to manage the pricing? 

  • Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team.