B Updating Workforce and Strategic Workforce Planning Artifacts
Overview
Enhancements available in certain releases, described here, require updates to some provided artifacts.
- If you haven't modified these artifacts (described in this topic), the artifacts and features are available to you automatically with the release.
- Because customized artifacts aren't updated during a new release, if you've customized these artifacts and want to take advantage of the new features, perform these steps:
-
Perform a full backup after the update and download it locally.
- Review the list of modified artifacts and consider whether the enhancements in the monthly update address the modifications you've made to artifacts. Evaluate whether you want to restore the modified artifacts to take advantage of the new features, and whether you will need to reapply some or all of your modifications.
Tip:
For any artifacts listed below that you have modified, consider creating a copy of your modified artifact and using that as a reference for the changes you made to it.Note:
Obsolete artifacts remain available for your use but will no longer be enhanced and could be removed from active forms, menus, dashboards, and so on. - After the update, reverse the customizations to the artifacts you've identified to restore the artifacts to the provided format. See Reversing Customizations.
- Reimplement your customizations to the artifacts, if necessary.
- For any restored Calculation Manager rules or templates, after they are final, be sure to deploy the updated rules or templates to the application for any impacted artifacts. See Showing the Usages of a Custom Template and Deploying Business Rules and Business Rulesets.
May 2024
The following information describes new and modified artifacts in the May 2024 update.
Table B-1 May 2024
Artifact Type | Modified Artifacts | New Artifacts |
---|---|---|
Templates |
|
|
Dimension Members |
OWP_Calculated Max Value OWP_AGE OWP_Age Band |
October 2023
The following information describes new and modified artifacts in the October 2023 update.
Table B-2 October 2023
Artifact Type | Modified Artifacts | New Artifacts |
---|---|---|
Templates |
|
|
Forms |
|
|
Member Formulas |
|
|
New Members Added in Account Dimension |
|
|
New Members Added in Property Dimension | OWP_Workforce Members For Forms (Shared hierarchy) |
May 2023 Update
The following information describes new and modified artifacts in the May 2023 update.
Table B-3 May 2023
Artifact Type | Modified Artifacts | New Artifacts |
---|---|---|
Forms |
|
|
Templates |
|
OWP_Custom Template |
Global RTP | Department—Global RTP created at the rule level for these
rules:
|
|
Global RTP | DepartmentFrom—Global RTP created at the rule level for these
rules:
|
|
Account Members | Formulas were updated for these members:
|
November 2022 Update
The following information describes new and modified artifacts in the November 2022 update.
Table B-4 November 2022 Update
Artifact Type | Modified Artifacts | New Artifacts |
---|---|---|
Groovy Templates | OWP_Process Master Data_T |
October 2022 Update
The following information describes new and modified artifacts in the October 2022 update.
For information about important tasks that you must complete immediately after updating the Workforce October 2022 content, see Post Update Tasks.
Review the following important information about artifacts you might have customized:
- If you have modified the Calculation Manager template for OWP_Change Existing Details_T, but not the Groovy template (OWP_Change Requisition_GT), you must restore the Calculation Manager template.
- If you have modified the Calculation Manager template for OWP_Enable Job_T, but not the Groovy template, you must restore the Calculation Manager template.
For information about restoring artifacts, see Reversing Customizations.
Table B-5 October 2022 Update
Artifact Type | Modified Artifacts | New Artifacts |
---|---|---|
Member Formulas |
|
|
Groovy Rules |
|
|
Templates |
|
|
Rules |
|
|
Forms |
|
|
User Variables |
|
|
Data Load Templates |
|
|
Accounts Enabled in the Reporting Cube |
|
|
Data Maps | Headcount Data for Reporting | |
Members |
|
April 2022 Update
The following information describes the modified artifacts related to the support of Essbase Hybrid Block Storage Option (BSO) cubes in Strategic Workforce Planning.
Table B-6 April 2022 Update
Artifact Type | Modified Artifacts |
---|---|
Calculation Manager Templates |
|
Members |
|
December 2021 Update
The following information describes new and modified artifacts related to the performance enhancements in the December 2021 update.
All Workforce and Strategic Workforce Planning rules and some member formulas have been updated with changes to enhance performance. There are no functional changes but the logic has been updated to leverage performance gains in the underlying technology. Any rule or member that is unmodified will automatically receive these performance enhancements. Any modified rule or member will remain as-is without these performance enhancements. Oracle recommends restoring these artifacts to their original state to uptake these performance enhancements and reapplying your modifications to the updated logic, if necessary.
Additionally, a new rule, Calculate Employee Compensation for All Data (or Calculate Job Compensation for All Data in a Job only model) allows administrators and power users to calculate compensation for all data within their scope.
Note:
In Workforce, when Hybrid is enabled, because Employee and Job dimension are expected to be set with all parents aggregated dynamically, Workforce does not aggregate these dimensions. In earlier releases, Add Requisition was aggregated; starting with 21.12 it is no longer aggregated.
Table B-7 December 2021 Update
Artifact Type | Modified Artifacts | New Artifacts |
---|---|---|
Calculation Manager Templates |
|
|
Calculation Manager Rules |
|
|
Members |
|
Note:
To further improve rules performance, you can modify all CYTD formulas in both Account and Property.Take the year range of both the plan and forecast scenarios and update the formulas to work only for that year range. For example, if the Plan scenario year range is set to FY21 to FY24 and the Forecast scenario year range is set to FY22 to FY24, update the formulas accordingly with the year range from FY21 to FY24.
These modifications are needed only in applications where January is not the start month.
Replace "Apr" in these formulas with the last month of the application.
- "OWP_CYTD Total Salary" formula
=
/* Plan and forecast year range sets from FY21 to FY24 */ IF(@ISMBR("OWP_Expense Amount")) IF("Fiscal TP-Index"==1 and "Yr-Index"!=0) IF(@ISMBR("FY22")) "OWP_Total Salary" + "FY21"->"Apr"->"OWP_CYTD Total Salary"; /*Hardcoded prior year and last month of the fiscal app*/ ELSEIF(@ISMBR("FY23")) "OWP_Total Salary" + "FY22"->"Apr"->"OWP_CYTD Total Salary"; ELSEIF(@ISMBR("FY24")) "OWP_Total Salary" + "FY23"->"Apr"->"OWP_CYTD Total Salary"; ENDIF; ELSEIF("Cal TP-Index"==1) "OWP_Total Salary"; ELSE "OWP_Total Salary" + @PRIOR("OWP_CYTD Total Salary"); ENDIF; ENDIF;
- "OWP_CYTD Gross Earnings" formula
=
IF(@ISMBR("OWP_Expense Amount")) IF("Fiscal TP-Index"==1 and "Yr-Index"!=0) IF(@ISMBR("FY22")) " OWP_Total Compensation" + "FY21"->"Apr"->"OWP_CYTD Gross Earnings"; ELSEIF(@ISMBR("FY23")) "OWP_Total Compensation" + "FY22"->"Apr"->"OWP_CYTD Gross Earnings"; ELSEIF(@ISMBR("FY24")) "OWP_Total Compensation" + "FY23"->"Apr"->"OWP_CYTD Gross Earnings"; ENDIF; ELSEIF("Cal TP-Index"==1) "OWP_Total Compensation"; ELSE "OWP_Total Compensation" + @PRIOR("OWP_CYTD Gross Earnings"); ENDIF; ENDIF;
- "OWP_CYTD Taxable Compensation" formula
=
IF(@ISMBR("OWP_Expense Amount")) IF("Fiscal TP-Index"==1 and "Yr-Index"!=0) IF(@ISMBR("FY22")) "OWP_Total Compensation" + "FY21"->"Apr"->"OWP_CYTD Taxable Compensation"; ELSEIF(@ISMBR("FY23")) "OWP_Total Compensation" + "FY22"->"Apr"->"OWP_CYTD Taxable Compensation"; ELSEIF(@ISMBR("FY24")) "OWP_Total Compensation" + "FY23"->"Apr"->"OWP_CYTD Taxable Compensation"; ENDIF; ELSEIF("Cal TP-Index"==1) "OWP_Total Compensation"; ELSE "OWP_Total Compensation" + @PRIOR("OWP_CYTD Taxable Compensation"); ENDIF; ENDIF;
- "OWP_CYTD(Prior)" Formula from property
=
IF(@ismbr(@relative("OWP_Total Compensation",0))) IF("Fiscal TP-Index"=="Cal TP-Index" OR ("Fiscal TP-Index"!="Cal TP-Index" and ("OWP_Payment Terms"->"BegBalance"==[OWP_PaymentTerms.FiscalMonth] OR "OWP_Payment Terms"->"BegBalance"==[OWP_PaymentTerms.FiscalQuarter] OR "OWP_Payment Terms"->"BegBalance"==[OWP_PaymentTerms.FiscalYear]))) @SUMRANGE("OWP_Expense Amount", @REMOVE(@CURRMBRRANGE("Period", LEV, 0, ,-1),@LIST("OEP_Yearly Plan","Qtrly 1","Qtrly 2","Qtrly 3","Qtrly 4"))); ELSE IF("Fiscal TP-Index"==1 and "Yr-Index"!=0) IF(@ISMBR("FY22")) "FY21"->"Apr"->"OWP_Expense Amount"+"FY21"->"Apr"->"OWP_CYTD(Prior)"+"BegBalance"->"OWP_Expense Amount"; ELSEIF(@ISMBR("FY23")) "FY22"->"Apr"->"OWP_Expense Amount"+"FY22"->"Apr"->"OWP_CYTD(Prior)"+"BegBalance"->"OWP_Expense Amount"; ELSEIF(@ISMBR("FY24")) "FY23"->"Apr"->"OWP_Expense Amount"+"FY23"->"Apr"->"OWP_CYTD(Prior)"+"BegBalance"->"OWP_Expense Amount"; ENDIF; ELSEIF("Cal TP-Index"==1 AND "OWP_Start Date"->"No Property" != #MISSING) #MISSING; ELSE @PRIOR("OWP_Expense Amount",1,@Relative("YearTotal",0)) + @PRIOR("OWP_CYTD(Prior)",1,@Relative("YearTotal",0)); ENDIF; ENDIF; ENDIF;
August 2021 Update
The following information describes modified artifacts relating to Workforce enhancements in the 21.08 update, along with changes you must make in the application to use the new features.
Adding Custom Dimensions to the Reporting Cube
In this update, for new applications, you have the option to choose whether to add custom dimensions to the reporting cube (OEP_REP) the first time you enable features.
For existing applications, you have a one-time option to add custom dimensions to the reporting cube the next time you enable features for either Workforce or Strategic Workforce. Before you enable features, you must clear data in the OEP_REP cube. Note that you can't disable Employee Demographics dimensions for an existing application.
To choose which dimensions are pushed to the reporting cube (OEP_REP), see Adding Custom Dimensions to the Reporting Cube:
- For new applications, you can perform this task only once, when you first enable features.
- For existing applications, you have a one-time option to perform this task the next time you make a change in Enable Features.
- For existing applications, you have a one-time option to perform this task the next time you make a change in Enable Features for either Workforce or Strategic Workforce.
Merit Assumptions
-
Give users access to access to the new dashboard Workforce and Merit Assumptions.
-
If you enabled Merit Assumptions, and you specify to plan at the Global level, the Workforce and Merit Assumptions dashboard uses Company Assumptions, and Entity is hidden. If you you specify to plan at the Per Entity level, the Workforce and Merit Assumptions dashboard uses Entity and Company Assumptions is hidden.
- For existing customers, if you enable Merit Assumptions and choose to plan by Entity or by Global, you must enter data for Merit Rate, Merit Month, and Cut-off Date at Entity or Global level. When you are loading data for existing employees using Data Management or Data Integration, these assumptions are copied to employees as part of the Incremental Process Data with Synchronize rule. Alternatvely, you can run Process Loaded Data whenever you update Merit Month or Cut-off Date.
Updated Employee Details Form
There is a new member, Merit Increase, in the Component dimension, which is assigned as a Smart List value for Merit Account. For existing customers, after updating content for 21.08, in the Employee Details form, the row heading for Merit displays 1 instead of the new Smart List value. To update the Employee Details form to display the new member, Merit Increase, run either the Calculate Compensation or Synchronize rule.
Table B-8 August 2021 Update - Workforce and Strategic Workforce Planning New and Modified Artifacts
Artifact Type | Modified Artifacts | New Artifacts |
---|---|---|
Dashboards | Workforce and Merit Assumptions Make sure to give users access to access to the new dashboard Workforce and Merit Assumptions. |
|
Forms |
|
Merit Assumptions |
Templates |
OWP_Calculate Demand is updated to correct the formula for the Previous Year's Ratio
|
|
Rules |
|
|
Accounts |
|
|
Data Maps | Headcount and FTE Data for Reporting—Headcount Data for Reporting is renamed to Headcount and FTE Data for Reporting, and is updated to include the OWP_FTE account. (Renamed existing data map.) | |
Data Load Templates |
|
November 2020 Update
The following information describes modified artifacts relating to Workforce currency conversion calculation for assumptions enhancements in the 20.11 update.
Beginning with the November 2020 release, as part of the Strategic Workforce Planning currency conversion calculation for assumptions enhancements, the following changes have been made.
With this update, added a new UDA Hsp_ConvertNonCurrencyValue
to all earnings, benefits, taxes, and basic salary in the accounts dimension and to No Property from property dimension. With this currency conversion batch calculation copies assumptions (smart list values of earning, benefits, taxes, and basic salary) to reporting currency in the Workforce. This populates data across the components in the reporting cube after running the Compensation Data for Reporting datamap.
Note:
Generate new currency conversion script using Currency Conversions under Create and Manage to generate new updated script.
Table B-9 November 2020 Update - Workforce Modified Artifacts
Artifact Type | Modified Artifacts | New Artifacts |
---|---|---|
Account |
|
|
Property |
No Property |
October 2020 Update
The following information describes modified artifacts relating to transfer enhancements in the 20.10 update.
Beginning with the October 2020 release, as part of the Strategic Workforce Planning transfer enhancements, the following changes have been made:
- With this update, you can now transfer an employee across custom dimensions and entities, in a one-step or two-step transfer. Previously, transfers were allowed for changing jobs and entities only. While transferring an employee from one entity to another entity, you can also select the same or different targets from the custom source. The same applies to transferring headcounts in Job Only models.
- In the source's transfer year, most of the employee properties, including FTE and Headcount, are cleared out starting in the transfer month. Applicable Union Code, Employee Type, Pay Type, and Status will remain but the Status will show as Transfer Out.
- If the employee transfer month is after the merit month in the year of transfer, merit rates are copied from the source. For subsequent years in the target entity, merit rates are calculated based on the target rates. When the employee is not active, the recommended merit rate is not populated. If the employee transfer month is before the merit month, merit rates are copied from the target.
- In the Job Only model, there is a restriction on the number of headcounts that can be transferred or departed based on the headcounts available on the job. This eliminates the need to run a calculate job compensation rule after departing headcounts from the job.
- Total FTE and Total Headcount are added to the New Hire request form, Employee Properties form, and Manage Existing Employee forms. Alias names for FTE and Headcount are modified to FTE Assumption and Headcount Assumption. FTE Assumption and Headcount Assumption are used for input assumptions to drive calculations. Total FTE and Total Headcount are used for reporting purposes.
- In the transfer year, earnings, benefits, and taxes paid in the source are considered while applying the target threshold. Computed expense in the source is copied to the transfer year's target as part of the transfer and change job process. After applying the entity defaults to the employee in target, the copied computed expense amount is considered while applying the threshold in the target in the transfer year for the earnings, benefits, and taxes that are the same across source and target. As part of the transfer headcount in Job Only model, computed expense in the source to target is based on the number of headcounts being transferred. This applies to a single-step and two-step transfer and change job actions on the employee in the Employee and Job model and Transfer Headcount action in Job Only model.
Table B-10 October 2020 Update - Workforce Modified Artifacts
Artifact Type | Modified Artifacts | New Artifacts | Obsolete Artifacts |
---|---|---|---|
Calculation Manager Templates |
|
||
Calculation Manager Rules |
|
||
Forms |
|
||
Account |
Alias name changed from FTE to FTE Assumption and HeadCount to HeadCount Assumption. |
||
Member Formula |
Account Dimension members:
Property Dimension members: OWP_CYTD(Prior) |
June 2020 Update
The following information describes new and modified artifacts relating to different planning years for Plan and Forecast scenarios in the 20.06 update.
Beginning with the June 2020 release, Strategic Workforce Planning forms and rules have been updated to allow different planning years for the Plan and Forecast scenarios. Previously, the Planning and Forecast Preparation configuration task for Workforce and Strategic Workforce set the &OEP_YearRange and &OWP_SWPYearRange substitution variables, respectively, for both Plan and Forecast scenarios based on the year range set for the Plan scenario per respective module. References to these substitution variables are being discontinued.
With the June 2020 release, Oracle Strategic Workforce Planning Cloud has updated all business rules and templates to use methods that read the start year and end year from the Planning and Forecast Preparation configuration task separately for each scenario. Forms are modified to display data based on the start and end periods for the scenario using valid intersections. When the update is applied, if you haven't modified these forms and business rules:
-
Predefined business rules and templates are updated.
-
Predefined forms are updated.
Because customized artifacts aren't updated during a new release, if you've customized forms or business rules, note the following.
- If you’ve modified rules that rely on the &OEP_YearRange or &OWP_SWPYearRange substitution variables, update the rules to use these functions (either in Business Rules or Groovy rules):
-
[[PlanningFunctions.getModuleStartYear("Workforce","ScenarioName")]]
—Returns start year of given scenario -
[[PlanningFunctions.getModuleEndYear("Workforce","ScenarioName")]]
—Returns end year of given scenario -
[[PlanningFunctions.getModuleStartYear("Strategic Workforce","ScenarioName")]]
—Returns start year of given scenario -
[[PlanningFunctions.getModuleEndYear("Strategic Workforce","ScenarioName")]]
—Returns end year of given scenario
Note:
Module name and Scenario name must be enclosed in double quotation marks.
-
-
If you've not modified the OWP_Process Loaded Data_T template but you have modified the OWP_Process Loaded Data rule, OWP_Incremental Process Data with Synchronize Defaults_GT template, or the OWP_Incremental Process Data with Synchronize Definition_GT template, which are dependent on OWP_Process Loaded Data_T, update these artifacts as follows since Design Time Prompt (DTP) values are now included to support different planning years for the Plan and Forecast scenarios:
-
OWP_Process Loaded Data rule must be updated to set the newly required DTP values at the rule level. To do so, open this rule in Calculation Manager, highlight the "OWP_Process Loaded_T" template object from within the rule (do not open the template itself), select the pencil icon to edit the DTP and update/enter the following information, then save and redeploy the rule.
-
Set DTP Year Range = [[PlanningFunctions.getModuleStartYear("WORKFORCE",{Scenario})]]:[[PlanningFunctions.getModuleEndYear("WORKFORCE",{Scenario})]]
-
Set DTP MODULENAME = "Workforce"
(including the double quotes)
-
-
OWP_Incremental Process Data with Syncronize Defaults_GT and OWP_Incremental Process Data with Synchronize Definition_GT templates should be copied or downloaded locally. Restore these artifacts then re-apply your modifications, save, and redeploy these templates.
-
-
Update custom forms for Workforce to use ILvl0Descendants of "All Years" instead of &OEP_YearRange.
Note:
Ensure the form properties to Suppress Invalid Data for Rows and Suppress Invalid Data for Columns are selected.
Table B-11 June 2020 Update - Workforce Modified and New Artifacts
Artifact Type | Modified Artifacts | New Artifacts | Obsolete Artifacts |
---|---|---|---|
Calculation Manager Rules (Workforce) |
Updated rules, templates, and forms to allow different planning years for the Plan and Forecast scenarios:
|
Run OWP_Copy Working to Prior FCST rule before the current period is changed in the Planning and Forecast Preparation configuration task. This rule makes a backup of the current forecast scenario for all periods, copies data from "OEP_Working" version to "OEP_Prior FCST" version and from scenario Start Year to End Year. |
NA |
Calculation Manager Rules (Strategic Workforce Planning) |
|
OWP_Copy Working to Prior FCST for Strategic Workforce Data Run this rule every time the forecast start period is changed. This rule makes a backup of the current forecast scenario for all periods, copies data from "OEP_Working" version to "OEP_Prior FCST" version and from scenario Start Year to End Year. |
|
Calculation Manager Templates (Workforce) |
Updated all templates to use methods that read the Start Year and End Year:
|
OWP_Set Valid Years for Scenario_T OWP_Synchronize Defaults_T OWP_Synchronize Definition_T OWP_AGG_T OWP_Assign Defaults_T OWP_Assign Defaults AGG_T OWP_Copy Working to Prior FCST_T Note: Run OWP_Copy Working to Prior FCST_T rule before the current period is changed. This rule makes a backup of current forecast scenario for all periods. |
|
Calculation Manager Templates (Strategic Workforce Planning) |
|
||
Forms (Workforce) |
Workforce Analysis
|
NA |
NA |
Forms (Strategic Workforce Planning) |
Workforce Dashboard Strategic
Workforce Plan Sheets Strategic
|
NA |
NA |
Forms (Workforce) |
Workforce Dashboard Compensation
|
NA |
NA |
Forms (Workforce) |
Workforce - Plan Sheets - Compensation
|
NA |
NA |
Forms (Workforce) |
Workforce Dashboard Demographics
|
NA |
NA |
Forms (Workforce) |
Workforce Plan Sheets Administration
|
NA |
NA |
Forms (Workforce) |
Workforce Assumptions
|
NA |
NA |
Dimensions |
Account |
NA |
NA |
Member Formula |
OWP_Basic Salary |
NA |
NA |
Valid Intersections |
Note: Added Account dimension to valid intersections when both Workforce and Strategic Workforce are enabled. |
OWP_SWP_Scenario Years OWP_SWP_Scenario Years_Reporting Note: These new valid intersections include the Account dimension when Workforce is also enabled. |
NA |
February 2020 Update
The following information describes new and modified artifacts relating to support for the new Start Date property in the 20.02 update.
Table B-12 February 2020 Update - Workforce Modified and New Artifacts
Artifact Type | Modified Artifacts | New Artifacts | Obsolete Artifacts |
---|---|---|---|
Calculation Manager and Groovy Templates and Rules |
All Calculation Manager and Groovy templates and rules in the Workforce OEP_WFP cube have been updated to accommodate Start Date. In Strategic Workforce Planning, Calculate Demand and Calculate Supply have not been modified. Tip: You can modify any obsolete rules that you are still using to take advantage of Start Date. |
1X Populate New Properties
Note to updating customers: Immediately after updating the February 2020 content, you must run the new rule 1X Populate New Properties to convert existing Start Month data to the Start Date account. Run this rule only once for each Scenario and Version combination with data, immediately after updating content. Specify only Scenario and Version combinations whose data you want to recalculate. For example, you may not want to recalculate historical data. NOTE: If you don’t run this rule immediately after updating, the consequence of running any rules is the possibility of losing some data. If you inadvertently run rules before running 1X Populate New Properties, run 1X - Populate New Properties and then rerun the rules that you previously ran. For optimum performance, before running 1x Populate New Properties, change the FIX Parallel dimension to use the dimension that is appropriate to parallelize the process by moving the dimension from FIX statement to FIX Parallel and move the entity member selection to FIX statement in the place of the dimension that's moved to FIX Parallel statement. This change needs to be made in OWP_Populate New Properties_T template in Calculation Manager. Save the changes and then deploy the OWP_Populate New Properties rule. |
NA |
Account Members |
NA |
|
NA |
Member Formulas |
All member formulas that calculate salaries have been updated:
|
NA |
NA |
Forms |
Updated to include a Start Date column:
|
NA |
NA |
Data Load Templates |
Updated to replace Start Month column with Start Date:
|
NA |
NA |
June 2019 Update
The following information describes modified artifacts resulting from a fixed defect in the 19.06 update.
Table B-13 June 2019 Update - Workforce Modified Artifacts
Artifact Type | Modified Artifacts | New Artifacts | Obsolete Artifacts |
---|---|---|---|
Templates | OWP_Assign Compensation Defaults | NA | NA |
Groovy Templates |
|
NA | NA |
May 2019 Update
The following information describes new and modified artifacts related to the enhancements in the May 2019 update.
Table B-14 May 2019 Update - Workforce Enhancements
Artifact Type | Modified Artifacts | New Artifacts | Obsolete Artifacts |
---|---|---|---|
Calculation Manager Rules |
|
Copy Compensation Details from BegBalance to Periods Note to updating customers: Run the rule 1 X Copy Compensation Details from BegBalance to Periods one time immediately after updating the May 2019 content to copy compensation details from BegBalance to all periods. |
|
Calculation Manager Templates |
|
|
|
Groovy Rules |
|
NA | NA |
Groovy Templates |
|
|
NA |
Forms |
|
NA | NA |
Menus |
Existing Actions |
|
NA |
Member Formulas |
OWP_Basic Salary |
NA | NA |
Smart Lists | NA | Employee Options | NA |
February 2019 Update
The following information describes new and modified artifacts related to the incremental data load functionality in the February 2019 update.
Table B-15 February 2019 Update - Enhancements Related to Incremental Data Load
Artifact Type | Modified Artifacts | New Artifacts | Obsolete Artifacts |
---|---|---|---|
Calculation Manager Rules | NA | NA | NA |
Calculation Manager Templates |
|
NA | NA |
Groovy Rules | NA |
|
NA |
Groovy Templates | NA |
|
NA |
Forms | NA |
|
NA |
Vertical Tab | NA | Mass Update | NA |
Horizontal Tabs | NA |
|
NA |
Data Import Templates |
|
NA | NA |
November 2018 Update
The following information describes new and modified artifacts related to the performance enhancements in the Add Hiring Requisition rule in the November 2018 update.
Table B-16 November 2018 Update - Enhancements Related to Add Hiring Requisition Rule Performance
Artifact Type | Modified Artifacts | New Artifacts | Obsolete Artifacts |
---|---|---|---|
Calculation Manager Rules | Add Requisition_GT | NA | NA |
Calculation Manager Templates |
|
NA | NA |
September 2018 Update
The following information describes new and modified artifacts related to the performance enhancements in the September 2018 update.
Table B-17 September 2018 Update - Enhancements Related to Performance Improvements
Artifact Type | Modified Artifacts | New Artifacts | Obsolete Artifacts |
---|---|---|---|
Calculation Manager Rules |
|
NA | NA |
Calculation Manager Templates |
|
OWP_Fix Parallel_T |
NA |
Members | OWP_Utilization | NA | NA |
July 2018 Update
The following information describes new and modified artifacts in the July 2018 update.
Table B-18 July 2018 - Enhancements Related to Add Requisition
Artifact Type | Modified Artifacts | New Artifacts | Obsolete Artifacts |
---|---|---|---|
Calculation Manager Rules | NA |
|
|
Calculation Manager Templates | NA |
|
|
Smart Lists | OWP_Status |
|
NA |
Menus | NA | NA |
July 2018 Update - Enhancements Related to Benefits and Tax Wizard Calculations
Artifact Type | Modified Artifacts | New Artifacts | Obsolete Artifacts |
---|---|---|---|
Calculation Manager Rules |
|
|
NA |
Calculation Manager Templates |
|
|
NA |
Members |
|
In the Property dimension:
|
NA |
Smart Lists | OWP_Payment Frequency |
|
NA |
Forms |
|
NA | NA |
Menus | NA | OWP_Copy Rates | NA |
Data Load Templates |
|
NA | NA |