This page (revision-11) was last changed on 26-Nov-2021 10:22 by kparrott

This page was created on 26-Nov-2021 10:22 by mmcfarland

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
11 26-Nov-2021 10:22 25 KB kparrott to previous
10 26-Nov-2021 10:22 25 KB mmcfarland to previous | to last
9 26-Nov-2021 10:22 25 KB mmcfarland to previous | to last
8 26-Nov-2021 10:22 25 KB mmcfarland to previous | to last
7 26-Nov-2021 10:22 25 KB mmcfarland to previous | to last
6 26-Nov-2021 10:22 25 KB mmcfarland to previous | to last
5 26-Nov-2021 10:22 24 KB mmcfarland to previous | to last
4 26-Nov-2021 10:22 24 KB mmcfarland to previous | to last
3 26-Nov-2021 10:22 24 KB mmcfarland to previous | to last
2 26-Nov-2021 10:22 646 bytes mmcfarland to previous | to last
1 26-Nov-2021 10:22 647 bytes mmcfarland to last

Page References

Incoming links Outgoing links
WEB SERVICES...nobody
WEB SERVICES

Version management

Difference between version and

At line 189 changed one line
The Workflow module is utilized to trigger the calls to this web service. When an update is made on the ASSIGNMENT DETAILS table of POSITION_CODE, GROUP_CODE, EMPLOYMENT_STATUS or WAGE_RATE, the workflow fires and invokes this web service, passing the information as needed. \\ \\
The Work Flow module is utilized to trigger the calls to this web service. When an update is made on the ASSIGNMENT DETAILS table of POSITION_CODE, GROUP_CODE, EMPLOYMENT_STATUS or WAGE_RATE, the workflow fires and invokes this web service, passing the information as needed. \\ \\
At line 191 changed one line
Workflows fire upon the commit of the updated/inserted/deleted data at the database level. If the EMPLOYMENT_STATUS change is one of a defined LEAVE or TERMINATION status, and the date of the transaction is a future date, then no action is taken. \\ \\
Work Flows fire upon the commit of the updated/inserted/deleted data at the database level. If the EMPLOYMENT_STATUS change is one of a defined LEAVE or TERMINATION status, and the date of the transaction is a future date, then no action is taken. \\ \\
At line 195 changed one line
!Workflow UserCalcs
!Work Flow UserCalcs
At line 221 changed 2 lines
!Pro-Active Workflow
For employee status changes dated in the future, which are not handled by the standard workflow, a pro-active workflow must be defined and scheduled to run each day. The UMPWF update process must have the following fields defined:
!Pro-Active Work Flow
For employee status changes dated in the future, which are not handled by the standard work flow, a pro-active work flow must be defined and scheduled to run each day. The UMPWF update process must have the following fields defined:
At line 315 changed one line
As mentioned above in the Workflow UserCalc section, the IMCT form holds the inbound URL, user name and password under the custom key LEAVE BALANCE. \\ \\The fourth sub-key AUTHORIZATION is used to identify the type of security the outbound service uses. \\ \\USERNAME defines the user name and password sent in the header of the request.
As mentioned above in the Work Flow UserCalc section, the IMCT form holds the inbound URL, user name and password under the custom key LEAVE BALANCE. \\ \\The fourth sub-key AUTHORIZATION is used to identify the type of security the outbound service uses. \\ \\USERNAME defines the user name and password sent in the header of the request.
At line 390 removed one line
This page (revision-11) was last changed on 26-Nov-2021 10:22 by kparrottTop