> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/example-gallery/how-to-guides/creating-other-please-specify-options.md).

# Creating "Other: please specify" Options

### Description

In many Q\&A applications, a radiolist or checklist question may need the option to select "Other" and specify an alternative not initially listed. While it is possible to model this scenario with a logicnet on a case-by-case basis, we have created a how-to guide here that systematically provides the user interface and associated background processing. The guide has been written using the LogicNets Assessment Framework but the feature will work in LogicNets Starter App framework aswell.

This guide includes the following:

* The "onstart" configuration you will need to add to your project
* The *Other: please specify* logic and logicnets you will need to process the user interface and context evaluation
* Simple styling for the LogicNets Assessment Framework. You may need to update this to fit in with your specific application's look and feel.

### Context Management

In addition to processing the user interface, the *Other: please specify* calculator manages the resulting variables behind the scenes. Assuming you have a checklist variable called *mychecklist*, the following is true:

* *mychecklist* always contains the "raw" selections made by the user, including if they select the \_"\_*other"* choice.
* *mychecklist\_expanded* contains the final verbose selections made by the user:
  * If they selected \_"\_*other"* but no additional details are provided, the *mychecklist\_expanded* will contain \_"\_*other"* as one of the items.
  * If they provide additional details *mychecklist\_expanded* substitutes the *other* value for the additional details.

### Setup Instructions

To set up this example, copy the How-to Guide into your Designer and make the following changes to your project:

1. Copy the set node defaults from node 20 in the *initialization* logicnet into a logicnet in the *onstart* folder of your project.
2. Copy the following logicnets into your project. Do not copy them to the forms, reports, or *onstart* folder: - decorator logicnet - order\_calculator logicnet
3. For each radio/checklist question where you want to use this feature, do the following:
   1. In the *final* answer option, set the value to *other.* The caption can be anything, such as "Other - please specify".
   2. Navigate to the *CODE* tab of the node. Right-click on the node, choose *Form Details*, and click on *CODE* in the part editor top bar.
   3. Type in *class = "order\_calculator",* as in the image below:

      ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-eb8eaad835a98620260a735ac1673712ca0ea8a6%2F683ecdc6-4a2c-4e44-b15e-5c0893ad8520.png?alt=media)

### Advanced Notes

This feature uses a "decorator" to process and present additional logic when the LogicNets runtime engine traverses specific nodes tagged with *class="X"*. You can use this methodology in a variety of ways to enhance standard parts with custom and more sophisticated behavior. Talk to your LogicNets Representative if you have other ideas where this approach may be helpful for your application.

## Attachments

* [ASF How-To Guide - Other\_please specify option.zip](https://github.com/logicnets/community-portal/tree/release-9/docs/.gitbook/assets/y7dv4z-ASF-How-To-Guide---Other_please-specify-option.zip)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/example-gallery/how-to-guides/creating-other-please-specify-options.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.