Recover Unsaved Integration Changes

You can recover unsaved changes in an integration that crashes during design time because of a browser crash, loss of network connectivity, a server going down, and so on.

As you design an integration, a backup copy is created whenever you complete a task such as configuring an action, deleting an invoke connection, configuring business identifier tracking, or defining global faults. There is no time limit in which you need to log back in and recover your changes. The unsaved changes remain as long as the integration is not unlocked by an administrator.

The following data in an integration cannot be recovered after a crash:

• Changes made while editing an action (for example, you are designing a stage file action when your integration crashes)
• Changes made while working inside the mapper
• Layout changes such as repositioning an action
• Connections page edits
• Any changes in a basic routing integration

Recovery behavior is different based on the roles assigned to the user. For example, assume you are designing the following integration when your browser crashes.

1. Design an integration as a user with the ServiceDeveloper role. Assume you have not yet saved your changes for the following integration when your browser crashes.
   
   
   
   
2. If you log back in as that same user with the ServiceDeveloper role, note the following behavior for recovering your unsaved changes.
   1. Go to the Integrations page and note that the words Unsaved Changes appear next to the impacted integration.
      
      
      
      
   2. Select to resume editing and recover your unsaved integration changes in any of the following ways:
      • Click the integration name in the Name field.
      • Click .
      • Select Resume Edit from the menu.
      • Select Unlock from the menu, then select Edit & Recover.
        
        
        
        

      Your integration design is displayed. The following message appears in the banner.

      Unsaved changes for integration OpportunitytoOrder (1.0) have been recovered and are displayed in the canvas, but not saved yet.

   3. Click Save to save your changes and continue with integration design.
3. If you instead log in as a user with the ServiceAdministrator role, note the following behavior.
   1. Go to the Integrations page and note that the word New instead of Unsaved Changes appears next to the impacted integration.
      
      
      
      
   2. Select from the following options. A user with the ServiceAdministrator role cannot recover the unsaved changes. Only the actual designer of the impacted integration can perform that task.
      • If you click the integration name in the Name field, you see none of the updates you made prior to the crash. The following message is displayed in the banner.

        Edit is not possible for OpportunitytoOrder (1.0) because this integration is locked. Integration is displayed in view mode.

      • If you select Edit from the menu, the following message is displayed.
        
        
        
        
      • If you then select Unlock from the menu, you are prompted with the following message. If you select Unlock & Discard, all changes are lost. Contact the integration designer to determine how to proceed.