The Department of Technology Services programmed eRules, the application agencies use to file rules with the Division, to a standard set of specifications. These specifications include operability with Internet Explorer 7 and higher, and Firefox 3 and higher. eRules was not programmed to work with, nor has it been tested with other web browsers.

The Division is aware of problems associated with using other browsers, including Google Chrome, with the eRules application. Validations written into eRules that help agencies make certain that the filing is complete do not work in these browsers. As a result, filings can be incomplete, in which case they are returned to the agency with the potential consequence that publication of the rule, and its eventual effective date, may be delayed.

Please remember that you must use the latest version of Firefox or Internet Explorer when using eRules. You may direct questions or comments about browser requirements to Mike Broschinsky at 801-538-3003.

Yes, it’s possible. Well, probably most things are possible, but this one really is possible. I know because I’ve seen it.

Here’s the scenario. You’re using Internet Explorer (IE) as your web browser. You need to start a rule filing, so you visit the eRules web site, click on “Proposed Rule Types” and start entering data in your form like noboby’s business.

You’re feeling particularly fine and invulnerable that day. You don’t listen to the little voice that says “Shouldn’t you save as draft? Shouldn’t you save as draft?” “No, I don’t need to,” you say. “I just need to do a little bit more and then I’ll be done, and then I’ll save the form. I promise!”

And you go on. Paragraphs of priceless prose proceed to populate the data entry fields. And then it happens…

You look at the Admin. Code Ref. fields. You notice that there’s an extra character in the rule number field. You click in the rule number field, but because you’re in a hurry, not paying attention, and invulnerable, you don’t notice that you clicked next to the field, not in the field. You press backspace, and then, you scream. You scream because you suddenly see the Rule Filing List, not your practically perfect form with paragraphs of priceless prose. They have vanished. They can’t be recovered.

The backspace key in IE performs two functions. The first, and the one you expect, is the delete function if used within a data-entry field. If the cursor is in the field, the field is said to have focus.

The second function, and the one you probably don’t expect, is the “move backward one page in the browser history” function. In other words, if your cursor is not in a data-entry field, if a data-entry field doesn’t have focus, then pressing backspace is just like pressing IE’s back button: you move back in the browser history. If you press the forward button in a (vain) attempt to retrieve your form, you will simply see an empty form.

So the two-part moral: 1) never press the backspace key unless you are certain that your cursor is in a data-entry field; and 2) always use the “Save as Draft” button regularly and frequently.

Yes, a cryptic title. But it makes more sense once you realize that I’m talking about a set of fields in the “Rule Information” box of the proposed amendment form, the change in proposed rule form, and the nonsubstantive change form. The fields are right below the “Utah Admin. Code ref. (R no.)” fields.

The “Changed to Admin. Code Ref. (R. no)” are optional fields (the “Utah Admin. Code ref. (R no.)” fields are not, but that’s another story). They are only to be used in certain very specific circumstances.

Because you crave knowledge, you ask “What are the circumstances when I can use these fields?” I’m glad you asked. These fields are only used when:

• An agency’s title number has changed because the agency is being moved from one department to another;
• A rule is being moved from one title to another; or
• A section of a rule is being moved to a different rule.

In each of these cases, you may use the “Changed to Admin. Code Ref. (R. no)” fields. So, for example, let’s say that the Division of Administrative Rules is moved from the Department of Administrative Services to the Lieutenant Governor’s Office. A proposed amendment for each rule from the Division would be prepared, and the “Changed to Admin. Code Ref. (R. no)” fields would be used to show the new title number:

Remember, these fields are only used when titles, rules, or sections are being moved from one part of the code to another.

An intrepid rulewriter has discovered a bug in eRules: if a user begins a form and tries to save as draft *without* having selected an agency authorizer, *then* an error condition is created that prevents you from later opening that draft.

The workaround is simple: always select an agency authorizer before saving your filing as draft.

This bug is part of a much larger issue that DTS is working to resolve.

Many of you have noticed that there doesn’t seem to be a form for rule amendment any more. If you look closely at the left-hand menu in eRules you seen entries for “Proposed Rule Types” or “Change in Proposed Rule (CPR)” or “Nonsubstantive Change” or something else. But nothing seems to cry out “HI, USE ME TO FILE AN AMENDMENT!”

Amendments, new rules, repeals of rules, and repeals and reenactments of rules are all different types of something called “proposed rules”. A proposed rule is a rulemaking actions that proposes to make some type of substantive change to an already existing rule (amendment, repeal, or repeal and reenact) or proposes to create a rule that has never existed before (new).

Because the questions asked for all proposed rules are exactly the same, eRules has one form, the proposed rule form, to accommodate the different types (new, amend, repeal, repeal and reenact). If you want to file and amendment to an existing rule, click on “Proposed Rule Types” in the left-hand menu. Scroll down the form to the box labeled “Notice Type”. You will see a drop-down list. Click the down-arrow and then select “Amendment”. Then continue to complete the form as you normally would.

Follow the same procedure for a New Rule, a Repeal, or a Repeal and Reenact.

As always, never hesitate to call the Division if you have any questions.

When we began reprogramming eRules, lots of people suggested the same new feature: a spell checker. I agree that this would have been a great addition. However, it wasn’t practical for two reasons:

1. Programming the spell checker would have added enormous cost to the project; and
2. Implementing a spell checker for eRules would have required a server-side solution (the spell checking would have occurred on the web server where eRules resides) which would have slowed down the application

Fortunately, there are alternatives that don’t cost much (or don’t cost at all) that provide spell checking within your browser.

Spell checking in Internet Explorer

Many of you use Internet Explorer. There are at least three possibilities for you; two don’t cost anything while one has a very modest price tag.

A product called IE7Pro (http://ie7pro.com) is available as an add-on for Internet Explorer version 6 and above. IE7Pro is available at no charge.

Another product, this time from Google, called the Google Toolbar (http://toolbar.google.com/) provides spell checking as well as a host of other browser enhancements.

The last product, ieSpell (http://www.iespell.com/) is available for modest licensing fee (see http://www.iespell.com/pricing.html for details)

Spell checking using Firefox

If you have some flexibility in the browser that you use, you may want to try Mozilla Firefox (http://www.mozilla.com/). Firefox has integrated spell-checking.

Remember, though, always check with your IT staff before downloading and installing any software.

Mike