Priority Number Calculation Rules

Leaf auto-creation with Assign Document

The priority number calculations are limited to the first parent folder with eCTD 4.0 Context of Use Code and are restarted for next folder with eCTD 4.0 Context of Use Code.

The priority number calculations are limited to whole assembly root for folders that have no parent folder in hierarchy with assigned Context of Use Code.

The priority number calculation is performed for all leafs under the folder with assigned Context of Use Code, including all leafs in all nested folders that have no Context of Use Code values.

The priority number calculation is performed for all leafs within the assembly root for all folders that have no parent folder in hierarchy with assigned Context of Use Code.

Reorder Child Leafs

The priority number calculation is performed for all the leafs under the folder with assigned Context of Use Code and all the nested folders that have no Context of Use Code values.

The priority number calculation is performed for all the leafs under an assembly root and on all the folders that have no parent folder in the hierarchy with assigned Context of use code.

The priority number of the moved/promoted/demoted leaf/reference leaf is changed within the folder or from another folder.

The priority number of duplicated leaf/reference leaf changes based on the following conditions:

— The priority number of the leafs under duplicated folder without assigned Context of use code and for all the folders without a parent folder in a hierarchy with assigned Context of use code, is calculated within and limited to the assembly root (not including the folders with Context of use code).

— The priority number of the leafs under duplicated folder without assigned context of use code is calculated within the first parent folder with assigned Context of use code (and limited to the same first parent folder with the assigned Context of use code).

— The priority number of the leafs under duplicated folder with assigned Context of use code is copied.

The priority number value does not change after the Convert to Reference Leaf action is performed.

If the folder hierarchy is changed or removed from the Context of use code, the reorder leafs action must be performed.

When performing some folder operations such as import, duplicate and so on, the priority number limit may exceed the default 999999 number. When this happens, the operations are not processed. The warning message is displayed when priority number limit is exceeded.

The priority number of new leafs created after using the one-to-many Replace operation is recalculated for each new replaced leaf.

Using the Revert operation after the following actions are performed with leafs or folders can create incorrect or duplicated priority numbers of reverted leafs:

— Move

— Promote or Demote

— Add Leaf

— Duplicate

— Leaf auto-creation during assigning Document on Folder

— Reorder Child Leafs eCTD 4.0 Working Assembly Created from eCTD 3.2 Assembly

The valid leaf priority number value is set after creating eCTD 4.0 working assembly from eCTD 3.2 assembly. See:Leaf Ordering Rules .