Knowledge quiz

Order is not important when adding field permissions in XML.

The permission to share private goals is not defined in XML but comes from RBP.

Fields can be placed in more than one permission block.

The default permission in a development goal plan is "none".

Goal Management Implementation Guide

objective-template_4_0.dtd

Career Development Planning Implementation Guide

SF-Form.dtd

EM+ should be able to see private goals.

E should be the only person who can delete goals.

EH should be able to edit goals.

EM should be able to add comments.

obj-plan-id (Development Plan ID)

obj-plan-start (default start date for goals)

obj-plan-due (default due date for goals)

obj-plan-name (Development Plan name)

The Admin must select permissions when adding the field.

The field is added to all existing field-permission blocks. 

The field is added to the plan layout.

A new permission block is created for the field.

They are sent when the manager edits a direct report's goal.

They are batch-sent daily instead of being sent immediately.

They are only sent when public goals are edited.

They can be turned off for Development Plans but left on for other Goal Plans.

Remove fields.

Add new table columns to table fields.

Add new values to enum fields.

Re-order fields.

Change permissions for fields.

The Goal Creation email goes only to the employee's manager.

Employees do not receive an email for self-created goals.

Mike's permission role does not have goal notifications enabled.

In XML, add a write permission for the E role at the end of the permissions and remove the field from all other write permission blocks.

Make the field an employee-only editable field in Admin Center.

In XML, remove write permissions for all roles except the E role.

In XML, verify the field is included in the write permission block for the EM role.

competencies

state

tasks

milestones