Setting Up Business Projects

This chapter provides overviews of business projects, business project workflow, and business project process definition and discusses how to:

• Define invalid actions.

• Define tasks.

• Define phases.

• Define business projects.

• Clone and delete phases and business projects.

See Also

Using Business Projects

Understanding Business Projects

This section lists common elements and discusses:

• Business project usage.

• Business project architecture.

• Business project workflow.

• Tasks in business projects.

• Invalid actions.

• Time and cost tracking.

Common Elements Used in this Chapter

Business Project Usage

Business projects are structured, workflow-enabled task lists. You use business projects to coordinate and track the work involved in performing tasks.

Organizational Processes

You can create business projects to codify and manage an organization's internal business processes. For example, a help desk might create business projects for commonly performed processes, such as upgrading a user's computer. Service orders, support cases, and helpdesk cases all support this use of business projects, enabling you to:

• Codify the best practices of an organization into a reusable template.

• Enforce the proper sequence of tasks.

• Automate work-related notifications.

• Coordinate any combination of manual processes and automated processes.

Business projects can be instantiated manually (as a related object, for example), or automatically through the Active Analytics Framework (AAF) as a result of the evaluation of business rules. Only one business project can exist for each parent object. For example, you can have only one business project for each case.

Automated Processes

PeopleSoft delivers business projects that manage certain predefined application processes. For example, in PeopleSoft Order Capture, the delivered CORE_ORDER_BP business project manages the order fulfillment process. This business project coordinates automated tasks such as publishing the data to an order fulfillment system and creating an installed product record. Using a business project to manage these tasks simplifies the management of conditional logic.

Refer to the PeopleBook for a specific application to learn about application processes that you can implement using business projects.

See Also

Configuring Business Project Actions

Working with Order Capture Business Projects

Business Project Architecture

Tasks are the basic unit of work in a business project. Task definitions describe the work to be performed and the amount of time that the task normally takes. Phases are groups of tasks. Phases can also incorporate sub-business projects, which are business projects that are nested within other business projects.

Task Sequencing

When you set up a phase, you define the sequence of tasks in the phase.

Tasks within a single phase can be performed either in parallel or in sequence. For example, when you set up an employee in a human resources system, the first task might be to enter employee personal information into the system. After this task is complete, you might enter other information in parallel, for example, tax withholding elections and benefits elections.

A task begins when all preceding tasks or sub-business projects in a phase are complete. For example, consider a phase that starts with three parallel tasks. These tasks are followed by two other parallel tasks that cannot start until the first three tasks are complete. The first three tasks begin when the phase begins, and the next two tasks begin when the first three tasks are complete.

When you set up a phase, you indicate required tasks and sub-business projects. The sequencing of tasks and sub-business projects, however, is not affected by the phase setup. So in the preceding example, the fourth and fifth tasks do not start until all three of the previous tasks are complete, even if only one of the three preceding tasks is required.

Phase Sequencing and Phase Transitions

Phases are always performed sequentially. Consequently, tasks that are performed in parallel must all belong to the same phase. For each phase in a business project, you define the possible target phases and the conditions under which each target is appropriate. These conditions are called transition rules.

Any phase in a business project can have a transition to any other phase in the business project. This architecture enables you to loop through a phase multiple times if necessary. A business project is complete when you reach the system-defined End the Business Project phase. (You cannot modify this phase except to change the descriptive text.)

Transitions can be automatic or manual. A phase that has multiple possible targets can use a combination of automatic and manual transition rules.

Automatic transition criteria are based on the status and outcome of required tasks and sub-business projects in the start phase. If the start phase definition includes elements that are not marked as required elements, the system does not use those elements when evaluating transition criteria.

The outcome of a task or sub-business project can be Canceled, Complete - Success, or Complete - Failed. A sub-business project's outcome can be set manually or automatically, depending on how the sub-business project is defined. If the outcome is set automatically, the sub-business project is considered successful when it is complete. If the outcome is set manually, the user specifies whether the sub-business project succeeded or failed.

The system evaluates transition rules at two points:

• When a task or sub-business project is completed.

  Because transition rules are based on the success or failure of tasks within phases, the system evaluates transition rules at the completion of a task.

• When a phase exceeds its maximum time.

  You can specify that an automatic transition occurs when tasks are not completed on time. If you set up this type of transition, then when the phase starts, the system schedules a process to run when the phase exceeds its maximum time. If the phase is still in progress when the process runs, the transition occurs.

