infor.com
concierge
infor u
developer portal
Posts
Categories
Groups
Hubs
Developer
Healthcare
Hospitality
Public Sector
CloudSuites
Aerospace & Defense (LN)
Automotive (LN)
Chemicals (M3)
Corporate (FSM/HRT)
Distribution (Sx.e/CSD)
Distribution Enterprise (M3)
Engineering & Construction (LN)
Fashion (M3)
Food & Beverage (M3)
Healthcare (FSM/HRT)
Industrial (Syteline/CSI)
Industrial Enterprise (LN)
Manufacturing (M3)
Public Sector (FSM/HRT)
Solutions
Supply Chain Management (SCM)
Human Capital Management (HCM)
Events
Groups
Your Groups
User Groups
Migrated Forums
FSM/HCM/S3 - Infor Lawson 10.x
HCM/S3 - Learning and Development
HCM/S3 - Global HR
HCM/S3 - Talent Acquisition
HR Service Delivery
Human Capital Management (HCM) - EMEA
Infor Configuration Management for Service Industries
Lawson - Business Intelligence
Lawson - Financials
Lawson - Human Resources
Lawson - Supply Chain
Lawson - Supply Chain Management
Lawson - Technology
MSCM on Landmark
About
Community News
Email Community Support
Home
Groups
FACTS - Partner Community
7.7 Limit by Terminal feature
Legacy Contributor
During the LA training webinar which took place on 01/21/10, a suggestion was made to use the SSI_BASE value to uniquely identify a physical workstation. I second this request and also would like to request that the SSI_BASE be made case-insensitive. We instruct admins on how to install the FACTS client piece and more often than not when a re-install is needed, the SSI_BASE case is ignored. At least in prior FACTS versions, this led to support calls from users wondering why their various defaults changed (I realize most of these defaults are handled differently in 7.7). I can't think of any reason to keep SSI_BASE case sensitive as it only leads to confusion.
Basing the physical terminal on an IP address is impractical for clients with a large user base and/or with users who connect remotely. DHCP is a more practical IP assignment method in these cases, and trying to base Limit By Terminal on IP address would be difficult to maintain.
Another difficulty with basing Limit by Terminal on FID(0) is for cases where a user opens up a new session of FACTS where a new FID(0) is assigned. Suddenly there may be more FID(0) values that an administrator is not aware of, and would then need to be populated in Program Security Maintenance. I could not tell from listening to the recorded webinar's whether FACTS will automatically populate the file edited by the Enter Terminals button with these new FID(0) values.
Find more posts tagged with
Comments
There are no comments yet
Important Links
Community Hubs
Discussion Forums
Groups
Community News
Popular Tags
CPQ: Ask a Colleague
FAQs, How-To, and Best Practices
Idea
Infor OS Portal
UI Design
CPQ: Tips and Tricks
Infor Homepages
Widget Development
Infor EPM Migration
Infor Ming.le