| 1. |
Create a process
that contains a custom data element and name it
appropriately. |
| 2. |
Create a GUIDE named ”PC:<XXXX>
G<xxxx> <Description>”
”PC:” denotes
that this is custom code
”<XXXX>” is a unique
four letter prefix for all of your code for this
particular custom data. Check existing PC active
links or guides to ensure you are choosing a unique
four character prefix.
”G” indicates that this object
is a guide.
”<xxxx>” is the same
unique four letter prefix but in small characters
”<Description>" is a
short description of what your custom data accomplishes.
An example of a guide name is “PC:IOPP
Giopp Run ProForma Report”
|
| 3. |
Create your active links that
perform your custom actions ensuring you prefix
them with the “PC:<XXXX> G<xxxx>
…” . If you are creating custom
forms for working purposes then also prefix them
with “PC:<XXXX> …”.
An example of an active link name is “PC:IOPP
Giopp00 REP Open Pro Forma”. An example
of a form name is “PC:IOPP Report Generator”. |
| 4. |
Include all of your active
links in the guide you created. |
| 5. |
Include a more detailed description
of your code in the DESCRIPTION field of the guide.
|
| 6. |
Create an active link named
“PP:01 Gcus00 G<xxxx> MyDescription”
where <xxx> is your unique four character
prefix and MyDescription is a brief description
of what your code does. Include a single IF action
calling the guide you previously created to hold
your custom code. |
| 7. |
Change the RUNIF statement
to include “( 'DT_col_Name' = "YYYYYYYY"
) AND ( 'DT_col_Value' = $NULL$ )" where
YYYYYYY is the name of the your custom data. The
last statement ('DT_col_Value' = $NULL$) is optional
as this will ensure that your code will only fire
once provided it pushes a value back into the
data element. |
| 8. |
Include the Active Link you
have just created at the end of the “PP:01
Gcus Custom Actions” guide. |
| 9. |
Ensure your code returns a
value on completion to the PP:11 Data form where
the HE_Data_ID field is equal to DT_col_ID field
on the “PP:01 Progress” form.
Be as descriptive with your feedback as possible
to avoid confusion. The value you push will appear
in the VALUE field of the custom data element.
|
| 10. |
Your code will now run every
time focus is set to a custom field named according
to your code. |
