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

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

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
29 26-Nov-2021 10:22 9 KB kparrott to previous
28 26-Nov-2021 10:22 9 KB kparrott to previous | to last
27 26-Nov-2021 10:22 9 KB kparrott to previous | to last
26 26-Nov-2021 10:22 9 KB kparrott to previous | to last
25 26-Nov-2021 10:22 9 KB kparrott to previous | to last
24 26-Nov-2021 10:22 9 KB JMyers to previous | to last
23 26-Nov-2021 10:22 9 KB JMyers to previous | to last
22 26-Nov-2021 10:22 9 KB JMyers to previous | to last
21 26-Nov-2021 10:22 9 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
WORKFLOW_SAMPLES
WORKFLOW_SAMPLES

Version management

Difference between version and

At line 1 changed one line
!!!WorkFlow Samples
[{TableOfContents }]
!!!WORKFLOW SAMPLES
----
At line 14 changed 8 lines
#Ensure that the employee is associated to a manager that has an email address indicated on their [IEAS] record. This is required to issue the email to the manager gets sent.
!!Sample 2 - Print Screens of Workflow Action Setup
[wf_9-1.jpg]\\
This figure reflects the WF action setup required to have the user go to the [IEID] screen. Please note that a log will only be generated when a workflow actions is fired.
#Ensure that the employee is associated to a manager that has an email address indicated on their [IEAS] record. This is required to issue the email to the manager gets sent.\\ \\
!Print Screens of Workflow Action Setup
[wf_9-1.jpg]\\
This figure reflects the WF action setup required to have the user go to the [IEID] screen.
%%information Please note that a log will only be generated when a workflow actions is fired.%%
\\
At line 23 removed one line
At line 25 changed one line
\\ \\
At line 27 removed one line
At line 29 changed one line
\\ \\
At line 31 changed 7 lines
This figure reflects the set up required to have the system generate the [RBBS] report.
!!Sample 3 - Set Up Of Workflow UserCalc
[wf_9-5.jpg]
This figure reflects the set up required to have the system generate the [RBBS] report. \\ \\
----
!Set Up Of Workflow UserCalc
[wf_9-5.jpg]\\
At line 59 added one line
At line 61 added one line
This line indicates what will be displayed in the popup message box.
At line 65 changed one line
Below is the line with what will be displayed in the popup message box.
''Please go to the Identity screen and Drivers License information for Employee <<eid.first_name>> <<eid.last_name>>.''\\ \\
At line 67 removed one line
Please go to the Employee Information screen to attach <<eid.first_name>> <<eid.last_name>> picture.
At line 71 changed one line
Below is the line with what will be displayed in the popup message box.
This line indicates what will be displayed in the popup message box.
At line 73 changed one line
Please go to the Benefit Elections screen to complete the necessary information for <<eid.first_name>> <<eid.last_name>>.
''Go to the Benefit Select form and add Benefit Information for Employee <<eid.first_name>> <<eid.last_name>>.''\\ \\
At line 78 changed 3 lines
What you should observe is our system's workflow leading you through a series of screens that have been defined in the New Hire UserCalc above. In addition to having the system navigate you through the required screens, an email will be sent to the manager of the employee being hired into the system. Therefore, the manager must have his email indicated in his [IEAS] screen and the new hire must be associated to this manager through the "Supervisor" in [IEQH].
!!Update the Job Seniority Date Field
What you should observe is the system's workflow leading you through a series of screens that have been defined in the New Hire UserCalc above. In addition to having the system navigate you through the required screens, an email will be sent to the manager of the employee being hired into the system. Therefore, the manager must have his email indicated in his [IEAS] screen and the new hire must be associated to this manager through the "Supervisor" in [IEQH].
\\ \\
----
!!Sample 2 - Update the Job Seniority Date Field
At line 90 changed one line
#Cut an effective record and save.\\ \\\
#Cut an effective record and save.\\ \\
At line 92 changed one line
The figure above displays the variables required for this UserCalc.
The figure above displays the variables required for this UserCalc.\\ \\
\\ \\
----
!!Sample 3 - Send An Email To The Manager At Specific Time Intervals
!Goal
To issue an email to the manager at a time interval of 8 days and 32 days after an employee has been put on leave. These will be future-dated emails and will ask the manager to verify that the employee has submitted the proper paper work, forms that we will call the STO1 and STO2 respectively.
!Notes
In order for the UserCalc to work, the employee must have their current employment status set to "ACTIVE".
!Logistics
The user will go into the [IEAS] screen and change the employment status from ACTIVE to LEAVE and they must also enter a LEAVE DATE. The system will issue an email at 8 days and 32 days after the leave date to remind the manager that they must check to see that the employee has submitted the necessary forms (STO1 and STO2). Since these are future dated emails, you can check the Logs tab of the specific workflow actions to determine if they were processed. Note that the workflow action will not be completed until the future date. You can run the [RMWF] process to provide you a list of the workflow actions and specify the date values in the "From Date" and "To Date" fields.
!Procedure
#Go into [IEAS] for an employee. Ensure that the record you are using is for an employee that is ACTIVE.
#Change the employment status field from ACTIVE to LEAVE.
#Enter a date value in the Leave Date field.
[wf_9-12.jpg]
This figure reflects the [IMWA] setup required for the email notifications. No completion clause is required for these email workflow actions as they are date sensitive not response sensitive. We will use the same action for both emails.
[wf_9-13.jpg]
The figure above describes the variables that are required for this workflow UserCalc.
[wf_9-14.jpg]
[wf_9-15.jpg]
Please refer to the Description section in the figure above, which indicates what will be displayed in the first email notice sent to the manager.
In order to future date the emails a specific number of days is required. Refer to line 30; a variable was created called 1ST EMAIL, which stores date value, specifically the Leave Date plus 8 days. Once it has been stored in the variable it is used in line 40 (in operand 2) to be the date that the email will be issued. The same concept was applied for the second email notice.
[wf_9-16.jpg]
Please refer to the Description section in the figure above, which indicates what will be displayed in the second email notice sent to the manager.
!Conclusion
What you should observe is that in the Logs Tab for the workflow action used in the UserCalc, there will be two entries. For example, the purpose of the first instance of the workflow action entitled "LV EMAIL NOTICE" is to issue the email 8 days after the employee has gone on leave. Therefore, if the employee has been placed on leave on 15-Sep-2007, the due date for this workflow action will be 23-Sep-2007 (+8 Days). With respect to the second instance of it, the due date will be 17-Oct-2007 (+32 Days).
\\ \\
----
!!Sample 4 - Sending An Email To A Specific Identity
!Statement
The company hires a new employee. An email is to be sent to a specific person (Identity) (other than the manager) to inform them to enroll the employee into the company's standard benefit package.
Set up the [IMWA] screen as indicated below.
[wf_9-17.jpg]\\
The person must have an email address in [IEAS] (Prime Assignment) in order for the system to issue the email to a business email account for them.
The following diagram illustrates the UserCalc that calls this workflow action.
[wf_9-18.jpg]
\\ \\
----
!!Sample 5 - Update A Field
!Statement
An employee changes from one unit to another. The Job Seniority Date field is to reflect this change and store the Effective Date as its new value. In this example, it is the Job Seniority Date field that is to be updated.
%%information Please note that for this example, there is no [IMWA] set up required. The update is handled through the UserCalc.%%
The following diagram illustrates the UserCalc that will be initiated to reflect the change in unit.
[wf_9-19.jpg]
----
!!Sample 6 – Create an ICS from Approved Leave Request (Update Outlook/Calandar)
!Goal
To create an entry on the Outlook Calendar when a Leave Request has been approved for an employee or when an employee has been enrolled in a class.
!Notes
For Leave Requests, the person must have an email address in [IEAS] (Prime Assignment) in order for the system to issue the email to a business email account for them.
For enrolling an employee in a class, the person must have an email address in [IEAS] (Prime Assignment), if not, there must be an email address on the [IEPI] (Personal Information).
\\ \\
Set up the [IMWA] screen as indicated below (for Leave Request)
[wf_9-20-2.jpg]\\
\\
Set up the [IMWA] screen as indicated below (for Class Registration)
[wf_9-21-2.jpg]\\
\\ \\
----
![Notes|Edit:Internal.WORKFLOW_SAMPLES]
[{InsertPage page='Internal.WORKFLOW_SAMPLES' default='Click to create a new notes page'}]
This page (revision-29) was last changed on 26-Nov-2021 10:22 by kparrottTop