Versions Compared

Old Version 2

changes.mady.by.user Blake Westmoreland

Saved on

compared with

New Version 3

changes.mady.by.user Jay-Ar Brouillard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Setup Tasks allow for export and import of setup task as a CSV File package (zip file). If supported, scope can be applied to export a subset of the CSV File package data via Export Criteria. Export Criteria can be easily configured via the FlexDeploy during manual file creation. In the case, scope cannot be applied, please see other supported Oracle Saas FSM object types as an alternative solution.

...

Name

Code

Description

Default Value

Supported Values

Source

SOURCE

Object Source Location Type

SCM

SCM, CLOUD

Task Code

TASK_CODE

Unique id for Setup Task

FILE_NAME*

Export Criteria 

EXPORT_CRITERIA

Export Criteria used to apply scope to a setup task.

Filter Criteria

FILTER_CRITERIA

After export, filter criteria is used to apply additional filtering to the setup task.

...

  • Manage HCM Extract Definitions - this requires use of ExtDefinitionId, which is not visible on FSM UI. Other values do not work with Export CSV API. See https://docs.oracle.com/en/cloud/saas/human-resources/21d/oedmh/payflows-20167.html#payflows-20167 to write an adhoc BIP report to query the underlying FSM tables and retrieve name & associated ExtDefinitionId. Other option would be to manually export from FSM UI to capture ExtDefinitionId from ASM_SETUP_CSV_METADATA.xml which is part of Export zip file.

  • Payroll Flow Patterns - this requires use of FlowId, which is not visible on FSM UI. Other values do not work with Export CSV API. There are few options to get FlowId:

    1. See https://docs.oracle.com/en/cloud/saas/human-resources/21d/oedmh/perextdefinitionsb-13198.html#perextdefinitionsb-13198 to write an adhoc BIP report to query the underlying FSM tables and retrieve name & associated FlowId.

    Other option would be to manually

    2. Manually export from FSM UI to capture FlowId from ASM_SETUP_CSV_METADATA.xml which is part of

    Export

    1. exported CSV zip file.

    2. Manually execute the Get all flow patterns REST API https://docs.oracle.com/en/cloud/saas/human-resources/24b/farws/op-flowpatterns-get.html using query parameter by BaseFlowNow or other field. The response body will contain FlowId. Example response below

      Code Block
      {
  "items" : [ 
  {
    "FlowId" : 100100075869005,
    "BaseFlowId" : 100100075869005,
    "BaseFlowName" : "123",
    "FlowStatus" : "A",
    "LDGRequired" : "N",
    "LegislationCode" : null,
    "FlowPattern" : "123",
    "Description" : null,
    "LegislativeDataGroupId" : null,
    "ConnectorName" : "123",
    "ConnectorStatus" : "PO",
    "links" : [ 
        {
           ...}   
      ]
    
  },
  ...
}

Filter Criteria

Filter criteria are a list of rules used to filter the setup data after CSV export. This means if export criteria are configured, then filter criteria are applied to the result of that. The filter criteria are useful when the user only wants to deploy, a subset of the setup data to the target Oracle SaaS environment(s) and export criteria alone is not sufficient. It is recommended to start with export criteria first and after use filter criteria to fill any gaps if additional filtering is required by your use case. While export criteria only works for specific tasks and attributes combinations; filter criteria are configurable for any task and attribute. A couple reasons export criteria is preferred:

...