2 Replies Latest reply on Jul 5, 2016 12:47 PM by pappast

    Request Offering Design

    pappast Apprentice

      Given the following example scenario...

      • We have two existing Request Offerings defined and published:
          1. "Request New Computer"
          2. "Request New Mobile Device"
      • We now need to define a new Request Offering: 3. "Request New Employee Setup".
      • In addition to its own activities and tasks, Request Offering (3) must collect the necessary data and invoke the workflows associated with (1) & (2) above.

      What is the best way to architect these three Request Offerings to facilitate ongoing maintenance?