Refresh Approvals

Refreshes approved components at the working level.

When a junior engineer makes changes to data and issues them for approval by a senior engineer (who can approve or reject the changes by setting the status), the changes are automatically saved - a save work is not needed.

The option allows the junior engineer to receive changes made by the senior engineer. Any changes to the writable discipline Databases (DBs) are received. The action does not receive published data from other disciplines.

Any attribute changes made to the working data is saved before the approval data is received.

Automatically Create Working Revisions

If the junior engineer makes changes to attributes on a component and submits them for approval, the approved components are refreshed at the working level, and automatically transitioned to the next working revision. This requires the status lifecycle to have a defined transition from the approved state to the working state. If there is no transition defined, the working revision is not created.

For example:

• The junior engineer submits Pump1 at Pending Approval, revision B2*

• The junior engineer changes an attribute on Pump1

• The senior engineer approves Pump1 at revision B3

• The junior engineer refreshes approvals - Pump1 displays as Approved at B3, then Working at B3*.