Create demand to rationalize software applications

  • リリースバージョン: Australia
  • 更新日 2026年03月12日
  • 所要時間:5分
  • Create demands to rationalize SaaS and SSO applications by discontinuing software subscriptions, reducing software usage, and migrating users to approved software.

    始める前に

    Role required: sam_admin or sam_user
    注:
    The sam_admin and sam_user roles must have the it_demand_user role to create demand.

    The PPM Standard (com.snc.financial_planning_pmo) plugin must be installed to create demands.

    The Software Asset Management application includes the following demand actions that are ready for you to use:
    • Discontinue after expiration
    • Migrate to approved product
    • Discontinue immediately
    • Reclaim licenses
    • No action

    このタスクについて

    Use the Overlapping usage view to drive SaaS and SSO application rationalization by viewing the feature level usage of each application. For more information, see Overlapping usage view.

    手順

    1. Navigate to Software Asset Workspace > Overlapping usage.
    2. Select the Application feature usage tab.
    3. Select the application in a category for which you want to create a demand.
    4. Select Create demand.
      The Create demand option is available only when you select an application that you want to create a demand for.
    5. On the form, fill in the fields.
      表 : 1. Software Asset Demand
      Field Description
      Name Name of the demand.
      Number Unique auto-generated identification number for the demand.
      Submission status Stage of the demand record.
      • Draft
      • Submitted
      • Screening
      • Qualified
      • Approved
      Start date Start date for the demand.

      The field name is replaced by Planned start date when the demand type is converted to a Project.

      注:

      When you change the planned start date of a demand or project, the associated cost and resource plans also change.

      Due date Requested completion date for the demand.

      The field name is replaced by Planned end date when the demand type is converted to a Project.

      Category Software category of the demand.
      • Strategic
      • Operational
      Type Type of demand.
      • Enhancement
      • Project
      • Change
      • Defect
      The Category field selection determines the selections available in this field.
      Assessment required Option for enabling the assessments for the demand.

      By default, the field is selected. When clear, the assessment questionnaire isn’t triggered for the demand.

      When this field is clear, and you reset the demand to Draft, the value for the Assessment Required field is retained as clear.

    6. オプション: Select the Demand Requirements tab to view the details of the already-created requirements.
      You can also create a demand requirement. For more information, see Create a demand requirement.
    7. Select Save.

    タスクの結果

    The demand is created with the Submission status field set to Submitted.

    次のタスク

    Use the ServiceNow® Demand Management application to approve and complete the demand. For more information, see Demand Management.

    You can create a project for the demand by selecting the Create Project related link. A project enables you to track the status, percent complete, and duration of the work required to accomplish the demand. You can also create project tasks to define the work items that are required to complete the project. For more information, see Project Management.

    To view all Software Asset Management demands, navigate to Software Asset > Software Asset Demand > Demands.

    To view all Software Asset Management demand requirements, navigate to Software Asset > Software Asset Demand > Demand Requirements.