As per the functionality, that the sorting process will first apply to the parent and then to its attachments.
[Describe problem and try to use the words of the client.]
Scenario 1 When the production contains both parent and child documents.
For example: Sorted by filename ascending order and with bates numbering
1: a.msg (parent)
x.txt (attachement)
2: b.msg (parent)
y.txt (attachement)
3: c.msg (parent)
z.txt (attachement)
And it is sorted by filename ascending order and with bates numbering.
The production will be produce likewise as the sorting will apply to parent first and then to it’s attachments.
a.msg bates1
x.txt bates2
b.msg bates3
y .txt bates4
c .msg bates5
z.txt bates6
Scenario 2 When the production contains only parent documents:
For example: Sorted by filename ascending order and with bates numbering
1: a.msg (parent)
2: b.msg (parent)
3: c.msg (parent)
And it is sorted by filename ascending order and with bates numbering.
The production will be produce likewise as the sorting will apply to parent first.
a.msg bates1
b.msg bates2
c .msg bates3
Scenario 3 When the production contains only one child file without it’s parent file and remain documents present are only parent files.
For example:
Sorted by filename ascending order and with bates numbering
1: a.msg (parent)
2: b.msg (parent) (When this file is not produced)
c.txt (attachment)
3: d.msg (parent)
And it is sorted by filename ascending order and with bates numbering.
The production will be produce likewise as the sorting will apply to parent first and then to it’s attachments.
a.msg bates1
d .msg bates2
c.txt bates3
As per the functionality, that the sorting process will first apply to the parent and then to its attachments, all the parent documents will be produced first and then that one child document which is produced without it’s parent file will be produced at last.
Here the c.txt is the only child document which is produced without it’s parent and so it will be produced last.