Fields
The Properties section of the View Designer and Module Designer views displays the properties that are available for the selected attribute, control, or widget. The list of available properties will vary, depending on the selected attribute, control, or widget.
| Field | Description |
|---|---|
| Investment/Title |
This paragraph exists to demonstrate how we can share this content into three places: 1) a standalone glossary topic, 2) pulled in as an overview of a scenario (or a task or wherever appropriate), and 3) the quick intro for a scenario/concept/whatever that has been pulled into a guidance page (using an iframe -- we're pulling in the actual glossary entry). This is a great example of reusing content and applying consistency of concepts and terms across the help experience. Only people who read the entire doc set will ever figure out that we're reusing entire paragraphs. And even then, 99% of them won't care. |
| Status |
This paragraph exists to demonstrate how we can share this content into three places: 1) a standalone glossary topic, 2) pulled in as an overview of a scenario (or a task or wherever appropriate), and 3) the quick intro for a scenario/concept/whatever that has been pulled into a guidance page (using an iframe -- we're pulling in the actual glossary entry). This is a great example of reusing content and applying consistency of concepts and terms across the help experience. Only people who read the entire doc set will ever figure out that we're reusing entire paragraphs. And even then, 99% of them won't care. |
| Priority |
This paragraph exists to demonstrate how we can share this content into three places: 1) a standalone glossary topic, 2) pulled in as an overview of a scenario (or a task or wherever appropriate), and 3) the quick intro for a scenario/concept/whatever that has been pulled into a guidance page (using an iframe -- we're pulling in the actual glossary entry). This is a great example of reusing content and applying consistency of concepts and terms across the help experience. Only people who read the entire doc set will ever figure out that we're reusing entire paragraphs. And even then, 99% of them won't care. |
| Assigned To |
This paragraph exists to demonstrate how we can share this content into three places: 1) a standalone glossary topic, 2) pulled in as an overview of a scenario (or a task or wherever appropriate), and 3) the quick intro for a scenario/concept/whatever that has been pulled into a guidance page (using an iframe -- we're pulling in the actual glossary entry). This is a great example of reusing content and applying consistency of concepts and terms across the help experience. Only people who read the entire doc set will ever figure out that we're reusing entire paragraphs. And even then, 99% of them won't care. |
| Approved |
This paragraph exists to demonstrate how we can share this content into three places: 1) a standalone glossary topic, 2) pulled in as an overview of a scenario (or a task or wherever appropriate), and 3) the quick intro for a scenario/concept/whatever that has been pulled into a guidance page (using an iframe -- we're pulling in the actual glossary entry). This is a great example of reusing content and applying consistency of concepts and terms across the help experience. Only people who read the entire doc set will ever figure out that we're reusing entire paragraphs. And even then, 99% of them won't care. |
| Approved By |
This paragraph exists to demonstrate how we can share this content into three places: 1) a standalone glossary topic, 2) pulled in as an overview of a scenario (or a task or wherever appropriate), and 3) the quick intro for a scenario/concept/whatever that has been pulled into a guidance page (using an iframe -- we're pulling in the actual glossary entry). This is a great example of reusing content and applying consistency of concepts and terms across the help experience. Only people who read the entire doc set will ever figure out that we're reusing entire paragraphs. And even then, 99% of them won't care. |
| Requested Date |
This paragraph exists to demonstrate how we can share this content into three places: 1) a standalone glossary topic, 2) pulled in as an overview of a scenario (or a task or wherever appropriate), and 3) the quick intro for a scenario/concept/whatever that has been pulled into a guidance page (using an iframe -- we're pulling in the actual glossary entry). This is a great example of reusing content and applying consistency of concepts and terms across the help experience. Only people who read the entire doc set will ever figure out that we're reusing entire paragraphs. And even then, 99% of them won't care. |
| Resolution Date |
This paragraph exists to demonstrate how we can share this content into three places: 1) a standalone glossary topic, 2) pulled in as an overview of a scenario (or a task or wherever appropriate), and 3) the quick intro for a scenario/concept/whatever that has been pulled into a guidance page (using an iframe -- we're pulling in the actual glossary entry). This is a great example of reusing content and applying consistency of concepts and terms across the help experience. Only people who read the entire doc set will ever figure out that we're reusing entire paragraphs. And even then, 99% of them won't care. |
| Escalation? |
This paragraph exists to demonstrate how we can share this content into three places: 1) a standalone glossary topic, 2) pulled in as an overview of a scenario (or a task or wherever appropriate), and 3) the quick intro for a scenario/concept/whatever that has been pulled into a guidance page (using an iframe -- we're pulling in the actual glossary entry). This is a great example of reusing content and applying consistency of concepts and terms across the help experience. Only people who read the entire doc set will ever figure out that we're reusing entire paragraphs. And even then, 99% of them won't care. |
| Escalated? |
This paragraph exists to demonstrate how we can share this content into three places: 1) a standalone glossary topic, 2) pulled in as an overview of a scenario (or a task or wherever appropriate), and 3) the quick intro for a scenario/concept/whatever that has been pulled into a guidance page (using an iframe -- we're pulling in the actual glossary entry). This is a great example of reusing content and applying consistency of concepts and terms across the help experience. Only people who read the entire doc set will ever figure out that we're reusing entire paragraphs. And even then, 99% of them won't care. |
| URL Link |
This paragraph exists to demonstrate how we can share this content into three places: 1) a standalone glossary topic, 2) pulled in as an overview of a scenario (or a task or wherever appropriate), and 3) the quick intro for a scenario/concept/whatever that has been pulled into a guidance page (using an iframe -- we're pulling in the actual glossary entry). This is a great example of reusing content and applying consistency of concepts and terms across the help experience. Only people who read the entire doc set will ever figure out that we're reusing entire paragraphs. And even then, 99% of them won't care. |