Document Stacks

A document stack is a list of document types that are used in a variety of ways such as viewing in the document viewer, bundle grouping and naming, printing and downloading, security profiles, as well as in Document Stack Security, which was covered in a previous section.

 

 

Creating a Document Stack - To create a document stack, go to the XDOC Admin section Projects Tab>Project Repository>Document Stacks, and do the following:

1. Click CREATE. The Document Stack editor will appear.

2. In the Document Stack Editor that pops up enter the following information:

Field Description
Name The name for the document stack
Code An addition Code reference for the stack used for matching when doing advanced document stack security. The best practice for this field is to make it the same as the name, but with no spaces and no special characters
Description Any added description if needed
Active Choose “Yes” to make it active, or available for use
Sequence Not actively used. You can ignore this field for now.
Sort Rule Stack Item Sequence – Orders the documents by how they are ordered in the stack
Doc Type Sequence – The Document Type sequence. Equivalent to the sequence number in the document type editor

3. Define how the document stack will be used - Check the appropriate check box to define how the document stack will be used. (You may choose more than one box): 

a. Bundle Naming – You can also configure the way the bundled documents get named that conforms to a way specified by an investor or other recipient

b. Bundle Documents – You can determine the document types that get sent with a bundle, as well as the order in which they get send

c. Printing (Downloading) - Printing and downloading a group of documents from the document viewer’s print and download icons

d. Profiles – Allow viewing and uploading of a specific set of documents per security profile.

e. Viewer - Will show up as a view stacks in the document viewer

f. Copy - Used for Document Copy

4. Add documents to the stack



  1. Select a document to add to the stack. There are a few ways to add documents to the stack:
    1. Double clicking on the document name - Automatically add the document to the end of the stack
    2. You can also type in the document type name in the --filter document types-- box, then choosing from the results
    3. Clicking once on the document name, and then selecting:
      1. Add to End of List - Adds the document to the end of the stack list
      2. Add Before Checked - Adds the document to the stack before the checked document in the list. This is especially helpful if you already have a large document stack list and need to add a document to the middle of the stack

Document Stack Editor - Ordering

 

  1. Once documents are selected, you can move one or more documents up or down in the order, or remove them from the list with the buttons just to the left. 
    1. To move or delete an individual document type, click the checkbox to the left of the document name
      1. ❌ removes the document from the list and places it back in the list of available document
      2. ▲ moves the document up one place in the list
      3. ▼ moves the document down one place in the list
    2. To move or delete a group of document types:
      1. Select the checkbox for each document type in the list
      2. Select the ❌, ▲, or ▼ box on the header column in blue
        Document Stack Editor - Actions

5. Click SAVE when done

 

Using Document Stacks for Document Naming - Some bundle recipients (Investors, MI companies, Servicers, etc.) may require that individual documents be named in a certain way that is different than how your company names it. In the document stack, the "Name", "Code", and "Ref Value" fields are three additional options for naming individual documents sent to these recipients. To use this alternate naming:

1. Place the alternate name for the document in the "Name" field. If there are additional names you want to use for this document, use the "Code" and "Ref Value" fields.

Document Stack Editor - Naming

2. Use the appropriate token in the bundle template or bundle profile that will use this field for naming the document. The tokens are:

a. Name field:  $$Naming.name$$

b. Code field:  $$Naming.code$$

c. Ref Value field:  $$Naming.refValue$$