Get CIS-SPM Dumps : Verified Certified Implementation Specialist - Strategic Portfolio Management

According to the Portfolio Planning document, the first step in the process when configuring Portfolio Planning to work with ServiceNow® Project Portfolio Management is to generate default mapping configurations. This step creates the default mappings between the Portfolio Planning fields and the ServiceNow® Project Portfolio Management fields. The other options are not correct, as they are not the first step in the process. Creating an alignment integration is the second step, creating custom mapping configurations is the third step, and creating personalized portfolio plans is the fourth step.

Resource capacity is the total number of hours that a resource or a group of resources is available for work in a given time period. According to the Product Documentation for ServiceNow, resource capacity is derived from the user or group schedule, which defines the working hours and days for each resource. The group capacity is rolled up from the schedules of all the members. Note: Capacity is not derived from FTE, but from schedules. Both FTE and schedules must be in synchronization with each other. FTE is a measure of how much work a resource can perform in a standard work week, and it is used to calculate the resource demand and allocation.

According to the ServiceNow documentation1, the Business Unit field on a Project or Demand form is a reference field that displays values from the cmn_department table. A reference field stores a link to a record on another table, rather than storing the data directly in the field2.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/reference/r_ProjectTable.html 2: https://docs.servicenow.com/bundle/vancouver-platform-administration/page/administer/form-administration/concept/c_ReferenceFields.html

According to the Category Configuration document, the default table that stores the idea categories that a user can select from when submitting an idea is im_category. This table contains the predefined categories for ideas, such as Business Process, Customer Service, or IT Service. The other options are not correct, as they are not the tables that store the idea categories. The dmn_demand table stores the demand records that are created from the approved ideas. The im_module table stores the idea modules that are used to group ideas by different criteria. The im_idea_core table stores the core fields of the idea records.

According to the Stakeholder Registry document, the combination of the user and the assigned portfolio must be unique when adding a user to the stakeholder registry. The stakeholder registry is a table that stores information about the stakeholders of a portfolio. The other options are not correct, as they are not registries that require a unique combination of user and portfolio. The application registry is a table that stores information about the applications in the system. The event registry is a table that stores information about the events that trigger notifications. The UX page registry is a table that stores information about the UX pages that are available for portfolios.