Transition Rule Validation

Before you can use a business project, the system must validate its phase transition rules. The following conditions cause the validation process to fail:

• No default target phase exists.

  Every start phase with a target phase must have a default target phase. The default target phase establishes a default path through the business project tree so that the system can calculate standard and maximum times for the business project. In addition, in an automatic transition, the system starts the default target phase when all tasks are complete but none of the transition criteria are satisfied.

• Multiple targets have the same automatic transition criteria.

  Automatic transition criteria enable the system to use one of multiple target phases. If multiple targets have the same automatic transition criteria, the system cannot perform the transition.

When the validation process is successful, the system marks the business project as valid and makes it available.

If you change the business project definition, you must validate it again and save it.

Sub-Business Projects

Sub-business projects are business projects that are incorporated into phases of other business projects. The sub-business project functions as a task in this context, even though it may be a complex and multiphased task. The standard task sequencing rules apply regardless of whether a phase has tasks, sub-business projects, or a combination of the two.

You define sub-business projects as you do main business projects. They consist of phases and tasks with specific sequencing and transition rules. Sub-business projects differ from main business projects in two ways:

• Sub-business projects include a field that determines whether the outcome is set by default or explicitly.

  Main business projects, which have a status but not an outcome, do not have this field.

• For sub-business projects, you do not need to identify the parent object that uses the sub-business project.

  The parent object for a sub-business project is always the business project to which it belongs.

A business project type indicator prevents main business projects from being used as sub-business projects. It also prevents sub-business projects from being used as main business projects. At runtime, when you prompt for a list of business projects to invoke, only main business projects appear. During the design stage, when you prompt for a list of business projects to include in a phase, only sub-business projects appear.

Like tasks and phases, sub-business projects are reusable. For example, a sub-business project for verifying a customer's credit might be embedded within several main business projects. You can even nest sub-business projects within sub-business projects.

Dynamic Sub-Business Projects

Using the Nested_Business_Project_Start PeopleCode function, you can dynamically add sub-business projects at runtime. For example, if you use a business project for order fulfillment and sub-business projects for each item ordered, you cannot know which sub-business projects will be needed for a specific order.

PeopleSoft Order Capture components incorporate the PeopleCode that is necessary for this processing. To take advantage of it, use the CORE_ORDER_BP business project or, in the communications industry solution, the TELCO_NEW_ORDER business project as the main fulfillment business project. Then make sure that each product definition references the sub-business project that is used when a customer orders the product.

Business Project Modifications

You cannot modify tasks, phases, and sub-business projects that belong to a currently instantiated business project. After all instances of the main business project are marked complete, these objects become editable again.

Business projects are effective-dated. You cannot modify the effective-dated row of data if an instance of the business project for the effective date is currently in progress. Instead, create a new effective-dated row of data for the changes.

Changes to a business project definition do not affect existing instantiations of the business project.

See Also

Using Business Projects

Definition of Processes That Dynamically Instantiate Sub-Business Projects

Business Project Workflow

Business project workflow automates the process of sending notifications and running processes. When you set up business project workflow, you specify three things:

• The event that triggers the workflow action.

  These events are predefined in the system, such as when a phase or business project begins, ends, or exceeds a preset time.

• The workflow action that the system performs.

  Workflow actions can schedule processes (for example, Application Engine processes) or send notifications.

• (Optional) A correspondence management email template that provides notification text.

  Only correspondence template packages with a usage of Business Project will be available for selection.

  Correspondence management email templates are only required for workflow actions that send email notifications.

When business project workflow sends a notification, the system logs the notification as an interaction, which you can view in the 360-degree view or other interaction lists. You can set up workflow actions at the task level as well.

See Also

Setting Up PeopleSoft CRM Workflow

Setting Up Correspondence Templates

Working with Interactions

Tasks in Business Projects

A task is the smallest unit of work in a business project. It can be performed automatically or manually.

Automatic Tasks

Certain tasks can be performed without human intervention. For example, the system can update inventory balances after an order is shipped.

To automate these tasks, set up workflow to run an Application Engine process that performs the task. When you do this, you need to pass task information to the Application Engine program, and you need to make sure the program updates the task status when it is complete.

Manual Tasks

