So, is there a Regular read license and a restricted read license? I hope
we get to keep our regular read licenses for some kind of fee! In fact, I
think this change is totally bogus and will probably keep my enterprise from
upgrading. The nice thing about the old Read license was that people could
submit tickets, check the status, and maybe update it if they made a
mistake. Now they won't be able to do any of that - perhaps not even submit
tickets. There had better be a few levels of licensing, including an
inexpensive read license that is equivalent to the old read license.

>-----Original Message-----
>From: Joel Sender [mailto:arslist@EARTHLINK.NET]
>Sent: Tuesday, December 16, 2003 6:12 PM
>To: ARSLIST@ARSLIST.ORG
>Subject: What's Coming in Version 6? Here it is ...
>
>
>**
>Hi Folks,
>I just took the ARS 6.0 Delta class, and, as usual, Doug & his team have
>taken another
>giant step forward. Here's a summary of the features that were covered in
>the class:
>
>
>1. Expect the 'First Customer Shipment' (FCS) in January. No official
>date was announced.
>
>2. SNMP integration is built-in
>
>3. Unicode is supported - just select it during install
>
>4. We loaded two ARS servers on one PC with one Oracle instance
>(different ORA tables)
>
>5. Mid-Tier installed & worked on the first try. Really
>
>6. Licensing is different. You send Remedy support your 'Remedy.lic'
>file and they'll send you the same licenses in the new format.
>
>7. The license tool is now included in the Admin tool, no longer a
>separate program.
>
>8. 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.
>
>9. You can only log on a Userid from ONE IP address. Except Admins
>running the Admin tool or "Read Restricted" users.
>
>10. You can only change a Fixed License entry in User 3 times in a
>WEEK.
>The 4th change locks the userid for 3 DAYS.
>
>11. 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.
>
>12. Server groups can be configured for 'fail-over'. If a server fails,
>it's dedicated function can be automatically picked-up by another server.
>
>13. Licenses are shared across the server group.
>
>14. AR workflow can be 'bundled' in 'Deployable Applications' This is
>different from Mid-Tier deployment. A form can only reside in one
>D.Application.
>
>15. D.Applications can be exported WITH DATA. You specify the import
>tool options when you add the data to the D.Application.
>
>16. 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'
>
>17. You can export a D.Application and LOCK it in 'Read-Only' or
>"Hidden" mode.
>
>18. There are lots of performance logging options for AR System forms.
>
>19. 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
>
>20. Dynamic groups are numbered from 60000 to 60999 and extend 'row
>level' access 'a thousand times'
>
>21. 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.
>
>22. 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.
>
>23. Entry points can be defined for applications, with security access
>control.
>
>24. Fields in forms can be 'automatically' laid out. You turn this on &
>off as needed.
>
>25. View fields are 'filled' in the admin tool to confirm they are
>correct. Once filled, they are not active.
>
>26. Char fields can be 'masked' with asterisks when typed in. The data
>remains in clear text for workflow.
>
>27. Char fields can be non-editable' so only menu choices can be
>entered. You can not type in the field. Automates the $MENU$ function.
>
>28. There's a GUID field that always generates a unique ID across
>servers.
>
>29. The new Windows Global Field remains the same when changing
>entries.
>
>
>30. Active links can execute on "Events" to synchronize multiple open
>windows. You can define 'events'
>
>31. Server-side tables allow filters to perform table operations.
>Reduces network overhead.
>
>32. 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.
>
>33. There are new keywords for multiple open windows, i.e.
>$CURRENTWINID$
>
>34. Remedy will work with developers to license their Deployable
>Applications.
>
>35. Flashboards is included. you can have 6 FB's with the ARS license.
>More that that requires an FB license
>
>36. 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)
>
>37. Mid-tier no longer requires a license, it's included with AR
>System.
>
>
>38. Mid-tier tracks the last time an app was deployed, so it won't
>re-deploy when not needed.
>
>39. Mid-tier an automatically 'deploy' an app when a user requests it.
>
>40. Custom Style Sheets (CSS) is supported.
>
>There's more, and the details go on & on. It was three intense days of
>class
>& labs, and a fourth for the "Exam"
>in order to be RAC certified for ARS 6.0. The labs and test are MUCH better
>than the ARS 5.0 materials - Remedy
>Educational (and everyone else) is clearly out from under Peregrim.
>
>HTH,
>Joel
>
>Joel Sender
>(ARSLIST Backup Admin)
>www.QMXS.com
>JSender@QMXS.com
>
> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
>(Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
>SERVICES at www.QMXS.com This posting was submitted via the Web interface
>
>
>
>UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
>mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
>www.QMXS.com


Have fun customizing MSN Messenger — learn how here!
http://www.msnmessenger-download.com/tracking/reachcustomize

Shannon,

A posting from James Van Sickle earlier this week clarify this;

------

Well, not all users. I got the below offlist reply from a technician at Remedy
about this issue. Based off the below email, you could have a generic login
for multiple users to use as long as the license is Read or Restricted Read.

-James

===========================
Yes, the READ license still exists and works just the same way as
it always has. We are simply adding one new license type,
RESTRICTED READ.

The purpose of the RESTRICTED READ type of license is to allow
the definition of a user who can Submit and Read but under no
condition (no condition means no condition -- even if submitter
locked is set) can they Modify an existing record. By trading off
the ability to Modify, there is no restriction on the number of
users who can be simultaneously connected as this user. This
allows the "anonymous login" for KB review or for surveys or
such with no problems.

The READ type of license still works as it does today, allowing
Submit and Read and even updates if Submitter Locked mode and you
are the Submitter. You are restricted to coming in from a single
station at a given time with this type of license.

A system can have an unlimited number of READ and an unlimited
number of RESTRICTED READ users at any time and there is no charge
for users of either of these types.

So, you should not notice any affect on your current environment.

One additional note, the functionality that restricts to one
machine does have allowance for cases where you forget to logout
at work and have an auto refresh window but you are at home and
want to connect -- or where you wander to a different building and
need to login to do a check from another station. The clients
will prompt you with a note indicating that you are logged in
elsewhere and allow you to "take over" the connection in your
new location. If you then logout of the new location, no one
using your name is on the system and when you get back to your
desk, you are good to go without interruption. If you leave the
new station logged in, then that station holds the connection.
We do restrict the ability to take over to no more often than
every 15 minutes from the last takeover. This eliminates two
users just bouncing a license back and forth, but it does mean
that if you did forget to disconnect from the other station, you
can take over again at a new station after 15 minutes has passed
from the time you initially took over the last time (of course, it
takes you 15 minutes to get from home to work or back to the
original building anyway so there is no real delay -- but you
would have logged out of the new station anyway so there was
no problem in the first place....)

Probably much more detail than you wanted, but I hope this is
useful.

=============================

--
Jarl


> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [mailto:ARSLIST@ARSLIST.ORG]On Behalf Of Shannon Davis
> Sent: 18. desember 2003 15:53
> To: ARSLIST@ARSLIST.ORG
> Subject: "Read Restricted" was Re: What's Coming in Version 6? Here it
> is ...
>
>
> So, is there a Regular read license and a restricted read
> license? I hope
> we get to keep our regular read licenses for some kind of
> fee! In fact, I
> think this change is totally bogus and will probably keep my
> enterprise from
> upgrading. The nice thing about the old Read license was
> that people could
> submit tickets, check the status, and maybe update it if they made a
> mistake. Now they won't be able to do any of that - perhaps
> not even submit
> tickets. There had better be a few levels of licensing, including an
> inexpensive read license that is equivalent to the old read license.
>
> >-----Original Message-----
> >From: Joel Sender [mailto:arslist@EARTHLINK.NET]
> >Sent: Tuesday, December 16, 2003 6:12 PM
> >To: ARSLIST@ARSLIST.ORG
> >Subject: What's Coming in Version 6? Here it is ...
> >
> >
> >**
> >Hi Folks,
> >I just took the ARS 6.0 Delta class, and, as usual, Doug &
> his team have
> >taken another
> >giant step forward. Here's a summary of the features that
> were covered in
> >the class:
> >
> >
> >1. Expect the 'First Customer Shipment' (FCS) in
> January. No official
> >date was announced.
> >
> >2. SNMP integration is built-in
> >
> >3. Unicode is supported - just select it during install
> >
> >4. We loaded two ARS servers on one PC with one Oracle instance
> >(different ORA tables)
> >
> >5. Mid-Tier installed & worked on the first try. Really
> >
> >6. Licensing is different. You send Remedy support your
> 'Remedy.lic'
> >file and they'll send you the same licenses in the new format.
> >
> >7. The license tool is now included in the Admin tool,
> no longer a
> >separate program.
> >
> >8. 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.
> >
> >9. You can only log on a Userid from ONE IP address.
> Except Admins
> >running the Admin tool or "Read Restricted" users.
> >
> >10. You can only change a Fixed License entry in User 3
> times in a
> >WEEK.
> >The 4th change locks the userid for 3 DAYS.
> >
> >11. 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.
> >
> >12. Server groups can be configured for 'fail-over'. If
> a server fails,
> >it's dedicated function can be automatically picked-up by
> another server.
> >
> >13. Licenses are shared across the server group.
> >
> >14. AR workflow can be 'bundled' in 'Deployable
> Applications' This is
> >different from Mid-Tier deployment. A form can only reside in one
> >D.Application.
> >
> >15. D.Applications can be exported WITH DATA. You
> specify the import
> >tool options when you add the data to the D.Application.
> >
> >16. 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'
> >
> >17. You can export a D.Application and LOCK it in 'Read-Only' or
> >"Hidden" mode.
> >
> >18. There are lots of performance logging options for AR
> System forms.
> >
> >19. 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
> >
> >20. Dynamic groups are numbered from 60000 to 60999 and
> extend 'row
> >level' access 'a thousand times'
> >
> >21. 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.
> >
> >22. 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.
> >
> >23. Entry points can be defined for applications, with
> security access
> >control.
> >
> >24. Fields in forms can be 'automatically' laid out. You
> turn this on &
> >off as needed.
> >
> >25. View fields are 'filled' in the admin tool to
> confirm they are
> >correct. Once filled, they are not active.
> >
> >26. Char fields can be 'masked' with asterisks when
> typed in. The data
> >remains in clear text for workflow.
> >
> >27. Char fields can be non-editable' so only menu choices can be
> >entered. You can not type in the field. Automates the $MENU$
> function.
> >
> >28. There's a GUID field that always generates a unique ID across
> >servers.
> >
> >29. The new Windows Global Field remains the same when changing
> >entries.
> >
> >
> >30. Active links can execute on "Events" to synchronize
> multiple open
> >windows. You can define 'events'
> >
> >31. Server-side tables allow filters to perform table operations.
> >Reduces network overhead.
> >
> >32. 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.
> >
> >33. There are new keywords for multiple open windows, i.e.
> >$CURRENTWINID$
> >
> >34. Remedy will work with developers to license their Deployable
> >Applications.
> >
> >35. Flashboards is included. you can have 6 FB's with
> the ARS license.
> >More that that requires an FB license
> >
> >36. 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)
> >
> >37. Mid-tier no longer requires a license, it's included with AR
> >System.
> >
> >
> >38. Mid-tier tracks the last time an app was deployed,
> so it won't
> >re-deploy when not needed.
> >
> >39. Mid-tier an automatically 'deploy' an app when a
> user requests it.
> >
> >40. Custom Style Sheets (CSS) is supported.
> >
> >There's more, and the details go on & on. It was three
> intense days of
> >class
> >& labs, and a fourth for the "Exam"
> >in order to be RAC certified for ARS 6.0. The labs and test
> are MUCH better
> >than the ARS 5.0 materials - Remedy
> >Educational (and everyone else) is clearly out from under Peregrim.
> >
> >HTH,
> >Joel
> >
> >Joel Sender
> >(ARSLIST Backup Admin)
> >www.QMXS.com
> >JSender@QMXS.com
> >
>
> > UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
> >(Support: mailto:support@arslist.org ) ARSList is hosted by
> QMX SUPPORT
> >SERVICES at www.QMXS.com This posting was submitted via the
> Web interface
> >
> >
> >
>
> >UNSUBSCRIBE or access ARSList Archives at
http://www.ARSLIST.org (Support:
>mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
>www.QMXS.com


