Bypassing the I Step

You are here: Primavera Unifier Administration Mode > Business Process Setup > Setting up Business Processes > Bypassing the I Step

Bypassing the I Step

During business process setup you can set up an auto-created workflow BP to skip the initiation step and send the record directly into the workflow, where it normally arrives at the first step after the Create step (or the first step in a conditional routing). For a workflow BP, you can specify the schema, the step in the workflow that the record should use as its first step, the workflow duration, and the name of the person or group who will be the owner of the auto-created record. When the record is created, data will roll up to the manager sheets at the appropriate status; however, if Primavera Unifier encounters errors or invalid data, the record will remain at the Create step, and roll-ups will not occur until the user resolves the errors.

For a non-workflow BP, you can set up an auto-created record to skip the initiation step. In this case, the non-workflow BP will be created and will appear in the BP log in either an “edit” or “finish edit” mode. If it appears in an “edit” mode, the user will have to open the record and add or correct information on the form. If it appears in a “finish edit” mode, the record is considered complete, and data will roll up to manager sheets.

Auto-Creation Protocol for Bypassing the I Step

Auto-creation uses details specified in the BP Creator element to create the record. If these details are not present in the BP Creator element, the auto-creation feature will use the following protocol to attempt to create the record.

For a Non-Workflow BP

For a Workflow BP

Checks for owner specification:

•

Checks the source BP setup

•

Checks the destination BP setup

•

If no owner can be identified, sends an error notification to those specified in source BP

Checks for owner specification:

•

Checks the source BP setup

•

Checks the destination BP setup

•

If no owner can be identified, sends an error notification to those specified in source BP.

Checks for status:

•

Checks the destination BP setup

•

If no status found, creates the record and puts it into “edit” mode for user to correct.

Checks for a workflow schema:

•

Checks the destination BP setup

•

If no schema is specified, the record will be sent as an I Step to the user’s Tasks log and the BP log to which the record belongs.The user must accept the task to manually launch the record.

Checks for an action specification

•

Checks the destination BP setup

•

If no action is specified, the record will be sent as an I Step to the user’s Tasks log and the BP log to which the record belongs.The user must accept the task to manually launch the record.

Oracle Corporation