This page (revision-54) was last changed on 26-Nov-2021 10:22 by Kevin Higgs

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

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
54 26-Nov-2021 10:22 12 KB Kevin Higgs to previous
53 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
52 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
51 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
50 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
49 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
48 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
47 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
46 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
45 26-Nov-2021 10:22 12 KB Meg McFarland to previous | to last
44 26-Nov-2021 10:22 12 KB kparrott to previous | to last
43 26-Nov-2021 10:22 12 KB kparrott to previous | to last
42 26-Nov-2021 10:22 12 KB kparrott to previous | to last
41 26-Nov-2021 10:22 12 KB kparrott to previous | to last

Page References

Incoming links Outgoing links
IMWA
IMWA

Version management

Difference between version and

At line 8 changed one line
;[Action|EVENT_CODE]:Action is a user-defined code that uniquely identifies the workflow action item. Action is tied to the database column Event_Code which is a 16 character alphanumeric mandatory field that the user must manually enter. It is through the event code that the workflow action is referenced in a workflow usercalc.
;[Action|EVENT_CODE]:Action is a user-defined code that uniquely identifies the workflow action item. Action is tied to the database column Event_Code which is a 16 character alphanumeric mandatory field that must be manually enter. It is through the event code that the workflow action is referenced in a workflow UserCalc.
At line 28 changed 5 lines
* ''User' - If this recipient type is used, ensure that the User has been set up properly in IMUS with the email address stated there (for workflow actions that are issuing emails). If the email address on the [IMUS] record is blank then IF there is a person filled in on the IMUS record the system will try to retrieve the email address from the "Employee".
* ''Employee'', ''Manager'', ''Current Identity'' or ''Specific Identity'' - If one of these recipient types is used, then ensure that the email address is stated on the person's Prime assignment record ([IEAS]). When an email is issued and this recipient type is used, the system will go to the employee's IEAS screen and read the email address from there. If there is no email address on the employee's Prime assignment, the system will go to their Personal Information ([IEPI]) to retrieve the email address. If their [IEPI] record does not have an email address, no email will be sent.
* ''Business Contact'' - If this recipient type is used, ensure that the contact has been set up on [IECI] with the email address stated there. It is important that the business contact have a contact type value of "Business Contact" for their IECI record in order to select the contact as the recipient type in the usercalc.
* ''Candidate '' - If this recipient type is used, ensure that the email address is stated on the candidate's profile record (IRCA).
* ''People List'' - If this recipient type is used; ensure that the email address is stated on the Person's Assignment record that the people list detail record points to. Again if one is not found on that Assignment the person information record will be checked for one.
|User|If this recipient type is used, ensure that the user has been set up properly in [IMUS] with the email address stated there (for workflow actions that are issuing emails). If the email address on the [IMUS] record is blank then IF there is a person filled in on the IMUS record the system will try to retrieve the email address from the "Employee".
|Employee'', ''Manager'', ''Current Identity'' or ''Specific Identity''|If one of these recipient types is used, then ensure that the email address is stated on the person's Prime assignment record ([IEAS]). When an email is issued and this recipient type is used, the system will go to the employee's [IEAS] screen and read the email address from there. If there is no email address on the employee's Prime assignment, the system will go to their Personal Information ([IEPI]) to retrieve the email address. If their [IEPI] record does not have an email address, no email will be sent.
|Business Contact|If this recipient type is used, ensure that the contact has been set up on [IECI] with the email address stated there. It is important that the business contact have a contact type value of "Business Contact" for their [IECI] record in order to select the contact as the recipient type in the UserCalc.
|Candidate |If this recipient type is used, ensure that the email address is stated on the candidate's profile record [IRCA].
|People List|If this recipient type is used; ensure that the email address is stated on the person's assignment record that the people list detail record points to. Again if no address is found on that assignment record, the person's information record will be checked for one.
At line 34 changed one line
;[Category|EVENT_CATEGORY]: This is a user-defined field that uniquely identifies the category to which the workflow action belongs. This field is for information purposes only and has no functionality behind it. There is only 1 supplied option (Not Specified) to select from; however, users can create new lexicon values accordingly.
;[Category|EVENT_CATEGORY]: This is a user-defined field that uniquely identifies the category to which the workflow action belongs. This field is for information purposes only and has no functionality behind it. There is only one supplied option (Not Specified) to select from; however, users can create new lexicon values accordingly.
At line 36 changed 6 lines
|Reports | Launches a Report. When this value is used the report that is specified is launched automatically (i.e. USPA)
|Forms | Launches an screen form (i.e. IEPI).
|Oracle Discoverer | Creates a list of subjects that Discoverer could report on.
|Message | Creates a task that is displayed on the Workflow Tasks Screen.
|Email | Allows for emails to be issued from within the application.
|ODBC | Creates a list of subjects that an ODBC link could merge from. When this event media type is used, a record is created with ties to the following [views|TABLES and VIEWS] in the database: [P2K_AM_VMWF_CONTACTS], [P2K_AM_VMWF_IDENTITIES] and [P2K_AM_VMWF_USERS]. These are views and the data within these can be reported on using [Discoverer|DISCOVERER].
|Reports | Launches a report. When this value is used the report that is specified is launched automatically (i.e. USPA)
|Forms | Launches an screen form (i.e. IEPI).
|Oracle Discoverer|Creates a list of subjects that [Discoverer|DISCOVERER] could report on.
|Message|Creates a task that is displayed on the Workflow Tasks Screen.
|Email|Allows for emails to be issued from within the application.
|ODBC|Creates a list of subjects that an ODBC link could merge from. When this event media type is used, a record is created with ties to the following [views|TABLES and VIEWS] in the database: [P2K_AM_VMWF_CONTACTS], [P2K_AM_VMWF_IDENTITIES] and [P2K_AM_VMWF_USERS]. These are views and the data within these can be reported on using [Discoverer|DISCOVERER].
At line 43 changed one line
;[Type Reference|MEDIA_NAME]: The Type used depicts what type of value needs to be entered here. For example, if the type is set to "Reports" then the value to be entered here must be the function name of the report to be run.
;[Type Reference|MEDIA_NAME]: The type used depicts what type of value needs to be entered here. For example, if the type is set to "Reports" then the value to be entered here must be the function name of the report to be run.
At line 52 changed one line
For Forms, the value stored in this field will be the name of the function you are referencing. For example, if the intent of the workflow action is to navigate to the IPRLU screen then the field should be set to "IPRLU".
For Forms, the value stored in this field will be the name of the function you are referencing. For example, if the intent of the workflow action is to navigate to the [IPRLU] screen then the field should be set to "IPRLU".
At line 59 changed one line
;Report Parm Set: The LOV contains a list of all [parameter sets|PARAMETER SETS] that were created. For example, if the Type is set to Reports and the report is for USPA, if a user has created a specific parameter set for USPA, then that parameter set can be specified.
;Report Parm Set: The LOV contains a list of all [parameter sets|PARAMETER SETS] that were created. For example, if the Type is set to Reports, the report is for [USPA], and a user has created a specific parameter set for [USPA], then that parameter set can be specified.
This page (revision-54) was last changed on 26-Nov-2021 10:22 by Kevin HiggsTop