• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Integration / Customization IPA/ProcessFlow

Custom Trigger changes - No Work Unit

 6 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Karen Sheridan
Veteran Member Send Private Message
Posts: 142
Veteran Member
8/30/2011 6:37 PM

I have a custom online update (ZZ07 - has supervisor data on it).  I created a End user exit (ZZ07EPD).  On my initial test I had employee number as my only service variable. 
Compiled the user exit, created the service, tied them together, voila - work unit.

Today, I added a few other service variables to the Cobol; added them to the service; recompiled the user exit; no work unit.  No errors in the compile; no errors that I can find in PF, but we have some of the logs turned off because of size issues.

Is there a special order the variables need to be in?
000700 ZZ07ES1-START.
           PERFORM 1000-OPEN-WORKFLOW-DB.
           MOVE "EMPLOYEE"             TO WFAPI-I-VARIABLE-NAME (1).
           MOVE ZZ07F1-MER-EMPLOYEE    TO WFAPI-I-VARIABLE-VAL  (1).
           MOVE "MER_COMPANY"          TO WFAPI-I-VARIABLE-NAME (2).
           MOVE ZZ07F1-MER-COMPANY     TO WFAPI-I-VARIABLE-VAL  (2).
           MOVE "MER_MERIT_LEVEL"      TO WFAPI-I-VARIABLE-NAME (3).
           MOVE ZZ07F1-MER-MERIT-LEVEL TO WFAPI-I-VARIABLE-VAL  (3).
           MOVE "MER_SUPERVISOR"       TO WFAPI-I-VARIABLE-NAME (4).
           MOVE ZZ07F1-MER-SUPERVISOR  TO WFAPI-I-VARIABLE-VAL  (4).
           PERFORM 1000-PROCESS-FLOW.

Is there a log that would help troubleshoot this issue?
Is there a cache that needs to be cleared?
Any help would be greatly appreciated.
Thanks,
Karen
Karen Sheridan
Veteran Member Send Private Message
Posts: 142
Veteran Member
8/30/2011 11:55 PM
I've tweaked and changed and no work unit; stepped away for a while - now its working
Sam Simpson
Veteran Member Send Private Message
Posts: 239
Veteran Member
9/2/2011 2:12 PM
Some applications like AP has to deliver a commit to the database before it can be granted by
the database to proceed with the release of the workunit. If the application tries to process
the workunit before the commit, then the database will deny to grant the authority until such
time a commit has been issued. The database will wait until the next instance of the workunit timer
from the event manager to check if a commit has been issued.

The default for eventMgrWorkunitTimer is 30 minutes. If you want the system to create workunits much faster then set it at 5 minutes (but not lower or it will have high memory usage). This value can be found in the bpm.properties file in LAWDIR/system directory.
Karen Sheridan
Veteran Member Send Private Message
Posts: 142
Veteran Member
9/6/2011 7:23 PM
It turnes out that I needed to implicity pass the service definition from the cobol

Here is an example: 
            IF (CU01F1-FC NOT = "A")
                GO TO CU01ES1-TRANSACTION-END.
               PERFORM 1000-OPEN-WORKFLOW-DB.
                MOVE "CU01E.1_I"              TO WFAPI-I-SERVICE.

Something to do with some OS versions not translating the service name call correctly.

Karen
KK - Infor
Veteran Member Send Private Message
Posts: 61
Veteran Member
9/6/2011 7:35 PM
Karen,
For consistent results, remove the special characters from your service name.
Karen Sheridan
Veteran Member Send Private Message
Posts: 142
Veteran Member
9/6/2011 8:08 PM
KK - The documentation is very specific about you call your service when you are adding a custom trigger in cobol - it is the form name, where the user exit is (B, M, E), DOT, the token number, underscore, the action

CU01E.1_I - is the example that Lawson gave me, but it straight from the developer documentation

Are you saying I should name it something else?

Thanks,
Karen
KK - Infor
Veteran Member Send Private Message
Posts: 61
Veteran Member
9/6/2011 11:31 PM
This used to work fine with PF 8.x; however I've experienced many issues around special characters in PF 9.x.
So, as a practice, I avoid special characters in PFlows.