AR System 6.0 Features

Okay, Joel Sender put a pretty comprehensive post out to the list on Dec. 16th. There are probably more items than this, but here's what he had to say after attending one of the 6.0 Delta classes

  • Expect the 'First Customer Shipment' (FCS) in January. No official date was announced.
  • SNMP integration is built-in
  • Unicode is supported - just select it during install
  • We loaded two ARS servers on one PC with one Oracle instance (different ORA tables)
  • Mid-Tier installed & worked on the first try. Really
  • Licensing is different. You send Remedy support your 'Remedy.lic' file and they'll send you the same licenses in the new format.
  • The license tool is now included in the Admin tool, no longer a separate program.
  • There's a new license type: "Read Restricted". It's the same as the old "Read" except that you can't change ANY DATA, regardless of the "Submitter Locked" setting.
  • You can only log on a Userid from ONE IP address. Except Admins running the Admin tool or "Read Restricted" users.
  • You can only change a Fixed License entry in User 3 times in a WEEK. The 4th change locks the userid for 3 DAYS.
  • AR Server groups allow different functions to reside on different servers (sharing a DB instance). Server groups CAN have separate machines for Assignment, DSO, Email, Escalations, Flashboards and FTS.
  • Server groups can be configured for 'fail-over'. If a server fails, it's dedicated function can be automatically picked-up by another server.
  • Licenses are shared across the server group.
  • AR workflow can be 'bundled' in 'Deployable Applications' This is different from Mid-Tier deployment. A form can only reside in one D.Application.
  • D.Applications can be exported WITH DATA. You specify the import tool options when you add the data to the D.Application.
  • Data Archiving has been automated. Open a form in the Admin tool and specify how you want it archived (move or copy, based upon a qualification). The Archive form is automatically generated, with additional fields for the 'Original Entry ID'
  • You can export a D.Application and LOCK it in 'Read-Only' or "Hidden" mode.
  • There are lots of performance logging options for AR System forms.
  • Security groups can be CALCULATED form existing groups. For example, a calculated group could include "Support Managers", "Development Managers" but NOT 'Education Managers". The group numbers are NEGATIVE
  • Dynamic groups are numbered from 60000 to 60999 and extend 'row level' access 'a thousand times'
  • D.Applications don't have security groups, they have "ROLES", which are mapped to local Groups. an application Role can be mapped on each local server to which it is deployed.
  • Any form can be designated as a 'Home Page'. Click the Home Page button and it opens that form. When you logon to AR User, the Home Page opens. Home Pages can have a new field type: "Application List". It will list the Application 'Entry Points" to which the user has access.
  • Entry points can be defined for applications, with security access control.
  • Fields in forms can be 'automatically' laid out. You turn this on & off as needed.
  • View fields are 'filled' in the admin tool to confirm they are correct. Once filled, they are not active.
  • Char fields can be 'masked' with asterisks when typed in. The data remains in clear text for workflow.
  • Char fields can be non-editable' so only menu choices can be entered. You can not type in the field. Automates the $MENU$ function.
  • There's a GUID field that always generates a unique ID across servers.
  • The new Windows Global Field remains the same when changing entries.
  • Active links can execute on "Events" to synchronize multiple open windows. You can define 'events'
  • Server-side tables allow filters to perform table operations. Reduces network overhead.
  • In filters and active links, the IF & ELSE actions can point to different Servers and Forms, based on workflow. If you have one form for customers and another for employees, you can set the FORM name in a field and the FORM specification would have the field name.
  • There are new keywords for multiple open windows, i.e. $CURRENTWINID$
  • Remedy will work with developers to license their Deployable Applications.
  • Flashboards is included. you can have 6 FB's with the ARS license. More that that requires an FB license
  • Mid-tier 6.0 supports BEA Weblogic 8.1 and Apache 1.3.28 and 2.0.43 & Mozilla (Sun 1.2.1, HP. Widows & IBM 1.4)
  • Mid-tier no longer requires a license, it's included with AR System.
  • Mid-tier tracks the last time an app was deployed, so it won't re-deploy when not needed.
  • Mid-tier an automatically 'deploy' an app when a user requests it.
  • Custom Style Sheets (CSS) is supported.
 

 
For comments or questions on this Northwest Remedy User Group website  
please email Geoff Endresen  at nwrug@geoffe.com