Configuring Workflow Objects

arrow icon   Before you make changes to workflow objects:

  1. Open WorkFlow Builder.

  2. On the File Menu select Help/About Workflow Builder.

  3. Ensure that you are using a version of Workflow Builder that is compatible with the version of Oracle Workflow installed on your server.

  4. Set the Access Level to 100.

    See: Workflow Objects and Item Types

  5. Deselect the Allow Modifications of Customized Objects check box.

  6. Select and display the Human Resources Self-Service Applications item type. Save it to a local file for backup.

    Note: We recommend that you maintain source control for the .wft files so that you can track changes to the original objects, move definitions to other database instances using the Workflow Loader, and revert to previous versions if necessary.

arrow icon   To modify delivered workflow objects:

  1. Open WorkFlow Builder.

  2. Select and display the Human Resources Self-Service Applications item type or the HR Self-Service Benefits item type.

  3. If required, change any configurable item attributes.

    Note: Some item attributes can be customized and other objects, such as processes, notifications, messages, and lookup types, are "read-only". You can change the "customizable" attributes directly in the workflow process. In SSHR item types, the only directly configurable objects are item-level attributes (including enterprise e-mail addresses) and dynamic approval levels.

    See: Defining Your Enterprise's Email Addresses

    See: Configuring Approvals with the Workflow Builder

  4. If required, create copies of the read-only objects.

    See: Copying Workflow Processes

  5. Save your work.

Copying Workflow Processes

arrow icon   To copy a workflow process:

  1. Copy the object and rename it.

    For example, you can copy the FYI Notification Process (FYI_NOTIFICATION_PRC) for use with Self-Service Benefits Enrollments. Make sure the new process has the same item type as the original process.

    Note: Prefix your copies with a consistent code, for example, a consistent numeral or a four-letter acronym for the company.

  2. You may have to copy multiple levels of the process, for example, to make changes to the Basic Details subprocess within the Personal Information process, you would have to copy the overall process (Personal Information) and the subprocesses (Process Basic Details and Process Personal Information).

  3. If you have copied (and modified) a subprocess, you will have to insert your copy of the subprocess into your copy of the higher level process in place of the original subprocess.

  4. Save your work.

  5. Create at least one function to point to the new process.

    See: Defining Functions for SSHR

arrow icon   After applying a patch:

During the application of an SSHR patch, the workflow loader utility ensures that your server has the latest versions of any delivered workflow objects. This upload overwrites any "read-only" objects but preserves any customizations that have been made to "customizable" objects.

If a patch includes new features or bug fixes for delivered objects that you have copied, you need to apply the same changes to your copied objects. Refer to the patch readme file for instructions. You may have to compare your copied object with the original read-only object.