SIT and EIT Seeded components – Applaud Support

The app delivers a number of seeded components to help you configure SITs and EITs quickly:

Three data objects: one for person SITs, one for person EITs, and one for assignment EITs
Three forms with corresponding form handlers, one for SITs and two for EITs.
Template view formulas

Data objects

The following two data objects are provided:

Applaud HR Person SIT. This is used for Person SITs and is based on the database view XXAS_PER_PERSON_ANALYSES_V.
Applaud HR Person EIT. This is used for Person EITs and is based on the database view XXAS_PER_PEOPLE_EXTRA_INFO_V.
Applaud HR Assignment EIT. This is used for Assignment EITs and is based on the database view XXAS_PER_ASG_EXTRA_INFO_V.

These have been carefully constructed to combine all useful information into a single view. The views contain:

Both data in the base Oracle base tables and in the hr_api_transaction tables
Columns for each flexfield segment's id, value, and meaning, eg, SEGMENT1, SEGMENT1_VALUE and SEGMENT1_MEANING
"_P" columns for all pending transaction data. For example, SEGMENT1 (base Oracle value) and SEGMENT1_P (transaction table value).
ID_FLEX_STRUCTURE_CODE (for SITs) and INFORMATION_TYPE (for EITs).

If a new SIT or EIT transaction is made, the _p columns will be populated and the base Oracle values will be empty. If an SIT or EIT is approved, the _p columns will be empty and the base Oracle values will be populated. If an SIT or EIT is being updated and the updates are pending approval, both the base Oracle values and _p columns will be populated.

SIT form

The seeded form is called Person SIT (/public/xxas/emp/view/personsit.xml). Use this with the form handler xxas_person_sit_pkg and the data source Applaud HR Person SIT.

The form contains the following fields:

Field	Description
DATE_FROM	The first day this SIT is effective.
DATE_TO	The last day this SIT is effective.
<SIT Flexfield>	The flexfields for this SIT.
COMMENTS_TO_APPROVER	The workflow comments
ATTACHMENTS	Attachments to upload for the workflow transaction. Uploads here are subject to file upload security. See Forms - File upload security for more information.

EIT forms

The seeded forms are called Person EIT (/public/xxas/emp/view/personeit.xml) and Assignment EIT (/public/xxas/emp/view/asgeit.xml). Use the Person EIT with the form handler xxas_person_eit_pkg and the data source Applaud HR Person EIT; use the Assignment EIT with the form handler xxas_asg_eit_pkg and the data source Applaud HR Assignment EIT.

The forms contain the following fields:

Field	Description
<EIT Flexfield>	The flexfields for this EIT.
COMMENTS_TO_APPROVER	The workflow comments
ATTACHMENTS	Attachments to upload for the workflow transaction. Uploads here are subject to file upload security. See Forms - File upload security for more information.

Template view formulas

Three templates Fast Formula are seeded, which you can copy for your View formulas:

XXAS_EMP_PERSONSIT_TEMPL_FF. Use for Person SITs.
XXAS_EMP_PERSONEIT_TEMPL_FF. Use for Person EITs.
XXAS_EMP_ASGEIT_TEMPL_FF. Use for Assignment EITs.

These display each visible segment as a separate read-only form field. You can alter your copied versions of the Fast Formula if you wish. For example, you might want to:

Hide certain visible segments from showing without disabling the underlying flexfield segment
Hide certain segments from certain groups of people (eg, allow a manager to see a field but not an employee)
Combine multiple similar segments into a single field. For example, if you have a business trip application form and you have 3 separate segments to request up to 3 trips in a single application form, you could combine the view so that the trips show as a bullet-pointed list in a single field
Supplement certain fields with additional bits of information

For more information on configuring view formulas, please see Defining flexible view formulas.

Edit personalization formula

To learn about edit personalization formulas in general, please see Using Fast Formula to personalize forms. In the context of SITs or EITs, you might use the Edit personalization formula to override your underlying flexfield definition at run-time. For example, you could:

Change a field’s label
Make a field read-only
Make a field mandatory
Hide or show a field
Set the value of a field explicitly
Add some tip text beneath a field
Override the value set used to validate a field (must be more restrictive than the base Oracle value set)

