The Content List displays all of the folders and files that are created in Process Director, or uploaded into Process Director as content. The Content List is a hierarchical list of all Process Director objects. The Content List includes all of the objects created in Process Director, such as eForms, Process Timelines, Knowledge Views, etc. In addition, the Content List can include uploaded files such as Excel spreadsheets used to import data, Word documents used as templates for output documents, and other files that become part of a process definition.
The Content List consists of a file structure that is located on the left side of the screen, and a file listing that is displayed on the right side of the screen. Navigation through the Content List is done by clicking on a folder on either side of the screen.
Many users think of the Content List as a file system that users can create inside of Process Director, but this isn't really correct. The content list organizes Process Director objects in a logical fashion for users who are browsing through the system, but the actual objects in Process Director are not really organized in the way that the Content List displays.
For instance, in a file system, the file name is the key element for identifying a file. Let's say you have a word document named "sample.docx", and you change the name to "NewSample.docx". If you go into Microsoft Word, and try to open the "sample.docx" file from the list of recent files, you will receive a message telling you
that the file can't be found. Changing the name of the file changes the identity of the file on your computer, making any references to the old file name invalid.
In Process Director, on the other hand, an object's name doesn't affect the identity of the object. Process Director tracks objects by a unique ID that you, as an end user will rarely, if ever, use. The object name is merely an attribute of the object that you can change at will without Process Director losing track of the object. Here's an example that demonstrates how object tracking works in Process Director.
- In this example, you have a business rule named "My Business Rule" and an eForm named "My eForm".
- The eForm references the Business Rule to determine when to enable the fields on the eForm, as shown below.
- Change the name of the Business Rule to "My Original Business Rule".
- Now, create a new Business Rule named "My Business Rule". This is the same name as the original business rule.
- Note that, even though you have a business rule with the name "My Business Rule", Process Director does not use it as the business rule on the eForm. Instead, Process Director has updated the eForm definition to show the new name you gave to the original Business Rule.
By the way, you can see the ID that Process Director uses to identify an object by opening the object definition. On an eForm, for example, at the bottom of the eForm definition screen, you'll see the Form URL, written in a format similar to:
The "formid" URL parameter contains the ID that Process Director uses to uniquely identify the eForm object, which, in this example, is
Changing the name of the eForm, or any other property, does not change this ID. So, you can identify the eForm with a name that is easily readable by humans, while Process Director identifies the eForm with this ID, which is easily readable by computers.