9.188 PUT_PROCESS_ACTIONS
Þ Note: Built-In Function Rules.
Puts the definition of an action bar layout into the definition of the process definition currently being edited by the START_PROCESS_EDIT Built-In Function.
Information passed into this Built-In Function is subjected to the same editing and validation rules as the equivalent online facility provided in a full LANSA development environment.
Special Note: This Built-In Function provides access to very advanced facilities that basically allow RDML functions to construct new RDML functions.
This is a very specialized area that requires very good knowledge of the LANSA product. Use of this Built-In Function in a "commercial" application (e.g. Order Entry) is not normal and should not be attempted.
Þ This is a Specialized Built-In Function for use in a Development Environment only.
For use with
|
LANSA for i
|
YES
|
Do not use on IBM i in an RDMLX partition.
|
|
Visual LANSA for Windows
|
YES
|
|
|
Visual LANSA for Linux
|
NO
|
|
|
Arguments
|
No
|
Type
|
Req/ Opt
|
Description
|
Min Len
|
Max Len
|
Min Dec
|
Max Dec
|
|
1
|
L
|
Req
|
Action Bar Definition List 1.
This working list must contain at least 1 entry and may contain at most 18.
For each entry in this list there must also be an entry in action bar definition list number 2.
Lists 1 and 2 are conceptually just one list that must be passed as two real lists to get around the 256 byte list entry length limit that LANSA imposes.
Each working list entry must have an aggregate length of 200 bytes and be formatted exactly as follows:
From - To Description
1 - 10 A(10) Action Bar Keyword
11 - 13 A(3) AB$OPT Code
14 - 15 P(3,0) Number of Pull Down Options define in following array structures.
16 - 195 A(9*20) Array of 9 x alpha 20 Pull Down Option Descriptions
196 - 200 A(5) Spare area for future expansion of function
|
|
|
|
|
|
2
|
L
|
Req
|
Action Bar Definition List 2
This working list must contain at least 1 entry and may contain at most 18.
For each entry in this list there must also be an entry in action bar definition list number 1. Lists 1 and 2 are conceptually just one list that must be passed as two real lists to get around the 256 byte list entry length limit that LANSA imposes.
Each working list entry must have an aggregate length of 200 bytes and be formatted exactly as follows:
From - To Description
1 - 18 A(9*2) Array of 9 x alpha 2 Accelerator Function Key Numbers.
19 - 45 A(9*3) Array of 9 x alpha 3 PD$OPT identification values.
46 - 54 A(9*1) Array of 9 x alpha 1 initial availability flags.
55 - 144 A(9*10) Array of 9 x alpha 10 function names. Used to indicate name of function within this process that is to be invoked.
145 - 171 A(9*3) Array of 9 x alpha 3 process attachment sequence numbers. Used to specify the sequence number of an "attached" process or function that is to be invoked.
172 - 200 A(29) Spare area for future expansion of function.
|
|
|
|
|
|
Return Values
|
No
|
Type
|
Req/ Opt
|
Description
|
Min Len
|
Max Len
|
Min Dec
|
Max Dec
|
|
1
|
A
|
Req
|
Return code
OK = operation completed
ER = fatal error detected
|
2
|
2
|
|
|
|