Have fun customizing MSN Messenger - learn how here!
http://www.msnmessenger-download.com/tracking/reachcustomize

Shannon, The following was posted yesterday concerning read and read
restricted licenses:

Yes, the READ license still exists and works just the same way as it always
has. We are simply adding one new license type, RESTRICTED READ.

The purpose of the RESTRICTED READ type of license is to allow the
definition of a user who can Submit and Read but under no condition (no
condition means no condition -- even if submitter locked is set) can they
Modify an existing record. By trading off the ability to Modify, there is
no restriction on the number of users who can be simultaneously connected as
this user. This allows the "anonymous login" for KB review or for surveys
or such with no problems.

The READ type of license still works as it does today, allowing Submit and
Read and even updates if Submitter Locked mode and you are the Submitter.
You are restricted to coming in from a single station at a given time with
this type of license.

A system can have an unlimited number of READ and an unlimited number of
RESTRICTED READ users at any time and there is no charge for users of either
of these types.

So, you should not notice any affect on your current environment.

Ron Gehring


-----Original Message-----
From: Shannon Davis [mailto:sbrookedavis@HOTMAIL.COM]
Sent: Thursday, December 18, 2003 8:53 AM
To: ARSLIST@ARSLIST.ORG
Subject: "Read Restricted" was Re: What's Coming in Version 6? Here it is
...


