Setting SoloSubmit project options

If you use SoloSubmit, you must enable it before users can submit issues to the Helix ALM project from the SoloSubmit web page. You can also enforce required field validation, enable the default values for SoloSubmit fields, and specify fields you do not want JavaScript to handle field relationships for.

See the SoloSubmit help for information about configuring SoloSubmit.

1. Choose Tools > Administration > Project Options.

The Project Options dialog box opens.

2. Select the SoloSubmit category.

3. To enable SoloSubmit, select Enable entering issues via the SoloSubmit web page and enter the SoloSubmit HTML page.

The default page is solosubmit.htm. If you use a customized page, enter the filename. Make sure the HTML file is in the ttweb directory on your web server.

SoloSubmit must be enabled for each project.

4. Select any additional options.

  • Email an acknowledgment to the submitter automatically emails the issue submitter using the content of the selected email template.
  • Enter next sequence number in issue’s Reference field enters the next available sequence number in the issue Reference field. You can set the next available sequence number in the Issues project options. See Setting issue project options.
  • Enforce required fields ensures values are entered for all required fields. Values are validated when users submit issues. Users are prompted to enter values for any incomplete required fields. Required fields are not enforced for the Entered By field because users do not log in to SoloSubmit. If Entered By is a required field, issues entered via SoloSubmit cannot enforce required field validation.

Use default values populates the SoloSubmit web page with default values.

When an issue is submitted via SoloSubmit, there is no associated user in the project, so the time zone to use in the issue cannot be applied for the user. The current time and date of the computer the SoloSubmit CGI is running on when the SoloSubmit page is loaded is used as the default value for date/time custom fields.

5. Select fields you do not want JavaScript to handle field relationships for on the SoloSubmit web page. You may not want to include the JavaScript because:

  • The SoloSubmit web page includes hidden fields. For example, you comment out a field you do not want customers to see. You can delete the HTML, but the field and values are still displayed in the JavaScript if a customer views the HTML source for the SoloSubmit page. Not including the JavaScript resolves this issue.
  • The SoloSubmit web page is customized and you do not want to overwrite the customization. For example, you hard code a list of field values in the HTML. If you include the JavaScript, your customization is overwritten. By ignoring JavaScript for the field, the hard coded list values are used.

If neither reason applies and you select a field from the list, it can result in unexpected behavior. For example, you ignore JavaScript for the Component field, which is a child field of the Product field. When SoloSubmit is accessed, Product and Component are populated with the initial values. If the user chooses a different Product, the Component values do not change.

6. Click OK to save the changes.

Remember to provide users and customers with the SoloSubmit URL. To submit issues or feature requests, they open a browser and enter the SoloSubmit URL.