Certain tasks are assigned to and performed by people. For example, a manual task might be a physical task, such as changing the toner in a printer.

To facilitate manual tasks, set up workflow that sends the assignee an email that describes the task and includes a link to the page where the person can update the system when the task is complete. You can set up additional workflow to notify the overall business project owner whenever a task status is updated.

Default values determine how the system initially assigns a task when the business project begins. The business project owner can change default assignment information before or after the task begins.

To set up workflow that sends notifications for newly assigned tasks, associate the notification with the Beginning of Task event or the Reassignment of Task event (or both). If you send a notification at the beginning of a task, the current assignee receives the notification. Consequently, for the first task of a business project (which starts as soon as the business project starts), the default assignee always receives a notification. For subsequent tasks, the default assignee receives the notification only if you do not change the assignee before the task starts.

The system sends reassignment notifications only for tasks that are in progress, so it does not send a notification if you change the assignee before the task starts.

Note. Task assignment does not trigger notifications unless you set up notification rules based on task assignment.

Invalid Actions

If a business project is in process, certain user actions may not be appropriate. For example, you may want to prevent users from canceling orders once the shipping phase of an order fulfillment business project begins.

To prevent the action from occurring, the system calls the BusProjectInvalidAction PeopleCode function when the action is attempted. The function determines if the action is invalid for the current phase of the business project. If the action is invalid, the function returns a value of True and sets any variables in the message catalog entry that is associated with the invalid action. The application that called the function can then take appropriate action.

The only component that is delivered with a call to the BusProjectInvalidAction function is the Order Tracking component. When an invalid action occurs in this component, the application prevents the user from canceling the order and displays an error message using text from the message catalog.

See Also

Working with Order Capture Business Projects

Time and Cost Tracking

As you define a task, you can specify the standard amount of time for the task and a maximum amount of time for the task.

You can roll up that information to calculate the standard and maximum duration of phases and business projects, or you can specify phase durations and business project durations that are separate from the calculated durations. The calculated duration of a phase includes the time required for tasks and for sub-business projects. The calculated duration of a business project is based on the assumption that every transition leads to the default target.

You can set up workflow notifications based on business project, phase, and task times—both calculated times and manually entered times. These timeout notifications enable an organization to monitor delays in the completion of a business project.

As you define tasks, phases, and business projects, you can also specify costs associated with each. The PeopleSoft system does not roll up costs from tasks to phases or from phases to business projects. Likewise, the system does not use the cost information in any processing. The cost information that you specify is for informational purposes only.

Understanding Business Project Workflow

This section discusses:

• Events that can trigger workflow actions.

• Workflow actions and email templates for business project notifications.

• Delivered workflow elements for case business projects.

Events That Can Trigger Workflow Actions

Business project events are conditions related to tasks, phases, and business projects. To set up business project workflow, you associate a workflow action with one of the predefined events.

You define workflow for task-related events at either the task level or the business project level. To set up workflow for every task in a business project without setting up the event for each individual task, use the business-project-level event.

Task, Phase, and Business-Project Initiation Events

Task, phase, and business project initiation events include the following:

• Business project begins

• Phase begins

  The first phase in a business project begins immediately when the business project is invoked. Subsequent phases begin after an automatic or manual transition.

• Task begins

  Initiation of a business project starts at least one task in the first phase of the business project. The sequence of tasks within the phase determines when the other tasks begin. This is available only at the task level.

• Task is reassigned

  The assignee of a task in progress changes from a blank value to a named value. This is available only at the task level.

Task, Phase, and Business Project Completion Events

Task, phase, and business-project completion events include the following:

• Business project is complete.

• Phase is complete.

  Phases are complete when you manually initiate a transition out of the phase or when the criteria for an automatic transition are met. This event does not require all tasks to be complete.

• Phase is complete—all tasks complete.

  This event does not distinguish between tasks that succeeded and tasks that failed.

• Phase is complete—all tasks complete and successful.

• Phase is complete—all tasks complete, any task fails.

• Phase transition occurs.

• Phase transition occurs—non-default.

• Task is complete.

  This event does not distinguish between tasks that succeeded and tasks that failed. This is available only at the task level.

• Task fails.

  This is available only at the task level.

• Task is successful.

  This is available only at the task level.

Timeout Events

Timeout events include the following:

• Business project exceeds maximum time.

