Ir al contenido principal

How to manage user timeouts in Sage Enterprise Management (v6 and lower)


Description
  • How to manage user timeouts in Sage Enterprise Management .
  • Time Out Management
  • Parameters - TIMEHGUP1, TIMEHGUP2, TIMEHGUP3
Note: This article applies to Enterprise Management v6 and prior.
For Enterprise Management v7 and higher, see KB article 41016 below.


Resolution
Note: This article applies to Enterprise Management  v6 and prior.  For Enterprise Management v7 and higher, see KB article 41016 below. (41016)
  • The Parameters TIMEHGUP1, TIMEHGUP2, TIMEHGUP3 can be set at the User level
    • Parameter Definition tab of the User - under Module - Supervisor and Group - SES
  • Parameter - TIMEHGUP1
    • This is the time limit, in seconds, that the user has not used the keyboard before which a message is displayed indicating that a user disconnection is imminent. 
    • If nothing has been entered on the keyboard after a second time delay defined by the TIMEHGUP2 parameter, the user will be disconnected.
  • Parameter - TIMEHGUP2
    • This parameter is used to define the time delay, expressed in seconds, during which a message indicating that a user disconnection is imminent is displayed, for the reason that nothing has been entered on the keyboard during the disconnection time delay defined by the TIMEHGUP1 parameter (for a primary session) or the TIMEHGUP3 parameter (for a secondary session), while the user interface has been waiting for an entry.
    • If nothing has been entered after this second time delay, the user is disconnected
  • Parameter - TIMEHGUP3
    • This parameter is used to define an inactivity delay for the keyboard for a secondary session, expressed in seconds, after which a message indicating that a user disconnection is imminent will be displayed during a number of seconds expressed by the TIMEHGUP2 parameter.
    • If the user does not intervene during this second time delay to cancel the disconnection process, the secondary session is stopped.


Related resources
Error: Your convergence sessions have been closed because of timeout (How to manage timeouts in v7 and higher with Syracuse) 
Category
Configuration
Settings and preferences

Entitlement
Open

Entradas populares de este blog

Valores de fstat

Fstat fstat  is a numeric status that is returned upon execution of a database operation, a sequential file operation, or a lock instruction. Syntax fstat Examples # MYTABLE is a table with a key called KEY1, that has a unique component called KEYVAL # Create a record in the table MYTABLE with they key value 1 if it doesn't exist Local File MYTABLE [MYT] Read [MYT]KEY1=1 If fstat [MYT]KEYVAL=1 : Write [MYT] If fstat MSG="The key was created in the mean time" Else MSG="Key created" Endif Else MSG="Key already exists" Endif Details fstat  is always set to '0' if the operation is successfully completed, and has a non-null value if there is an error: In a sequential read ( Getseq  and  Rdseq ),  fstat  is set to '1' at the end of the file. On  Lock ,  fstat  is set to '1' if the lock could not be performed. For a database operation ( Read ,  Look ,  Readlock ,  For ,  Write ,  ...
Leer más

How to create an additional line text (ACLOB) on purchase orders for internal notes

Sin conexión Kyle Klinger hace 1 día Origen:  https://www.sagecity.com/support_communities/sage_erp_x3/f/sage-x3-general-discussion-forum/143870/how-to-create-an-additional-line-text-aclob-on-purchase-orders-for-internal-notes I was trying to add internal notes to the purchase orders at a line level and was thought I would share a how to.  If you have a better way, please share.     Add column to PORDERQ; YLINTEX2, Type TXC   Save and validate table This is where the ID of the text will be stored at the record level, i.e. POQ~00000007, this is similar to field LINTEX  On screen POH2 Add column YLINTEX2, to Block 1. Most likely you will want this field to be hidden. On column NBLIG add a button action ACLOB2, description "Text internal" This button action will require an action parameter "CODE2", it will not be available until after save. Set the parameter "CODE2" to [M:POH2]YLINTEX2(nolign-2), the field that was just added....
Leer más

3 ways to send a mail from code in Sage X3, with more attachments too

Origen Fuente:  https://en.sagedev.it/sagex3/send-mail-from-code-with-attachments-sage-x3/ Autor:  https://en.sagedev.it/category/sagex3/ In this post I’ll show you how to send a mail from adonix code in Sage X3. The points we will face are: 1) Meladx/Send introduction 2) Sending  through  meladx (the best way for me: at the end with just a single code line you send a mail!) 3) Sending  through  Workflow 4) Sending  through  ENVOI_MAIL(…) From AWRKMEL Sending mail from code in Sage X3: Send vs meladx Sage X3 has two native ways for sending mails. The first way is  meladx  executable file, that you can find in  runtime\bin  directory. The seconde one is Send instruction, that was used to send mail through an application of the client station (for more information on “Send GSERMES”  go here ). The Meladx executable Meladx send messages through SMTP/POP3 protocols by means of the mail  ...
Leer más