trigerring a flow via WFWK

I have called WFWK from the JavaScript in Design Studio, so it can probably be done from the MSS code as well.
You need to create a Service and assign it to the flow. After that it is just a question of making an AGS to WFWK with the keys and variables populated.

You can bring up WFWK in LID or Portal and try manually submitting to see what fields are required etc.

The best way to do this is to work-flow enable the Personnel Action. Then when a Personnel Action is added either via the portal PA52 or via MSS-Personnel Actions, the Process Flow will be triggered. There are a number of KB articles on this. See 557613, 130938 to get a start.

I agree with Barb.... You would want to attach a service instead of customizing MSS. There is a standard trigger for personnel actions. It is a little tricky but not too bad with knowledge base articles.

Thanks for your suggestions. The article was pretty useful.

I just found the service i require in personnel action(HRSCHANG - Hour Change) it is already there.
now ,if i am not wrong
1) I need to design a flow using PF designer
2) Link that flow to the HRSCHANG on <server>/bpm/menu.do
Please correct me if i am wrong and if i still need to do additional settings.

Thanks- Vijay

The PA52 trigger is to service "Action Approval". Your ProcessFlow should be developed with right-click Process Properties to that service name. As to your own Personnel action, name it anything you want, e.g. one of mine is FTECHANGE. In bpm/menu.do, create a service called FTECHANGE as an exact copy of Action Approval. Then create your FTECHANGE service criteria definition and service process definition. You don't need to create variables, since the Action Approval variables will be used (though warning - these are delivered incorrectly and need to be fixed, I think there is a KB on that too). It took me a while to "hack through" all this, but now I have 15 or so work-flow enabled personnel actions and customers are very pleased with how it works.

Other good stuff to know:
PA50 is used to work-flow enable your Personnel action (e.g. FTECHANGE).
Any action that is work-flow enabled will be placed on PA53 in an unapproved status so that PA100 will not pickup and process the action before the work-flow is complete.
The work-flow (the process flow you write, e.g. ftechg.xml) must be sure to approve the action before it finishes (via an AGS call to PA53 to set the approved flag) so that PA100 can then process the action.