• Business project exceeds standard time.

• Business project exceeds maximum calculated time.

• Business project exceeds standard calculated time.

• Phase exceeds maximum time.

• Phase exceeds standard time.

• Phase exceeds maximum calculated time.

• Phase exceeds standard calculated time.

• Task exceeds maximum time.

• Task exceeds standard time.

There are two ways to define standard and maximum times for phases and business projects. You can enter a time manually, or you can have the system calculate it. When you define timeout workflow for phases and business projects, you must know whether to base the workflow on the manual or calculated time.

Workflow Actions and Correspondence Templates for Business Project Notifications

Workflow actions are PeopleSoft CRM workflow objects that trigger processes (for example, Application Engine processes) and notifications.

When you set up a workflow action for business project notifications, you need to select a PeopleTools business process, activity, and event. (PeopleTools events are not the same as business project events.) You do not need to use PeopleTools to create these objects. Instead, use the delivered objects described in the documentation for workflow actions.

See Defining Workflow Actions for Business Projects.

You define notification text for email notifications by selecting a correspondence template. Correspondence templates are used for email notifications only; worklist notifications do not include notification text.

See Setting Up Correspondence Templates.

Delivered Workflow Elements for Case Business Projects

PeopleSoft delivers the following elements to use when setting up workflow for business projects in cases:

• Roles for task assignees

• Roles for case assignees

• Workflow actions

• Processes

• Correspondence templates and template packages

Roles for Task Assignees

The following query roles identify the person, provider group, or role associated with a task.

These query roles require three bind variables:

• RC_TASK_STATUS.BUS_PROC_INSTANCE

• RC_TASK_STATUS.TRANS_FROM_NODE

• RC_TASK_STATUS.RC_TASK_ID

Roles for Case Assignees

The following query roles identify the person or provider group associated with the business project's parent case. Use different roles for the notifications sent from main business projects and from sub-business projects.

The query roles that identify a case assignee have only one bind variable: the business project instance (RC_BP_STATUS. BUS_PROC_INSTANCE).

Workflow Actions

PeopleSoft provides the following workflow actions that you can use with business project workflow.

Workflow actions associated with task assignees include three routing rules for different assignment types: provider, role, and person. This configuration ensures a valid rule even if you change the assignment type for a particular instance of the task.

Workflow actions associated with case assignees include two routing rules for different assignment types: agent and provider group. Business project workflow incorporates special logic to ensure that the provider group routing is used only if the case is not assigned to an individual agent.

Processes

PeopleSoft delivers the RC_BP_CASE process as part of the BP_CC_Case_Close workflow action. The RC_BP_CASE process closes cases. By invoking the BP_CC_Case_Close workflow action when a business project is complete, you ensure that cases are automatically closed as soon as associated business projects are complete.

Delivered Templates for Email Notifications

PeopleSoft provides correspondence templates for sending email notifications that are related to events in business projects. You can use the templates as delivered, modify them, or create your own.

The following correspondence templates apply to business project and phase events, and they all include a link to the Business Project Status page:

• BP Non-Default Transition (Business Project Non-Default Transition).

• BP Transition (Business Project Transition).

• Business Project Begins (Business Project Begins).

• Business Project Completes (Business Project Completes).

• Business Project Exceeds Time (Business Project Exceeds Time).

• BP Phase Begins (Phase Begins).

• BP Phase Completes (Phase Completes).

• BP Phase Exceeds Time (Phase Exceeds Time).

• BP Task in Phase Fails (Tasks in Phase Fail).

• BP Tasks in Phase Succeed (Tasks in Phase are Successful).

• Traffic Signal Receipt (Report of Traffic Signal Problem Received).

The following templates apply to task events and include a link to the Business Project Status page:

• BP Task Begins (Business Project Task Begins)

• BP Task Ends (Business Project Task Ends)

• BP Task Exceeds Time (Business Project Task Exceeds Time).

• BP Task Fails (Business Project Task Fails)

• BP Task Reassigned (Business Project Task Reassigned)

• BP Task Succeeds (Business Project Task Succeeds)

Understanding Business Project Process Definition

This section discusses:

• Definition of workflow actions that run processes.

• Definition of processes that dynamically instantiate sub-business projects.

• PeopleCode for setting task status.

Definition of Workflow Actions That Run Processes

