Let’s take a look at the Unpack feature in DocBoss which you can use to handle and manage document packages you send to your customers.

Here is the screen shot of a package sent to the customer by way of an example.

notes_pdf_2020-03-22_10-51-29.jpg

Assign returned package to the package card

Follow the normal steps to bring the package card into an incoming submittal. Assign the incoming package to the PACKAGE CARD. You will see a small notification in the assign slide in, indicating you will be given the unpack option once you complete the assignment.

2020-03-22_10-53-18.jpg

Once you complete the assignment, you will see this pop up:

2020-03-18_19-27-43.jpg

Here you can choose the following options:

  • Yes to Unpack AND Mark the checkbox to navigate immediately to the sub-folder to complete the unpacking 
  • Not Unpack
  • Yes Unpack and DON’T Mark the checkbox to navigate immediately to the sub-folder. This last option allows you to Process the file and return and Unpack the file later. When you are ready to Unpack just navigate back to the Incoming Documents and click on the Unpacking Transmittal. 
Unpacking_2.jpg

Review Unpacking

After accepting this pop-up, you will be redirected to a sub-submittal folder where you will review the prospective unpacking.

2020-03-22_10-57-23.jpg
  1. The sub-folder has a naming convention which uses the original transmittal number, PLUS “_Unpack_Card Name”. This will show in your submittals list, but all reports use only the original transmittal number.
  2. This shows the card which is being unpacked. NOTE: this is a COPY of the uploaded file. You original assignment is still in place. You are now assigning each individual card.
  3. Grid showing all expected document, their expected position in the package, page number etc. You can edit this grid.
  4. Grid summary. This must balance to 0 to allow unpacking.
  5. Unpack button – click to proceed to split files, and assign to cards.

Ensure the unpacking will be accurate

Edit segments

If your customer edited the package before returning, you can change how we allocate pages to cards.

Page Counts, Cover Pages & Comment pages

Maybe the customer removed cover pages, added comment pages, removed doc pages etc.. That information can be edited on the grid, and the PAGES RANGE will auto-update.

Note that you need to ensure the summary data is accurate to enable the unpacking button. In the below example, I added a comment page, and changes doc pages from 1-2. You can see that the system now is trying to understand WHY I made that change (we expected 21 pages, the returned doc HAS 21 pages, and now the grid says to expect 23 pages)

2020-03-22_11-22-13.jpg

Reorder cards

If your customer changed the order of the cards in the package prior to returning, you must edit the grid to match the returned file. 

2020-03-22_11-38-34.jpg

Add or remove segments

You can remove any card from the grid (maybe the customer did not return that card). You can also add non-card segments to the packages. If you have pages which are applicable to existing cards (maybe the customer has embedded old cards into the package) you should mark them as non-card segment. After the unpack, you can assign non-card segments to back into existing cards.

2020-03-22_11-22-13.jpg

Package Comments Sheet

During the unpacking process, comment sheets are often provided for each returned card. In some situations, all comments are added to a single comment sheet for the entire package. You may now designate a set of pages as the package comment sheet which will be circulated with each individual card.

We call them “Master Comments Sheets” and these can be added same as any other non-card segment:

Image_1.jpg
  1. Click + sign under Tools column
  2. Fill in all mandatory fields marked with an asterisk
  3. Select “Master Comment Sheet” on the Type drop down
  4. Click Save

The Master Comment Sheet is the only segment that can be circulated with each individual card.


So if the comments are included in the Cover Page instead of an additional comment sheet, and this is the page that needs to be circulated with each individual card:
– First add a Master Comment Sheet


– Delete the Cover Page segment
– Select appropriate Page Range to include all the pages that need to be attached to each Card.

Image_4.jpg

Segment Type

DocBoss identifies every page, and allocated it to a card, or sets it as a non-card segment. This is done automatically, based on the composition of the package when sending.

Image_3.jpg

Start the unpacking

Could take a few minutes to split the incoming PDF. You’ll see the status at the bottom of the screen.

2020-03-18_19-40-27.jpg

Review results

The user is moved into a normal BULK match process to verify cards.

2020-03-22_11-43-04.jpg
  1. The user starts on the To Match header tab. Once you have completed your review, click to complete the status and routing process.
  2. To Match and Matched are the normal tabs. We now have Non-Card Segments to show you TOC’s cover pages and any non-card segments created during matching. Note that you CAN move non-card segments into the To Match area for assignment (like any other normal card)
  3. Note that you default to the document cards grid. if you wish to review the unpacking data, you can click Unpacking structure. This also gives you the option to UNDO the unpacking.

Non-Card Segments

If you wish to move a non-card segment back into the To Match area, you just select it, and click Allow Match.

2020-03-22_11-58-17.jpg

Apply Status and Routing

The last step (as with bulk processing) is to assign statuses and routing to the individual files. You can do this through the same process as the bulk submittal processing (individually or process in bulk). You have the option to add meta data to the files, change revs etc (just as with a normal bulk upload).

2020-03-22_12-03-14.jpg

Final result

After unpacking you will have

1. The ORIGINAL package card in some status/routing.

2. Each component card containing the applicable pages from the package. They will have their own status/routing. So you could send one of the component files back to a supplier etc…. Once returned, regenerate the package, and send to customer etc.

Share This