GETTING STARTED
CONTINUITY

The ability for an organisation (enterprise) to operate continuously (its continuity) is deeply linked to the continuity of its supporting information system.

entityOS inherently has a number of mechanisms to ensure it is continuously available.

More about ibCom information security compliance

Based on your own information security needs, you can also build your own information continuity systems using entityOS methods within the ADMIN endpoint.
HOW IT WORKS
You can then use the CORE_DATA_TRACKING_SEARCH method to find out what has changed within your space and then using standard entityOS methods request the actual data.

You can do this when-and-how your risk management or master data management (MDM) system requires.

EXAMPLES
Periodic Backup

Check out the example starter node app on github...
  1. Get the last backup date and time using SETUP_SPACE_SETTINGS_SEARCH &DataTrackingLastBackupDate field.  If you want to do updates only from now, then use the current date.

  2. Run the CORE_DATA_TRACKING_SEARCH with modifieddate filter.  This will then return all data that has changed state since that date/time.

  3. Iterate through the returned list in step 2.  You can enhance performance by gathering state change for the same object type into a IN_LIST request and get the data for each object in bulk.

  4. Get the maximum modifieddate from CORE_DATA_TRACKING_SEARCH data and using SETUP_SPACE_SETTINGS_MANAGE update DataTrackingLastBackupDate and/or save within your system.

  5. Save the data as per your continuity/risk management system.
 
METHODS
CORE_DATA_TRACKING_SEARCH
CORE_OBJECT_SEARCH
SETUP_SPACE_SETTINGS_MANAGE