Páginas filhas
  • Task Control (ACDA180 - SIGAACD)

Versões comparadas

Chave

  • Esta linha foi adicionada.
  • Esta linha foi removida.
  • A formatação mudou.


Use the Task Control process to send messages with tasks, to an operator, requesting their execution in the system.  The operator can receive a message via RF Pickup and automatically run a routine, without running through menu options. For this process to occur, the person responsible must add a task for this routine, entering the code of the operator receiving the message, the body of the message, the status, the routine to be executed and the keyboard buffer. The operator has access to the messages in the RF Pickup through the Messages routine.

The process also allows any existing idle operator in the system to run an unread task, eliminating the need to attach it to a particular operator, so long as the person in charge of the register leaves the CBF_PARA field blank. Upon reading the message, the operator becomes responsible for the task, which may return and become pending to any other operator if, while editing, the person responsible for task control clears the contents of field CBF_PARA.

Important: If the routine to be executed is not entered, the operator receives only the message.

If a message is received and the execution of the task is not confirmed, its status becomes pending, expecting to be finalized. To execute a task, the operator must access the Messages routine, select the message and press the ENTER key.



Procedures

To add task control:

  1. In Task Control, access Add.
  2. Enter field values as detailed below:
  • To (CBF_PARA): Code of operator responsible for the task. To grant all operators access to the task, leave field blank.
  • Subject (CBF_MSG): Message content viewed by operator.
  • Status (CBF_STATUS): Status of message.
  • Routine (CBF_ROTINA): Name of routine called when operator confirms task execution.
  • Keyboard (CBF_KEYB): A chain of characters containing buffered data for the execution of specified routine.

3. Check the data and confirm addition.


Usage example:

We need operator 000001 to request 10 units of product PA-001, using the 501 transaction type in the Internal Transactions routine.

To (CBF_PARA):                   000001

Subject (CBF_MSG):             Proceed with request of product PA-001

Status (CBF_STATUS):         Not Read

Routine (CBF_ROTINA):       ACDV130

When adding the task, we already need to know the size of the Fields in the Internal Transactions routine in order to correctly register the character chain. Let us consider, for this example, that the flow of the routine is to fill out the fields below:


 


Given this structure, we must register the Keyboard with the data we have, considering the total size of all fields to be filled out:

Keyboard (CBF_KEYB):         501PA-001                                          01           10

Notice the need to link together all the task data, considering the size of each field of the routine. When the operator executes this task via RF Pickup, the routine is loaded with all data filled out, requiring only confirmation.



Notes:

  • To add tasks for the other routines, you must know each field called, in the sequence they are called, to correctly assemble the character chain.
  • The Keyboard field does not accept ADVPL formulas, only the character chain.