When a task can be performed with an Application Engine process, you use a workflow action to schedule the process. For example, the delivered order fulfillment business project includes a task with a workflow action that schedules a process. The process triggers the EIP that publishes order information to the order fulfillment system.

Follow these guidelines when creating an Application Engine process to be used with a business project:

• Make sure that the state record includes the RC_BP_AE_SBR subrecord.

  The fields in this record store information about the business project that is instantiated.

• Make sure that the state record includes the RUN_CNTL_ID field and uses it to store the run control ID.

  This process does not use any other field names (for example, RUNCNTLID).

• The first step in the program should be a call to the POPULATE section in the RC_BPAET_LIB library.

  This section populates the RC_BP_AE_SBR subrecord.

• When the program completes a task, it can call the Trigger_Transition function to update the task status.

Fields in the RC_BP_AE_SBR Subrecord

The following fields provide the Application Engine process with information about the business project from which the process is invoked:

• ACTIVITY_INSTANCE

• BUS_PROC_INSTANCE

• COMPONENT_ID

• MAIN_ACTIVITY_ID

• MAIN_ACTIVITY_INST

• MARKET

• NESTED_BP_IND

• PARENT_ACTIVITY_ID

• PARENT_ACTVTY_INST

• PARENT_BP_INSTNCE

• PROCESSNAME

• PROCESSTYPE

• RC_ACTIVITY_ID

• RC_BUS_PROCESS_ID

• RC_MAIN_BP_INSTNCE

• RC_OUTCOME

• RC_TASK_ID

• RC_TASK_STATUS

• SEQ_NUM

Definition of Processes That Dynamically Instantiate Sub-Business Projects

To dynamically instantiate a sub-business project at runtime, you need to:

1. Create a task at the point in the phase when the sub-business project is instantiated.

2. Set up the task to trigger an Application Engine process.

3. In the process, create logic to determine which sub-business project to instantiate.

4. In the process, call the Nested_Business_Project_Start function to instantiate the sub-business project.

Nested_Business_Project_Start Function

The Nested_Business_Project_Start function (in DERIVED_RC_BP2.RC_BUS_PROCESS_ID.FIELDFORMULA) instantiates the specified sub-business project. Use the following syntax:

&dyn_sbp_inst = nested_business_process_start(&D_nbp_id, &nbp_effdt, &D_nbp_⇒
instance, &main_bp_instance, &nbp_activity_id, &nbp_activity_instance, &component_⇒
id, &task_seq_number, &run_parallel);

The function returns the instance ID of the instantiated sub-business project.

The following table describes the function parameters:

Note. The values for the parameters that refer to the business project instance, phase instance, activity instance, and task sequence number are available in the state record of the Application Engine process.

PeopleSoft delivers an example of the Nested_Business_Project_Start function in the RBT_STARTSBP process.

See Also

Definition of Workflow Actions That Run Processes

PeopleCode for Setting Task Status

Use the Trigger_Transition function (in FUNCLIB_RC_BP3.TRIGGER_TRANSITION.FIELDFORMULA) to set the status and outcome of a task or sub-business project that functions as a task. Depending on the business project definition, setting the outcome of a task or sub-business project may trigger a phase transition.

You can call this function from a process (such as an Application Engine process), from PeopleCode (for example, on the page where a user completes a task), or from an EIP.

Use the following syntax for the Trigger_Transition function:

Trigger_Transition(&Business_Proc_Instance, &Bp_Id, &Activity_Id, &Activity_⇒
Instance, &Task_Id, &Task_Seqnum, &Sub_Bp_Id, &Status, &Outcome, &Process_Type,⇒
 &Process_Name)

The following table describes the function parameters:

PeopleSoft delivers an example of the Trigger_Transition function in the BPMINITEST process.

Defining Invalid Actions

To define invalid actions, use the Invalid Actions (RC_INVALID_ACTIONS) component.

This section provides an overview of the PeopleCode for an invalid action and discusses how to:

• Define a message catalog entry for an invalid action error message.

• Create invalid actions.

Understanding the PeopleCode for an Invalid Action

To enforce invalid action processing, a PeopleCode program calls the BusProjectInvalidAction PeopleCode function and passes it the business project instance and the name of the attempted action. The BusProjectInvalidAction function uses the definition of the phase that is in progress and determines if the action is invalid for that phase.

