Field Service

Get Involved. Join the Conversation.

Topic

    Shilpa Shonkhia
    Activity purge time documentation linkAnswered
    Topic posted November 8, 2017 by Shilpa ShonkhiaBronze Medal: 1,250+ Points 
    95 Views, 4 Comments
    Title:
    Activity purge time documentation link
    Content:

    Hi,

    Can someone point me to the document where oracle has mentioned activity purge timeline.

    Thanks

    Shilpa

    Version:
    latest

    Best Comment

    Brett Wallace

    Hi Shilpa,

    I'm not sure which activity purging you are referring too. From what I know there are 2:

    1. FTP data is purged every 10 days - see the following article: https://cx.rightnow.com/app/answers/detail/a_id/8353/kw/policy

    2. Overall transaction data retention in OFSC is 92 days by default. (i.e. 3 calendar months) keeping in line with PCI-DSS standards. This is documented in 2 separate places in an Oracle document titled: "Oracle Field Service Cloud System Architecture & Hosting 2017". There is a client facing version of this document I have seen, which I obtained from Oracle. I suggest contacting Oracle Sale/Presales, partner people or perhap support, as I could not find a copy on the this portal. 

    Also note that in the TOA days this "92 days" could be changed when requested, I'm not sure if this is still the case with Oracle, but the wording in the document "by default" suggests that it might be possible.

    Lastly here is an extract from one of the references in the document:

    Data Storage

    Oracle Field Service Cloud is not considered the system of record for historic data.

    As a standard practice, Oracle limits retention of data within the core application to 92 days/three calendar months as recommended by PCI-DSS, ISO and other standards. Oracle provides a data warehouse extract on a daily basis, allowing the customer to load the data and events from OFSC into its own data warehouse for ad hoc reporting, analysis, and long-term storage.

    The OFSC Outbound API also provides real-time updates for events within OFSC, enabling the capture of changes in work order source systems as soon as they occur. 

    Comment

     

    • Zsolt Tolgyesi

      Hi Shilpa,

      This is a kind of
      https://docs.oracle.com/cloud/latest/fieldservicecs_gs/CXFSC/op-rest-ofscCore-v1-folders-dailyExtract-folders-%7BdailyExtractDate%7D-files-get.html

      I'm not able to find a closer one.

      Regards,
      Zsolt

    • Brett Wallace

      Hi Shilpa,

      I'm not sure which activity purging you are referring too. From what I know there are 2:

      1. FTP data is purged every 10 days - see the following article: https://cx.rightnow.com/app/answers/detail/a_id/8353/kw/policy

      2. Overall transaction data retention in OFSC is 92 days by default. (i.e. 3 calendar months) keeping in line with PCI-DSS standards. This is documented in 2 separate places in an Oracle document titled: "Oracle Field Service Cloud System Architecture & Hosting 2017". There is a client facing version of this document I have seen, which I obtained from Oracle. I suggest contacting Oracle Sale/Presales, partner people or perhap support, as I could not find a copy on the this portal. 

      Also note that in the TOA days this "92 days" could be changed when requested, I'm not sure if this is still the case with Oracle, but the wording in the document "by default" suggests that it might be possible.

      Lastly here is an extract from one of the references in the document:

      Data Storage

      Oracle Field Service Cloud is not considered the system of record for historic data.

      As a standard practice, Oracle limits retention of data within the core application to 92 days/three calendar months as recommended by PCI-DSS, ISO and other standards. Oracle provides a data warehouse extract on a daily basis, allowing the customer to load the data and events from OFSC into its own data warehouse for ad hoc reporting, analysis, and long-term storage.

      The OFSC Outbound API also provides real-time updates for events within OFSC, enabling the capture of changes in work order source systems as soon as they occur. 

    • Shilpa Shonkhia

      Thank you Brett and Zsolt. I really appreicate your help.