So, is there a Regular read license and a restricted read license? I hope
we get to keep our regular read licenses for some kind of fee! In fact, I
think this change is totally bogus and will probably keep my enterprise from
upgrading. The nice thing about the old Read license was that people could
submit tickets, check the status, and maybe update it if they made a
mistake. Now they won't be able to do any of that - perhaps not even submit
tickets. There had better be a few levels of licensing, including an
inexpensive read license that is equivalent to the old read license.

>-----Original Message-----
>From: Joel Sender [mailto:arslist@EARTHLINK.NET]
>Sent: Tuesday, December 16, 2003 6:12 PM
>To: ARSLIST@ARSLIST.ORG
>Subject: What's Coming in Version 6? Here it is ...
>
>
>**
>Hi Folks,
>I just took the ARS 6.0 Delta class, and, as usual, Doug & his team
>have taken another giant step forward. Here's a summary of the features
>that were covered in the class:
>
>
>1. Expect the 'First Customer Shipment' (FCS) in January. No official
>date was announced.
>
>2. SNMP integration is built-in
>
>3. Unicode is supported - just select it during install
>
>4. We loaded two ARS servers on one PC with one Oracle instance
>(different ORA tables)
>
>5. Mid-Tier installed & worked on the first try. Really
>
>6. Licensing is different. You send Remedy support your 'Remedy.lic'
>file and they'll send you the same licenses in the new format.
>
>7. The license tool is now included in the Admin tool, no longer a
>separate program.
>
>8. 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.
>
>9. You can only log on a Userid from ONE IP address. Except Admins
>running the Admin tool or "Read Restricted" users.
>
>10. You can only change a Fixed License entry in User 3 times in a
>WEEK.
>The 4th change locks the userid for 3 DAYS.
>
>11. 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.
>
>12. Server groups can be configured for 'fail-over'. If a server fails,
>it's dedicated function can be automatically picked-up by another
>server.
>
>13. Licenses are shared across the server group.
>
>14. AR workflow can be 'bundled' in 'Deployable Applications' This is
>different from Mid-Tier deployment. A form can only reside in one
>D.Application.
>
>15. D.Applications can be exported WITH DATA. You specify the import
>tool options when you add the data to the D.Application.
>
>16. 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'
>
>17. You can export a D.Application and LOCK it in 'Read-Only' or
>"Hidden" mode.
>
>18. There are lots of performance logging options for AR System forms.
>
>19. 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
>
>20. Dynamic groups are numbered from 60000 to 60999 and extend 'row
>level' access 'a thousand times'
>
>21. 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.
>
>22. 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.
>
>23. Entry points can be defined for applications, with security access
>control.
>
>24. Fields in forms can be 'automatically' laid out. You turn this on &
>off as needed.
>
>25. View fields are 'filled' in the admin tool to confirm they are
>correct. Once filled, they are not active.
>
>26. Char fields can be 'masked' with asterisks when typed in. The data
>remains in clear text for workflow.
>
>27. Char fields can be non-editable' so only menu choices can be
>entered. You can not type in the field. Automates the $MENU$ function.
>
>28. There's a GUID field that always generates a unique ID across
>servers.
>
>29. The new Windows Global Field remains the same when changing
>entries.
>
>
>30. Active links can execute on "Events" to synchronize multiple open
>windows. You can define 'events'
>
>31. Server-side tables allow filters to perform table operations.
>Reduces network overhead.
>
>32. 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.
>
>33. There are new keywords for multiple open windows, i.e.
>$CURRENTWINID$
>
>34. Remedy will work with developers to license their Deployable
>Applications.
>
>35. Flashboards is included. you can have 6 FB's with the ARS license.
>More that that requires an FB license
>
>36. 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)
>
>37. Mid-tier no longer requires a license, it's included with AR
>System.
>
>
>38. Mid-tier tracks the last time an app was deployed, so it won't
>re-deploy when not needed.
>
>39. Mid-tier an automatically 'deploy' an app when a user requests it.
>
>40. Custom Style Sheets (CSS) is supported.
>
>There's more, and the details go on & on. It was three intense days of
>class & labs, and a fourth for the "Exam"
>in order to be RAC certified for ARS 6.0. The labs and test are MUCH better
>than the ARS 5.0 materials - Remedy
>Educational (and everyone else) is clearly out from under Peregrim.
>
>HTH,
>Joel
>
>Joel Sender
>(ARSLIST Backup Admin)
>www.QMXS.com
>JSender@QMXS.com
>
>
> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
>(Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
>SERVICES at www.QMXS.com This posting was submitted via the Web interface
>
>
>
>
>UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
>mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
>www.QMXS.com


Have fun customizing MSN Messenger - learn how here!
http://www.msnmessenger-download.com/tracking/reachcustomize



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
www.QMXS.com

Everyone,

Slow down there...

I think there is some confusion about what things are, and what
things might be. (Since it is the Christmas time, let me speak in terms of
the three "Christmas" Ghosts....) Let me try to summarize this....

Remedy Past Licenses:

Read: Can Create(Submit), Can Read(Query), Can Modify (Under
submitter mode locked conditions)
Fixed: Can Create(Submit), Can Read(Query), Can Modify
Float: Can Create(Submit), Can Read(Query), Can Modify

Remedy Present Licenses: (v5.1.2)

Read: Can Create(Submit), Can Read(Query), Can Modify (Under
submitter mode locked conditions)
Fixed: Can Create(Submit), Can Read(Query), Can Modify
Float: Can Create(Submit), Can Read(Query), Can Modify

All licenses were intended to be used per person, and no
"Global"/"Shared" use of a single 'Login Name' is really covered from a
legal perspective. (Read your license agreement if you must, but I see the
word "individual" in there describing the use of a license. Try to find the
word "Anonymous", "Shared", etc...)(Really all is the same as the "Past")


The following is a forward looking analysis, based on what I have heard
about this new feature. Note I have yet to see this feature in use, and
have not tested this list of assumptions. However this is what I understand
the future to possibly hold.....

Remedy Future Licenses: (>v5.1.2, AKA v6)

Read: Can Create(Submit), Can Read(Query), Can Modify (Under
submitter mode locked conditions), Only from one IP address at a time
Fixed: Can Create(Submit), Can Read(Query), Can Modify, Only from one
IP address at a time
Float: Can Create(Submit), Can Read(Query), Can Modify, Only from one
IP address at a time
Read Restricted: Can Create(Submit), Can Read(Query), Can connect
from more than one IP at a time.

To my knowledge "Read Restricted" will not in anyway further restrict the
ability to "Create". The difference is in the modify logic, and the
connection logic.

( "Read Restricted" ~= "Read" +"Can connect from more than one IP at a
time" - "Submitter mode locked logic".)
The trade off here is that "Read Restricted" kind of equals "Read" if you
add the ability to connect from more than one IP at a time and remove the
Submitter mode locked logic.


So:

You should still be able to use a "Global"/"shared" "Read Restricted"
licenses to do all of your "anonymous" Web (or otherwise) Read/Submit
actions.
You should still be able to use a NON "shared" "Read" license to do all of
your authenticated Web (or otherwise) Read/Submit/Modify using "Submitter
mode locked".
"Fixed" and "Float" can only be used from one IP at a time, but there is no
connection limit. So a user can use the Mid-Tier, User tool, API program
(etc..), all from the same IP at the same time with no problems. (Switching
IP's is possible via a Logout, or "forced take over" action from the new IP
once every 15 minutes.) [So tell your users to logout when they leave a PC.
They should be doing that anyway.]



However, will all new features(and futures).... only time will tell what
really happens.

Hope that helps.

For those of you who choose to "stay at v5", you need to understand
that is only an option for so long. (about 2 years if Remedy's support
model holds true to past events.) At some point Remedy will stop supporting
that version and if you ever need a key change... well you may find them
less likely to help at some point. (Like when they no longer support the
version.)


Furthermore, if you are using the system within the bounds of the
current legal definition of how the system is licensed then I would expect
no technical restrictions in what you can use the system for in the future.
(Maybe a need to alter some implementation choices, like if you give an
account a "Read" vs "Read Restricted" license, but that cost you minimally
the time to make the decision.) WARNING: If you are breaking the rules..
then things might be getting tougher for you to do so.



--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
Never ascribe to malice, that which can be explained by incompetence.