If the action is invalid, the function returns a value of True and sets any variables in the message catalog entry associated with the invalid action. The application that called the function must then take the appropriate action.

BusProjectInvalidAction Function

Use the following syntax for the BusProjectInvalidAction function:

BusProjectInvalidAction(&BPInstance, &strAction, &Msg_Set_Nbr, &Msg_Nbr);

The following table explains the function's parameters:

Strategies

To prevent users from changing a specific field, create a single invalid action definition and then use PeopleCode to pass the name of that invalid action to the BusProjectInvalidAction function every time that the field changes.

To disallow specific field values, create invalid action definitions for each disallowed value and then use PeopleCode to pass the field value to the BusProjectInvalidAction function every time that the field changes. As long as you use the exact field value as the invalid action name, one PeopleCode program suffices for all of the invalid actions.

For other invalid actions, use PeopleCode to determine when the action occurs and to pass the appropriate action name to the BusProjectInvalidAction function.

Page Used to Define Invalid Actions

Defining a Message Catalog Entry for an Invalid Action Error Message

Definition of message catalog entries is discussed in the documentation for the message catalog.

See Enterprise PeopleTools 8.50 PeopleBook: PeopleSoft Application Designer Developer's Guide

Creating Invalid Actions

Access the Invalid Action Definitions page (Set Up CRM, Common Definitions, Business Projects, Invalid Actions, Invalid Action Definitions).

Invalid Action	Enter the name of the action. If the invalid action is an invalid field value (for example, if users are not permitted to set the status to Canceled), use the field value as the action name. This simplifies the PeopleCode that verifies whether an action is invalid.
Message Set, Message Number, and Message Text	Enter the set number and message number for the error message that the system displays when a user attempts an invalid action. After you select a message, the corresponding text appears.

Defining Tasks

To define tasks, use the Task (RC_TASK) component.

This section discusses how to:

• Create tasks.

• Set up task assignment rules and workflow.

• View task references.

Pages Used to Define Tasks

Creating Tasks

Access the Task page (Set Up CRM, Common Definitions, Business Projects, Task, Task).

Billable Indicator	Select if the caller is billed for this task. The external billing system can query this field for information.
External Source	Select if an external process (rather than a person) performs the task and closes it. This check box is for informational purposes only.

Setting Up Task Assignment Rules and Workflow

Access the Assign/Events page (Set Up CRM, Common Definitions, Business Projects, Task, Assign/Events).

Assignment

Specify default assignment information for manual tasks. The business project owner can change the assignments. If you do not enter default assignment information, the business project owner must assign the tasks.

Automated tasks (which are performed by an Application Engine process) do not need to be assigned to a person. However, entering assignment information for automated tasks enables you to send the assignee notifications related to the tasks.

Task Event Setup

Configure workflow associated with a task. You can create multiple events for each task.

Workflow that you set up for a task is used by every business project that includes the task. If the action is an email notification, you must reference a template that has the notification text before defining the workflow.

See Also

Setting Up PeopleSoft CRM Workflow

Viewing Task References

Access the References page (Set Up CRM, Common Definitions, Business Projects, Task, References).

View the lists of phases and business projects that reference the selected task.

Defining Phases

To define phases, use the Phase (RC_ACTIVITY) component.

This section discusses how to:

• Create phases.

• View phase references.

Pages Used to Define Phases

Creating Phases

Access the Phase page (Set Up CRM, Common Definitions, Business Projects, Phase, Phase).

Task List

The task list can include both tasks and sub-business projects.

Viewing Phase References

Access the References page (Set Up CRM, Common Definitions, Business Projects, Phase, References).

View the list of business projects that reference the selected phase.

Defining Business Projects

To define business projects, use the Business Project (RC_BUS_PROCESS) component.

This section discusses how to:

• Create business projects.

• Define phase transitions.

• Set up business project workflow notifications.

• Identify invalid actions.

• Identify parent objects.

• View sub-business project references.

Pages Used to Define Business Projects

Creating Business Projects

Access the Business Project page (Set Up CRM, Common Definitions, Business Projects, Business Project, Business Project).

Business projects must be current, active, and validated in order to be used.

See Also

Business Project Architecture

Defining Phase Transitions

Access the Transitions page (Set Up CRM, Common Definitions, Business Projects, Business Project, Transitions).

