4 Activate and Run the Recipe

After you've configured the connections and other resources, you can activate and run the recipe.

  1. In the project workspace, click Activate. In the Activate project panel, with the default project deployment selected, choose an appropriate tracing option, then click Activate.

    A message confirms that the integration has been activated. Refresh the page to view the updated status of the integration.

  2. Update property values for integration flows.
    1. For the Oracle FTP OFS Employee Resource Sync flow, update the following properties:
      Integration Property Description
      Default Employee Status Specify the default value of Workday employee status.
      EmailTo Specify the email address to which run-time exception emails are sent. Enter an email address of your choice.
      DefaultResourceType Specify the default value of resource type.
      RetryCount Specify the number of possible retries if any record fails while creating resources at run time.
    2. For the Oracle Workday OFS Resource Work Schedule Sync flow, update the following property:

      EmailTo: Specify the email address to which run-time exception emails are sent. Enter an email address of your choice.

      For the procedure to update integration properties, see Steps 7 to 9 in Override Design-Time Properties in an Integration.

  3. Run the integration Oracle FTP OFS Employee2Resource Sync to fetch the resources from FTP to Oracle Field Service Cloud.
    1. In the Integrations section of the project workspace, click Actions Actions icon on the integration flow, then select Run.

      The Configure and run page is displayed with the following parameters. Update the parameters with appropriate values.

      • schedule_paramErrorFilePath: Specify the FTP error file path in which the error records are stored after unsuccessful execution.
      • schedule_param_ErrorFileName: Specify the name of the FTP error file in which the error records is stored after unsuccessful execution.
      • schedule_param_FileName: Specify the name for the FTP file from which the Workday employee records must be fetched.
      • schedule_param_FilePath: Specify the path of the FTP file from which the Workday employee records must be fetched.
      • schedule_param_NextRun: Stores the date and time of the most-recent successful run of the integration flow. The parameter’s value is automatically updated after each successful run, and only the Workday employee records created after the date-time stamp stored as the parameter’s Current Value are processed by the integration in each run. If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm.
    2. On the Configure and run page, click Run.

      You've now successfully submitted the integration for execution.

      Note:

      You can also schedule this integration to run at a date, time, and frequency of your choosing. See Define the Integration Schedule.
  4. Monitor the running of the integration flow in Oracle Integration.
    1. In the project workspace, click Observe. You'll see the integration flow being triggered and running successfully.
    2. To manage errors in your project, see Manage Errors in a Project.
  5. Log in to your Oracle Field Service Cloud instance and check for the new resources created.
    1. Log in to the Oracle Field Service Cloud instance.
    2. In the top-left corner, click the hamburger icon, then click Resources.
    3. In the search box, enter the ID of the Workday employee you want to search for.

      Note:

      The Workday employee ID is the sourceSystemId in FTP.
    4. Check if the new resource is created.
  6. Run the integration Oracle Workday OFS Resource Work Schedule Sync to synchronize the work schedules with Oracle Field Service Cloud.
    1. In the Integrations section of the project workspace, click Actions Actions icon on the integration flow, then select Run.

      The Configure and run page is displayed with the following parameter. Update the parameter with appropriate value.

      • schedule_para_LastRunTime: Stores the date and time of the most-recent successful run of the integration flow. The parameter’s value is automatically updated after each successful run, and only the Workday schedules created after the date-time stamp stored as the parameter’s Current Value are processed by the integration in each run. If you want to change the date-time stamp for a specific scenario, enter the date and time of your choice in the New Value field in the format, yyyy-MM-dd HH:mm.
    2. On the Configure and run page, click Run.

      You've now successfully submitted the integration for execution.

      Note:

      • You can also schedule this integration to run at a date, time, and frequency of your choosing. See Define the Integration Schedule.
      • If any record fails while setting up the work schedule in Oracle Field Service Cloud, an email notification is sent to the user. The admin must update that record in Workday again, so that it is fetched in the next run automatically.
  7. Monitor the execution of the integration flow in Oracle Integration. See Step 4.
  8. Log in to your Oracle Field Service Cloud instance and check for work schedules assigned to the resources.
    1. Log in to the Oracle Field Service Cloud instance.
    2. In the top-left corner, click the hamburger icon, then click Resources.
    3. In the search box, enter the ID of the Workday employee you want to search for.

      Note:

      The Workday employee ID is the sourceSystemId in FTP.
    4. To view the assigned work schedule, open the resource, then click Resource Calendar.