processflow trigger

Do you see a workunit created? ie, is the trigger working but the e-mail failing? I'm not familiar with a service named EMSSAddrChg. Are you sure this wasn't a custom triggered flow in your v9 environment? If so, then you are probably missing some custom code in the EMSS Address Change html/javascript files.

Thanks for the hint; I was able to find the htm page on the server and the javascript that creates the ProcessFlowObject and calls EMSSAddrChg. I'll see if i can debug this.

I don't see a workunit created. I don't think the trigger is working. Where can I check it?

I don't know enough about custom triggered flow to determine if this is one. but I do see in the flows description that it is by created by somebody at lawson.

The EMSSAdrChg service is the delivered service for the address change.

I am assuming you had the address change notification working in V9? Kind of sounds like it - but just checking.

Also - there is a standard delivered flow that does the email notification - I see you said you made a custom one so I was just currious why not use the standard one and customize the email node if you need it customized.

Anyway - if you did have it working in V9 and the move to V10 has caused it to stop. I would check the emssconfig file. I believe there is a setting in there that turns on and off the use of process flow.

In your move to V10, did you also go to IPA from process flow? Based on your notes, it sounds like it but just checking.

When we made the move from V9 to V10 and from PFI to IPA, we had the issue where the address change notifications stopped working and it was related to the settings in emssconfig (I believe - I can double check my notes when I get back to the office) it may have been in another setup file in EMSS but is was definatielty a "flag" item that we had to set to allow IPA to work with the EMSS items (address change, tax changes, direct deposit). Once we set that flag to use process flow (IPA) it all worked.

As Dave says there is a process_flows_enabled flag in emss_config.l that needs to be set to true. Also, I'm assuming the flows and services are installed and enabled in IPA.

FYI the config file is in your webdir/lawson/xhrnet/xml/ directory and is called emss_config.xml and the setting appears to be process_flows_enabled 

 

Thank you for the info. I found our config file in [lawsondir]\web\lawson\xhrnet\xml\config
I set the setting from "false" to "true", restarted but still no go.

I have several other questions if you guys don't mind;
1.) When I finally get the flow triggered, I will see it on Administration>Work Units>Work Units right?
2.) I found this info from the link below; LID:"manage grid list" does not work for me, where can I access the Manage Grid Client?
http://blogs.infor.com/te...omation-integration/

Dave,
We went with IPA when we converted to v10. The custom process flow is just for testing once I get it working I'll switch it over to the standard one. It was working on v9. I downloaded the .xml files on v9 and renamed them to .lpa for v10.

You can't just copy the xml files from v9 to v10. there is a migration process they must go through, and they need to be uploaded into IPA. Alternatively, for ESS, there is a procedure at the end of the ESS installation manual for installing the ones that come with ESS.

and yes, when you get the flow triggered, you will see it in the workunits. However, if it can't be created (i.e. the flow associated with the service doesn't exist), you won't see it. You should not have to go into the Grid to do anything.

Look first at the logs in /bpm/ on the LSF server. You should see something there.

As John said, there are items that have to be converted with the move to IPA. There are references to the Lawson server that need updating to LandMark etc.

Might seem like a basic question but do you have the setup in HS08 (I think that is the form - sorry - I’ll check later). But make sure you have the settings so the change in EMSS is set to send the email.

If you are not seeing a Workunit in the Admin tool under work units then it would lead me to believe it is not even being triggered.

Do you use the tax or direct deposit changes in EMSS? Are those notification processing working?

The grid does give you some insight into what is going on as far as the server level but not necessary to monitor work unit etc. you should be able to see everything needed in the IPA Admin tool.

Thank you very much for taking the time to help. No basic question is too basic for me. This is my 2nd month on the job and I'm swamped with things I need to learn for our upgrade.
My original task was to convert our scheduled process flows in v9 to v10. I used the v9 process flow designer to download the .xml, renamed it to .lpd, edited & tested it in the v10 infor process designer. then upload it into the new server. Got it working through Process Server Administrator.
I noticed the emss addr chg flow in v9 and proceeded to research to get it working in v10.
There are several folders named bpm. are a few folders in \bpm but their dates does not indicate that they've been updated for a few months. even the pfrepository folder do not contain the new flows that I've uploaded.

I'm suspecting that there is a configuration I need to set somewhere. The Infor Process Designer program connects to a different machine. LID connects to another. the people setting us up says that our system have not been federated yet. Could this be the cause triggers are not working?

I found bpm/menu.do "site" in our v9 and v10 system. I'm assuming that service+process flows in v9 was configured here but not anymore in v10?

I also read about WFWK. is this only for v9? (I think we might need to trigger a process flow after the PR160 job finishes and I'm wondering if this is the place to connect them)

Any information will be helpful.

Do you have any triggered flows that are working?
Do you use IPA to manage actions entered on PA52? If so - do those get triggered when an action is submitted?
I am not a systems level technical expert but I do know the systems being set up to talk to each other is important yes - which is where federation comes in. Your IPA system is on Landmark, which (in my experience) is on a separate server most likely and is separate from your S3 system. They do need to be set up to talk to each other for sure.

Do you have any triggered flows that are working?

Looking at the workunits screen, only the scheduled flows that I created are being run.
I believe we don't have any flows running for PA52. (I would see them on the workunits screen right?)

the log files at gen\bpm\LPSforLSF_xx.log have not been updated for a couple of months.
I got wfapi_x.log running by going into /bpm/menu.do and setting Configuration Property-WFCONFIG DEBUG to 1
Entries are created in the log file whenever I do an address change in ESS.

I tried creating a test service in lpaAdmin but WFWK will say service is not defined if I 'Inquire' about it.
should it show up?

I'm very interested to know how your PA52 flow trigger was created.
Would you mind creating a writeup on the steps?

Dave, nevermind the PA52 request.
I'll try to work it out as detailed here:
https://www.lawsonguru.co...d=96&aft=9104&afpg=1

finally got it working; here are some notes:
- HS07 is where email recipient is configured

- our installer performed "pfserv config lps" in LID

- when you test the address change and browser opens a new window or a send email screen opens up, the setting in web\lawson\xhrnet\xml\config is not working. it is sending email manually instead of trying to trigger service to run process flow.
- this document was helpful https://www.inforxtreme.c...HRIG_10.0.7.0_UW.pdf
- last part of document details how to setup service definition for flow
- user needs to have access to WFWK
- test communication by manually triggering the service in WFWW. service name is case sensitive. no drill around available.
- if test successful, workunit will be created.
- test with other browser. service did not trigger with firefox.

- KB 1205851 (copypasta)
Resolution:
If you are using the ProcessFlow solution for emails for EMSS, one reason could be security.
1. In 9.0.1.6 Employee and Manager Self-Service and earlier, we make a DATA servlet call to the LOGAN tables, WFSERVICE, WFSERVPROC through a FIELD parameter) to see if the appropriate EMSS process flow and service has been uploaded to the database. If we find the service and flow, we go on to create the workunit via a call to WEBDIR/bpm/trigger.do and send the appropriate email through the flow. You must make sure that the tables WFSERVICE and WFSERVPROC are accessible in security.
2. Starting with EMSS version 10.0.x, we went to doing a Transaction servlet call to WFWK.1 to create the workunit and kick off the flow. This was done to make the process compatible with LPA. In this case you need to make sure that the user has access to the system code WF, program WFWK and form WFWK.1.