To define the phases within a business project, you create transition definitions that pair a source phase with a target phase. A phase can appear in multiple transition definitions. When a phase has multiple target phases, transition rules determine which target is used at runtime. Because any phase can have a transition to any other phase, the system can loop through a phase multiple times at runtime.

The left side of the Transitions page provides an alphabetical list of all source phases and their possible targets. Select a target phase to see the associated transition definition on the right side of the page.

Transition Definition

Automatic Transition When

Use these fields to set criteria for automatic transitions to the current target phase. These fields are not available for entry when the start phase is set up for manual transitions.

Business Project Validation

Setting Up Business Project Workflow Notifications

Access the Events page (Set Up CRM, Common Definitions, Business Projects, Business Project, Events).

Notification Type

Select an event to associate with a workflow notification. Options are: BP - Begins (business process begins). BP - Completes (business process is completed). BP - Exceeds Max Calc Time (business process exceeds maximum calculated time). BP - Exceeds Max Time (business process exceeds maximum time). BP - Exceeds Stan Calc Time (business process exceeds standard calculated time). BP - Exceeds Stan Time (business process exceeds standard time). Phs - All Complete (all tasks in the phase are complete, regardless of which succeeded or failed). Phs - All Complete/All Success (all tasks in the phase are complete successfully). Phs - All Complete/Any Fail (all tasks in the phase are complete and not all are successful). Phs - Begins (phase begins). Phs - Completes (phase is completed). Phs - Exceeds Max Calc Time (phase exceeds maximum calculated time). Phs - Exceeds Max Time (phase exceeds maximum time). Phs - Exceeds Stan Calc Time (phase exceeds standard calculated time). Phs - Exceeds Stan Time (phase exceeds standard time). Task - Exceeds Max Time (task exceeds maximum time). Task - Exceeds Stan Time (task exceeds standard time). Transition - Any (transition any). Transition - Non-Default (transition non-default).

Rule Name and Email Template

Select the workflow action to trigger when the associated event occurs. If the workflow action sends an email notification, select the template to use to construct the email.

See Also

Setting Up PeopleSoft CRM Workflow

Identifying Invalid Actions

Access the Invalid Actions page (Set Up CRM, Common Definitions, Business Projects, Business Project, Invalid Actions).

Phase ID	Select the phase during which the specified actions are invalid.
Invalid Action	Enter the actions that are invalid during the specified phase.
Message Text	Displays the message that appears if a user attempts the action during the phase. You can change the message on the Invalid Actions Definition page.

Identifying Parent Objects

Access the Parent Object page (Set Up CRM, Common Definitions, Business Projects, Business Project, Parent Object).

Establish the relationship between the business project and the parent object, which is an object such as a case or an order that can invoke the business project. This page does not apply to sub-business projects.

Viewing Sub-Business Project References

Access the References page (Set Up CRM, Common Definitions, Business Projects, Business Project, References).

View the lists of phases and business projects that reference the selected sub-business project. This page does not apply to main business projects.

Cloning and Deleting Phases and Business Projects

To clone and delete phases, use the Phase Save As and Delete Phase components.

To clone and delete business projects, use the Business Project Save As and Delete Business Project components.

This section discusses how to:

• Clone phases or business projects.

• Delete phases or business projects.

Pages Used to Clone and Delete Phases and Business Projects

Cloning Phases or Business Projects

Access the Business Project Definitions Save As page (Set Up CRM, Common Definitions, Business Projects, Business Project Save As, Business Project Definitions Save As) or the Phase Definitions Save As page (Set Up CRM, Common Definitions, Business Projects, Phase Save As, Phase Definitions Save As).

Select the object to clone, and enter a name and description for the object to be created. If you are cloning a business project, you must also select whether to save the new business project as a main business project or a sub-business project.

When you save the page, the new object is created. Newly created business projects are inactive and must be validated before they are active.

Deleting Phases or Business Projects

Access the Delete Phase Definitions page (Set Up CRM, Common Definitions, Business Projects, Delete Phase, Delete Phase Definitions) or the Delete Business Projects Definition page (Set Up CRM, Common Definitions, Business Projects, Delete Business Project, Delete Business Projects Definition).

Select the objects to delete. You cannot delete business projects that have already been instantiated. Likewise, you cannot delete sub-business projects that are incorporated into a phase.

When you save the page, the objects are deleted.