All of the above attributes can be set conditionally based on the logic you define. This can be very useful when you have dependencies between fields. For example, you can set one field to be required based on the value of a dependent field. Similarly, you can hide or show fields based on the values in a preceding field.

You are not obliged to set any of the above; if you are happy with the default behavior you do not need to specify an Edit personalization formula.

Sample attributes

The below describes some sample attributes you may wish to override in the Edit personalization formula:

SIT Attribute	EIT Attribute	Description
Segment1_Label	Pei_Information1_Label	The field label of segment/attribute 1, eg, Segment1_Label = 'Fill me in'
Segment5_Enabled	Pei_Information5_Enabled	Whether segment/attribute 5 is editable or not, eg, Segment5_Enabled = 'false'
Segment7_Value	Pei_Information7_Value	The value of segment/attribute 7, eg, Segment7_Value = 'abc'
Segment10_Description	Pei_Information10_Description	The description for segment/attribute 10, eg, Segment10_Description = 'Only enter this if you know the value'
Segment15_Empty_Value	Pei_Information15_Empty_Value	The prompt tht appears inside segment/attribute 15. Eg, Segment15_Empty_Value = 'Enter contact''s name' Note here the apostrophe is escaped using a double apostrophe.
Segment20_List_Provider	Pei_Information20_List_Provider	The list provider for segment/attribute 20, eg, Segment20_List_Provider = 'LOOKUP_TYPE:YES_NO' or Segment20_List_Provider = 'VALUE_SET_NAME:XXX_MY_VSET'
Segment24_Refresh_on_Change	Pei_Information24_Refresh_on_Change	Triggers a re-run of this Fast Formula when segment/attribute 24 is changed, eg, Segment24_Refresh_on_Change = 'true' Note you'll need to set this if you want a $FLEX$ reference to fire on a dependent segment/attribute.

Sample edit personalization formula

This sample Person SIT formula overrides a few field properties and toggles the required flag of Segment18 based on the value of Segment15:

/*======================================================
Formula Name: XXX_BK_SOME_SIT_EDIT
Formula Type: Applaud Assignment
Description:  Sample Edit Formula
=======================================================*/
  Default for Segment15_Value_in is 'Unknown'
  
  Inputs are Segment15_Value_in

  /* Change the Date From field so it’s not required */
  Date_From_required = 'false'

  /* Hide the Start and End Dates on the SIT */
  Date_From_visible  = 'false'
  Date_To_visible    = 'false'

  /* Hide Segment7 */
  segment7_visible    = 'false'

  /* Add Help text for Departure / Arrival Times */
  Segment21_Label = 'Departure Time' 
  Segment21_Description = 'Required only for Local trips'

  Segment22_Label = 'Arrival Time'
  Segment22_Description = 'Required only for Local trips'

  /* Set Training Details to show if Mission Type = Training */

  Segment15_Refresh_On_Change = 'true'

  if Segment15_Value_In = 'TRAINING' then
  (     Segment18_Required = 'true'  )
  else
  (     Segment18_Required = 'false'  )

RETURN
     Date_From_required,
     Date_From_visible,
     Date_To_visible, 
     segment7_visible,
     Segment21_Description,
     Segment22_Description,
     Segment15_Refresh_On_Change,
     Segment18_Required,
     Segment21_Label,
     Segment22_Label,
     Comments_to_approver_visible

Auto setup

When you first install the app, you will run auto-setup. If you have already deployed Oracle self-service SITs and EITs to your user population, auto-setup will automatically configure these in the app. It:

Inspects the menus and functions on your self-service responsibilities that you selected to deploy through Auto setup
Configures SITs and EITs already deployed on these functions. If you have restricted the display of EITs or SITs by personalization the Flex OAF item, it will only deploy those that are specified in this personalization
Respects multiple SIT and EIT functions on a menu and observes the personalizations in each
Also looks at personalizations to the Add, Edit, and Delete buttons and automatically grants access in the app accordingly
Checks that responsibility has access to a given EIT through Information Types Security before granting. This does not apply to SITs.

If you wish to configure additional SITs or EITs after initial deployment, please Configure a new SIT and Configure a new EIT.

Sections in this article