Administration > Events > Event control > Setup activity - robinfeng/beashelp GitHub Wiki
Here, activities are defined.
Field Meaning Event For which event is this activity started? ID Unique ID of this definition Description Description of this definition
Tabs Field Meaning Message Setup, which kind of message is created and what is displayed. Event Under which conditions the activity is created Button 1...3 Up to three buttons can be defined, which will be displayed in the message/activity Recipient Who will receive the message
Message tab Field Meaning Save as Which kind of message is created? Further information see separate table Title Message title (Email, activity...) Message Message text. Place holder are allowed. If the event is linked to a screen, all information from this screen can be accessed. Available variables are displayed at the bottom of the screen. Business partner If an SAP Business One-activity is to be created, enter the business partner ID. Script (return cardcode) Business partner can also be determined per script, is returned in variable ls_cardcode Example: Update customer order setvar=ls_carcode=
Bitmap If the message is saved as "beas event with decision" a bitmap can be displayed. Send report Access to macro system, select the macro to be executed. Send as Determines how the macro is executed Script to create subject and long text Using script the title and long text can be created. Title is returned in Variable ls_subject Message is returned in Variable ls_longtext
Per default these variables are loaded with the text stored in "Title" and "Message" Example: setvar=ls_subject=hello world
Event tab Field Meaning event script Script checks if the activity shall be executed use "return false" to block the creation of an activity Example: (itemchange): the activity shall be created only for material group "A500" select u_gruppe from oitm where itemcode='<e_itemcode>' if <> A500 then return false end if
from, to In which period to create the activity Example: if during late shift (from 18:00 - 23:59) only a message shall be created. Enter a period exceeding midnight (eg. 18:00 - 6:00) is not possible. In that case, two activities are required (eg.: 18:00 - 23:59 and 0:00 - 6:00) Sunday ... Saturday On which weekday to create this activity Example: daily event: the message shall be created only on Wednesday. Remove the hooklet for all other days No message to yourself If you create an event which causes an activity, you can select not to receive the message. Example itemchange: create message only if item was changed by someone else Each message only once If for example 20 changes are made for one item, this would lead to 20 messages. Activate this option to create only one message (if there are no other unconfirmed messages)
Message types Save as Meaning beas event with decision A beas-message with up to three buttons (decision). It can be processed in the message screen quickly. SAP Business One-activity with decision SAP Business One-activity with up to three buttons. Advantage: integrated into the SAP Business One-activity system. Disadvantage: no quick processing. In parallel this message is also displayed in beas-message screen. If the message is closed there, the SAP Business One-activity will also be closed. Command Only the script entered in command-tab is executed. Message without decision Only a pure beas-message is created without decision criteria
Button tab If the message is defined as "beas-message with decision" or "SAP Business One-activity with decision" up to three buttons can be displayed. There, these buttons are defined and filled with functions. Field Meaning Name Button name (displayed in activity) Visible Button visible? Close activity If enabled, the activity is closed after clicking this button Script execution Pressing the button the script is executed. Important: There is no reference to the event or the affected window. That why only variables basenr1, basenr2 and basenr3 are available. basenr1 is of type "Char", basenr2 and 3 of type "Integer" Content of these variables depends on the event.
Example: Event with reference to work order In variables the work order document number is stored Task: call work order document openwindow=fert_fthaupt_edit.psr=belnr_id:
Bitmap If the message is saved as "beas event with decision" a bitmap can be displayed. Script visibility Define the button visibility. Script is executed at the moment the activity is created. All variables and reference to the current window are available. If the script is ended with "return false" the button is no more visible.
Recipient tab Field Meaning Recipient 1...3 Up to 3 recipients can be selected. Not all selected recipients get the message. beas decides according to the following principle:
- is recipient 1 currently logged on in beas (program registration, not attendance) If yes, then he is the recipient. If no:
- is recipient 2 logged on ? If yes, then he is the recipient. If no:
- is recipient 2 logged on ? If yes, then he is the recipient If not, message is sent to recipient 1, even if not logged on. Recipient-Script Use script to determine who will get the message. ousr.internal_k is returned in variable "value".
Example: manager to get the message (User_code=manger) select internal_k from ousr where user_code='' setvar=value=
Command tab This tab is only visible if in Message - Save as "Commando" was selected. Field Meaning Script Window to enter any script
返回 主页