When do you enable submission phases for an approval process?

Study for the Oracle FCCS Certification Test. Prepare with flashcards and multiple choice questions, each question accompanied by hints and explanations. Get ready for your exam!

Multiple Choice

When do you enable submission phases for an approval process?

Explanation:
Submission phases are defined as part of configuring the approval workflow, which you set up when you create the approval unit hierarchy. By establishing the hierarchy, you lay out the units, the order of approvals, and where phases will occur. Enabling submission phases then activates that phased routing so submissions move through the planned sequence of approvals. Linking the hierarchy to a specific scenario, period, or year just applies the workflow to those data contexts and doesn’t enable the phased behavior. Setting member properties for an entity is unrelated to the approval workflow configuration, and starting the approval process simply begins the workflow using whatever phases have already been defined.

Submission phases are defined as part of configuring the approval workflow, which you set up when you create the approval unit hierarchy. By establishing the hierarchy, you lay out the units, the order of approvals, and where phases will occur. Enabling submission phases then activates that phased routing so submissions move through the planned sequence of approvals. Linking the hierarchy to a specific scenario, period, or year just applies the workflow to those data contexts and doesn’t enable the phased behavior. Setting member properties for an entity is unrelated to the approval workflow configuration, and starting the approval process simply begins the workflow using whatever phases have already been defined.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy