Default Setting Change for Create Ticket Per Affected Members in New Registration Codes

Modified on Fri, May 30 at 11:51 AM

Default Setting Change for Create Ticket Per Affected Members in New Registration Codes


Purpose / Overview

This article outlines a recent enhancement to the Create Ticket Per Affected Member setting in Irth UtiliSphere registration codes. Previously, when new registration codes were added, this setting was enabled by default, leading to a risk of unintended ticket creation during the brief period before an admin could disable it.


To address this, Irth has updated the system behavior so that newly created registration codes will now have the Create Ticket Per Affected Member setting disabled by default.


Enable Settings as System Administrator

  1. Log in as a System Administrator.

  2. Go to Company Setup > Companies.

  3. Select the company you want to modify.
    Image

  4. In the Company Detail, click the Task to Modify the Company.

  5. Under the Add-Ons section, check the box for Create Tickets Per Affected Member.

  6. Click Save.

Enable the Feature Toggle

  1. Navigate to Administration > Toggles.

  2. Search for the toggle named Prevent Default Create Ticket Per Affected Member.

  3. Enable this toggle for the selected company.


Request a Registration Code

  1. Log in as a Company Admin.

  2. Navigate to System Management > Ticket Management > Registrations.
    Image

  3. Click the Task "Request a Registration Code".

  4. Confirm that the task "Select Codes for Creating Tickets Per Affected User?" is available.

  5. Submit a new registration code request.

Approve the Registration Code

  1. Log back in as a System Administrator.

  2. Go to Company Setup > Registrations.

  3. Approve the new registration code request.

Verify Default Setting

  1. Log back in as the Company Admin.

  2. Go to the Registration Code Summary.

  3. Click the Task "Select Codes for Creating Tickets Per Affected User".

  4. Confirm that the new registration code is not selected by default.



Key Benefits / Use Cases:

  • By defaulting the Create Ticket Per Affected Member setting to disabled, this update eliminates the risk of premature or unnecessary ticket creation during the registration approval process. Benefits include: fewer erroneous tickets generated and reduced administrative cleanup and confusion.


Things to Know:

  • User must have administrative credentials to make these changes.

Questions?  Contact us!




Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article