The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Re-Aligning Form Security?
Posted: 21 Feb 08 1:49 PM
|
Hi folks,
I've got a client running Slx v6.2.3 that wants to allow some new employees to do data entry, but doesn't want them to have access to the tabs, forms and reports that they had previously released to everyone. The only way I could think of to do this was the "hard way" - re-aligning all the various users into groups, and then removing the release to everyone and releasing the individual items to each group as appropriate.
Does anyone have a better idea? I sure hope so as I can see that doing it this way is going to be a royal pain.
|
|
|
|
Re: Re-Aligning Form Security?
Posted: 21 Feb 08 3:16 PM
|
Honestly, this is one of the ideal applications for external development. In other words, write a standalone application that utilizes the slx oledb provider and allows the employees to do the data entry.
This saves the pain of having to edit releases for everyone else since these seem to be a small group of temporary slx users. It also keeps your client from having to spend 1000+ per named user license or additional concurrent user licenses as the external application consumes a single license essentially. |
|
|
|
Re: Re-Aligning Form Security?
Posted: 22 Feb 08 7:49 AM
|
Matt,
Actually.. this approach can be considered a violation of the SalesLogix license.
All users that do "data entry" must have a named (or concurrent) user license.
The legal way to do this is the original approach.. use SalesLogix security the way it was designed to be used... ownership.. releases, etc.
--
RJLedger - rjlSystems. |
|
|
|
Re: Re-Aligning Form Security?
Posted: 22 Feb 08 8:29 AM
|
Interesting. When I took my original slxd certification, granted it was years ago, the instructor and materials implied that this was specifically what this was for. In fact the practical application I had to develop was based on that premise.
I don't doubt you though RJ. |
|
|
|
Re: Re-Aligning Form Security?
Posted: 22 Feb 08 11:57 AM
|
We've got plenty of named (and concurrent) licenses to get the job done, the problem is that they don't want the new data entry people to be able to change data in certain tabs (which they don't need and shouldn't be able to see anyway).
So the original question still is there - is there a way to not have to re-release everything that was released to "everyone" and still keep some users from seeing some tabs / forms / reports?
|
|
|
|
Re: Re-Aligning Form Security?
Posted: 22 Feb 08 12:08 PM
|
We did an external app that allowed a processing center to enter leads into SLX over the internet via a secure web service. The processing center was at a different location than the main office and they had no need for other SLX functions than just the ability to enter in data for leads and contacts. We were told by our Sage rep that all we needed was the external access license for this (although we did end up using named users since they company had way more user licenses then they ended up needing anyway).
We've built endless extenal applications that read/write/etc with the SLX database for customers. AFAIK, all is good as long as you have the external access license and you're not building an app that is meant to replace the SLX client in order to save on licenses. |
|
|
|
Re: Re-Aligning Form Security?
Posted: 22 Feb 08 12:19 PM
|
Right, the external access license was the one we were told to use as well. I didn't specify that. The most recent one was a few months ago for a web interface that inserted records into SalesLogix and the Sage rep told us the same thing.
|
|
|
|
Re: Re-Aligning Form Security?
Posted: 23 Feb 08 10:55 AM
|
The license thing has been passed around several times... I remember Chris Reich (formerly of SalesLogix) posting the "rules" in the Partner NG..
You cannot deploy an external app that replaces the functionality/purpose of the SalesLogix Client and goes around licensing... However, IF you do build a "login" page (and Ryan has an example onthis site) that requires the user to sign in as a SalesLogix (licensed) user - just like the SalesLogix client.. then you are ok... (as long as you are not using the SAME user over and over!)
--
RJLEdger - rjlSystems |
|
|
|
Re: Re-Aligning Form Security?
Posted: 25 Feb 08 9:15 AM
|
| So you can use the external access license then for things like a server component that users do not log in to, but not for a standalone app that users will log in to. Is that what you're saying RJ? |
|
|
|
Re: Re-Aligning Form Security?
Posted: 25 Feb 08 12:49 PM
|
Originally posted by Matt Dockins
So you can use the external access license then for things like a server component that users do not log in to, but not for a standalone app that users will log in to. Is that what you're saying RJ? |
|
That is not correct (not sure if that is what RJ is saying though). You can have external apps that allow individual users to add or change data in SLX as long as the intent is not to replace client functionality with something else to avoid purchasing a license.
It's best to just contact your Sage rep for specific scenarios to make sure your covered for licensing. The whole external license thing has always been something that was never very well explained by Sage and everyone seems to have their own opinion about it. |
|
|
|
Re: Re-Aligning Form Security?
Posted: 25 Feb 08 2:02 PM
|
Originally posted by Ryan Farley
That is not correct (not sure if that is what RJ is saying though). You can have external apps that allow individual users to add or change data in SLX as long as the intent is not to replace client functionality with something else to avoid purchasing a license.
It's best to just contact your Sage rep for specific scenarios to make sure your covered for licensing. The whole external license thing has always been something that was never very well explained by Sage and everyone seems to have their own opinion about it. |
|
Ryan,
Yes.. what you are saying is correct.
However, (as you say) one should consult Sage to be absolutely sure... Sage owns the software.. Sage licenses it directly to th e End User Customer... (it's in the fine print when you install it 
--
RJLedger - rjlSystems |
|
|
|