Create an RFP Project component

The RFP Project subsection is used to create a component where end users can work with an RFP. This subsection is only available from a document type.

Once you have completed the fields for a subsection and saved the information, a component is created for the subsection.

If the Sample Database is installed with Upland Qvidian, predefined document types (for example, Formal Proposal, RFP Project, Formal Presentation, etc.) complete with model sections and subsection components are available for your use. Reviewing how each component is structured and implemented may help you in the architecture process.

Create an RFP Project component

  1. From the Toolkit, select RFP Project.
  2. Enter the name of the component. This name displays in the navigation panel.
  3. Enter the display title. This title displays on the created document's Assemble tab.
  4. Select one of the following options from the Include drop-down menu:
    • Always: Select if you want this subsection required for completion for created documents or projects using the document type.
    • Optional: Select if you want this component to be listed in the Optional Tasks panel on a created document's Assemble tab or on a project's navigational panel so that end users have the option of including the component.
    • By Inclusion: Select if you want this component automatically included when an optional component is included. The Component / Selection Group tree displays listing the optional component and selection groups for this document type. Check the box for the optional component with which you want to associate this component. When the user includes the associated optional component, the by inclusion component is also included. Check the boxes for each item that you want this component included with a required for completion status.
    • Optional or by inclusion: Select if you want this component included either as an optional component or to be included by inclusion of a different optional component. The Subsection / Selection Group tree displays listing the optional components and selection groups for this document type. Check the box for the optional component with which you want to associate this component. When the user includes the associated optional component, the by inclusion component is also included. The component is also listed in the Optional Sections pane on the created document's Assemble tab or on the project’s navigation panel, so that users can select the component in a document build without selecting the component with which it is associated.
  5. Click Save.

Add help text for users

You can create help text to display at the top of the component to help users complete the fields. In designing the help text, you can work in design mode or HTML text. You can also preview the help text. When the help text first displays, the region is in Design mode. Most users will use this mode to create the help text and use the available standard formatting functions.

Text format bar

  • To remove any formatting that you added or that was applied to text pasted from the clipboard, select the text and click the Eraser Eraser button icon to revert to the default Font and Size (Verdana, 10pt).
  • If you want to edit the item in HTML, click the HTML Text HTML text button icon. The formatting toolbar will disappear.
  • To view the help text as it will display on the page, click the Preview Preview button icon. The help text area will change to view only.
  • To return to design mode, click the Design Mode Design Mode button icon.

    • Note: Hyperlinks cannot be added to the help text field.

View component usage

The Usage panel, at the bottom of the component, displays how this component is being used in all document types and sections. The associated document types and components are listed as links so that they can be opened from the Navigation panel.

Common functions

The following common functions are listed at the top of the component workspace:

  • Test Build: Click to display the created document page where you can see the document type from the user's perspective and run a test build to verify it appears as you intended. For more information, see Test Build.
  • Reset Test Build: Click to delete any existing test build associated with the document type so you can start again with a fresh test document. For more information, see Test build a document type.
  • Export: Click to export the document type. For more information, see Export a document type.
  • Content Tray: Click to display the Content Tray dialog. The content tray is a holding area for content records that you can drag from the tray and drop in the content area for select components. For more information, see Content tray.