Category Archives: eRules

Update to eRules Scheduled

The Division of Administrative Rules has scheduled an update to the eRules application.  State agencies use eRules to file administrative rules and that the Division uses eRules to publish administrative rules in the Utah State Bulletin.  The changes in this update are in response to feedback the Division has received.

The update is scheduled for Wednesday, November 14 at 10 AM.  Users will be notified before the system is taken down.

This update includes a number of changes that will directly affect rulefilers.

  1. The “Rule Filing List” that appears on the main screen has been changed.  A check box has been added next to the filter button to allow users to list all filings.  A new column has been added to show the filing effective date, if one has been set.  Column headings have now been enabled as links.  Clicking a column heading link will sort the column content for all filings that appear on the screen.  Filter options have been debugged so that the “Date Range” filter no longer conflicts with the “Year Filter”.
  2. A form may now be saved as a draft without completing the “Agency Authorization” section.
  3. The “incorporation materials” fields (box 11) have been changed.  Field names have been clarified to provide better instructions.  For incorporated materials that have a complete date as the issue date, use the “Date Issued (mm/dd/yyyy)” field.  For materials that have only a partial date (month and year, or just year), use “Issue, or version (including partial dates)” field.  A bug that prevented the “Add Additional Materials” button from working properly has been resolved.
  4. eRules now requires rulefilers to use Firefox or Internet Explorer.  DTS developed eRules to work with Firefox and Internet Explorer.  Using other browsers circumvents the edit checks built into eRules that prevent incomplete filings from being submitted.
  5. Content in the “Attention” box on the initial screen has been updated.  Support hours have been corrected.
  6. The Notice of Effective Date form has been updated.  In box 3, the field name has been changed to “Effective Date: (mm/dd/yyyy)” to clarify the date format required.  The system will not permit the effective date to be entered with hyphens.  In addition, the effective date field now validates that the effective date entered falls within the parameters set by statute (from seven days following the close of public comment through 120 days after publication).  PLEASE NOTE:  This change to eRules will change the way agencies process effective dates for filings on which they have submitted a Change in Proposed Rule (CPR).  Before this change, the Division asked agencies to make both a Notice of Change in Proposed Rule, and the Notice of Proposed Rule upon which the CPR was based, effective at the same time.  Now, the agency will make only the final Notice of Change in Proposed Rule effective.  The Division will set the effective date for the corresponding Notice of Proposed Rule.  The end result is still the same:  when a change in proposed rule is made effective, all of the underlying filings on which it is based must also be made effective (see Subsection 63G-3-303(1)).

The left navigation links have been modified.  Now, an agency rulefiler will see only those filing types the rulefiler is authorized to submit. Other changes that affect the publication side of the eRules application are also included in this update to eRules.

  1. The underlying software on which eRules relies to create the Utah State Bulletin (OpenOffice.org) has been updated.  This resolves several publication production problems.
  2. The output of the Utah State Digest was updated to make formatting consistent throughout the document and minimize editing required prior to distribution.
  3. DTS verified that the e-mail notification functions of eRules will continue to function as the state migrates to Gmail.

Questions about these changes may be directed to Mike Broschinsky (801-538-3003).

Changes to eRules

On August 24 and August 25, several changes were made to the eRules application.  Three of the changes were based on feedback we received from agency rule filers.  We hope that they will improve the usability of the application.  These changes:

  • fix the problem of old, resolved correction notice reappearing when a new correction is requested;
  • add text to the login page indicating that only Firefox and Internet Explorer are supported browsers and increase the size of the “Login” link; and
  • add text in the left navigation menu under “Proposed Rule Types” that lists the different types of proposed rules, all of which can be filed by clicking on the “Proposed Rule Types” link.

Notice of these changes was sent out over the eRules ListServ.  If you aren’t receiving those notices, and you’d like to, or if you have questions about these changes to eRules, please contact Mike Broschinsky at 801-538-3003.

Are Your Agency Contacts in eRules Current?

The next time you file a rule, look at the names listed under the “Contact Person(s)” and “Agency head or designee” scroll boxes.  If the names listed for your agency are not current or complete, please send an e-mail to “Administrative Rules” or rules “at” utah.gov and notify us of changes.   We use the contact information in eRules to notify agencies of rules due for review, rules about to expire and lapse, to forward questions about your agency’s rules, and for other communications.

eRules Browser Requirement

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.

eRules Manual Available

The Division has issued ERules for Agencies, an agency user manual for eRules.  It is available from the eRules help page.   It is available in HTML, PDF, and epub (for your ebook reader) editions.

Rulemaking Training Scheduled for December 16, 2009

The Division of Administrative Rules has scheduled two rulemaking training sessions for Wednesday, December 16, 2009.  Both sessions will be held in 4112 State Office Building, Salt Lake City.  The 8:30 AM to 11:30 AM session will provide a basic rulewriting process review for state rulewriters.  The 1:30 to 4 PM session will be a free-form question and answer session for novice and more experienced rulewriters alike.

Seating is limited.  State rulewriters may make a reservation by sending an e-mail to smanousa@utah.gov.   Please include the attendee’s department and division name, and phone number.  Please indicate which training session(s) you wish to attend.   If you have questions about the training, please call Sophia at 801-538-3764.

Backspace + IE = “I’ve lost my form!”

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.

“Changed to Admin. Code Ref. (R. no)”

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:

changed-to2

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

eRules Training Handouts

For those of you who attended training on September 16, you’ll recall that we pointed you to a copy of the notes the presenter used for the training. We posted that copy to the Division of Administrative Rules’s website. There are three ways to get to those materials.

  1. Go to the Division’s home page; click on “Rule Filing Agency Resources (eRules)”; click on “Help for eRules”; then scroll down the page to the section that talks about training;
  2. Log into eRules; click on the “Help” link in the left-hand menu; then scroll down the page to the section that talks about training; or
  3. Use this direct link: http://www.rules.utah.gov/eRules/2009-09-16-eRulesTrainingOutline.pdf.

Thanks to everyone who attended the training on September 16th. For those who are signed up for the training on the 24th, we look forward to seeing you!

If you haven’t signed up for training yet, and you would like to come on the 24th, please contact the Division.

Bug when trying to save a filing as draft with no agency head selected

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.