You are on page 1of 16

Attachments in Appraisals Using the Personalization Function (R11i and R12)

An Oracle White Paper June 2008

Table of Contents Attachments in Appraisals Using the Personalization Function.............. 1


INTRODUCTION ..................................................................................................... 3 Solution Overview ..................................................................................................... 3 Add Attachments for Competencies ........................................................................... 3 Add Attachments to Objectives. ............................................................................... 11 Add Attachments to Overall Assessment ................................................................. 12

INTRODUCTION
This document describes the steps to enable attachments in the application. You can enable attachments in appraisals using the Oracle Applications Framework (OAF) Personalization function. The scope of the document is to enable attachments in Appraisals using personalization: Add Attachments to Competencies.

Add Attachments to Objectives. Add Attachments to Overall Assessment.

Solution Overview
NOTE: To retain the attachments ensure that the attachments are created on the Update page and NOT on the Review page. Add Attachments to Competencies You can enable attachments as a column to the existing Competency table. The steps are as follows: 1. On the Overview Page click the "Personalize Page" link. 2. Navigate to Complete view, Expand All and then click focus of "Table: Competencies" 3. Click the Create icon on the personalization page in Table: Competencies Row in CompetenciesRN.

Here you can create an attachment column to the existing Competency table.

In this page, select the following: Level of personalization Site level Function Level Organization Level Select site level. Select Item Style: Attachment Image ID - A unique ID for the attachment region item. (Like CompAttach) View Instance - The name of the view instance for the entity you are enabling an attachmen. For Competency its "CompetenceElementsVO". Rendered - Set to True. Enable Document Catalog - Set to `True to enable adding attachments from the document catalog or set to `False to disable access to the document catalog. The default value is True.

Render Search Region - Set to `True to render the Search region for the Attachments page or region. The Search region allows you to query for a specific set of attachments. Prompt: A label for the attachment column. If this property is null, the prompt defaults to "Attachments". Auto Save: By default, changes made to the Attachments table or page are saved (committed) only when a user selects the Apply button on the base page from which Attachments is launched. If you want changes to the Attachments table or page to commit automatically, without requiring a user to select Apply in the base page, you can turn on "auto-commit" by setting the Automatic Save property to `True for attachment Image item. With "auto-commit" turned on, each action ("Add", "Update", "Detach") performed by the user in the Attachments table or page is automatically committed.

4. Click Apply after Filling up the required Fields. An asterisk marks mandatory fields. 5. Move to the Competence table region by clicking on the focus icon. Now a new item of type Attachment Image is created. Expand the item. 6. Click the Create Icon on entityMappings.

7. On this page you can create an entity to uniquely identify an attachment.

On the Create Item page, select the following: Level of personalization: Select site. ID: Enter a unique ID for the entity map e.g. entityCompAttach. Delete Allowed (true/false). Insert Allowed (true/false). Update Allowed (true/false). Entity: Enter a unique arbitrary value for Entity e.g. entityCompAttach

NOTE: If you want to make the Attachments table or page read-only so that it does not display the Update and Detach columns, set the Insert Allowed, Update Allowed, and Delete Allowed properties to False. You can however set any combination of these properties to False to control the level of change you want users to have on the Attachments table or page. An entity is created. After you click apply the previous page you will observe that an entity will have two more items Category Map and Primary Key. Both these items have to be created for an entity. First create a primary key

8. Click Create item for primary key. 9. Fill the mandatory fields ID: Unique id for the primary key View Attribute: Enter a view attribute name for the primary key, Many regions can share an entity; in fact, if you want the same attachment(s) to be viewable from different regions, those regions must share the same entity. In addition, the attachment region items of those different regions must have the same view attribute name and reference the same view instance. For Competencies use the CompetenceElementId 10. Click Apply. 11. Create a category map to specify the category of documents that can be associated with the attachment. Click create icon for CategoryMap item.

Document categories provide security by restricting the documents that can be viewed or added as an attachment. Fill up the following fields in the category creation page ID: Specify a unique id for the category map and enter a Category for your entity. Category: This value must be a predefined Name (internal name, rather than display name). Use MISC. OA Framework creates a default category map for the entity and sets the category to MISC. NOTE: Once you define a categoryMap and if the showAll property on the entityMap is set to false, only then the attachments assigned with the same category as specified in your categoryMap(s) can be queried or added from the Attachments page. If the property is set to true, it disregards the category maps, as all categories are available. You have successfully added attachments to competency table. Click Return to Application.

10

Add Attachments to Objectives. You enable attachments as a column to the existing Objective table. The procedure for creating attachments for Objectives is same as Competency mentioned above. Click the Create icon on the personalization page in the Table: Objectives Row in ObjectivesRN.

Create an Attachment Image Item, followed by an entityMap, Primary key and Category similarly as previously done for competencies. The data to be provided for objectives is different and is given below. 1. View Instance (Attachment Image Object): PerObjPerfRatingsVO 2. View Attribute (in Primary Key): ObjectiveId

11

Add Attachments to Overall Assessment Following are the steps to create an attachment table for Overall Assessment. Create an Item in the OverallRatingRN.

1. Select the Attachment Table item style 2. Enter the mandatory fields: ID: Any unique name View Instance: AppraisalVO Text - A display name for the Attachments table. Icon URI - A gif file containing the image to display next to the Attachments table display name. Rendered - Set to `True. Enable Document Catalog - Set to `True to enable adding attachments from the document catalog or False to disable access to the document catalog. The default value is `True. Render Search Region - Set to `True to render the Search region for the Attachments page or region. The Search region allows you to query for a specific set of attachments.

12

3. From this step proceed as done previously for enabling attachments for competencies and objectives. 4. Create an Entity Map, followed by the primary key and the Category Map. The View Attribute field to be filled for the primary key will be AppraisalId. Return to application when finished.

The Final Competency region after creating attachments

13

The Final Objective region after creating attachments

14

The Final Overall region after creating attachments

15

Attachments in Appraisals Using the Personalization Function (R11i and R12) June 2008 Author: Arumoy Mukherjee Contributing Authors: Bina Kulkarni Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 www.oracle.com

Copyright 2007, Oracle. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle, JD Edwards, and PeopleSoft, are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

16